District Government Land Line Dimensions. A layer showing District of Columbia government related properties (owned, operated, and or managed) to be used by many DC Government agencies, private companies and the public. It supports the daily business process of District agencies that originate and manage land records. Transfers of Jurisdiction (TOJ) are also in this layer. This map should not be considered comprehensive as District agencies continuously work to update properties as transactions occur.

Parcels and Land Ownership dataset current as of unknown. This data set consists of digital map files containing parcel-level cadastral information obtained from property descriptions. Cadastral features contained in the data set include real property boundary lines, rights-of-way boundaries, property dimensions.

The dataset contains locations and attributes of owner lines with dimensions. The tax information (attribution) comes from the Office of Tax and Revenue's Public Extract file. The creation of this layer is automated, occurs weekly, and uses the most currently available tax information. The date of the extract can be found in the EXTRACTDAT field in this layer.

We are also including a tabular version that’s slightly more comprehensive (would include anything that didn’t join to the parcel basefile due to lot alterations or resubdivisions since 2023 and/or due to parcels comprised of condos). This Excel file can be downloaded HERE, and does not contain the latitude and longitude information.Data Dictionary: Attribute Label Definition Source

TAX_ID Unique 26 character property tax identification number Onondaga County Planning

PRINTKEY Abbreviated tax identification number (section-block-lot) Onondaga County Planning

ADDRESSNUM Property’s physical street address Onondaga County Planning

ADDRESSNAM Property’s physical street name Onondaga County Planning

LAT Latitude Onondaga County Planning

LONG Longitude Onondaga County Planning

TAX_ID_1 City Tax ID number (26 digit number used for parcel mapping) City of Syracuse - Assessment

SBL Property Tax Map Number (Section, Block, Lot) City of Syracuse - Assessment

PNUMBR Property Number (10 digit number) City of Syracuse - Assessment

StNum Parcel street number City of Syracuse - Assessment

StName Parcel street name City of Syracuse - Assessment

FullAddress Street number and street name City of Syracuse - Assessment

Zip Parcel zip code City of Syracuse - Assessment

desc_1 Lot description including dimensions City of Syracuse - Assessment

desc_2 Lot description including dimensions City of Syracuse - Assessment

desc_3 Lot description including dimensions City of Syracuse - Assessment

SHAPE_IND

City of Syracuse - Assessment

LUC_parcel New York State property type classification code assigned by assessor during each roll categorizing the property by use. For more details: https://www.tax.ny.gov/research/property/assess/manuals/prclas.htm City of Syracuse - Assessment

LU_parcel New York State property type classification name City of Syracuse - Assessment

LUCat_Old Legacy land use category that corresponds to the overarching NYS category, i.e. all 400s = commercial, all 300s = vacant land, etc. NA

land_av Land assessed value City of Syracuse - Assessment

total_av Full assessed value City of Syracuse - Assessment

Owner Property owner name (First, Initial, Last, Suffix) City of Syracuse - Assessment

Add1_OwnPOBox Property owner mailing address (PO Box) City of Syracuse - Assessment

Add2_OwnStAdd Property owner mailing address (street number, street name, street direction) City of Syracuse - Assessment

Add3_OwnUnitInfo Property owner mailing address unit info (unit name, unit number) City of Syracuse - Assessment

Add4_OwnCityStateZip Property owner mailing address (city, state or country, zip code) City of Syracuse - Assessment

FRONT Front footage for square or rectangular shaped lots and the effective front feet on irregularly shaped lots in feet City of Syracuse - Assessment

DEPTH Actual depth of rectangular shaped lots in feet (irregular lots are usually measured in acres or square feet) City of Syracuse - Assessment

ACRES Number of acres (where values were 0, acreage calculated as FRONT*DEPTH)/43560) City of Syracuse - Assessment

yr_built Year built. Where year built was "0" or null, effective year built is given. (Effective age is determined by comparing the physical condition of one building with that of other like-use, newer buildings. Effective age may or may not represent the actual year built; if there have been constant upgrades or excellent maintenance this may be more recent than the original year built.) City of Syracuse - Assessment

n_ResUnits Number of residential units NA - Calculated field

IPSVacant Is it a vacant structure? ("Commercial" or "Residential" = Yes; null = No) City of Syracuse - Division of Code Enforcement

IPS_Condition Property Condition Score assigned to vacant properties by housing inspectors during routine vacant inspections (1 = Worst; 5 = Best) City of Syracuse - Division of Code Enforcement

NREligible National Register of Historic Places Eligible ("NR Eligible (SHPO)," or "NR Listed") City of Syracuse - Neighborhood and Business Development

LPSS Locally Protected Site Status ("Eligible/Architecturally Significant" or "Local Protected Site or Local District") City of Syracuse - Neighborhood and Business Development

WTR_ACTIVE Water activity code ("I" = Inactive; "A" = Active) City of Syracuse - Water

RNI Is property located in Resurgent Neighborhood Initiative (RNI) Area? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DPW_Quad Geographic quadrant property is located in. Quadrants are divided Northwest, Northeast, Southwest, and Southeast based on property location in relation to I-81 and I-690. DPW uses the quad designation for some types of staff assignments. City of Syracuse - Department of Public Works

TNT_NAME TNT Sector property is located in City of Syracuse - Neighborhood and Business Development

NHOOD City Neighborhood Syracuse-Onondaga County Planning Agency (SOCPA)

NRSA Is property located in Neighborhood Revitilization Strategy Area (NRSA)? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DOCE_Area Geographic boundary use to assign Division of Code Enforcement cases City of Syracuse - Neighborhood and Business Development

ZONE_DIST_PREV Former zoning district code Syracuse-Onondaga County Planning Agency (SOCPA)

REZONE ReZone designation (adopted June 2023) City of Syracuse - Neighborhood and Business Development

New_CC_DIST Current Common Council District property is located in Onondaga County Board of Elections

CTID_2020 Census Tract ID (2020) U.S. Census Bureau

CTLAB_2020 Census Tract Label (2020) U.S. Census Bureau

CT_2020 Census Tract (2020) U.S. Census Bureau

SpecNhood Is property located in a special Neighborhood historic preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

InPD Is property located in preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

PDNAME Preservation District name Syracuse-Onondaga County Planning Agency (SOCPA)

ELECT_DIST Election district number Onondaga County Board of Elections

CITY_WARD City ward number Onondaga County Board of Elections

COUNTY_LEG Onondaga County Legislative District number (as of Dec 2022) Onondaga County Board of Elections

NYS_ASSEMB New York State Assembly District number (as of Dec 2022) Onondaga County Board of Elections

NYS_SENATE New York State Senate District number (as of Dec 2022) Onondaga County Board of Elections

US_CONGR United States Congressional District number Onondaga County Board of Elections

Dataset Contact InformationOrganization: Neighborhood & Business DevelopmentPosition:Data Program ManagerCity:Syracuse, NYE-Mail Address:opendata@syrgov.netPlease note there is a data quality issue in this iteration with the preservation district (“InPD,” “PDNAME”) and special neighborhood historic district (“SpecNhood”) fields erroneously showing null results for all parcels.

The property cadastral boundaries include lot lines, property lines and their dimensions (lengths). Other related datasets can be found by filtering on the property keyword. Data currencyThis data in City systems is updated frequently in the normal course of business, however priorities and resources determine how fast a change in reality is reflected in the database. The extract on this website is updated weekly. Data accuracyMuch of the City's land base is created using survey accuracy however some features are not as precise.

Approximate boundaries for all land parcels in New Brunswick. The boundaries are structured as Polygons. The Property Identifier number or PID is included for each parcel.

City of Austin Open Data Terms of Use https://data.austintexas.gov/stories/s/ranj-cccq

Map showing lot sizes broken down by typical sizes to qualify for certain developments

These data were compiled to demonstrate new predictive mapping approaches and provide comprehensive gridded 30-meter resolution soil property maps for the Colorado River Basin above Hoover Dam. Random forest models related environmental raster layers representing soil forming factors with field samples to render predictive maps that interpolate between sample locations. Maps represented soil pH, texture fractions (sand, silt clay, fine sand, very fine sand), rock, electrical conductivity (ec), gypsum, CaCO3, sodium adsorption ratio (sar), available water capacity (awc), bulk density (dbovendry), erodibility (kwfact), and organic matter (om) at 7 depths (0, 5, 15, 30, 60, 100, and 200 cm) as well as depth to restrictive layer (resdept) and surface rock size and cover. Accuracy and error estimated using a 10-fold cross validation indicated a range of model performances with coefficient of variation (R2) for models ranging from 0.20 to 0.76 with mean of 0.52 and a standard deviation of 0.12. Models of pH, om and ec had the best accuracy (R2 > 0.6). Most texture fractions, CaCO3, and SAR models had R2 values from 0.5-0.6. Models of kwfact, dbovendry, resdept, rock models, gypsum and awc had R2 values from 0.4-0.5 excepting near surface models which tended to perform better. Very fine sands and 200 cm estimates for other models generally performed poorly (R2 from 0.2-0.4), and sample size for the 200 cm models was too low for reliable model building. More than 90% of the soils data used was sampled since 2000, but some older samples are included. Uncertainty estimates were also developed by creating relative prediction intervals, which allow end users to evaluate uncertainty easily.

These data were compiled to demonstrate new predictive mapping approaches and provide comprehensive gridded 30-meter resolution soil property maps for the Colorado River Basin above Hoover Dam. Random forest models related environmental raster layers representing soil forming factors with field samples to render predictive maps that interpolate between sample locations. Maps represented soil pH, texture fractions (sand, silt clay, fine sand, very fine sand), rock, electrical conductivity (ec), gypsum, CaCO3, sodium adsorption ratio (sar), available water capacity (awc), bulk density (dbovendry), erodibility (kwfact), and organic matter (om) at 7 depths (0, 5, 15, 30, 60, 100, and 200 cm) as well as depth to restrictive layer (resdept) and surface rock size and cover. Accuracy and error estimated using a 10-fold cross validation indicated a range of model performances with coefficient of variation (R2) for models ranging from 0.20 to 0.76 with mean of 0.52 and a standard deviation of 0.12. Models of pH, om and ec had the best accuracy (R2 > 0.6). Most texture fractions, CaCO3, and SAR models had R2 values from 0.5-0.6. Models of kwfact, dbovendry, resdept, rock models, gypsum and awc had R2 values from 0.4-0.5 excepting near surface models which tended to perform better. Very fine sands and 200 cm estimates for other models generally performed poorly (R2 from 0.2-0.4), and sample size for the 200 cm models was too low for reliable model building. More than 90% of the soils data used was sampled since 2000, but some older samples are included. Uncertainty estimates were also developed by creating relative prediction intervals, which allow end users to evaluate uncertainty easily.

Parcels and property data maintained and provided by Lee County Property Appraiser are converted to points. Property attribute data joined to parcel GIS layer by Lee County Government GIS. This dataset is generally used in spatial analysis.Process description: Parcel polygons, condominium points and property data provided by the Lee County Property Appraiser are processed by Lee County's GIS Department using the following steps:Join property data to parcel polygons Join property data to condo pointsConvert parcel polygons to points using ESRI's ArcGIS tool "Feature to Point" and designate the "Source" field "P".Load Condominium points into this layer and designate the "Source" field "C". Add X/Y coordinates in Florida State Plane West, NAD 83, feet using the "Add X/Y" tool.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue. See https://leepa.org/Docs/Codes/DOR_Code_List.pdf


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13

The service represents all parcels and areas of Saxony. The plot boundaries shown are based on data from the real estate register. These differ according to origin, accuracy and trustworthiness. This map service is therefore not suitable with its contents for a calculation of dimensions, in particular limit dimensions or boundary distances. From the common presentation of the parcel boundaries together with other map contents (e.g. aerial image/DOP), it cannot be concluded to the actual legal situation on site. The presentation of data from the real estate register, in particular the parcel boundaries in this service, is not considered to be official proof, but merely has an informative character.

Digital line graph (DLG) data are digital representations of cartographic information. DLGs of map features are converted to digital form from maps and related sources. Intermediate-scale DLG data are derived from USGS 1:100,000-scale 30- by 60-minute quadrangle maps. If these maps are not available, Bureau of Land Management planimetric maps at a scale of 1:100,000 are used. Intermediate-scale DLGs are sold in five categories: (1) Public Land Survey System; (2) boundaries; (3) transportation; (4) hydrography; and (5) hypsography. All DLG data distributed by the USGS are DLG-Level 3 (DLG-3), which means the data contain a full range of attribute codes, have full topological structuring, and have passed certain quality-control checks.

This ownership dataset utilizes a methodology that results in a federal ownership extent that matches the Federal Responsibility Areas (FRA) footprint from CAL FIRE's State Responsibility Areas for Fire Protection (SRA) data. FRA lands are snapped to county parcel data, thus federal ownership areas will also be snapped. Since SRA Fees were first implemented in 2011, CAL FIRE has devoted significant resources to improve the quality of SRA data. This includes comparing SRA data to data from other federal, state, and local agencies, an annual comparison to county assessor roll files, and a formal SRA review process that includes input from CAL FIRE Units. As a result, FRA lands provide a solid basis as the footprint for federal lands in California (except in the southeastern desert area). The methodology for federal lands involves:

This dataset was updated April, 2024.

This ownership dataset was generated primarily from CPAD data, which already tracks the majority of ownership information in California. CPAD is utilized without any snapping or clipping to FRA/SRA/LRA. CPAD has some important data gaps, so additional data sources are used to supplement the CPAD data. Currently this includes the most currently available data from BIA, DOD, and FWS. Additional sources may be added in subsequent versions. Decision rules were developed to identify priority layers in areas of overlap.

Starting in 2022, the ownership dataset was compiled using a new methodology. Previous versions attempted to match federal ownership boundaries to the FRA footprint, and used a manual process for checking and tracking Federal ownership changes within the FRA, with CPAD ownership information only being used for SRA and LRA lands. The manual portion of that process was proving difficult to maintain, and the new method (described below) was developed in order to decrease the manual workload, and increase accountability by using an automated process by which any final ownership designation could be traced back to a specific dataset.

The current process for compiling the data sources includes:

* Clipping input datasets to the California boundary

* Filtering the FWS data on the Primary Interest field to exclude lands that are managed by but not owned by FWS (ex: Leases, Easements, etc)

* Supplementing the BIA Pacific Region Surface Trust lands data with the Western Region portion of the LAR dataset which extends into California.

* Filtering the BIA data on the Trust Status field to exclude areas that represent mineral rights only.

* Filtering the CPAD data on the Ownership Level field to exclude areas that are Privately owned (ex: HOAs)

* In the case of overlap, sources were prioritized as follows: FWS > BIA > CPAD > DOD

* As an exception to the above, DOD lands on FRA which overlapped with CPAD lands that were incorrectly coded as non-Federal were treated as an override, such that the DOD designation could win out over CPAD.

In addition to this ownership dataset, a supplemental _source dataset is available which designates the source that was used to determine the ownership in this dataset.

Data Sources:

* GreenInfo Network's California Protected Areas Database (CPAD2023a). https://www.calands.org/cpad/; https://www.calands.org/wp-content/uploads/2023/06/CPAD-2023a-Database-Manual.pdf

* US Fish and Wildlife Service FWSInterest dataset (updated December, 2023). https://gis-fws.opendata.arcgis.com/datasets/9c49bd03b8dc4b9188a8c84062792cff_0/explore

* Department of Defense Military Bases dataset (updated September 2023) https://catalog.data.gov/dataset/military-bases

* Bureau of Indian Affairs, Pacific Region, Surface Trust and Pacific Region Office (PRO) land boundaries data (2023) via John Mosley John.Mosley@bia.gov

* Bureau of Indian Affairs, Land Area Representations (LAR) and BIA Regions datasets (updated Oct 2019) https://biamaps.doi.gov/bogs/datadownload.html

Data Gaps & Changes:

Known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. Additionally, any feedback received about missing or inaccurate data can be taken back to the appropriate source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.

24_1: Input datasets this year included numerous changes since the previous version, particularly the CPAD and DOD inputs. Of particular note was the re-addition of Camp Pendleton to the DOD input dataset, which is reflected in this version of the ownership

City of Staunton Lot Lines

The Canadian County Parcel Data Public View is a set of geospatial features representing the surface ownership of property in fee simple for property tax purposes as required by 68 O.S. § 2821 and other related data used to produce the parcels such as subdivision boundaries and subdivision lots. The data is created from source documentation filed with the Canadian County Clerk's Office including deeds, easements, and plats. Other data sources such as filed Certified Corner Records filed with the State of Oklahoma or highway plans produced by the Department of Transportation may be used to adjust parcel boundaries. Single legal descriptions may be split up into two or more parcels if the description crosses the boundaries of multiple taxing jurisdictions or crosses quarter section boundaries. Accuracy of parcel data can vary considerably due to a combination of factors. Most parcels and subdivision legal descriptions reference a quarter section or quarter section corner. The accuracy of the quarter section corners is discussed with Canadian County's Public Land Survey System Data. Accuracy is further enhanced or degraded by the quality of the legal description used to create the feature. Generally, legal descriptions created from surveys will have higher accuracy the newer they were created due to improvements in the field of surveying. However, it can be difficult to determine the age of a legal description as descriptions are generally reused on subsequent deeds after the description was first created. Legal descriptions can occasionally contain updated bearings and distances and may denote the updates. The Assessor's Office uses the latest available legal description for creating parcels. Legal descriptions may lack specificity such as the use of "North" instead of a measured bearing or have missing parameters such as missing bearings for curved boundaries. In these cases, parcel data accuracy can be degraded. Further, if a legal description contains a specific landmark or boundary, sometimes called a "bound", the boundary is drawn to that point or landmark regardless of whether the bearing and/or distance accurately arrive at that point. For instance, if a legal description reads "...to the south line of the southeast quarter", the boundary is drawn to the south line of the quarter section even if the bearing and distance are short of or extend beyond that point. Because parcel data must be created for the entire county regardless of the accuracy of the descriptions used to create those parcels, parcels may need to be "stretched" or "squeezed" to make them fit together. When possible, the Assessor's Office relies on the most accurate legal descriptions to set the boundaries and then fits older boundaries to them. Due to the large number of variables, parcel data accuracy cannot be guaranteed nor can the level of accuracy be described for the entire dataset. While Canadian County makes every reasonable effort to make sure parcel data is accurate, this data cannot be used in place of a survey performed by an Oklahoma Licensed Professional Land Surveyor.ParcelDataExternal - Polygons representing surface fee simple title. This parcel data formatted and prepared for public use. Some fields may be blank to comply with 22 O.S. § 60.14 & 68 O.S. § 2899.1Attributes:Account (account): The unique identifier for parcel data generated by the appraisal software used by the Assessor's Office"A" Number (a_number): An integer assigned in approximate chronological order to represent each parcel divided per quarter sectionParcel ID (parcel_id): Number used to identify parcels geographically, see Parcel Data Export Appendix A for an in-depth explanation. This identifier is not unique for all parcelsParcel Size (parcel_size): Size of the parcels, must be used in conjunction with following units fieldParcel Size Units (parcel_size_units): Units for the size of the parcel. Can be "Acres" or "Lots" for parcels within subdivisions that are valued per lotOwner's Name (owners_name): Name of the surface owner of the property in fee simple on recordMailing Information (mail_info): Extra space for the owners name if needed or trustee namesMailing Information 2 (mail_info2): Forwarded mail or "In care of" mailing informationMailing Address (mail_address): Mailing address for the owner or forwarding mailing addressMailing City (mail_city): Mailing or postal cityMailing State (mail_state): Mailing state abbreviated to standard United States Postal Service codesMailing ZIP Code (mail_zip): Mailing ZIP code as determined by the United States Postal ServiceTax Area Code (tax_area): Integer numeric code representing an area in which all the taxing jurisdictions are the same. See Parcel Data Appendix B for a more detailed description of each tax areaTax Area Description (tax_area_desc): Character string code representing the tax area. See Parcel Data Appendix B for a more detailed description of each tax areaProperty Class (prop_class): The Assessor's Office classification of each parcel by rural (no city taxes) or urban (subject to city taxes) and exempt, residential, commercial, or agriculture. This classification system is for property appraisal purposes and does not reflect zoning classifications in use by municipalities. See Parcel Data Appendix B for a more detailed description of each property classificationLegal Description (legal): A highly abbreviated version of the legal description for each parcel. This legal description may not match the most recent legal description for any given property due to administrative divisions as described above, or changes made to the property by way of recorded instruments dividing smaller parcels from the original description. This description may NOT be used in place of a true legal descriptionSubdivision Code (subdiv_code): A numeric code representing a recorded subdivision plat which contains the parcel. This value will be "0" for any parcel not part of a recorded subdivision plat.Subdivision Name (subdiv_name): The name of the recorded subdivision plat abbreviated as needed to adapt to appraisal software field limitationsSubdivision Block Number (subdiv_block): Numeric field representing the block number of a parcel. This value will be "0" if the parcel is not in a recorded subdivision plat or if the plat did not contain block numbersSubdivision Lot Number (subdiv_lot): Numeric field representing the lot number of a parcel. This value will be "0" if the parcel is not in a recorded subdivision platTownship Number (township): Numeric field representing the Public Land Survey System tier or township the parcel is located in. All townships or tiers in Canadian County are north of the base line of the Indian Meridian.Range Number (range): Numeric field representing the Public Land Survey System range the parcel is located in. All Ranges in Canadian County are west of the Indian MeridianSection Number (section): Numeric field representing the Public Land Survey System section number the parcel is located inQuarter Section Code (quarter_sec): Numeric field with a code representing the quarter section a majority of the parcel is located in, 1 = Northeast Quarter, 2 = Northwest Quarter, 3 = Southwest Quarter, 4 = Southeast QuarterSitus Address (situs): Address of the property itself if it is knownSitus City (situs_city): Name of the city the parcel is actually located in (regardless of the postal city) or "Unincorporated" if the parcel is outside any incorporated city limitsSitus ZIP Code (situs_zip): ZIP Code as determined by the United States Postal Service for the property itself if it is knownLand Value (land_val): Appraised value of the land encompassed by the parcel as determined by the Assessor's OfficeImprovement Value (impr_val): Appraised value of the improvements (house, commercial building, etc.) on the property as determined by the Assessor's OfficeManufactured Home Value (mh_val): Appraised value of any manufactured homes on the property and owned by the same owner of the land as determined by the Assessor's OfficeTotal Value (total_val): Total appraised value for the property as determined by the Assessor's OfficeTotal Capped Value (cap_val): The capped value as required by Article X, Section 8B of the Oklahoma ConstitutionTotal Assessed Value (total_assess): The capped value multiplied by the assessment ratio of Canadian County, which is 12% of the capped valueHomestead Exempt Amount (hs_ex_amount): The amount exempt from the assessed value if a homestead exemption is in placeOther Exempt Value (other_ex_amount): The amount exempt from the assessed value if other exemptions are in placeTaxable Value (taxable_val): The amount taxes are calculated on which is the total assessed value minus all exemptionsSubdivisions - Polygons representing a plat or subdivision filed with the County Clerk of Canadian County. Subdivision boundaries may be revised by vacations of the plat or subdivision or by replatting a portion or all of a subdivision. Therefore, subdivision boundaries may not match the boundaries as shown on the originally filed plat.Attributes:Subdivision Name (subdivision_name): The name of the plat or subdivisionSubdivision Number (subdivision_number): An ID for each subdivision created as a portion of the parcel ID discussed in Parcel Data Export Appendix APlat Book Number (book): The book number for the recorded documentPlat Book Page Number (page): The page number for the recorded documentRecorded Acres (acres): The number of acres within the subdivision if knownRecorded Date (recorded_date): The date the document creating the subdivision was recordedDocument URL (clerk_url): URL to download a copy of the document recorded by the Canadian County Clerk's OfficeBlocks - Polygons derived from subdivision lots representing the blocks

Land based information extracted from the Sunshine Council Regional Council corporate database (T1 Property), linked to the cadastre for representation of the land parcel boundaries. Attribute information includes land parcel addresses, property names and area details.

"Cadastral Area Boundary is a line layer belonging to Vicmap Property and consists of data representing Victoria's land parcels and properties and is used extensively in Geographic Information Systems (GIS) by the public and private sectors. More Information: https://www.data.vic.gov.au/data/dataset/cadastral-area-boundary-vicmap-property Author: Department of Environment and Primary Industries Owner: Department of Environment and Primary Industries"