California County Boundaries and Identifiers

<p><span style='font-size:14px;'><strong>Note: The schema changed in February 2025 - </strong>please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable.<strong> For deployment status of new services beginning in February 2025, see </strong></span><a target='_blank' href='https://gis.data.ca.gov/pages/city-and-county-boundary-data-status' rel='nofollow ugc noopener noreferrer'>https://gis.data.ca.gov/pages/city-and-county-boundary-data-status</a>. Additional roadmap and status links at the bottom of this metadata.</p><div><span style='font-size:14px;'>This dataset is regularly updated as </span><a target='_blank' href='https://gis.data.ca.gov/datasets/CDTFA::city-and-county-boundary-line-changes/' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'>the source data from CDTFA</span></a><span style='font-size:14px;'> is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.</span></div><p>&nbsp;</p><div>&nbsp;</div><p><span style='font-size:x-large;'>Purpose</span><br />&nbsp;</p><p><span style='font-size:14px;'>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.</span></p><p><span style='font-size:14px;'>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.</span></p><p>&nbsp;</p><p><span style='font-size:24px;'>Related Layers</span></p><p><span style='font-size:14px;'>This dataset is part of a grouping of many datasets:</span></p><ol><li><span style='font-size:14px;'><strong>Cities</strong>: Only the city boundaries and attributes, without any unincorporated areas</span><ul><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=be8a1cd8eff242b0a25feb54e5a2f5a6' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'>With Coastal Buffers</span></a></li><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=8cd5d2038c5547ba911eea7bec48e28b' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'>Without Coastal Buffers</span></a></li></ul></li><li><span style='font-size:14px;'><strong>Counties</strong>: Full county boundaries and attributes, including all cities within as a single polygon</span><ul><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=28c9f9dd8c3d4eb5a534cb30ddb3ce39' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'>With Coastal Buffers</span></a></li><li><span style='font-size:14px;'>Without Coastal Buffers (this dataset)</span></li></ul></li><li><span style='font-size:14px;'><strong>Cities and Full Counties</strong>: 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<strong>.</strong></span><ul><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=14ff938d4a3045aea74fe18cbf954aa5' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'>With Coastal Buffers</span></a></li><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=894e9cda46bb45c2a0c7b5534b9a6b4a' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'>Without Coastal Buffers</span></a></li></ul></li><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=edc05d5bf2ce44bca2f4ce0851a2fdf0' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'><strong>City and County Abbreviations</strong></span></a></li><li><span style='font-size:14px;'><strong>Unincorporated Areas</strong> (Coming Soon)</span></li><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=d1a79f9faea241ab9a3f9ef549a19fd7' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'><strong>Census Designated Places</strong></span></a></li><li><span style='font-size:14px;'><strong>Cartographic Coastline</strong></span><ul><li><a target='_blank' href='https://california.maps.arcgis.com/home/item.html?id=f7c7ac7e62c645779c98f46a117cf062' rel='nofollow ugc noopener noreferrer'><span style='font-size:14px;'>Polygon</span></a></li><li><span style='font-size:14px;'>Line source (Coming Soon)</span></li></ul></li></ol><div>&nbsp;</div><div><span style='font-size:x-large;'>Working with Coastal Buffers</span><br />&nbsp;</div><div><span style='font-size:14px;'>The dataset you are currently viewing <strong>excludes</strong> the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields <strong>except</strong> OFFSHOR</span><span style='font-family:Consolas, Courier New; font-size:14px;'>E and AREA_SQMI</span><span style='font-size:14px;'> to get a version with the correct identifiers.</span></div><div><br />&nbsp;</div><div>&nbsp;</div><div>&nbsp;</div><p><span style='font-size:x-large;'>Point of Contact</span></p><p><span style='font-size:14px;'>California Department of Technology, Office of Digital Services, </span><a href='mailto:gis@state.ca.gov' rel='nofollow ugc'><span style='font-size:14px;'>gis@state.ca.gov</span></a></p><p>&nbsp;</p><p>&nbsp;</p><p><span style='font-size:x-large;'>Field and Abbreviation Definitions</span></p><ul><li><span style='font-size:14px;'><strong>CDTFA_COUNTY</strong>: 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.</span></li><li><span style='font-size:14px;'><strong>CDTFA_COPRI</strong>: 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.</span></li><li><span style='font-size:14px;'><strong>CENSUS_GEOID</strong>: numeric geographic identifiers from the US Census Bureau</span></li><li><span style='font-size:14px;'>CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.</span></li><li><span style='font-size:14px;'><strong>GNIS_PLACE_NAME</strong>: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System</span></li><li><span style='font-size:14px;'><strong>GNIS_ID: </strong>The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.</span></li><li><span style='font-size:14px;'><strong>CDT_COUNTY_ABBR</strong>: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.</span></li><li><span style='font-size:14px;'><strong>CDT_NAME_SHORT</strong>: 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.</span></li><li><span style='font-size:14px;'><strong>AREA_SQMI</strong>: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.</span></li><li><span style='font-size:14px;'><strong>OFFSHORE</strong>: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".</span></li><li><span style='font-size:14px;'><strong>PRIMARY_DOMAIN</strong>: Currently empty/null for all records. Placeholder field for official URL of the city or county</span></li><li><span style='font-size:14px;'><strong>CENSUS_POPULATION</strong>: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.</span></li><li><strong>GlobalID</strong>: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do <strong>not</strong> 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.</li></ul><p>&nbsp;</p><div><span style='font-size:x-large;'>Boundary Accuracy</span></div><div><span>County boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.</span><br /><br /><span>Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel </span><i><span>is </span></i><span>in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor.</span></div><div><br />&nbsp;</div><div>CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information.</div><div>&nbsp;</div><p>&nbsp;</p><p><span style='font-size:14px;'>CDTFA's source data notes the following about accuracy:</span></p><p>&nbsp;</p><blockquote><p><span style='font-size:14px;'>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.&nbsp;</span><br />&nbsp;</p></blockquote><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><div><span style='font-size:x-large;'>Boundary Processing</span></div><div><span style='font-size:14px;'>These data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.</span><br /><br />&nbsp;</div><div><span style='font-size:14px;'>In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.</span></div><div><br />&nbsp;</div><div>&nbsp;</div><div>&nbsp;</div><div><span style='font-size:large;'><strong>Slivers</strong></span></div><div><span style='font-size:14px;'>In cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.</span></div><div><br />&nbsp;</div><div>&nbsp;</div><div><span style='font-size:large;'><strong>Coastline Caveats</strong></span></div><div><span style='font-size:14px;'>Some cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.</span></div><div><br />&nbsp;</div><div>&nbsp;</div><div><span style='font-size:24px;'>Offline Use</span></div><div>This service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).</div><div>&nbsp;</div><div>&nbsp;</div><div><span style='font-size:x-large;'>Updates and Date of Processing</span></div><div><span style='font-size:14px;'>Concurrent with CDTFA updates, approximately every two weeks, Last Processed: 03/01/2025 by Nick Santos using code path at&nbsp;</span><a target='_blank' href='https://github.com/Office-of-Digital-Services/gis-city-county' rel='nofollow ugc noopener noreferrer'>https://github.com/Office-of-Digital-Services/gis-city-county</a><span style='font-size:14px;'> at commit 1ecb474343f85747bdf106dbefac1ed18809f23b. It incorporates updates from CDTFA as of 02/21/2025. Future updates will include improvements to metadata and update frequency.</span></div><div><br />&nbsp;</div><div><span style='font-size:x-large;'>Software, Changes, Issues, and Roadmap</span></div><div><span style='font-size:14px;'>The code that builds and deploys this dataset is a work in progress and receives updates that change data, features, metadata, and more. To contribute a change, please reach out to the email address above or see the links below:</span></div><div><ol><li><a target='_blank' href='https://github.com/Office-of-Digital-Services/gis-city-county/' rel='nofollow ugc noopener noreferrer'>Software repository</a></li><li><a target='_blank' href='https://github.com/Office-of-Digital-Services/gis-city-county/' rel='nofollow ugc noopener noreferrer'>File an issue, request a change, or report a problem</a></li><li><a target='_blank' href='https://gis.data.ca.gov/pages/city-and-county-boundary-data-status' rel='nofollow ugc noopener noreferrer'>Service deployment status page</a></li><li><a target='_blank' href='https://github.com/orgs/Office-of-Digital-Services/projects/14/views/3' rel='nofollow ugc noopener noreferrer'>Software roadmap</a></li></ol></div>