Vector polygon map data of property parcels from Oregon containing 97,943 features.

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

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

This polygon feature class is a representation of Public Land Survey System (PLSS) quarter sections. The data are a subset of the Wisconsin DNR's 'Landnet' database, automated from 1:24,000-scale sources.*DNR staff have added an alpha field for the range direction field in this layer called DIR_ALPHA which uses W and E instead of numerical direction codes.

Shapefile of zoning section map index, grid to determine which zoning section map relates to specific areas of NYC. A sectional index grid to determine which Zoning Map refers to specific areas of New York City. Zoning maps show the boundaries of zoning districts throughout the city. The maps are regularly updated after the City Planning Commission and the City Council have approved proposed zoning changes. The set of 126 maps, which are part of the Zoning Resolution, are displayed in 35 sections. Each section is identified by a number from 1 to 35. Each map covers an area of approximately 8,000 feet (north/south) by 12,500 feet (east/west).

Section data including township and range info for the State of Kansas. This data is distributed by the Kansas Geological Survey. This data has been cleaned up using county sources in March 2024.

The Digital Geologic-GIS Map of the Seven Pines Quadrangle, Virginia 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 (svpn_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 (svpn_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 (svpn_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 (rich_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (rich_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 (svpn_geology_metadata_faq.pdf). Please read the rich_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: Virginia Division of Geology and Mineral Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (svpn_geology_metadata.txt or svpn_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).

Displays the smallest unit in the Public Land Survey System; Township/Ranges are subdivided into 36 Sections; each Section is approximately one square mile. These polygons are maintained in the Parcel Fabric. This layer has been adjusted to Section corner data from the GIS parcel Section Auto CAD drawings. It also includes the half Township South of 12S14E Sections 31-34, designated as 12F14E (field TR). TOWNSHIP and RANGE field values are four characters where the last two characters indicate the direction where 01 is North, 02 is East, 03 is South and 04 is West.https://gis.pima.gov/data/contents/metadet.cfm?name=trsPurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 – OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsThe Canoa Land Grant area is not part of the Public Land Survey System. The trs layer includes sections in the Canoa Land Grant area as if it had been included in the survey.2021 - This layer contains a Stated Area field in square miles. This is a GIS calculated estimate and should not be used in place of official stated areas from the original documents.Contactgisdata@pima.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Allows for querying a quarter section and downloading a black and white quarter-section parcel map in PDF format.

description: Special Use Districts City and County of San Francisco Planning Department. The Special Use Districts are a component of the Zoning Map. The Zoning - Map comprises: - Zoning Districts - Height and Bulk Districts - Special Use Districts - Preservation Districts - Coastal Zone Area - Sprcial Sign Districts The official Zoning Map can be found in the San Francisco Planning Code: http://library.municode.com/index.aspx?clientId=14145&stateId=5&stateName=California (click on the links under ZONING MAPS on the left navigation column). Sec 235 of the Planning Code states: "In addition to the use districts that are established by Section 201 of this Code, there shall also be in the City such special use districts as are established in this Section and Sections 236 through 249.5, in order to carry out further the purposes of this Code. The designations, locations and boundaries of these special use districts shall be as provided in Sections 236 through 249.5, and as shown on the Zoning Map referred to in Section 105 of this Code, subject to the provisions of Section 105. The original of the numbered sectional maps of the Zoning Map for Special Use Districts referred to in Sections 236 through 249.5 is on file with the Clerk of the Board of Supervisors under File No. 191-67-2. and No. 273.80. In any special use district the provisions of the applicable use district established by Section 201 shall prevail, except as specifically provided in Sections 236 through 249.5."; abstract: Special Use Districts City and County of San Francisco Planning Department. The Special Use Districts are a component of the Zoning Map. The Zoning - Map comprises: - Zoning Districts - Height and Bulk Districts - Special Use Districts - Preservation Districts - Coastal Zone Area - Sprcial Sign Districts The official Zoning Map can be found in the San Francisco Planning Code: http://library.municode.com/index.aspx?clientId=14145&stateId=5&stateName=California (click on the links under ZONING MAPS on the left navigation column). Sec 235 of the Planning Code states: "In addition to the use districts that are established by Section 201 of this Code, there shall also be in the City such special use districts as are established in this Section and Sections 236 through 249.5, in order to carry out further the purposes of this Code. The designations, locations and boundaries of these special use districts shall be as provided in Sections 236 through 249.5, and as shown on the Zoning Map referred to in Section 105 of this Code, subject to the provisions of Section 105. The original of the numbered sectional maps of the Zoning Map for Special Use Districts referred to in Sections 236 through 249.5 is on file with the Clerk of the Board of Supervisors under File No. 191-67-2. and No. 273.80. In any special use district the provisions of the applicable use district established by Section 201 shall prevail, except as specifically provided in Sections 236 through 249.5."

The City Engineering Quarter Section Map Index contains information regarding City Engineering quarter section numbers and Public Land Survey System (PLSS) information for each quarter section in the City and County of Denver, as well as a few of the surrounding section quarters. For each quarter section of the PLSS in the City and County of Denver, the City Engineering (later the City Surveyor's office) developed and maintained a linen sheet depicting subdivision, lot, ordinance, and easement data in that quarter section. Using Broadway and Colfax Avenue as the dividing lines, the CCD is broken into four quadrants, and the quarter sections for each quadrant are numbered beginning with 1. NOTE: Maintenance of these quarter section sheets was discontinued after 1996 due to the development of the CCD GIS.

The original historic plat maps for Wisconsin were created between 1832 and 1866. In most cases, the UW Digital Collections Center does not record a specific creation date for the original maps. However, the collection also contains maps which correct previous editions. These more modern maps typically have a specific date or year defined. To view the survey notes associated with this plat map, please visit http://digicoll.library.wisc.edu/cgi-bin/SurveyNotes/SurveyNotes-idx?type=PLSS&town=T026N&range=R024E.

Terms of UseData Limitations and DisclaimerThe user’s use of and/or reliance on the information contained in the Document shall be at the user’s own risk and expense. MassDEP disclaims any responsibility for any loss or harm that may result to the user of this data or to any other person due to the user’s use of the Document.This is an ongoing data development project. Attempts have been made to contact all PWS systems, but not all have responded with information on their service area. MassDEP will continue to collect and verify this information. Some PWS service areas included in this datalayer have not been verified by the PWS or the municipality involved, but since many of those areas are based on information published online by the municipality, the PWS, or in a publicly available report, they are included in the estimated PWS service area datalayer.Please note: All PWS service area delineations are estimates for broad planning purposes and should only be used as a guide. The data is not appropriate for site-specific or parcel-specific analysis. Not all properties within a PWS service area are necessarily served by the system, and some properties outside the mapped service areas could be served by the PWS – please contact the relevant PWS. Not all service areas have been confirmed by the systems.Please use the following citation to reference these data:MassDEP, Water Utility Resilience Program. 2025. Community and Non-Transient Non-Community Public Water System Service Area (PubV2025_3).IMPORTANT NOTICE: This MassDEP Estimated Water Service datalayer may not be complete, may contain errors, omissions, and other inaccuracies and the data are subject to change. This version is published through MassGIS. We want to learn about the data uses. If you use this dataset, please notify staff in the Water Utility Resilience Program (WURP@mass.gov).This GIS datalayer represents approximate service areas for Public Water Systems (PWS) in Massachusetts. In 2017, as part of its “Enhancing Resilience and Emergency Preparedness of Water Utilities through Improved Mapping” (Critical Infrastructure Mapping Project ), the MassDEP Water Utility Resilience Program (WURP) began to uniformly map drinking water service areas throughout Massachusetts using information collected from various sources. Along with confirming existing public water system (PWS) service area information, the project collected and verified estimated service area delineations for PWSs not previously delineated and will continue to update the information contained in the datalayers. As of the date of publication, WURP has delineated Community (COM) and Non-Transient Non-Community (NTNC) service areas. Transient non-community (TNCs) are not part of this mapping project.Layers and Tables:The MassDEP Estimated Public Water System Service Area data comprises two polygon feature classes and a supporting table. Some data fields are populated from the MassDEP Drinking Water Program’s Water Quality Testing System (WQTS) and Annual Statistical Reports (ASR).The Community Water Service Areas feature class (PWS_WATER_SERVICE_AREA_COMM_POLY) includes polygon features that represent the approximate service areas for PWS classified as Community systems.The NTNC Water Service Areas feature class (PWS_WATER_SERVICE_AREA_NTNC_POLY) includes polygon features that represent the approximate service areas for PWS classified as Non-Transient Non-Community systems.The Unlocated Sites List table (PWS_WATER_SERVICE_AREA_USL) contains a list of known, unmapped active Community and NTNC PWS services areas at the time of publication.ProductionData UniversePublic Water Systems in Massachusetts are permitted and regulated through the MassDEP Drinking Water Program. The WURP has mapped service areas for all active and inactive municipal and non-municipal Community PWSs in MassDEP’s Water Quality Testing Database (WQTS). Community PWS refers to a public water system that serves at least 15 service connections used by year-round residents or regularly serves at least 25 year-round residents.All active and inactive NTNC PWS were also mapped using information contained in WQTS. An NTNC or Non-transient Non-community Water System refers to a public water system that is not a community water system and that has at least 15 service connections or regularly serves at least 25 of the same persons or more approximately four or more hours per day, four or more days per week, more than six months or 180 days per year, such as a workplace providing water to its employees.These data may include declassified PWSs. Staff will work to rectify the status/water services to properties previously served by declassified PWSs and remove or incorporate these service areas as needed.Maps of service areas for these systems were collected from various online and MassDEP sources to create service areas digitally in GIS. Every PWS is assigned a unique PWSID by MassDEP that incorporates the municipal ID of the municipality it serves (or the largest municipality it serves if it serves multiple municipalities). Some municipalities contain more than one PWS, but each PWS has a unique PWSID. The Estimated PWS Service Area datalayer, therefore, contains polygons with a unique PWSID for each PWS service area.A service area for a community PWS may serve all of one municipality (e.g. Watertown Water Department), multiple municipalities (e.g. Abington-Rockland Joint Water Works), all or portions of two or more municipalities (e.g. Provincetown Water Dept which serves all of Provincetown and a portion of Truro), or a portion of a municipality (e.g. Hyannis Water System, which is one of four PWSs in the town of Barnstable).Some service areas have not been mapped but their general location is represented by a small circle which serves as a placeholder. The location of these circles are estimates based on the general location of the source wells or the general estimated location of the service area - these do not represent the actual service area.Service areas were mapped initially from 2017 to 2022 and reflect varying years for which service is implemented for that service area boundary. WURP maintains the dataset quarterly with annual data updates; however, the dataset may not include all current active PWSs. A list of unmapped PWS systems is included in the USL table PWS_WATER_SERVICE_AREA_USL available for download with the dataset. Some PWSs that are not mapped may have come online after this iteration of the mapping project; these will be reconciled and mapped during the next phase of the WURP project. PWS IDs that represent regional or joint boards with (e.g. Tri Town Water Board, Randolph/Holbrook Water Board, Upper Cape Regional Water Cooperative) will not be mapped because their individual municipal service areas are included in this datalayer.PWSs that do not have corresponding sources, may be part of consecutive systems, may have been incorporated into another PWSs, reclassified as a different type of PWS, or otherwise taken offline. PWSs that have been incorporated, reclassified, or taken offline will be reconciled during the next data update.Methodologies and Data SourcesSeveral methodologies were used to create service area boundaries using various sources, including data received from the systems in response to requests for information from the MassDEP WURP project, information on file at MassDEP, and service area maps found online at municipal and PWS websites. When provided with water line data rather than generalized areas, 300-foot buffers were created around the water lines to denote service areas and then edited to incorporate generalizations. Some municipalities submitted parcel data or address information to be used in delineating service areas.Verification ProcessSmall-scale PDF file maps with roads and other infrastructure were sent to every PWS for corrections or verifications. For small systems, such as a condominium complex or residential school, the relevant parcels were often used as the basis for the delineated service area. In towns where 97% or more of their population is served by the PWS and no other service area delineation was available, the town boundary was used as the service area boundary. Some towns responded to the request for information or verification of service areas by stating that the town boundary should be used since all or nearly all of the municipality is served by the PWS.Sources of information for estimated drinking water service areasThe following information was used to develop estimated drinking water service areas:EOEEA Water Assets Project (2005) water lines (these were buffered to create service areas)Horsely Witten Report 2008Municipal Master Plans, Open Space Plans, Facilities Plans, Water Supply System Webpages, reports and online interactive mapsGIS data received from PWSDetailed infrastructure mapping completed through the MassDEP WURP Critical Infrastructure InitiativeIn the absence of other service area information, for municipalities served by a town-wide water system serving at least 97% of the population, the municipality’s boundary was used. Determinations of which municipalities are 97% or more served by the PWS were made based on the Percent Water Service Map created in 2018 by MassDEP based on various sources of information including but not limited to:The Winter population served submitted by the PWS in the ASR submittalThe number of services from WQTS as a percent of developed parcelsTaken directly from a Master Plan, Water Department Website, Open Space Plan, etc. found onlineCalculated using information from the town on the population servedMassDEP staff estimateHorsely Witten Report 2008Calculation based on Water System Areas Mapped through MassDEP WURP Critical Infrastructure Initiative, 2017-2022Information found in publicly available PWS planning documents submitted to MassDEP or as part of infrastructure planningMaintenanceThe

The Digital Geologic-GIS Map of Richmond National Battlefield Park and Vicinity, Virginia 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 (rich_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (rich_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 (rich_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (rich_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (rich_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 (rich_geology_metadata_faq.pdf). Please read the rich_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Virginia Division of Geology and Mineral Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (rich_geology_metadata.txt or rich_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 Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

See full Data Guide here. This layer includes polygon features that depict protected open space for towns of the Protected Open Space Mapping (POSM) project, which is administered by the Connecticut Department of Energy and Environmental Protection, Land Acquisition and Management. Only parcels that meet the criteria of protected open space as defined in the POSM project are in this layer. Protected open space is defined as: (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non-facility-based outdoor recreation, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities. Includes protected open space data for the towns of Andover, Ansonia, Ashford, Avon, Beacon Falls, Canaan, Clinton, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bridgewater, Bolton, Brookfield, Brooklyn, Canterbury, Canton, Chaplin, Cheshire, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Goshen, Granby, Griswold, Groton, Guilford, Haddam, Hampton, Hartford, Hebron, Kent, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Monroe, Montville, Morris, New Britain, New Canaan, New Fairfield, New Milford, New Hartford, Newington, Newtown, Norfolk, North, Norwich, Preston, Ridgefield, Shelton, Stonington, Oxford, Plainfield, Plainville, Pomfret, Portland, Prospect, Putnam, Redding, Rocky Hill, Roxbury, Salem, Salisbury, Scotland, Seymour, Sharon, Sherman, Simsbury, Somers, South Windsor, Southbury, Southington, Sprague, Sterling, Suffield, Thomaston, Thompson, Tolland, Torrington, Union, Vernon, Wallingford, Windham, Warren, Washington, Waterbury, Watertown, West Hartford, Westbrook, Weston, Wethersfield, Willington, Wilton, Windsor, Windsor Locks, Wolcott, Woodbridge, Woodbury, and Woodstock. Additional towns are added to this list as they are completed. The layer is based on information from various sources collected and compiled during the period from March 2005 through the present. These sources include but are not limited to municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions as of the date of research at each city or town hall. The Protected Open Space layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town Assessor's lot numbering system, and system-defined (automatically generated) fields. The Protected Open Space layer has an accompanying table containing more detailed information about each feature (parcel). This table is called Protected Open Space Dat, and can be joined to Protected Open Space in ArcMap using the parcel ID (PAR_ID) field. Detailed information in the Protected Open Space Data attribute table includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the unique parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, and acreage. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygons that represent the best available locational information, and are "best fit" to the land base available for each.

The Connecticut Department of Environmental Protection's (CTDEP) Permanently Protected Open Space Phase Mapping Project Phase 1 (Protected Open Space Phase1) layer includes permanently protected open space parcels in towns in Phase 1 that meet the CTDEP's definition for this project, the Permanently Protected Open Space Mapping (CT POSM) Project. The CTDEP defines permanently protected open space as (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non facility-based outdoor recreations, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities.

Towns in Phase 1 of the CT POSM project are situated along the CT coast and portions of the Thames River and are the following: Branford, Bridgeport, Chester, Clinton, Darien, Deep River, East Haven, East Lyme, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Lyme, Madison, Milford, Montville, New Haven, New London, North Branford, North Haven, Norwalk, Norwich, Old Lyme, Old Saybrook, Orange, Preston, Shelton, Stamford, Stonington, Stratford, Waterford, West Haven, Westbrook, Westport.

For the purposes of the project a number of categories or classifications of open space have also been created. These include: Land Trust, Land Trust with buidlings, Private, Private with buildings, Utility Company, Utility Company with buildings, Federal, State, Municipal, Municipal with buildings, Conservation easement, and non-DEP State land. The layer is based on information from various sources collected and compiled during the period from August 2002 trhough October 2003. These sources include municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions on the date of research at each city or town hall.

The Protected Open Space Phase1 layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town's Assessor lot numbering system, and system-defined (automatically generated) fields. In addition, the Protected_Open_Space_Phase1 layer has an accompanying table containing more detailed information about each parcel's collection, standardization and storage. This table is called Protected Open Space Phase1 Data and can be joined to Protected Open Space Phase1 in ArcMap using the parcel ID (PAR_ID) field. Detailed information includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the project-specific parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, acreage collected during site reconaissance and the data source. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygon feature type that represent the best available locational information, i.e. "best fit" to the land base available for each.

Phase 1 of the Protected Open Space Mapping (POSM) Project was accomplished by a contractor using only a querying process to identify open space. The contractor obtained assessor's data from the various towns and created programs to cull open space parcels strictly by query processes. We have found many errors and omissions in the data, but at this point in the project we cannot revisit all the coastal towns. Therefore, this data is being sent with a disclaimer for accuracy. You are welcome to use it but not to publish it. Please note that we do not include any water company parcels despite them being listed as part of our criteria because we must first obtain written clarification and clearance from the U.S. Department of Homeland Security.

We have since changed our data collection method for Phase 2 of this project. DEP staff now visit each town hall and thoroughly research the land records. The project is expected to be complete by 2010.

Shapefile of zoning quartersection map index. Grid to determine which zoning quartersection map relates to specific areas of NYC.

A sectional index grid to determine which Zoning Map refers to specific areas of New York City. Zoning maps show the boundaries of zoning districts throughout the city. The maps are regularly updated after the City Planning Commission and the City Council have approved proposed zoning changes. The set of 126 maps, which are part of the Zoning Resolution, are displayed in 35 sections. Each section is identified by a number from 1 to 35 and is further divided into one to four quarters, each identified by a letter a, b, c or d (map 8d or 33c for example). Each map covers an area of approximately 8,000 feet (north/south) by 12,500 feet (east/west).

Official sheet cuts for the map series 1:25,000, 1:50,000, 1:100,000.

California's Coastal Zone generally extends seaward to the state's outer limit of jurisdiction, including all offshore islands, and inland to approximately 1,000 yards from the mean high tide line (MHTL) of the sea, or in significant coastal estuarine, habitat, and recreational areas to the first major ridgeline paralleling the sea or five miles from the mean high tide line of the sea, whichever is less. In developed urban areas the zone generally extends inland less than 1,000 yards. This data set represents the landward boundary of California's Coastal Zone. Public Resources Code (PRC) Section 30103(a) specifically defines California's Coastal Zone as that land and water area of the State of California from the Oregon border to the border of the Republic of Mexico depicted on maps identified and set forth in Section 17 of that chapter of the Statutes of the 1975-76 Regular Session enacting PRC Division 20 (the Coastal Act of 1976). PRC Section 30103(b) directed the Coastal Commission to prepare and adopt more detailed 1:24,000 scale Coastal Zone Boundary (CZB) maps, which occurred March 1, 1977. These 161 adopted maps provide the official basis for all other representations of the landward CZB. The digital version of the CZB created by developing this shapefile is a conformed copy of the official boundary, and in some locations reflects legislative changes and Coastal Commission minor adjustments adopted from time to time since March 1977.

Section 30103 of the Coastal Act:

Coastal zone; map; purpose (a) "Coastal zone" means that land and water area of the State of California from the Oregon border to the border of the Republic of Mexico, specified on the maps identified and set forth in Section 17 of Chapter 1330 of the Statutes of 1976, extending seaward to the state's outer limit of jurisdiction, including all offshore islands, and 11 extending inland generally 1,000 yards from the mean high tide line of the sea. In significant coastal estuarine, habitat, and recreational areas it extends inland to the first major ridgeline paralleling the sea or five miles from the mean high tide line of the sea, whichever is less, and in developed urban areas the zone generally extends inland less than 1,000 yards. The coastal zone does not include the area of jurisdiction of the San Francisco Bay Conservation and Development Commission, established pursuant to Title 7.2 (commencing with Section 66600) of the Government Code, nor any area contiguous thereto, including any river, stream, tributary, creek, or flood control or drainage channel flowing into such area.

Note that the California's State Waters limit, which generally is 3 nautical miles [5.6 km] from shore, extends farther offshore (as much as 12 nautical miles) between Santa Cruz and Monterey, so that it encompasses all of Monterey Bay.

ADMMR map collection: Section of Lucky Cuss; 1 in. to 50 feet; 12 x 20 in.

Geospatial data about Ohio Townships. Export to CAD, GIS, PDF, CSV and access via API.

The Digital Geologic-GIS Map of the Lake Roosevelt National Recreation Area and Vicinity, Washington 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 (laro_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (laro_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 (laro_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (laro_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (laro_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 (laro_geology_metadata_faq.pdf). Please read the laro_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: 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: Washington Division of Earth Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (laro_geology_metadata.txt or laro_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:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).