DOUGLAS COUNTY SURVEY/GISGIS PARCEL MAPPING GUIDELINES FOR PARCEL DISCREPANCIESIt is the intent of the Douglas County GIS Parcel Mapping to accurately identify the areas of land parcels to be valued and taxed 1. Discrepancies in areas• The Auditor/Assessor (tax) acreage areas started with the original US General Land Office (GLO) township plat maps created from the Public Land Survey (PLS) that was done between 1858 and 1871. The recovery of the PLS corners and the accurate location of these corners with GPS obtained coordinates has allowed for accurate section subdivisions, which results in accurate areas for parcels based on legal descriptions, which may be significantly different than the original areas. (See Example 2)• Any parcel bordering a meandered lake and/or a water boundary will likely have a disparity of area between the Auditor/Assessor acreages and the GIS acreages because of the inaccuracy of the original GLO meander lines from which the original areas were determined. Water lines are not able to be drafted to the same accuracy as the normal parcel lines. The water lines are usually just sketched on a survey and their dimensions are not generally given on a land record. The water boundaries of our GIS parcels are located from aerial photography. This is a subjective determination based on the interpretation by the Survey/GIS technician of what is water. Some lakes fluctuate significantly and the areas of all parcels bordering water are subject to constant change. In these cases the ordinary high water line (OHW) is attempted to be identified. Use of 2-foot contours will be made, if available. (See Example 1)• Some land records do not accurately report the area described in the land description and the description area is ignored. (See Example 3)• The parcel mapping has made every attempt to map the parcels based on available survey information as surveyed and located on the ground. This may conflict with some record legal descriptions.Solutions• If an actual survey by a licensed Land Surveyor is available, it will be utilized for the tax acreage.• If the Auditor/Assessor finds a discrepancy between the tax and GIS areas, they will request a review by the County Survey/GIS department.• As a starting guideline, the County Survey/GIS department will identify all parcels that differ in tax area versus GIS parcel area of 10 % or more and a difference of at least 5 acres. (This could be expanded later after the initial review.)• Each of these identified parcels will be reviewed individually by the County Survey/GIS department to determine the reason for the discrepancy and a recommendation will be made by the County Survey/GIS department to the Auditor/Assessor if the change should be made or not.• If a change is to be made to the tax area, a letter will be sent to the taxpayer informing them that their area will be changed during the next tax cycle, which could affect their property valuation. This letter will originate from the Auditor/Assessor with explanation from the County Survey/GIS department. 2. Gaps and Overlaps• Land descriptions for adjoining parcels sometimes overlap or leave a gap between them.o In these instances the Survey/GIS technician has to make a decision where to place this boundary. A number of circumstances are reviewed to facilitate this decision as these dilemmas are usually decided on a case by case basis. All effort will be made to not leave a gap, but sometimes this is not possible and the gap will be shown with “unknown” ownership. (Note: The County does not have the authority to change boundaries!)o Some of the circumstances reviewed are: Which parcel had the initial legal description? Does the physical occupation of the parcel line as shown on the air photo more closely fit one of the described parcels? Interpretation of the intent of the legal description. Is the legal description surveyable?Note: These overlaps will be shown on the GIS map with a dashed “survey line” and accompanying text for the line not used for the parcel boundary. 3. Parcel lines that do not match location of buildings Structures on parcels do not always lie within the boundaries of the parcel. This may be a circumstance of building without the benefit of a survey or of misinterpreting these boundaries. The parcel lines should be shown accurately as surveyed and/or described regardless of the location of structures on the ground. NOTE: The GIS mapping is not a survey, but is an interpretation of parcel boundaries predicated upon resources available to the County Survey/GIS department.Gary Stevenson Page 1 7/21/2017Example 1Example 2A Example 2B Example 3

Layers in this dataset represent Public Land Survey System subdivisions for Canadian County. Included are Townships, Sections, Quarter Sections and Government Lots. This data was created from 2019 to 2021 as part of a project to update county parcel data in partnership with ProWest & Associates (https://www.prowestgis.com/) and CEC Corporation (https://www.connectcec.com/). Corners were located to the quarter section level and additional corners were determined for the South Canadian River meanders based on the original government surveys. Quarter section corners were located using Certified Corner Records ( filed by Oklahoma licensed professional surveyors with the Oklahoma Department of Libraries where those records included coordinates. When a corner record could not be found or did not include coordinates, other interpolation methods were employed. These included connecting known corner record locations to unknown corners using data from filed subdivisions or from highway plans on record with the Oklahoma Department of Transportation. Where no corner records with coordinates were available and no interpolation methods could be used, aerial inspection was used to locate corners as the last option.Corner location accuracy varies as the method of locating the corner varies. For corners located using Certified Corner Records, accuracy is high depending on the age of the corner record and can possibly be less than 1 U.S. Foot. For corners located using interpolation methods, accuracy depends on the additional material used to interpolate the corner. In general, newer subdivisions and highway plans yield higher accuracy. For meander corners located using original government surveys, accuracy will be low due to the age of those surveys which date to the 1870's at the earliest. Additionally, corners that were located with aerials as the last available option cannot be assumed to be accurate.The data was built at the quarter section level first by connecting located corners and larger subdivisions were created from the quarter sections. For townships that extend into Grady County, township lines were only roughly located outside sections not in Canadian County.

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is regularly updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. PurposeCounty boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use. Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal Buffers (this dataset)Without Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead. Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA's source data notes the following about accuracy: City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties. In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose. SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these

This data set contains polygons that represent quarter quarter sections. In 1985, Ramsey County began a 5 year project to modernize it's land records mapping system to create a computerized Land Information System. As part of the project, the County developed an accurate coordinate control base for this mapping system. The 27 existing State and Federal first order accuracy positions in Ramsey County were densified by a GPS (Global Positioning System) Network of 171 second order accuracy positions. These positions were established and recorded on existing public land survey corner monuments and accessory monuments through out the county.

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

The Digital Geologic-GIS Map of Fayette County, Pennsylvania is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (faco_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (faco_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (faco_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (fone_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (fone_frhi_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (faco_geology_metadata_faq.pdf). Please read the fone_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Pennsylvania Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (faco_geology_metadata.txt or faco_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:50,000 and United States National Map Accuracy Standards features are within (horizontally) 25.4 meters or 83.3 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Detailed information on individual parcels within Cumberland County, NC, including the City of Fayetteville, the Town of Hope Mills, the Town of Spring Lake, the Town of Eastover, the Town of Falcon, the Town of Godwin, the Town of Linden, the Town of Stedman, and the Town of Wade. Attributes include:Parcel REID (PIN Number): A unique identifier assigned to each parcel for tax purposes.Owner Information: Name and contact details of the property owner(s).Parcel Boundaries: Geospatial data defining the exact boundaries of each parcel.Assessed Value: The assessed value of the land and any improvements for property tax purposes.Land Use: Current land use classification (e.g., residential, commercial, agricultural).Size: Area of the parcel in square feet or acres.Zoning: Zoning classification and any applicable zoning restrictions.Legal Descriptions: Detailed legal description of the parcel boundaries and location.This layer is crucial for tax assessors, urban planners, developers, and other stakeholders who require accurate and up-to-date parcel information for decision-making and operational purposes. It supports a wide range of applications, including property tax assessments, land use planning, infrastructure development, and real estate transactions.More information at https://cumberlandgis.maps.arcgis.com/apps/webappviewer/index.html?id=a6ea68995c2349e9a177366288589be7

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal Buffers (this dataset)Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing excludes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections. Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor.CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information.CDTFA's source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and

This dataset is designed to represent and identify the property boundaries in Lexington-Fayette County. The original dataset was created in late 1990's by a third party that converted existing paper maps to digital GIS files. The data has since been updated by georeferencing recorded plats for corrections and new additions. In cases where the plats do not appear accurate, aerial photos are utilized in attempt to properly locate the property lines. The only except for this process are changes to highway right-of-way in which calls are run from deeds. The geometry of this data is not of survey quality and should not be used for survey purposes. The data is intended for general reference purposes only.As part of the basemap data layers, the parcel boundary map layer is an integral part of the Lexington Fayette-Urban County Government Geographic Information System. Basemap data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production. More advanced user applications may focus on thematic mapping, summarization of data by geography, or planning purposes (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, and presentation output).

The Digital Glacial and Surficial Geologic-GIS Map of Summit County and Parts of Cuyahoga County, Ohio is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (cuva_glacial_surficial_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (cuva_glacial_surficial_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (cuva_geology.gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (cuva_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (cuva_glacial_surficial_geology_metadata_faq.pdf). Please read the cuva_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: http://www.google.com/earth/index.html. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Ohio Division of Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (cuva_glacial_surficial_geology_metadata.txt or cuva_glacial_surficial_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

This layer contains parcels data for Oswego County, NY as taken from the current digitized version of the county tax maps. Originally drawn by Stewart Mapping Services, Inc of San Antonio Texas in 1975, but with digital topology corrected by Oswego County's Department of Real Property Tax Services from 1996-present. Contains taxable parcels attributed with assessment data taken from local assessment rolls.Geography is based upon the taxable status date of March 1st, 2025. Assessment attributes are from the latest final assessment roll (2024) except ownership which is updated bi-monthly on Fridays to reflect the most current owners of record. Click here to retrieve a data dictionary for decoding fields.Note: The original tax maps that these files were digitized from only had an accuracy between 10-20 feet on ground. While every effort is made to maintain this geographic data in an accurate format, the lines drawn from this data are fundamentally informational in nature and are not equivalent to survey grade. Geoprocessing has been applied to this specific web layer to allow faster drawing of lines which can further degrade the accuracy of their geometry. Finally, these parcels are used to create county tax maps which have the sole use case of giving assistance for local municipal assessors in the fulfillment of their duties, there is no warranty (expressed or implied) for any other use.

Purpose:To provide a spatially accurate representation of the Wood County boundary in Ohio, supporting county-level mapping, jurisdictional delineation, public service delivery, and regional planning.Supplemental Information:This dataset is intended for general mapping and administrative use within Wood County, assisting with public safety, land management, and jurisdictional clarity.Keywords:County Boundary, Administrative Boundary, Jurisdiction, Wood County, Ohio, Mapping, Regional Planning.Lineage:Source(s): Derived from authoritative state and county records, maintained by Wood County GIS for accuracy and alignment with Ohio jurisdictional standards.Process Steps:Boundaries were digitized based on official county records and validated to ensure consistency with Ohio Department of Transportation and state standards.Accuracy and Consistency:Positional Accuracy: Conforms to county records and official state boundary definitions.Attribute Accuracy: Boundary attributes have been verified against county and state records.Logical Consistency: Ensures complete and closed boundary with no overlaps or gaps.Data Type:Vector (Polygon)Composition:Polygon feature representing the boundary of Wood County, Ohio.Spatial Reference:Coordinate System: NAD 1983 NSRS2007 StatePlane Ohio North FIPS 3401 (US Feet)Projection: Lambert Conformal ConicDatum: NAD 1983 NSRS2007Time Period of Content:Reflects conditions as of the latest boundary confirmation from Wood County GIS.Currentness Reference:Updated as needed to reflect any jurisdictional changes, in alignment with county and state standards.This dataset was created and last updated prior to the current GIS Manager.Contacts:Primary Contact:David L. Price, GIS Coordinator, Wood County GIS DepartmentPhone: (419) 373-3984Email: dprice@woodcountyohio.govDistributor:Available upon request through Wood County GIS or via the Wood County GIS Public Data Site.Distribution Liability:Wood County disclaims responsibility for improper or incorrect use of this dataset. Provided "as-is" without warranty for completeness or accuracy for any specific use.Metadata Date:October 21, 2024Metadata Review Date:October 21, 2025Metadata Contact:David L. Price, (419) 373-3984, dprice@woodcountyohio.gov

This data set was developed to provide accurate framework data (including address points, street centerlines, land parcels, and governmental boundaries) for Indiana, as part of the Indiana Data Sharing Initiative (IDSI) of the Indiana Geographic Information Office (IGIO). Last updated October 2019. Parcel geometries loaded between 11/26/2018 and 6/18/2019. DLGF information from "Real Property 2018 - Pay 2019" data records.COUNTY_PARCEL is a polygon feature class that contains land parcels maintained by county agencies in Indiana, provided by personnel of Indiana Geographic Information Office (IGIO) on October 17, 2019. These data were compiled by IGIO as part of the Indiana Data Sharing Initiative (IDSI) between Indiana Geographic Information Council (IGIC), Indiana Geographic Information Office (IGIO), Indiana Geological and Water Survey (IGWS) and participating Indiana counties to provide the most accurate framework data (including address points, street centerlines, land parcels, and governmental boundaries) for the citizens of Indiana. The attributes have been expanded to now include parcel ID, dates of harvest from each county, property classification codes, property classification descriptions, street address information, and tax district ID numbers. Last updated October 2019. Parcel geometries loaded between 11/26/2018 and 6/18/2019 (see LOAD_DATE attribute field). DLGF information from "Real Property 2018 - Pay 2019" data records.

The data depicted in the Wilson County GIS was prepared solely for the purpose of inventory and representation of the Wilson County Cadastre and its source documents and should not be used for any other purpose. The information contained herein was compiled from previously georeferenced data and/or public records, and these primary sources must be consulted for verification of the information contained in this map. This GIS data is not intended to indicate the authoritative location of property boundaries, shape or contour of the earth, or fixed works. GIS maps are not surveys and do not meet the minimum accuracy standards of a Land Information System/Geographic Information System Survey in North Carolina (21 NCAC 56.1608).

This is a connection to the York County Spatial GIS Open Data Portal managed by the York County Planning Commission with coordination from York County Departments.

Contact Information: York County Planning Commission 28 East Market Street, 3rd Floor York, PA 17401-1580 T: 717.771.9870 F: 717.771.9511 E: InformationSystemschief@ycpc.org

Website: www.ycpc.org includes all the latest news

Visit http://yorkcountypa.maps.arcgis.com/home/index.html to view our interactive web mapping applications.

Disclaimer: The York County Planning Commission provides this Geographic Information System map and/or data (collectively the "Data") as a public information service. The Data is not a legally recorded plan, survey, official tax map, or engineering schematic and should be used for only general information. Reasonable effort has been made to ensure that the Data is correct; however the Commission does not guarantee its accuracy, completeness, or timeliness. The Commission shall not be liable for any damages that may arise from the use of the Data.

Tax Parcel shape files, metadata, and geodatabases by town and city available to download: https://gisdata.ny.gov/GISData/County/Greene/Parcel_Data/Greene_County_Tax_Parcels.zip Database was prepared for assessment administration purposes only. It is not intended for use in the conveyance of land. Absolutely no accuracy or completeness is implied or intended. All the information is subject to such variations and corrections that may result from an accurate instrument survey and or abstract of title Spatial Reference of Source Data: NAD 83 State Plane – New York East.Spatial Reference of Web Service: WGS 1984 Web Mercator Auxiliary Sphere. Data current as of July 2025. Contact Information:Greene County Real Property Tax Service411 Main Street Suite 447Catskill, New York 12414PH: 518-719-3525FAX: 518-719-3791rpts@greenecountyny.gov

Northeastern United States County Boundary data are intended for geographic display of state and county boundaries at statewide and regional levels. Use it to map and label counties on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 59 counties that have opted-in as of the publication date of this dataset: Aitkin County, Anoka County, Becker County, Benton County, Big Stone County, Carlton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Clearwater County, Cook County, Crow Wing County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Lyon County, Marshall County, McLeod County, Mille Lacs County, Morrison County, Mower County, Murray County, Norman County, Olmsted County, Otter Tail County, Pennington County, Pipestone County, Polk County, Pope County, Ramsey County, Red Lake County, Renville County, Rice County, Scott County, Sherburne County, St. Louis County, Stearns County, Steele County, Stevens County, Traverse County, Wabasha County, Waseca County, Washington County, Wilkin County, Winona County, Wright County, and Yellow Medicine County.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

Contour lines derived from 2011 aerial photography.