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 seamless, county-wide parcel layer was digitized from official Assessor Parcel (AP) Maps which were originally maintained on mylar sheets and/or maintained as individual Computer Aided Design (CAD) drawing files (e.g., DWG). The CRA office continues to maintain the official AP Maps in CAD drawings and Information Systems Department/Geographic Information Systems (ISD/GIS) staff apply updates from these maps to the seamless parcel base in the County’s Enterprise GIS. The seamless parcel layer is updated and published to the Internet on a monthly basis.The seamless parcel layer was developed from the source data using the general methodology outlined below. The mylar sheets were scanned and saved to standard image file format (e.g., TIFF). The individual scanned maps or CAD drawing files were imported into GIS software and geo-referenced to their corresponding real-world locations using high resolution orthophotography as control. The standard approach was to rescale and rotate the scanned drawing (or CAD file) to match the general location on the orthophotograph. Then, appropriate control points were selected to register and rectify features on the scanned map (or CAD drawing file) to the orthophotography. In the process, features in the scanned map (or CAD drawing file) were transformed to real-world coordinates, and line features were created using “heads-up digitizing” and stored in new GIS feature classes. Recommended industry best practices were followed to minimize root mean square (RMS) error in the transformation of the data, and to ensure the integrity of the overall pattern of each AP map relative to neighboring pages. Where available Coordinate Geometry (COGO) & survey data, tied to global positioning systems (GPS) coordinates, were also referenced and input to improve the fit and absolute location of each page. The vector lines were then assembled into a polygon features, with each polygon being assigned a unique identifier, the Assessor Parcel Number (APN). The APN field in the parcel table was joined to the corresponding APN field in the assessor property characteristics table extracted from the MPTS database to create the final parcel layer. The result is a seamless parcel land base, each parcel polygon coded with a unique APN, assembled from approximately 6,000 individual map page of varying scale and accuracy, but ensuring the correct topology of each feature within the whole (i.e., no gaps or overlaps). The accuracy and quality of the parcels varies depending on the source. See the fields RANK and DESCRIPTION fields below for information on the fit assessment for each source page. These data should be used only for general reference and planning purposes. It is important to note that while these data were generated from authoritative public records, and checked for quality assurance, they do not provide survey-quality spatial accuracy and should NOT be used to interpret the true location of individual property boundary lines. Please contact the Sonoma County CRA and/or a licensed land surveyor before making a business decision that involves official boundary descriptions.

This parcels polygons feature class represents current city parcels within the City of Los Angeles. It shares topology with the Landbase parcel lines feature class. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcels is entered into attributes. Principal attributes include:PIN and PIND: represents the unique auto-generated parcel identifier and key to related features and tables. This field is related to the LA_LEGAL, LA_APN and LA_HSE_NBR tables. PIN contains spaces and PIND replaces those spaces with a dash (-).LA_LEGAL - Table attributes containing legal description. Principal attributes include the following:TRACT: The subdivision tract number as recorded by the County of Los AngelesMAP_REF: Identifies the subdivision map book reference as recorded by the County of Los Angeles.LOT: The subdivision lot number as recorded by the County of Los Angeles.ENG_DIST: The four engineering Districts (W=Westla, C=Central, V= Valley and H=Harbor).CNCL_DIST: Council Districts 1-15 of the City of Los Angeles. OUTLA means parcel is outside the City.LA_APN- Table attributes containing County of Los Angeles Assessors information. Principal attributes include the following:BPP: The Book, Page and Parcel from the Los Angeles County Assessors office. SITUS*: Address for the property.LA_HSE_NBR - Table attributes containing housenumber information. Principal attributes include the following:HSE_ID: Unique id of each housenumber record.HSE_NBR: housenumber numerical valueSTR_*: Official housenumber addressFor a complete list of attribute values, please refer to Landbase_parcel_polygons_data_dictionary.Landbase parcels polygons data layer was created in geographical information systems (GIS) software to display the location of the right of way. The parcels polygons layer delineates the right of way from Landbase parcels lots. The parcels polygons layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a polygon feature class and attribute data for the features. The area inside a polygon feature is a parcel lot. The area outside of the parcel polygon feature is the right of way. Several polygon features are adjacent, sharing one line between two polygons. For each parcel, there is a unique identifier in the PIND and PIN fields. The only difference is PIND has a dash and PIN does not. The types of edits include new subdivisions and lot cuts. Associated legal information about the landbase parcels lots is entered into attributes. The landbase parcels layer is vital to other City of LA Departments, by supporting property and land record operations and identifying legal information for City of Los Angeles. The landbase parcels polygons are inherited from a database originally created by the City's Survey and Mapping Division. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.ASSETID: User-defined feature autonumber.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral grid index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers. An A-map is the smallest grid in the index map and is used when there is a large amount of spatial information in the map display. There are more parcel lines and annotation than can fit in the B-map, and thus, an A-map is used. There are 4 A-maps in a B-map. In areas where parcel lines and annotation can fit comfortably in an index map, a B-map is used. The B-maps are at a scale of 100 feet, and A-maps are at a scale of 50 feet.OBJECTID: Internal feature number.BPPMAP_REFTRACTBLOCKMODLOTARBCNCL_DIST: LA City Council District. Values: • (numbers 1-15) - Current City Council Member for that District can be found on the mapping website http://navigatela.lacity.org/navigatela, click Council Districts layer name, under Boundaries layer group.SHAPE: Feature geometry.BOOKPAGEPARCELPIND: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. The D in the field name PIND, means "dash", and there is a dash between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • H - Harbor Engineering District. • C - Central Engineering District. • V - Valley Engineering District. • W - West LA Engineering District.PIN: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. There are spaces between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.

Cadastral Mapping Market Outlook

The global cadastral mapping market size was valued at approximately USD 4.2 billion in 2023 and is projected to reach around USD 7.9 billion by 2032, growing at a compound annual growth rate (CAGR) of 7.2% during the forecast period. This market growth can be attributed to increasing urbanization, rapid advancements in geospatial technologies, and the growing need for efficient land management systems across various regions.

The expansion of urban areas and the corresponding increase in the need for effective land management infrastructure are significant growth factors driving the cadastral mapping market. As urbanization accelerates globally, local governments and planning agencies require sophisticated tools to manage and record land ownership, boundaries, and property information. Enhanced geospatial technologies, including Geographic Information Systems (GIS) and remote sensing, are pivotal in facilitating accurate and efficient cadastral mapping, thus contributing to market growth.

Another key growth factor is the rising demand for infrastructure development. As nations invest in large-scale infrastructure projects such as roads, railways, and smart cities, there is an increased need for precise land data to ensure the proper allocation of resources and to avoid legal disputes. Cadastral mapping provides the critical data needed for these projects, hence its demand is surging. Additionally, governments worldwide are increasingly adopting digital platforms to streamline land administration processes, further propelling the market.

Furthermore, the agricultural sector is also significantly contributing to the growth of the cadastral mapping market. Modern agriculture relies heavily on accurate land parcel information for planning and optimizing crop production. By integrating cadastral maps with other geospatial data, farmers can improve land use efficiency, monitor crop health, and enhance yield predictions. This integration is particularly valuable in precision farming, which is becoming more prevalent as the world's population grows and the demand for food increases.

Regionally, Asia Pacific is expected to witness the highest growth in the cadastral mapping market. Factors such as rapid urbanization, extensive infrastructure development projects, and the need for improved land management are driving the demand in this region. Moreover, governments in countries like India and China are investing heavily in creating digital land records and implementing smart city initiatives, which further boosts the market. The North American and European markets are also substantial, driven by the advanced technological infrastructure and well-established land administration systems.

Component Analysis

The cadastral mapping market can be segmented by component into software, hardware, and services. The software segment holds a significant share in this market, driven by the increasing adoption of advanced GIS and mapping software solutions. These software solutions enable accurate land parcel mapping, data analysis, and integration with other geospatial data systems, making them indispensable tools for cadastral mapping. Companies are continuously innovating to provide more intuitive and comprehensive software solutions, which is expected to fuel growth in this segment.

Hardware components, including GPS devices, drones, and other surveying equipment, are also critical to the cadastral mapping market. The hardware segment is expected to grow steadily as technological advancements improve the accuracy and efficiency of these devices. Innovations such as high-resolution aerial imaging and LIDAR technology are enhancing the capabilities of cadastral mapping hardware, allowing for more detailed and precise data collection. This segment is particularly essential for field surveying and data acquisition, forming the backbone of cadastral mapping projects.

The services segment encompasses a wide range of offerings, including consulting, implementation, and maintenance services. Professional services are vital for the successful deployment and operation of cadastral mapping systems. Governments and private sector organizations often rely on specialized service providers to implement these systems, train personnel, and ensure ongoing support. As the complexity of cadastral mapping projects increases, the demand for expert services is also expected to rise, contributing to the growth of this segment.

Integration services are another critical component within the

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

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.

The Digital Geologic-GIS Map of the Leipers Fork Quadrangle, Tennessee 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 (lefo_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 (lefo_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 (lefo_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 (natr_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (natr_tn_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 (lefo_geology_metadata_faq.pdf). Please read the natr_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: Tennessee Division of Geology. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (lefo_geology_metadata.txt or lefo_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:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 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).

The Tioga County Geographic Information Tool is intended to be a parcel map viewer with additional layers of information of special interest to property owners. The parcel boundaries do not appear until the user zooms in on the map. Other layers can be turned on and off using from the layers list which can be exposed by clicking the Layer button in the upper right corner of the interface. A button at the bottom of the viewer opens a table viewer which can be used to explore the data related to each of the map layers. The table includes tools for filtering the data and selected records may be exported to a CSV file which can be opened as a text file using spreadsheet software. By default, clicking in a parcel brings up a popup of the parcel's attribute information. Popups for other layers can be enabled through the layer list. Other buttons allow the user to search for street addresses in Tioga County NY, locate the user's position using the GNSS capability of mobile devices, changing the base map, measuring distances and areas, identifying the coordinates of any location (a function of the measure tool), and displaying a legend.

Please note that this dataset is not an official City of Toronto land use dataset. It was created for personal and academic use using City of Toronto Land Use Maps (2019) found on the City of Toronto Official Plan website at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/official-plan-maps-copy, along with the City of Toronto parcel fabric (Property Boundaries) found at https://open.toronto.ca/dataset/property-boundaries/ and Statistics Canada Census Dissemination Blocks level boundary files (2016). The property boundaries used were dated November 11, 2021. Further detail about the City of Toronto's Official Plan, consolidation of the information presented in its online form, and considerations for its interpretation can be found at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/ Data Creation Documentation and Procedures Software Used The spatial vector data were created using ArcGIS Pro 2.9.0 in December 2021. PDF File Conversions Using Adobe Acrobat Pro DC software, the following downloaded PDF map images were converted to TIF format. 9028-cp-official-plan-Map-14_LandUse_AODA.pdf 9042-cp-official-plan-Map-22_LandUse_AODA.pdf 9070-cp-official-plan-Map-20_LandUse_AODA.pdf 908a-cp-official-plan-Map-13_LandUse_AODA.pdf 978e-cp-official-plan-Map-17_LandUse_AODA.pdf 97cc-cp-official-plan-Map-15_LandUse_AODA.pdf 97d4-cp-official-plan-Map-23_LandUse_AODA.pdf 97f2-cp-official-plan-Map-19_LandUse_AODA.pdf 97fe-cp-official-plan-Map-18_LandUse_AODA.pdf 9811-cp-official-plan-Map-16_LandUse_AODA.pdf 982d-cp-official-plan-Map-21_LandUse_AODA.pdf Georeferencing and Reprojecting Data Files The original projection of the PDF maps is unknown but were most likely published using MTM Zone 10 EPSG 2019 as per many of the City of Toronto's many datasets. They could also have possibly been published in UTM Zone 17 EPSG 26917 The TIF images were georeferenced in ArcGIS Pro using this projection with very good results. The images were matched against the City of Toronto's Centreline dataset found here The resulting TIF files and their supporting spatial files include: TOLandUseMap13.tfwx TOLandUseMap13.tif TOLandUseMap13.tif.aux.xml TOLandUseMap13.tif.ovr TOLandUseMap14.tfwx TOLandUseMap14.tif TOLandUseMap14.tif.aux.xml TOLandUseMap14.tif.ovr TOLandUseMap15.tfwx TOLandUseMap15.tif TOLandUseMap15.tif.aux.xml TOLandUseMap15.tif.ovr TOLandUseMap16.tfwx TOLandUseMap16.tif TOLandUseMap16.tif.aux.xml TOLandUseMap16.tif.ovr TOLandUseMap17.tfwx TOLandUseMap17.tif TOLandUseMap17.tif.aux.xml TOLandUseMap17.tif.ovr TOLandUseMap18.tfwx TOLandUseMap18.tif TOLandUseMap18.tif.aux.xml TOLandUseMap18.tif.ovr TOLandUseMap19.tif TOLandUseMap19.tif.aux.xml TOLandUseMap19.tif.ovr TOLandUseMap20.tfwx TOLandUseMap20.tif TOLandUseMap20.tif.aux.xml TOLandUseMap20.tif.ovr TOLandUseMap21.tfwx TOLandUseMap21.tif TOLandUseMap21.tif.aux.xml TOLandUseMap21.tif.ovr TOLandUseMap22.tfwx TOLandUseMap22.tif TOLandUseMap22.tif.aux.xml TOLandUseMap22.tif.ovr TOLandUseMap23.tfwx TOLandUseMap23.tif TOLandUseMap23.tif.aux.xml TOLandUseMap23.tif.ov Ground control points were saved for all georeferenced images. The files are the following: map13.txt map14.txt map15.txt map16.txt map17.txt map18.txt map19.txt map21.txt map22.txt map23.txt The City of Toronto's Property Boundaries shapefile, "property_bnds_gcc_wgs84.zip" were unzipped and also reprojected to EPSG 26917 (UTM Zone 17) into a new shapefile, "Property_Boundaries_UTM.shp" Mosaicing Images Once georeferenced, all images were then mosaiced into one image file, "LandUseMosaic20211220v01", within the project-generated Geodatabase, "Landuse.gdb" and exported TIF, "LandUseMosaic20211220.tif" Reclassifying Images Because the original images were of low quality and the conversion to TIF made the image colours even more inconsistent, a method was required to reclassify the images so that different land use classes could be identified. Using Deep learning Objects, the images were re-classified into useful consistent colours. Deep Learning Objects and Training The resulting mosaic was then prepared for reclassification using the Label Objects for Deep Learning tool in ArcGIS Pro. A training sample, "LandUseTrainingSamples20211220", was created in the geodatabase for all land use types as follows: Neighbourhoods Insitutional Natural Areas Core Employment Areas Mixed Use Areas Apartment Neighbourhoods Parks Roads Utility Corridors Other Open Spaces General Employment Areas Regeneration Areas Lettering (not a land use type, but an image colour (black), used to label streets). By identifying the letters, it then made the reclassification and vectorization results easier to clean up of unnecessary clutter caused by the labels of streets. Reclassification Once the training samples were created and saved, the raster was then reclassified using the Image Classification Wizard tool in ArcGIS Pro, using the Support...

California State Lands Commission Offshore Oil Leases in the vicinity of Santa Barbara, Ventura, and Orange County.The polygons in this layer show the position of Offshore Oil Leases as documented by former State Lands Senior Boundary Determination Officer, Cris N. Perez and as reviewed and updated by GIS and Boundary staff.Background: This layer represents active offshore oil and gas agreements in California waters, which are what remain of the more than 60 originally issued. These leases were issued prior to the catastrophic 1969 oil spill from Platform A in federal waters off Santa Barbara County, and some predate the formation of the Commission. Between 2010 and 2014, the bulk of the approximately $300 million generated annually for the state's General Fund from oil and gas agreements was from these offshore leases.In 1921, the Legislature created the first tidelands oil and gas leasing program. Between 1921 and 1929, approximately 100 permits and leases were issued and over 850 wells were drilled in Santa Barbara and Ventura Counties. In 1929, the Legislature prohibited any new leases or permits. In 1933, however, the prohibition was partially lifted in response to an alleged theft of tidelands oil in Huntington Beach. It wasn't until 1938, and again in 1955, that the Legislature would allow new offshore oil and gas leasing. Except for limited circumstances, the Legislature has consistently placed limits on the areas that the Commission may offer for lease and in 1994, placed the entirety of California's coast off-limits to new oil and gas leases. Layer Creation Process:In 1997 Cris N. Perez, Senior Boundary Determination Officer of the Southern California Section of the State Lands Division, prepared a report on the Commission’s Offshore Oil Leases to:A. Show the position of Offshore Oil Leases. B. Produce a hard copy of 1927 NAD Coordinates for each lease. C. Discuss any problems evident after plotting the leases.Below are some of the details Cris included in the report:I have plotted the leases that were supplied to me by the Long Beach Office and computed 1927 NAD California Coordinates for each one. Where the Mean High Tide Line (MHTL) was called for and not described in the deed, I have plotted the California State Lands Commission CB Map Coordinates, from the actual field surveys of the Mean High Water Line and referenced them wherever used. Where the MHTL was called for and not described in the deed and no California State Lands Coordinates were available, I digitized the maps entitled, “Map of the Offshore Ownership Boundary of the State of California Drawn pursuant to the Supplemental Decree of the U.S. Supreme Court in the U.S. V. California, 382 U.S. 448 (1966), Scale 1:10000 Sheets 1-161.” The shore line depicted on these maps is the Mean Lower Low Water (MLLW) Line as shown on the Hydrographic or Topographic Sheets for the coastline. If a better fit is needed, a field survey to position this line will need to be done.The coordinates listed in Cris’ report were retrieved through Optical Character Recognition (OCR) and used to produce GIS polygons using Esri ArcGIS software. Coordinates were checked after the OCR process when producing the polygons in ArcMap to ensure accuracy. Original Coordinate systems (NAD 1927 California State Plane Zones 5 and 6) were used initially, with each zone being reprojected to NAD 83 Teale Albers Meters and merged after the review process.While Cris’ expertise and documentation were relied upon to produce this GIS Layer, certain polygons were reviewed further for any potential updates since Cris’ document and for any unusual geometry. Boundary Determination Officers addressed these issues and plotted leases currently listed as active, but not originally in Cris’ report. On December 24, 2014, the SLA boundary offshore of California was fixed (permanently immobilized) by a decree issued by the U.S. Supreme Court United States v. California, 135 S. Ct. 563 (2014). Offshore leases were clipped so as not to exceed the limits of this fixed boundary. Lease Notes:PRC 1482The “lease area” for this lease is based on the Compensatory Royalty Agreement dated 1-21-1955 as found on the CSLC Insider. The document spells out the distinction between “leased lands” and “state lands”. The leased lands are between two private companies and the agreement only makes a claim to the State’s interest as those lands as identified and surveyed per the map Tract 893, Bk 27 Pg 24. The map shows the State’s interest as being confined to the meanders of three sloughs, one of which is severed from the bay (Anaheim) by a Tideland sale. It should be noted that the actual sovereign tide and or submerged lands for this area is all those historic tide and submerged lands minus and valid tide land sales patents. The three parcels identified were also compared to what the Orange County GIS land records system has for their parcels. Shapefiles were downloaded from that site as well as two centerline monuments for 2 roads covered by the Tract 893. It corresponded well, so their GIS linework was held and clipped or extended to make a parcel.MJF Boundary Determination Officer 12/19/16PRC 3455The “lease area” for this lease is based on the Tract No. 2 Agreement, Long Beach Unit, Wilmington Oil Field, CA dated 4/01/1965 and found on the CSLC insider (also recorded March 12, 1965 in Book M 1799, Page 801).Unit Operating Agreement, Long Beach Unit recorded March 12, 1965 in Book M 1799 page 599.“City’s Portion of the Offshore Area” shall mean the undeveloped portion of the Long Beach tidelands as defined in Section 1(f) of Chapter 138, and includes Tract No. 1”“State’s Portion of the Offshore Area” shall mean that portion of the Alamitos Beach Park Lands, as defined in Chapter 138, included within the Unit Area and includes Tract No. 2.”“Alamitos Beach Park Lands” means those tidelands and submerged lands, whether filled or unfilled, described in that certain Judgment After Remittitur in The People of the State of California v. City of Long Beach, Case No. 683824 in the Superior Court of the State of California for the County of Los Angeles, dated May 8, 1962, and entered on May 15, 1962 in Judgment Book 4481, at Page 76, of the Official Records of the above entitled court”*The description for Tract 2 has an EXCEPTING (statement) “therefrom that portion lying Southerly of the Southerly line of the Boundary of Subsidence Area, as shown on Long Beach Harbor Department {LBHD} Drawing No. D-98. This map could not be found in records nor via a PRA request to the LBHD directly. Some maps were located that show the extents of subsidence in this area being approximately 700 feet waterward of the MHTL as determined by SCC 683824. Although the “EXCEPTING” statement appears to exclude most of what would seem like the offshore area (out to 3 nautical miles from the MHTL which is different than the actual CA offshore boundary measured from MLLW) the 1964, ch 138 grant (pg25) seems to reference the lands lying seaward of that MHTL and ”westerly of the easterly boundary of the undeveloped portion of the Long Beach tidelands, the latter of which is the same boundary (NW) of tract 2. This appears to then indicate that the “EXCEPTING” area is not part of the Lands Granted to City of Long Beach and appears to indicate that this portion might be then the “State’s Portion of the Offshore Area” as referenced in the Grant and the Unit Operating Agreement. Section “f” in the CSLC insider document (pg 9) defines the Contract Lands: means Tract No. 2 as described in Exhibit “A” to the Unit Agreement, and as shown on Exhibit “B” to the Unit Agreement, together with all other lands within the State’s Portion of the Offshore Area.Linework has been plotted in accordance with the methods used to produce this layer, with record lines rotated to those as listed in the descriptions. The main boundaries being the MHTL(north/northeast) that appears to be fixed for most of the area (projected to the city boundary on the east/southeast); 3 nautical miles from said MHTL on the south/southwest; and the prolongation of the NWly line of Block 50 of Alamitos Bay Tract.MJF Boundary Determination Officer 12-27-16PRC 4736The “lease area” for this lease is based on the Oil and Gas Lease and Agreement as found on the CSLC insider and recorded August 17, 1973 in BK 10855 PG 432 Official Records, Orange County. The State’s Mineral Interests are confined to Parcels “B-1” and “B-2” and are referred to as “State Mineral Lands” comprising 70.00 Acres. The lessee each has a right to certain uses including but not limited to usage of utility corridors, 110 foot radius parcels surrounding well-sites and roads. The State also has access to those same roads per this agreement/lease. Those uses are allowed in what are termed “State Lands”-Parcel E and “Leased Lands” which are defined as the “South Bolsa Lease Area”-Parcel C (2 parcels) and “North Bolsa Lease Area”-Parcel D. The “State Lands”-Parcel E are actually 3 parcels, 2 of which are within road right-of-ways. MJF Boundary Determination Officer 12-28-16

Parcel data from Fulton County for the most recent tax year. This layer can be used in software programs and apps so only the data layer needs to be updated instead of each individual program or app. Fulton Update Date attribute is the Last Updated Date from the Fulton County GIS Open Data site. From Fulton:This dataset represents the boundary of each parcel of land in Fulton County recorded for the purpose of aiding in the appraisal of real property and the determination of property tax. A parcel dataset is created each year in association with that year's tax digest. The parcel dataset for any given year is not considered final until the completion of the digest, which generally occurs around mid-year. Until the completion of the digest, the parcel dataset is considered to be a work in progress. Any necessary corrections and omissions may continue to be made even after the completion of the digest. The parcel dataset in its published form incorporates information from the CAMA (computer-aided mass appraisal) database. The CAMA information included with the published dataset is selected based on its value to the typical consumer of the data and includes the parcel identification number, the property address, property owner, owner's mailing address, tax district, assessed and appraised value for land and improvements, the number of livable units, acreage, property class and land use class.

This layer contains polygons representing parcel ownership for Allamakee County, Iowa. It represents map features similar to those previously shown on hand drawn tax maps. The geometry was created by the Schneider Corporation using coordinate geometry (COGO) software in an ArcGIS environment. Individual parcel features were digitized from official recorded documents when available. Special care was taken to correlate map features with survey controlled coordinate values of the Public Land Survey System (PLSS).

To download:1. Click the Download button above.2. A side panel will appear showing download options. Under Shapefile, click the Download button.3. When the download completes, browse to the location of the downloaded .zip, copy it to the location where you manage your redistricting files, then right-click to extract the contents. You will then be able to use the file in GIS software.If, rather than downloading the data, you wish the reference online versions of these datasets directly to ensure you are always using the most up-to-date data, please contact the County of San Bernardino Innovation and Technology Departments at 909-884-4884 or by emailing OpenData@isd.sbcounty.gov for informations and instructions for doing so.Parcel polygons for the County of San Bernardino with assessment and zoning attributes. This parcel data is maintained by the County of San Bernardino Land Use Services Department, and the Surveyor and Assessor offices.

Summary: This dataset contains an inventory of City of Los Angeles Sidewalks and related features (Access Ramps, Curbs, Driveways, and Parkways).Background: This inventory was performed throughout 2017 using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines. The dataset has not been updated since its creation.Description: The following provides more detail about the feature classes in this dataset. All features were digitized (“traced”) as observed in the orthophotography (digital aerial photos) and assigned the Parcel Identification Number (PIN) of their corresponding property:Sidewalk (polygon) – represents paved pedestrian walkways. Typical widths are between 3‐6 feet in residential areas and larger and more variable in commercial and high‐density traffic areas.Alley-Sidewalk (polygon) – represents the prevailing walkway or path of travel at the entrance/exit of an alley. Digitized as Sidewalk features but categorized as Alley Sidewalk and assigned a generic PIN value, ALLEY SIDEWALK.Corner Polygon (polygon) - feature created where sidewalks from two streets meet but do not intersect (i.e. at corner lots). There’s no standard shape/type and configurations vary widely. These are part of the Sidewalk feature class.In commercial and high‐density residential areas where there is only continuous sidewalk (no parkway strip), the sidewalk also functions as a Driveway.Driveway (polygon) – represents area that provides vehicular access to a property. Features are not split by extended parcel lot lines except when two adjacent properties are served by the same driveway approach (e.g. a common driveway), in which case they are and assigned a corresponding PIN.Parkway (polygon) – represents the strip of land behind the curb and in front of the sidewalk. Generally, they are landscaped with ground cover but they may also be filled in with decorative stone, pavers, decomposed granite, or concrete. They are created by offsetting lines, the Back of Curb (BOC) line and the Face of Walk (FOW). The distance between the BOC and FOW is measured off the aerial image and rounded to the nearest 0.5 foot, typically 6 – 10 feet.Curb (polygon) – represents the concrete edging built along the street to form part of the gutter. Features are always 6” wide strips and are digitized using the front of curb and back of curb digitized lines. They are the leading improvement polygon and are created for all corner, parkway, driveway and, sidewalk (if no parkway strip is present) features.Curb Ramp, aka Access Ramp (point) – represents the geographic center (centroid) of Corner Polygon features in the Sidewalk feature class. They have either a “Yes” or “No” attribute that indicates the presence or absence of a wheelchair access ramp, respectively.Fields: All features include the following fields...FeatureID – a unique feature identifier that is populated using the feature class’ OBJECTID fieldAssetID – a unique feature identifier populated by Los Angeles City staff for internal usePIND – a unique Parcel Identification Number (PIN) for all parcels within the City of L.A. All Sidewalk related features will be split, non-overlapping, and have one associated Parcel Identification Number (PIN). CreateDate – indicates date feature was createdModifiedDate – indicates date feature was revised/editedCalc_Width (excluding Access Ramps) – a generalized width of the feature calculated using spatial and mathematical algorithms on the feature. In almost all cases where features have variable widths, the minimum width is used. Widths are rounded to the nearest whole number. In cases where there is no value for the width, the applied algorithms were unable to calculate a reliable value.Calc_Length (excluding Access Ramps) – a generalized length of the feature calculated using spatial and mathematical algorithms on the feature. Lengths are rounded to the nearest whole number. In cases where there is no value for the length, the applied algorithms were unable to calculate a reliable value.Methodology: This dataset was digitized using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines.The general work flow is as follows:Create line work based on digital orthophotography, working from the face‐of‐curb (FOC) inward to the property right-of-way (ROW)Build sidewalk, parkway, driveway, and curb polygons from the digitized line workPopulate all polygons with the adjacent property PIN and classify all featuresCreate Curb Ramp pointsWarnings: This dataset has been provided to allow easy access and a visual display of Sidewalk and related features (Parkways, Driveway, Curb Ramps and Curbs). Every reasonable effort has been made to assure the accuracy of the data provided; nevertheless, some information may not be accurate. The City of Los Angeles assumes no responsibility arising from use of this information. THE MAPS AND ASSOCIATED DATA ARE PROVIDED WITHOUT WARRANTY OF ANY KIND, either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Other things to keep in mind about this dataset are listed below:Obscured Features – The existence of dense tree canopy or dark shadows in the aerial imagery tend to obscure or make it difficult to discern the extent of certain features, such as Driveways. In these cases, they may have been inferred from the path in the corresponding parcel. If a feature and approach was completely obscured, it was not digitized. In certain instances the coloring of the sidewalk and adjacent pavement rendered it impossible to identify the curb line or that a sidewalk existed. Therefore a sidewalk may or may not be shown where one actually may or may not exist.Context: The following links provide information on the policy context surrounding the creation of this dataset. It includes links to City of L.A. websites:Willits v. City of Los Angeles Class Action Lawsuit Settlementhttps://www.lamayor.org/willits-v-city-la-sidewalk-settlement-announcedSafe Sidewalks LA – program implemented to repair broken sidewalks in the City of L.A., partly in response to the above class action lawsuit settlementhttps://sidewalks.lacity.org/Data Source: Bureau of EngineeringNotes: Please be aware that this dataset is not actively being maintainedLast Updated: 5/20/20215/20/2021 - Added Calc_Width and Calc_Length fieldsRefresh Rate: One-time deliverable. Dataset not actively being maintained.

This fee feature class represents current wastewater information in the City of Los Angeles. This fee indicates that a property owner has paid the fee for a Special House Connection Sewer or Bonded Sewer House Connection Sewer permit, and the property has not been assessed for a public sewer. Fee information is inputted into the Wastewater Database by the District Office Staff. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most rigorous geographic information of the sanitary sewer system using a geometric network model, to ensure that its sewers reflect current ground conditions. The sanitary sewer system, pump plants, wyes, maintenance holes, and other structures represent the sewer infrastructure in the City of Los Angeles. Wye and sewer information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary).Wastewater Fee points layer was created in geographical information systems (GIS) software to display points representing bonded or special fee parcels. The fee points layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a points feature class and attribute data for the features. The points are entered manually based on wastewater sewer maps and BOE standard plans, and information about the points is entered into attributes. The fee points data layer indicate that property owner have paid the fee for a Special House Connection Sewer or Bonded Sewer House Connection Sewer permit, and the property has not been assessed for a public sewer. The wastewater fee points are inherited from a sewer spatial database originally created by the City's Wastewater program. The database was known as SIMMS, Sewer Inventory and Maintenance Management System. Fee information should only be added to the Wastewater Fee layer if documentation exists, such as a wastewater map approved by the City Engineer. Sewers plans and specifications proposed under private development are reviewed and approved by Bureau of Engineering. The Department of Public Works, Bureau of Engineering's, Brown Book (current as of 2010) outlines standard specifications for public works construction. For more information on sewer materials and structures, look at the Bureau of Engineering Manual, Part F, Sewer Design section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf. For more information on maintenance holes, a copy can be viewed at http://boemaps.eng.ci.la.ca.us/reports/pdf/s140-0_std_pl.pdf.List of Fields:BOE_PROCESS_DATEFEE_NO: This value is the number of the document filed to establish the fees owed.AMOUNT: This value is the dollar amount of the fee owed.STATUS: This value shows the fees that were transferred to other SFC sites in the City of Los Angeles. The value indicates whether that record was a Transfer donor or a transfer recipient. Values: • TD - Transfer donor. • TR - Transfer recipient.VERIFIED: This value of is Y or null.LAT: The value is the latitude coordinate of the point.SHAPE: Feature geometry.LAST_MODF_DT: Last modification date of the point feature.LON: The value is the longitude coordinate of the point.SEWER_MAPREF_NO: This value is the reference number.PIN: The value is a combination of MAPSHEET and ID fields in Landbase Parcels data, creating a unique value for each parcel. There are spaces between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables. This attribute is automatically generated by the Wastewater Application during background processes, running the identity process.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • V - Valley Engineering District. • H - Harbor Engineering District. • W - West LA Engineering District. • C - Central Engineering District.OBJECTID: Internal feature number.CRTN_DTJOB_ADDRESS: This value is the the address for the parcel.USER_ID: The name of the user carrying out the edits of the fee points.TYPE: This value is the text as indicated on the map containing Wastewater Wye data. Values: • H - Unknown. • UNK - Unknown. • SSC - Sewer service charge. • LP - Letters of Participation. • SFC - Sewer facilities charge. • SF - Special fees. • OF - Outlet facilities charge. • C - Unknown. • F - Fee. • D - Unknown. • BL - Bonded lateral. • AF - No fees. • A - Unknown. • B - Bonded fee due. • S - Unknown.REMARKS: This attribute contains additional comments regarding fee points.

The polygons in this layer show the position of Offshore Oil Leases as documented by former State Lands Senior Boundary Determination Officer, Cris N. Perez and as reviewed and updated by GIS and Boundary staff.Background:This layer represents active offshore oil and gas agreements in California waters, which are what remain of the more than 60 originally issued. These leases were issued prior to the catastrophic 1969 oil spill from Platform A in federal waters off Santa Barbara County, and some predate the formation of the Commission. Between 2010 and 2014, the bulk of the approximately $300 million generated annually for the state's General Fund from oil and gas agreements was from these offshore leases.In 1921, the Legislature created the first tidelands oil and gas leasing program. Between 1921 and 1929, approximately 100 permits and leases were issued and over 850 wells were drilled in Santa Barbara and Ventura Counties. In 1929, the Legislature prohibited any new leases or permits. In 1933, however, the prohibition was partially lifted in response to an alleged theft of tidelands oil in Huntington Beach. It wasn't until 1938, and again in 1955, that the Legislature would allow new offshore oil and gas leasing. Except for limited circumstances, the Legislature has consistently placed limits on the areas that the Commission may offer for lease and in 1994, placed the entirety of California's coast off-limits to new oil and gas leases.Layer Creation Process:In 1997 Cris N. Perez, Senior Boundary Determination Officer of the Southern California Section of the State Lands Division, prepared a report on the Commission’s Offshore Oil Leases to:A. Show the position of Offshore Oil Leases.B. Produce a hard copy of 1927 NAD Coordinates for each lease.C. Discuss any problems evident after plotting the leases.Below are some of the details Cris included in the report:I have plotted the leases that were supplied to me by the Long Beach Office and computed 1927 NAD California Coordinates for each one. Where the Mean High Tide Line (MHTL) was called for and not described in the deed, I have plotted the California State Lands Commission CB Map Coordinates, from the actual field surveys of the Mean High Water Line and referenced them wherever used.Where the MHTL was called for and not described in the deed and no California State Lands Coordinates were available, I digitized the maps entitled, “Map of the Offshore Ownership Boundary of the State of California Drawn pursuant to the Supplemental Decree of the U.S. Supreme Court in the U.S. V. California, 382 U.S. 448 (1966), Scale 1:10000 Sheets 1-161.” The shore line depicted on these maps is the Mean Lower Low Water (MLLW) Line as shown on the Hydrographic or Topographic Sheets for the coastline. If a better fit is needed, a field survey to position this line will need to be done.The coordinates listed in Cris’ report were retrieved through Optical Character Recognition (OCR) and used to produce GIS polygons using Esri ArcGIS software. Coordinates were checked after the OCR process when producing the polygons in ArcMap to ensure accuracy. Original Coordinate systems (NAD 1927 California State Plane Zones 5 and 6) were used initially, with each zone being reprojected to NAD 83 Teale Albers Meters and merged after the review process.While Cris’ expertise and documentation were relied upon to produce this GIS Layer, certain polygons were reviewed further for any potential updates since Cris’ document and for any unusual geometry. Boundary Determination Officers addressed these issues and plotted leases currently listed as active, but not originally in Cris’ report.On December 24, 2014, the SLA boundary offshore of California was fixed (permanently immobilized) by a decree issued by the U.S. Supreme Court United States v. California, 135 S. Ct. 563 (2014). Offshore leases were clipped so as not to exceed the limits of this fixed boundary.Lease Notes:PRC 1482The “lease area” for this lease is based on the Compensatory Royalty Agreement dated 1-21-1955 as found on the CSLC Insider. The document spells out the distinction between “leased lands” and “state lands”. The leased lands are between two private companies and the agreement only makes a claim to the State’s interest as those lands as identified and surveyed per the map Tract 893, Bk 27 Pg 24. The map shows the State’s interest as being confined to the meanders of three sloughs, one of which is severed from the bay (Anaheim) by a Tideland sale. It should be noted that the actual sovereign tide and or submerged lands for this area is all those historic tide and submerged lands minus and valid tide land sales patents. The three parcels identified were also compared to what the Orange County GIS land records system has for their parcels. Shapefiles were downloaded from that site as well as two centerline monuments for 2 roads covered by the Tract 893. It corresponded well, so their GIS linework was held and clipped or extended to make a parcel.MJF Boundary Determination Officer 12/19/16PRC 3455The “lease area” for this lease is based on the Tract No. 2 Agreement, Long Beach Unit, Wilmington Oil Field, CA dated 4/01/1965 and found on the CSLC insider (also recorded March 12, 1965 in Book M 1799, Page 801).Unit Operating Agreement, Long Beach Unit recorded March 12, 1965 in Book M 1799 page 599.“City’s Portion of the Offshore Area” shall mean the undeveloped portion of the Long Beach tidelands as defined in Section 1(f) of Chapter 138, and includes Tract No. 1”“State’s Portion of the Offshore Area” shall mean that portion of the Alamitos Beach Park Lands, as defined in Chapter 138, included within the Unit Area and includes Tract No. 2.”“Alamitos Beach Park Lands” means those tidelands and submerged lands, whether filled or unfilled, described in that certain Judgment After Remittitur in The People of the State of California v. City of Long Beach, Case No. 683824 in the Superior Court of the State of California for the County of Los Angeles, dated May 8, 1962, and entered on May 15, 1962 in Judgment Book 4481, at Page 76, of the Official Records of the above entitled court”*The description for Tract 2 has an EXCEPTING (statement) “therefrom that portion lying Southerly of the Southerly line of the Boundary of Subsidence Area, as shown on Long Beach Harbor Department {LBHD} Drawing No. D-98. This map could not be found in records nor via a PRA request to the LBHD directly. Some maps were located that show the extents of subsidence in this area being approximately 700 feet waterward of the MHTL as determined by SCC 683824. Although the “EXCEPTING” statement appears to exclude most of what would seem like the offshore area (out to 3 nautical miles from the MHTL which is different than the actual CA offshore boundary measured from MLLW) the 1964, ch 138 grant (pg25) seems to reference the lands lying seaward of that MHTL and ”westerly of the easterly boundary of the undeveloped portion of the Long Beach tidelands, the latter of which is the same boundary (NW) of tract 2. This appears to then indicate that the “EXCEPTING” area is not part of the Lands Granted to City of Long Beach and appears to indicate that this portion might be then the “State’s Portion of the Offshore Area” as referenced in the Grant and the Unit Operating Agreement. Section “f” in the CSLC insider document (pg 9) defines the Contract Lands: means Tract No. 2 as described in Exhibit “A” to the Unit Agreement, and as shown on Exhibit “B” to the Unit Agreement, together with all other lands within the State’s Portion of the Offshore Area.Linework has been plotted in accordance with the methods used to produce this layer, with record lines rotated to those as listed in the descriptions. The main boundaries being the MHTL(north/northeast) that appears to be fixed for most of the area (projected to the city boundary on the east/southeast); 3 nautical miles from said MHTL on the south/southwest; and the prolongation of the NWly line of Block 50 of Alamitos Bay Tract.MJF Boundary Determination Officer 12-27-16PRC 4736The “lease area” for this lease is based on the Oil and Gas Lease and Agreement as found on the CSLC insider and recorded August 17, 1973 in BK 10855 PG 432 Official Records, Orange County.The State’s Mineral Interests are confined to Parcels “B-1” and “B-2” and are referred to as “State Mineral Lands” comprising 70.00 Acres.The lessee each has a right to certain uses including but not limited to usage of utility corridors, 110 foot radius parcels surrounding well-sites and roads. The State also has access to those same roads per this agreement/lease. Those uses are allowed in what are termed “State Lands”-Parcel E and “Leased Lands” which are defined as the “South Bolsa Lease Area”-Parcel C (2 parcels) and “North Bolsa Lease Area”-Parcel D. The “State Lands”-Parcel E are actually 3 parcels, 2 of which are within road right-of-ways.MJF Boundary Determination Officer 12-28-16

Summary: This dataset contains an inventory of City of Los Angeles Sidewalks and related features (Access Ramps, Curbs, Driveways, and Parkways).Background: This inventory was performed throughout 2017 using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines. The dataset has not been updated since its creation.Description: The following provides more detail about the feature classes in this dataset. All features were digitized (“traced”) as observed in the orthophotography (digital aerial photos) and assigned the Parcel Identification Number (PIN) of their corresponding property:Sidewalk (polygon) – represents paved pedestrian walkways. Typical widths are between 3‐6 feet in residential areas and larger and more variable in commercial and high‐density traffic areas.Alley-Sidewalk (polygon) – represents the prevailing walkway or path of travel at the entrance/exit of an alley. Digitized as Sidewalk features but categorized as Alley Sidewalk and assigned a generic PIN value, ALLEY SIDEWALK.Corner Polygon (polygon) - feature created where sidewalks from two streets meet but do not intersect (i.e. at corner lots). There’s no standard shape/type and configurations vary widely. These are part of the Sidewalk feature class.In commercial and high‐density residential areas where there is only continuous sidewalk (no parkway strip), the sidewalk also functions as a Driveway.Driveway (polygon) – represents area that provides vehicular access to a property. Features are not split by extended parcel lot lines except when two adjacent properties are served by the same driveway approach (e.g. a common driveway), in which case they are and assigned a corresponding PIN.Parkway (polygon) – represents the strip of land behind the curb and in front of the sidewalk. Generally, they are landscaped with ground cover but they may also be filled in with decorative stone, pavers, decomposed granite, or concrete. They are created by offsetting lines, the Back of Curb (BOC) line and the Face of Walk (FOW). The distance between the BOC and FOW is measured off the aerial image and rounded to the nearest 0.5 foot, typically 6 – 10 feet.Curb (polygon) – represents the concrete edging built along the street to form part of the gutter. Features are always 6” wide strips and are digitized using the front of curb and back of curb digitized lines. They are the leading improvement polygon and are created for all corner, parkway, driveway and, sidewalk (if no parkway strip is present) features.Curb Ramp, aka Access Ramp (point) – represents the geographic center (centroid) of Corner Polygon features in the Sidewalk feature class. They have either a “Yes” or “No” attribute that indicates the presence or absence of a wheelchair access ramp, respectively.Fields: All features include the following fields...FeatureID – a unique feature identifier that is populated using the feature class’ OBJECTID fieldAssetID – a unique feature identifier populated by Los Angeles City staff for internal usePIND – a unique Parcel Identification Number (PIN) for all parcels within the City of L.A. All Sidewalk related features will be split, non-overlapping, and have one associated Parcel Identification Number (PIN). CreateDate – indicates date feature was createdModifiedDate – indicates date feature was revised/editedCalc_Width (excluding Access Ramps) – a generalized width of the feature calculated using spatial and mathematical algorithms on the feature. In almost all cases where features have variable widths, the minimum width is used. Widths are rounded to the nearest whole number. In cases where there is no value for the width, the applied algorithms were unable to calculate a reliable value.Calc_Length (excluding Access Ramps) – a generalized length of the feature calculated using spatial and mathematical algorithms on the feature. Lengths are rounded to the nearest whole number. In cases where there is no value for the length, the applied algorithms were unable to calculate a reliable value.Methodology: This dataset was digitized using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines.The general work flow is as follows:Create line work based on digital orthophotography, working from the face‐of‐curb (FOC) inward to the property right-of-way (ROW)Build sidewalk, parkway, driveway, and curb polygons from the digitized line workPopulate all polygons with the adjacent property PIN and classify all featuresCreate Curb Ramp pointsWarnings: This dataset has been provided to allow easy access and a visual display of Sidewalk and related features (Parkways, Driveway, Curb Ramps and Curbs). Every reasonable effort has been made to assure the accuracy of the data provided; nevertheless, some information may not be accurate. The City of Los Angeles assumes no responsibility arising from use of this information. THE MAPS AND ASSOCIATED DATA ARE PROVIDED WITHOUT WARRANTY OF ANY KIND, either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Other things to keep in mind about this dataset are listed below:Obscured Features – The existence of dense tree canopy or dark shadows in the aerial imagery tend to obscure or make it difficult to discern the extent of certain features, such as Driveways. In these cases, they may have been inferred from the path in the corresponding parcel. If a feature and approach was completely obscured, it was not digitized. In certain instances the coloring of the sidewalk and adjacent pavement rendered it impossible to identify the curb line or that a sidewalk existed. Therefore a sidewalk may or may not be shown where one actually may or may not exist.Context: The following links provide information on the policy context surrounding the creation of this dataset. It includes links to City of L.A. websites:Willits v. City of Los Angeles Class Action Lawsuit Settlementhttps://www.lamayor.org/willits-v-city-la-sidewalk-settlement-announcedSafe Sidewalks LA – program implemented to repair broken sidewalks in the City of L.A., partly in response to the above class action lawsuit settlementhttps://sidewalks.lacity.org/Data Source: Bureau of EngineeringNotes: Please be aware that this dataset is not actively being maintainedLast Updated: 5/20/20215/20/2021 - Added Calc_Width and Calc_Length fieldsRefresh Rate: One-time deliverable. Dataset not actively being maintained.

Parcels affected by the adoption of the 2015 International Wildland Urban-Interface Code (WUIC), which was adopted by Austin City Council April9, 2020, and implementation beginning January 1st, 2021. Parcels that are within 1.5 miles of a wildland area greater than 750 acres and parcels within 150 feet of a wildland area greater than 40 acres are wildland_urban_interface_code parcels. Parcels designated as "preserves" have been removed and are not subject to the WUI code.Dataset was created in 2020 by Austin Fire Department Wildfire Division. It was derived from the most recent Travis County Appraisal District (TCAD) Parcels, and queried based upon their planar distance to wildland areas. Wildlands are defined as undeveloped continuous areas,. The wildlands feature class is maintained by the Austin Fire Department and is derived from the City of Austin Planimetric dataset, also known as impervious cover data, and are updated every two years. ArcGIS Pro version 2 software was used to create this dataset. The data is meant to be ingested by a GIS system. Changes to the City of Austin & LTD jurisdiction warrant an update to this dataset. The data is scheduled to be updated every two years.Included in the attributes are parcel condition variables that determine the parcel's "fire hazard severity' class. These include the composite score of three variables: slope score, fuel score, and WUI class (proximity). Slope score was determined by the average degree slope of the area within each parcel and classified as less than 10%, 10% to 25%, or greater then 25%. Fuel score was determined by the average fuel class area within each parcels as defined by the Austin Travis County Community Wildfire Protection Plan (CWPP) and classified as light, medium, or heavy fuels. Proximity class was defined by the proximity of each parcel to wildlands, either as within 1.5 miles of wildlands greater than 750 acres, or within 150 feet of wildlands greater than 40 acres.Description of data fieldsGLOBALID_1 = Used for Global IdentificationOBJECTID = Object IdentificationSLOPE_DEGREE = The average slope of each parcel in degreesFIRE_HAZARD_SEVERITY = The "fire hazard severity" class of each parcelPROXIMITY_CLASS = The proximity class of each parcelSLOPE_CLASS = The slope classification of each parcelFUEL_CLASS = The fuel class of each parcelCREATED_BY = Creators nameCREATED_DATE = Date createdMODIFIED_BY = Modifiers nameMODIFIED_DATE = Date modifiedUNIQUE_ID = Unique Identification number (mirror object id)Shape_Area = Shape areaShape_Length = Shape lengthIteration ID: Parcels_AustinLTD4 2020Contact: Steven Casebeer at Steven.casebeer@austintexas.gov | Austin Fire Department Wildfire Division

Santa Rosa Plain Programmatic Biological Opinion Parcels - Data "CDR_PARCELS" obtained from County of Sonoma GIS Central.

A distinction should be made with respect to this layer which includes GIS parcels and the official Assessor Parcels residing in the Assessor Map books at the Sonoma County Assessor Office. For official parcel records please contact the Sonoma County Assessor (707)565-1888. These parcels should NOT be represented as survey data, and the official record of survey takes precedence where there are discrepancies. It is the end user's responsibility to check the accuracy of the GIS data by comparing it with the published data from the Sonoma County Assessor / Recorder office. The Sonoma County parcel base was originally compiled from Assessor Parcel maps at a scale of 1:6000. The individual Assessor Parcel maps were enlarged or reduced in size using an electrostatic process to produce the maps at the 1:6000 scale, the maps were then fit together by hand and transcribed on to mylar. The mylar base consisted of 1:6000 USGS base map information typically found on the 7.5 USGS quad series. This base information consisted of Topography, Roads, Section, and Rancho lines to name some. Using this information, the Assessor Parcel maps were fit to the individual 1:6000 scale maps. Each 1:6000 scale map represents 1/6 (quad sixths) of a 7.5 minute USGS Quadrangle series map. In 1998 the State Board of Equalization provided the impetus to produce the Russian River Project for all of Planning Area 4. One aspect required for this project was a digital parcel base for Planning Area 4. This involved the conversion of the 1:6000 mylars with the transcribed parcels on them into a digital version of the parcels. The mylars where scanned and geo-referenced using the base map information originally included with the 1:6000 mylar base. The maps were geo-referenced to a digital version of the USGS 7.5 minute Quadrangle series available from the Teale Data Center. The original projection was California State Plane Zone 2 NAD 1927. County Staff then used AutoCAD software to heads up digitize each 1:6000 scale map in Planning Area 4. A custom application was created and used by GIS staff involving the use of Avenue and ArcView 3.2 to create a point for all the parcels in Planning Area 4, attributes included Assessor Parcel Number. The DWGs were then converted to shapefiles and then converted to ArcINFO coverages, the parcel tags were converted from shapefiles to ArcINFO coverages and the point coverage was merged with the polygon coverage with the IDENTITY command. An exhaustive process was involved to eliminate errors once the DWGs were converted to ArcINFO coverages so polygons could be generated. The coverages were then aggregated using the MAPJOIN command, the original boundary of the 1:6000 scale maps was removed using the REGIONDISSOLVE command to merge adjacent polygons with the same AP number. In 1999 the remainder of the planning areas were converted to digital form following the Russian River Project and the seamless base was completed in 2001. The seamless parcel base was maintained in ArcINFO until the release of ArcGIS 8.3, which included topology tools necessary for its maintenance. The seamless base prior to late 2002 was suitable for 1:100000 scale while the control points (the corners for the 1:6000 scale maps) were suitable for 1:24000 scale. Prior to rectification to the Merrick 2000 orthophotography, the parcel data were derived from 1:6000 scale maps (enlarged from USGS 7.5 minute quadrangle 1:24,000 series) and digitized in California State Plane, Zone II, NAD 27 coordinates (survey feet), but were converted to California State Plane, Zone II, NAD 83 coordinates (survey feet) as part of a rectification process now underway. The parcels used to use the USGS 7.5 minute quadrangle (1:24,000) series for coordinate control, but no guarantee is made for their spatial accuracy. The data were re-projected to NAD 83 coordinates to overlay the orthophotography, but the parcel boundaries will not correspond precisely with features in the images. The parcels were rectified to orthophotography flown in April - May 2000 using geo-referencing tools available in ArcGIS 8.3. This project was completed in July 2005. In general, the parcels meet National Accuracy Standards for 1:24,000 scale maps, and likely exceed that accuracy in urban areas. A complete description of the process is detailed in a series of documents located on a local file server: S:\COMMON\GIS\Documentation\Parcel Rectification & Update Process\Procedure - *. doc. A brief summary is as follows. Individual Assessor Parcel pages or CAD drawings are rectified to the orthophoto. COGO & survey data are used when available and in sufficient quantities to enable the bulk of an Assessor Parcel page to be digitized using said information. Polygons are generated directly from the COGO data, CAD dwg are exported to feature classes, where polygons are then generated, rectified Assessor Parcel pages are vectorized using ArcScan and subsequently polygons are generated. A spatial join is used to assign attributes to the newly generated polygons. Polygons are then assigned an accuracy rank based on source, quality of the fit to the orthophoto, and RMS error encountered during rectification (only the scanned Assessor maps will have and RMS error associated with them). See the fields RANK and DESCRIPTION for information on fit assessment. Areas that have been successfully updated as such have a reasonable expectation of accuracy of +/- 10 and possibly better, areas that have not been updated or are flagged in SCAMP under the GIS group Projects as Needs Survey Data, the original accuracy assessment of 1:100000 applies.

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

Assessors parcel data for Town/City of Oak Bluffs. Developed from existing digital data that is maintained annually from deeds and plans using GIS software tools. Geometry and attribute data updated on 4/2015