Three feature layers of Unites States internal state boundaries at different scales: 1:500K, 1:5M, and 1:20M. These layers are intended for use as a cartographic product. It is up to the user to determine which layer is most appropriate for their map.Derived from 2019 US Census Bureau Cartographic Boundary Files for state boundaries using ArcGIS Pro 2.4.3. Process:Original files were downloaded from US Census for the three different scales.Polygons were then converted to lines using the Polygon-to-Line tool.To remove the coastlines, all rows not having a LEFT_FID or RIGHT_FID attribute equal to -1 were then exported to a new geodatabase feature class.The geodatabase was zipped and uploaded to ArcGIS Online.For more information on Cartographic Boundary Files visit https://www.census.gov/programs-surveys/geography/technical-documentation/naming-convention/cartographic-boundary-file.html and https://www.census.gov/geographies/mapping-files/time-series/geo/cartographic-boundary.html.Created by Ryan Davis (RDavis9@cdc.gov) on behalf of CDC/ATSDR/DTHHS/GRASP.

This map layer portrays the State boundaries of the United States, Puerto Rico, and the U.S. Virgin Islands. The map layer was created by extracting county polygon features from the CENSUS 2006 TIGER/Line files produced by the U.S. Census Bureau. These files were then merged into a single file and county boundaries within States were removed. This is a revised version of the July 2012 map layer.The data and related materials are made available through Esri (http://www.esri.com) and are intended for educational purposes only (see Access and Use Constraints section).

This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.

The North Carolina State and County Boundary vector polygon data provides location information for North Carolina State and County Boundary lines derived from the best available survey and/or Geographic Information System (GIS) data. Sources for information are the North Carolina Geodetic Survey (NCGS), NC Department of Transportation (NCDOT), United States Geological Survey (USGS), and field surveys conducted by licensed surveyors in North Carolina and neighboring states that have been approved and recorded in their respective counties. North Carolina Geodetic Survey assists counties on a cooperative basis (NC General Statute 153A-18) in defining and monumenting the location of uncertain or disputed boundaries as established by law. Some counties have completed boundary surveys for at least a portion of their county boundary. However, the majority of county boundaries have not been surveyed and are represented by the best currently available data from GIS sources, including NCDOT county maps (which originally came from the USGS) and updated county parcel maps.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers (this dataset)
   • Without Coastal Buffers
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated

Original dataset created by Kentucky Transportation Cabinet. Updates done by Division of Geographic Information staff. This work product represents an administrative geographical inventory of incorporated city boundaries as registered and filed at the office of the Secretary of State for the Commonwealth of Kentucky, and is not intended to be used as a definitive or accurate source for the legal location of any real estate boundary, whether through coincidental or relative reference, as interpreted or implied from the recorded definitions of the boundary lines conveyed herein. Not all boundaries have not been verified against official annexation actions or deed descriptions.

Integrated terrain models covering 16,357 square kilometers of the Massachusetts coastal zone and offshore waters were built to provide a continuous elevation and bathymetry terrain model for ocean planning purposes. The area is divided into the following four geographical areas to reduce file size and facilitate publishing: Massachusetts Bay from the Massachusetts-New Hampshire border south to Provincetown and Scituate and east to Stellwagen Bank; Cape Cod Bay from Provincetown to Scituate and south to Hyannis; Buzzards Bay from the Cape Cod Canal southwest to the State border including the Elizabeth Islands and extending north to Fall River and Mount Hope Bay; and Nantucket and Vineyard Sounds, from Hyannis south to the border of the Massachusetts Coastal zone approximately 8 kilometers south of Nantucket. A Triangulated Irregular Network was created from public-domain bathymetric and LiDAR data using the ArcGIS terrain-model framework and then interpolated into a 32-bit GeoTiff of 10 meter resolution. The grids for each of the four geographical areas are referenced to the Universal Transverse Mercator, Zone 19, North American Datum of 1983 coordinate system, and the North American Vertical Datum of 1988. A polygon shapefile recording the source datasets accompanies each of the four grids.

The Arkansas Secretary of State contracted the University of Arkansas at Little Rock, GIS Applications Laboratory (UALRGIS) to use modern geographic information technology and improved base maps to create a current and spatially accurate statewide depiction of school district boundaries in the State of Arkansas. The Arkansas Geographic Information Office merged annexed and consolidated districts. UALRGIS followed a work plan for the project that was established by the Arkansas Geographic Information Office (AGIO) for the Secretary of State. The school district boundary editing rules were as follows: 1. Legal descriptions take precedent. 2. If no legal description was provided the visual evidence presented on the digital ortho quarter quadrangle (DOQQ) was followed. 3. Section lines, county boundaries, city boundaries and / or roads have only be used as supporting visual evidence viewed on the DOQQ.

The municipal boundary change is a publication consisting of multiple individual polygons each representing a unique boundary description. The Arkansas GIS Office maintains this file in coordination with the municipalities of the State. It represents boundary changes across time for any cities beginning in 2016. 2016 is the year beginning in which the Arkansas Legislature mandated the Arkansas GIS Office to coordinate with any entity on municipal boundary changes and report these changes to the US Census Bureau. These change polygons can represent annexation, consolidation, detachment, incorporation and unincorporation of territory representing area per description. These change polygons can also represent geometry corrections where both minor and substantial corrections were needed. Where substantial corrections are needed, the feature will contain a link to pertinent documentation supporting the geometry correction. Various methods to annex, detach, create a new incorporation or unincorporate an existing incorporation may be used. Data developed with coordinate geometry (COGO) from legal descriptions were used. When necessary the data were adjusted to conform to known physical features. This dataset does not represent exact legal boundaries as per surveyed description, but, rather a set of boundaries used for the administrative purposes that conforms to logical & administrative rules.

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose
City boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, gis@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

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.

Dataset content available to registered users only

SP ENW - Control Boundary

Polygon depicting the extents of the SP Electricity North West control area

While we use reasonable endeavours to ensure that the data contained within this dataset is accurate, we do not accept any responsibility or liability for the accuracy or the completeness of the content held, or for any loss which may arise from reliance on this dataset and/or its related information.

If you have any query related to this SP ENW Control Boundary dataset, please contact us

HERE

Actual dataset content is available to registered users only – If you have not already done so, log-in or create new account below

New User? - Create your new account

HERE

Already registered as a SP ENW Portal User? - Log-In

HERE

Have you an ODS Portal account created elsewhere? - Log-In

HERE

(Link to Metadata) Generated from exact latitude-longitude coordinates and projected from Geographic coordinates (Lat/Long) NAD83 into State Plane Meters NAD83. The Arc/Info GENERATE command was used with the following parameters; generate BoundaryTile_QUAD83 fishnet no labels -73.500,42.625 -73.500,42.725 0.125,0.125 20,17 The Arc/Info project command was then used to re-project from Geographic (DD)NAD83 into Vermont State Plane Meters (NAD83). Extraneous polygons where removed. Polygon label points where transfered from the QUAD coverage into the new coverage, resulting in duplicate attribute items. The tics in this data layer should only be used for digitizing if your source data is in NAD83! Use BoundaryTile_QUAD27 if your source data is in NAD27. In both cases you should re-project this coverage into UTM before digitizing. When you've completed your digitizing work re-project the data back into Vermont State Plane Meters NAD83.

District of Columbia boundary. The dataset is a polygon representing the District of Columbia boundary, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. The boundary was identified from public records and heads-up digitized using a combination of the 1995 orthophotographs, planimetric roads features, and the USGS digital raster graphic quad sheets, and 1999 planimetrics for the Potomac River boundary.Also see the District's Boundary Stone markers.

This service depicts National Park Service tract and boundary data that was created by the Land Resources Division. NPS Director's Order #25 states: "Land status maps will be prepared to identify the ownership of the lands within the authorized boundaries of the park unit. These maps, showing ownership and acreage, are the 'official record' of the acreage of Federal and non-federal lands within the park boundaries. While these maps are the official record of the lands and acreage within the unit's authorized boundaries, they are not of survey quality and not intended to be used for survey purposes." As such this data is intended for use as a tool for GIS analysis. It is in no way intended for engineering or legal purposes. The data accuracy is checked against best available sources which may be dated and vary by location. NPS assumes no liability for use of this data. The boundary polygons represent the current legislated boundary of a given NPS unit. NPS does not necessarily have full fee ownership or hold another interest (easement, right of way, etc...) in all parcels contained within this boundary. Equivalently NPS may own or have an interest in parcels outside the legislated boundary of a given unit. In order to obtain complete information about current NPS interests both inside and outside a unit’s legislated boundary tract level polygons are also created by NPS Land Resources Division and should be used in conjunction with this boundary data. To download this data directly from the NPS go to https://irma.nps.gov Property ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.

Publication Date: February 2020. Updated as needed. Current as of the Publication Date.

A vector polygon layer of all city and town boundaries in New York State. The source data was originally a compilation of U.S. Geological Survey 1:100,000-scale digital vector files and NYS Department of Transportation 1:24,000-scale and 1:75,000-scale digital vector files. Boundaries were revised to 1:24,000-scale positional accuracy and selectively updated based on municipal boundary reviews, court decisions and NYS Department of State Local Law filings for annexations, dissolutions, and incorporations. Currently, boundary changes are made based on NYS Department of State Local Law filings (http://locallaws.dos.ny.gov/). Additional updates and corrections are made as needed in partnership with municipalities.

Additional metadata, including field descriptions, can be found at the NYS GIS Clearinghouse: http://gis.ny.gov/gisdata/inventories/details.cfm?DSID=927.

Spatial Reference of Source Data: NAD 1983 UTM Zone 18N. Spatial Reference of Map Service: WGS 1984 Web Mercator Auxiliary Sphere. This map service is available to the public.

The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.Credit: NYS Office of Information Technology Services GIS Program Office (GPO). Primary Contact: GPO, GISBoundaries@its.ny.gov, 518-242-5029.

Maine County Boundary Polygons contains county boundary polygons for all sixteen counties in Maine, mapped at the 1:24,000 scale. The data layer has polygon topology and was originally created in ArcInfo using METWP24P with a selection on arcs coded "TYPE=state,county, and coastline".

Bathymetric Terrain Models (BTMs) of seafloor morphology are an important component of marine geological investigations. Advances in acquisition and processing technologies of bathymetry data have facilitated the creation of high-resolution bathymetric surfaces that approach the resolution of those available for onshore investigations. These BTMs provide a detailed representation of the Earth's subaqueous surface and when combined with other geophysical and geologic datasets, allow for interpretation of modern and ancient geologic processes.

MassGIS had received quarterly updates of these data as part of its license for the HERE (Navteq) core map release (streets and related data); however, that license has expired. These ZIP Code boundaries are aligned to the street centerlines of the Q2 2018 HERE product (with a release date of April 1, 2018) and use a then-recent USPS source file.In March 2024, MassGIS modified the boundaries for all ZIP Code areas in Boston based on the U.S. Postal Service's ZIP Code Look Up by Address website. MassGIS also added polygons for ZIP Codes 02199 and 02203.Five-digit ZIP Codes were developed by the USPS and first introduced in 1963 for efficient mail delivery (the term ZIP stands for Zone Improvement Plan) but are difficult to map with complete certainty. In most cases, addresses in close proximity to each other are grouped in the same ZIP Code, which gives the appearance that ZIP Codes are defined by a clear geographic boundary. However, even when ZIP Codes appear to be geographically grouped, a clear ZIP Code boundary cannot always be drawn because ZIP Codes are only assigned to a point of delivery and not the spaces between delivery points. In areas without a regular postal route or no mail delivery, ZIP Codes may not be defined or have unclear boundaries.The USPS does not maintain an official ZIP Code map. The Census Bureau and many other commercial services will interpolate the data to create polygons to represent the approximate area covered by a ZIP code, but none of these maps are official or entirely accurate. Please see this good discussion of the issues of mapping ZIP Codes.See full metadata.Feature service also available.