This service provides vector polygon dataset defining the official boundaries of the 100 counties within North Carolina as well as the boundaries between North Carolina and the states which border North Carolina.The North Carolina county polygon boundary service 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. Some boundaries cannot be surveyed in cases where boundaries are coincident with river centers. 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.This data is updated annually, first quarter (usually in February).MetadataThe metadata for the contained layer of the NCDOT County Boundaries Service is available through the following link:County Boundaries PolygonPoint of Contact North Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the County Boundaries data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product Team

This data set provides a generalized outline of the 72 counties in Wisconsin. The data is derived from 1:24,000-scale sources.

COB_POLY: This theme shows the jurisdictional and cartographic county areas for Oregon and Washington. The POCA layer is an integrated set of geographic- referencing data covering the state of Washington. It is derived from land surveys, DNR orthophotos, USGS 7.5' quadrangles, and DNR tract books.

This dataset was created by the Transportation Planning and Programming (TPP) Division of the Texas Department of Transportation (TxDOT) for planning and asset inventory purposes, as well as for visualization and general mapping. County boundaries were digitized by TxDOT using USGS quad maps, and converted to line features using the Feature to Line tool. This dataset depicts a generalized coastline.Update Frequency: As NeededSource: Texas General Land OfficeSecurity Level: PublicOwned by TxDOT: FalseRelated LinksData Dictionary PDF [Generated 2025/03/14]

This layer contains detailed outlines of Maryland counties. The Maryland land county boundaries were built using political county boundaries and the National Hydrology Data (NHD). Land boundaries are a key geographic featue in our mapping process.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Last Updated: UnknownFeature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PhysicalBoundaries/FeatureServer/0

1. US Census Bureau Cartographic Boundary File of county boundaries for the Commonwealth of Virginia.

From the US Census Bureau: "The cartographic boundary files are simplified representations of selected geographic areas from the Census Bureau’s MAF/TIGER geographic database. These boundary files are specifically designed for small scale thematic mapping."

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.

US Census Bureau Cartographic Boundary File of county boundaries for each state in the Unites States.

From the US Census Bureau: "The cartographic boundary files are simplified representations of selected geographic areas from the Census Bureau’s MAF/TIGER geographic database. These boundary files are specifically designed for small scale thematic mapping."

This dataset represents the county boundaries, as recognized by the Minnesota Department of Transportation. There are 87 counties in Minnesota.

Check other metadata records in this package for more information on County Boundaries Information.


Link to ESRI Feature Service:

County Boundaries in Minnesota: County Boundaries

This dataset contains County Boundary Lines for the Commonwealth of Kentucky. State boundary along Ohio River has been updated to reflect the Supreme Court Case regarding a boundary dispute between Kentucky, Indiana and Ohio in 1980 (Ohio v. Kentucky, 444 U.S. 335 (1980)).Online Linkage: https://ky.box.com/v/kymartian-KyBnds-County

This layer is a component of SC Statewide Address Points and Centerlines.

© SC DOT, SC Counties, SC Geographic Information Council

County boundaries (polygon features) for Pennsylvania, New Jersey, Delaware, Maryland, New York, Connecticut, and the District of Columbia. Original Sources: PA - PennDOT NJ - NJOIT DE - DE Geological Survey MD, NY, CT, DC - ESRI Linework has been adjusted using the following methodology. NJ's boundaries overrode PA, since NJ's were highly accurate. PA overrode MD since PennDOT's were more accurate than ESRI's, and DE overrode PA & MD, since the "arc" of northernmost DE was a bit more accurate than PennDOT's or our original county boundaries. County boundaries in the DVRPC region have been adjusted to align with parcel data (where appropriate). NOTE: Use the following definition query if only need one county in DVRPC Region "Co_Name" LIKE '%Bucks%'

This is the standard Minnesota State County Boundary dataset that is used by MNDNR and many other state agencies. It is maintained by the MNDNR Lands and Minerals Division.

Please read at the accuracy and lineage sections of this metadata to make sure this dataset is appropriate for your application!

Cartographic Boundary Map provided the State of Texas Open Data Portal here: https://data.texas.gov/dataset/Texas-Counties-Cartographic-Boundary-Map/sw7f-2kkd/about_data Terms of Use This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries. This product has been provided by the City of Austin via the US Census Bureau for the sole purpose of geographic reference. No warranty is made by the City of Austin regarding specific accuracy or completeness.

1. US Census Bureau Cartographic Boundary File of county boundaries for each state in the Unites States.

From the US Census Bureau: "The cartographic boundary files are simplified representations of selected geographic areas from the Census Bureau’s MAF/TIGER geographic database. These boundary files are specifically designed for small scale thematic mapping."

January 2023 - Census population data were downloaded for 2020 and appended to the county dataset. Population fields were re-ordered and named for consistency.April 2013 - Census data were downloaded for 2010 and appended to the county coverage. Upon further review by the ND GIS Technical Meeting at their April 2013 meeting, it was decided that the demographic data included with the previous county feature class would be dropped, leaving only basic information with the necessary relational fields intact for joining of Census data tables and other related North Dakota data.The North Dakota county coverage was originally created by the North Dakota Geological Survey using US Census Bureau TIGER data in 1994. The source scale on these data was 1:100,000. Since its creation, with USGS Public Land Survey DLG data, and USGS DRG derived data. The North Dakota State Water Commission revamped this coverage by using the NDGS PLSS coverage (combination of ND PSC, USGS DLG and DRG 24k data) to obtain county boundaries that coincided with PLSS linework, and heads-up digitized irregular boundaries such as that on the State borders, and those that followed river/stream boundaries with USGS 1:24,000 scale Digital Raster Graphics. The resultant coverage should be much better than a 1:100,000 scale coverage, but may not meet 1:24,000 scale accuracy standards.

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

County Boundaries from the Nebraska Department of Transportation

This data layer is an Esri file geodatabase polygon feature class that contains county boundaries maintained by county agencies in Indiana. It was released by the Indiana Geographic Information Office (IGIO) on November 30, 2023. The IGIO compiled the data as part of the Indiana Data Harvest program between the Indiana Geographic Information Council (IGIC) and all Indiana counties to provide the most accurate framework data for the citizens of Indiana. These layers include address points, street centerlines, land parcels, and governmental boundaries.