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]

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

In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata.A dataset was made available (approximately 2004) through CALFIRE - FRAP and the California Spatial Information Library (CaSIL), with additional updates throughout subsequent years. More recently, an effort was made to improve the coastal linework by using the previous interior linework from the 24k data, but replacing the coastal linework based on NOAA's ERMA coastal dataset (which used NAIP 2010). In this dataset, all bays (plus bay islands and constructed features) are merged into the mainland, and coastal features (such as islands and constructed features) are not included, with the exception of the Channel Islands which ARE included.This service represents the latest released version, and is updated when new versions are released. As of June, 2019 it represents cnty19_1.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's 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 jurisdictions. The boundaries are continuously being revised 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 and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; 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 (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

Download In State Plane Projection Here. This is our working version of the Lake County boundary. Although technically the county's eastern border extends eastward into Lake Michigan to the state line where Illinois meets Michigan, we routinely use the Lake Michigan shoreline as our eastern boundary for mapping purposes. The north, west and south boundaries are based on a compilation of survey data which aligns well, but not perfectly, with the border as mapped by neighboring counties and the State of Wisconsin, which forms the northern boundary of the county. Update Frequency: This dataset is updated on a weekly basis.

This layer contains Legal City boundaries within Los Angeles County. The Los Angeles County Department of Public Works provides the most current shape file of these city boundaries for download at its Spatial Information Library.Note: This boundary layer will not line up with the Thomas Brothers city layer. Principal attributes include:CITY_NAME: represents the city's name.CITY_TYPE: may be used for definition queries; "Unincorporated" or "City".FEAT_TYPE: contains the type of feature each polygon represents:Land - Use this value for your definition query if you want to see only land features on your map.Pier - One example is the Santa Monica Pier. Man-made features may be regarded as extensions of the coastline.Breakwater - Examples include the breakwater barriers that protect the Los Angeles Harbor.Water - Polygons with this attribute value represent internal navigable waters. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.3NM Buffer - Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles (a nautical mile is 1852 meters) from the coastline.

The division into counties based on the model used in the English system, was introduced gradually by English settlers from the late 12th century onwards. These land divisions were formed following the Norman invasion of Ireland in imitation of the counties then in use as units of local government in the Kingdom of England. The older term "shire" was historically equivalent to "county". The principal function of the county was to impose royal control in the areas of taxation, security and the administration of justice at local level. Following a survey under the 1825 Boundary Survey Act, an extensive series of maps of Ireland was created by the Irish division of the Tailte Éireann for taxation purposes. These maps both documented and standardised the boundaries of the thirty two counties of Ireland.Coordinate Reference System: Irish Transverse Mercator.This dataset is provided by Tailte Éireann

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.

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.)

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

Polygon vector map data covering county boundaries for Escambia County, Florida County containing 64 features.

Boundary GIS (Geographic Information System) data is spatial information that delineates the geographic boundaries of specific geographic features. This data typically includes polygons representing the outlines of these features, along with attributes such as names, codes, and other relevant information.

Boundary GIS data is used for a variety of purposes across multiple industries, including urban planning, environmental management, public health, transportation, and business analysis.

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.

Published to allow joining of spreadsheet data to county geometry in ESRI Maps for Office or Map Analysis Tools, contains Iowa DOM County Code (1-99) as a small integer, Census County FIPS as a both an string and integer. This data was originally created by the Iowa DNR and digitized from USGS 7.5' topographic maps.Click on the data tab above to see an example of expected data. OCIO has a tutorial on how to join your spreadsheet to this Feature layer to create a new feature layer with your county based information. Please contact patrick.wilke-brown@iowa.gov.

Map of Kansas county boundaries.The full Kansas geospatial catalog is administered by the Kansas Data Access & Support Center (DASC) and can be found at the following URL: https://hub.kansasgis.org/

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.

This data is maintained by and obtained from Metro GIS. Click the link above to view the Metro GIS metadata for this dataset.

This data is maintained by and obtained from Metro Data Resource Center. Please go to https://gis.oregonmetro.gov/rlis-metadata/#/details/155 for the complete metadata.-- Additional Information: Category: Boundary Purpose: For use as a "base" layer on map products to shade county areas and in analysis to capture areas within each county. Update Frequency: None planned-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=155

This dataset represents a summary of potential cropland inundation for the state of California applying high-frequency surface water map composites derived from two satellite remote sensing platforms (Landsat and Moderate Resolution Imaging Spectroradiometer [MODIS]) with high-quality cropland maps generated by the California Department of Water Resources (DWR). Using Google Earth Engine, we examined inundation dynamics in California croplands from 2003 –2020 by intersecting monthly surface water maps (n=216 months) with mapped locations of precipitation amounts, rice, field, truck (which comprises truck, nursery, and berry crops), deciduous (deciduous fruits and nuts), citrus (citrus and subtropical), vineyards, and young perennial crops. Surface water maps were produced using the Dynamic Surface Water Extent (DSWE) model, in which satellite image pixels are classified into different levels of detection confidence. Our analysis focused on calculating the monthly occurrence of “high confidence” water from each satellite collection across eight cropland types and 58 counties. The resulting tabular data have been joined to a county GIS shapefile covering the state of California. The file includes attributes summarizing each crop contained within the county boundaries along with a summary of how much cropland intersects past locations of cropland inundation, the relative percentage of cropland inundated, and the frequency of crop inundation. These summaries were generated using both the Landsat and MODIS water inundation maps, and are presented separately in the data release.

It includes the following counties: Bullitt County, Hardin County, Jefferson County, Clark County, Oldham County, Henry County, Meade County, Harrison County, Shelby County, Spencer County, Trimble County, Floyd County. This area is also the extent of our base map caches.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

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, odsdataservices@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.