State of California Boundary with Bay Cuts

Purpose Boundary is derived from the California Department of Tax and Fee Administration (CDTFA). Their county boundaries are the most-up to date 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. CDT GIS attached a GEOID attribute with the value ‘06’ to identify California and create ease of joins with other Census-based datasets. Finally, this layer removes the coastal buffer polygons and cuts out the bay area water region. 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] * [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) 8. State Boundary * With Bay Cuts (this dataset) * [Without Bay Cuts] Point of Contact California Department of Technology, Office of Digital Services, [gis@state.ca.gov] Field and Abbreviation Definitions * CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau Boundary Accuracy State boundary is created from county boundaries that 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. 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. 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. CDTFA's source data notes the following about accuracy (derived from the California County Boundaries and Identifiers): > 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. > Boundary Processing 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. Slivers 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. Coastline Caveats 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. Offline Use This service is fully enabled for sync and export using Esri Field Maps or other similar tools.