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.This dataset is continuously updated as the source data from CDTFA 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.PurposeCounty 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 LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal Buffers (this dataset)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 BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing excludes 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 except OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_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 BureauCENSUS_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 SystemGNIS_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 countyCENSUS_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.Boundary AccuracyCounty 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. 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 is 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.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: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 ProcessingThese 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.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.SliversIn 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 CaveatsSome 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

This dataset includes the boundaries for the six counties in the Southern California Association of Governments (SCAG) Region.

This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.

Land boundaries for Orange County, cities, and unincorporated areas (based on the five supervisorial districts). Contains additional geodemographic data on population and housing from the US Census 2021 American Community Survey (ACS).

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.This dataset is continuously updated as the source data from CDTFA 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.PurposeCounty 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 LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal Buffers (this dataset)Without Coastal BuffersCities 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 BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes 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 except OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_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 BureauCENSUS_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 SystemGNIS_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 countyCENSUS_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.Boundary AccuracyCounty 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. 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 is 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.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: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 ProcessingThese 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.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.SliversIn 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 CaveatsSome 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

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.

County boundaries within TRPA jurisdiction. It was derived from the U.S. Geological Survey State Boundaries, which were derived from Digital Line Graph (DLG) files representing the 1:2,000,000-scale map in the National Atlas of the United States.

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.This dataset is continuously updated as the source data from CDTFA 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.PurposeCounty 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 LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities 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 BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative 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 except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: 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 SystemGNIS_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 SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_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.AccuracyCDTFA"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 territory; COPRI = county number followed by the 3-digit city primary number used in the California State 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).Boundary ProcessingThese 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.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.SliversIn 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 CaveatsSome 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 UseThis 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).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

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.This dataset is regularly updated as the source data from CDTFA 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. 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 LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal Buffers (this dataset)Counties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities 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 BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon) Working with Coastal Buffers The dataset you are currently viewing includes 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 except OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov Field and Abbreviation DefinitionsCDTFA_CITY: CDTFA incorporated city nameCDTFA_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 BureauCENSUS_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 SystemGNIS_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 countyCENSUS_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. Boundary AccuracyCounty 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.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 is 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. 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: 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 ProcessingThese 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. 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. SliversIn 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 CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These

This dataset contains the county boundaries that make up the Southern California Association of Governments service area. These county boundaries are consistent with the LAFCO city boundaries as of 08/2016 (Ver. 1.0).

Feature layer of the Counties in California as used by Cal OES. Columns designating CalOES Regions, Fire and Law Mutual Aid Regions, and county name.

The 1998 Dress Rehearsal was conducted as a prelude to the United States Census of Population and Housing, 2000, in the following locations: (1) Columbia, South Carolina, and surrounding areas, including the town of Irmo and the counties of Chester, Chesterfield, Darlington, Fairfield, Kershaw, Lancaster, Lee, Marlboro, Newberry, Richland, and Union, (2) Sacramento, California, and (3) Menominee County, Wisconsin, including the Menominee American Indian Reservation. This collection contains map files showing various levels of geography (in the form of Census Tract Outline Maps, Voting District/State Legislative District Outline Maps, and County Block Maps), TIGER/Line digital files, and Corner Point files for the Census 2000 Dress Rehearsal sites. The Corner Point data files contain the bounding latitude and longitude coordinates for each individual map sheet of the 1998 Dress Rehearsal Public Law (P.L.) 94-171 map products. These files include a sheet identifier, minimum and maximum longitude, minimum and maximum latitude, and the map scale (integer value) for each map sheet. The latitude and longitude coordinates are in decimal degrees and expressed as integer values with six implied decimal places. There is a separate Corner Point File for each of the three map types: County Block Map, Census Tract Outline Map, and Voting District/State Legislative District Outline Map. Each of the three map file types is provided in two formats: Portable Document Format (PDF), for viewing, and Hewlett-Packard Graphics Language (HP-GL) format, for plotting. The County Block Maps show the greatest detail and the most complete set of geographic information of all the maps. These large-scale maps depict the smallest geographic entities for which the Census Bureau presents data -- the census blocks -- by displaying the features that delineate them and the numbers that identify them. These maps show the boundaries, names, and codes for American Indian/Alaska Native areas, county subdivisions, places, census tracts, and, for this series, the geographic entities that the states delineated in Phase 2, Voting District Project, of the Redistricting Data Program. The HP-GL version of the County Block Maps is broken down into index maps and map sheets. The map sheets cover a small area, and the index maps are composed of multiple map sheets, showing the entire area. The intent of the County Block Map series is to provide a map for each county on the smallest possible number of map sheets at the maximum practical scale, dependent on the area size of the county and the density of the block pattern. The latter affects the display of block numbers and feature identifiers. The Census Tract Outline Maps show the boundaries and numbers of census tracts, and name the features underlying the boundaries. These maps also show the boundaries and names of counties, county subdivisions, and places. They identify census tracts in relation to governmental unit boundaries. The mapping unit is the county. These large-format maps are produced to support the P.L. 94-171 program and all other 1998 Dress Rehearsal data tabulations. The Voting District/State Legislative District Outline Maps show the boundaries and codes for voting districts as delineated by the states in Phase 2, Voting District Project, of the Redistricting Data Program. The features underlying the voting district boundaries are shown, as well as the names of these features. Additionally, for states that submit the information, these maps show the boundaries and codes for state legislative districts and their underlying features. These maps also show the boundaries of and names of American Indian/Alaska Native areas, counties, county subdivisions, and places. The scale of the district maps is optimized to keep the number of map sheets for each area to a minimum, but the scale and number of map sheets will vary by the area size of the county and the voting districts and state legislative districts delineated by the states. The Census 2000 Dress Rehearsal TIGER/Line Files consist of line segments representing physical features and governmental and statistical boundaries. The files contain information distributed over a series of record types for the spatial objects of a county. These TIGER/Line Files are an extract of selected geographic and cartographic information from the Census TIGER (Topological

This is SCAG’s 2019 city boundary data (v.1.0), updated as of July 6, 2021, including the boundaries for each of the 191 cities and 6 county unincorporated areas in the SCAG region. The original city boundary data was obtained from county LAFCOs to reflect the most current updates and annexations to the city boundaries. This data will be further reviewed and updated as SCAG continues to receive feedbacks from LAFCOs, subregions and local jurisdictions.Data-field description:COUNTY: County name COUNTY_ID: County FIPS CodeCITY: City NameCITY_ID: City FIPS CodeACRES: Area in acresSQMI: Area in square milesYEAR: Dataset year

Except as provided in Section 366, bear may be taken only as follows:(a) Areas:(1) Northern California: In the counties of Del Norte, Humboldt, Plumas, Shasta, Siskiyou, Tehama and Trinity; and those portions of Lassen and Modoc counties west of the following line: Beginning at Highway 395 and the Sierra-Lassen county line; north on Highway 395 to the junction of Highway 36; west on Highway 36 to the junction of Highway 139; north on Highway 139 to Highway 299; north on Highway 299 to County Road 87; west on County Road 87 to Lookout-Hackamore Road; north on Lookout-Hackamore Road to Highway 139; north on Highway 139 to the Modoc-Siskiyou county line; north on the Modoc-Siskiyou county line to the Oregon border.(2) Central California: In the counties of Alpine, Amador, Butte, Calaveras, Colusa, El Dorado, Glenn, Lake, Mendocino, Nevada, Placer, Sacramento, Sierra, Sutter, Yolo and Yuba and those portions of Napa and Sonoma counties northeast of Highway 128.(3) Southern Sierra: That portion of Kern County west of Highway 14 and east of the following line: Beginning at the intersection of Highway 99 and the Kern-Tulare county line; south on Highway 99 to Highway 166; west and south on Highway 166 to the Kern-Santa Barbara county line; and those portions of Fresno, Madera, Mariposa, Merced, Stanislaus, Tulare and Tuolumne counties east of Highway 99.(4) Southern California: In the counties of Los Angeles, Santa Barbara and Ventura; that portion of Riverside County north of Interstate 10 and west of Highway 62; and that portion of San Bernardino County south and west of the following line: Beginning at the intersection of Highway 18 and the Los Angeles-San Bernardino county line; east along Highway 18 to Highway 247; southeast on Highway 247 to Highway 62; southwest along Highway 62 to the Riverside-San Bernardino county line.(5) Southeastern Sierra: Those portions of Inyo and Mono counties west of Highway 395; and that portion of Madera County within the following line: Beginning at the junction of the Fresno-Madera-Mono county lines; north and west along the Madera-Mono county line to the boundary of the Inyo-Sierra National Forest; south along the Inyo-Sierra National Forest boundary to the Fresno-Madera county line; north and east on the Fresno-Madera county line to the point of beginning. Also, that portion of Inyo county west of Highway 395; and that portion of Mono county beginning at the intersection of Highway 6 and the Mono county line; north along Highway 6 to the Nevada state line; north along the Nevada state line to the Alpine county line; south along the Mono-Alpine county line to the Mono-Tuolumne county line and the Inyo National Forest Boundary; south along the Inyo National Forest Boundary to the Inyo-Sierra Forest boundary; south along the Inyo-Sierra Forest boundary to the Fresno-Madera county line; north and east along the Fresno-Madera county line to the junction of the Fresno-Madera-Mono county line; south along the Mono-Fresno county line to the Mono-Inyo County line; east along the Mono-Inyo county line to the point of beginning.

The data set for the Butler Peak quadrangle has been prepared by the Southern California Areal Mapping Project (SCAMP), a cooperative project sponsored jointly by the U.S. Geological Survey and the California Division of Mines and Geology, as part of an ongoing effort to utilize a Geographical Information System (GIS) format to create a regional digital geologic database for southern California. This regional database is being developed as a contribution to the National Geologic Map Data Base of the National Cooperative Geologic Mapping Program of the USGS. Development of the data set for the Butler Peak quadrangle has also been supported by the U.S. Forest Service, San Bernardino National Forest.

The digital geologic map database for the Butler Peak quadrangle has been created as a general-purpose data set that is applicable to other land-related investigations in the earth and biological sciences. For example, the U.S. Forest Service, San Bernardino National Forest, is using the database as part of a study of an endangered plant species that shows preference for particular rock type environments. The Butler Peak database is not suitable for site-specific geologic evaluations at scales greater than 1:24,000 (1 in = 2,000 ft).

This data set maps and describes the geology of the Butler Peak 7.5' quadrangle, San Bernardino County, California. Created using Environmental Systems Research Institute's ARC/INFO software, the data base consists of the following items: (1) a map coverage showing geologic contacts and units,(2) a scanned topographic base at a scale of 1:24,000, and (3) attribute tables for geologic units (polygons), contacts (arcs), and site-specific data (points). In addition, the data set includes the following graphic and text products: (1) A PostScript graphic plot-file containing the geologic map on a 1:24,000 topographic base accompanied by a Description of Map Units (DMU), a Correlation of Map Units (CMU), and a key to point and line symbols; (2) PDF files of the DMU and CMU, and of this Readme, and (3) this metadata file.

The geologic map data base contains original U.S. Geological Survey data generated by detailed field observation and by interpretation of aerial photographs. The map was created by transferring lines from the aerial photographs to a 1:24,000 mylar orthophoto-quadrangle and then to a base-stable topographic map. This map was then scribed, and a .007 mil, right-reading, black line clear film made by contact photographic processes.The black line was scanned and auto-vectorized by Optronics Specialty Company, Northridge, CA. The non-attributed scan was imported into ARC/INFO, where the database was built. Within the database, geologic contacts are represented as lines (arcs), geologic units as polygons, and site-specific data as points. Polygon, arc, and point attribute tables (.pat, .aat, and .pat, respectively) uniquely identify each geologic datum and link it to other tables (.rel) that provide more detailed geologic information.

This digital map database represents the general distribution of bedrock and surficial geologic units, and related data in the Fonts Point and Seventeen Palms 7.5’ quadrangles, California. The database delineates map units that are identified by general age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. This investigation delineates the geologic framework of an area of 75 square kilometers (km2) located west of the Salton Sea in southern California. The study area encompasses the south flank of the Santa Rosa Mountains and the eastern part of the Borrego Badlands. In this study area, regionally important stratigraphic and structural elements collectively inform the late Cenozoic geologic evolution of the Anza-Borrego sector of the Salton Trough province. This geodatabase contains all of the map information used to publish the Preliminary Geologic Map of the Southern Santa Rosa Mountains and Borrego Badlands, San Diego County, Southern Califo ...

Description for i03_DAU_county_cnty2018 is as follows:Detailed Analysis Unit-(DAU) Convergence via County Boundary cnty18_1 for Cal-Fire, (See metadata for CAL-FIRE cnty18_1), State of California.The existing DAU boundaries were aligned with cnty18_1 feature class.Originally a collaboration by Department of Water Resources, Region Office personnel, Michael L. Serna, NRO, Jason Harbaugh - NCRO, Cynthia Moffett - SCRO and Robert Fastenau - SRO with the final merge of all data into a cohesive feature class to create i03_DAU_COUNTY_cnty24k09 alignment which has been updated to create i03_DAU_COUNTY_cnty18_1.This version was derived from a preexisting “dau_v2_105, 27, i03_DAU_COUNTY_cnty24k09” Detailed Analysis Unit feature class's and aligned with Cal-Fire's 2018 boundary.Manmade structures such as piers and breakers, small islands and coastal rocks have been removed from this version. Inlets waters are listed on the coast only.These features are reachable by County\DAU. This allows the county boundaries, the DAU boundaries and the State of California Boundary to match Cal-Fire cnty18_1.DAU BackgroundThe first investigation of California's water resources began in 1873 when President Ulysses S. Grant commissioned an investigation by Colonel B. S. Alexander of the U.S. Army Corps of Engineers. The state followed with its own study in 1878 when the State Engineer's office was created and filled by William Hammond Hall. The concept of a statewide water development project was first raised in 1919 by Lt. Robert B. Marshall of the U.S. Geological Survey.In 1931, State Engineer Edward Hyatt introduced a report identifying the facilities required and the economic means to accomplish a north-to-south water transfer. Called the "State Water Plan", the report took nine years to prepare. To implement the plan, the Legislature passed the Central Valley Act of 1933, which authorized the project. Due to lack of funds, the federal government took over the CVP as a public works project to provide jobs and its construction began in 1935.In 1945, the California Legislature authorized an investigation of statewide water resources and in 1947, the California Legislature requested that an investigation be conducted of the water resources as well as present and future water needs for all hydrologic regions in the State. Accordingly, DWR and its predecessor agencies began to collect the urban and agricultural land use and water use data that serve as the basis for the computations of current and projected water uses.The work, conducted by the Division of Water Resources (DWR’s predecessor) under the Department of Public Works, led to the publication of three important bulletins: Bulletin 1 (1951), "Water Resources of California," a collection of data on precipitation, unimpaired stream flows, flood flows and frequency, and water quality statewide; Bulletin 2 (1955), "Water Utilization and Requirements of California," estimates of water uses and forecasts of "ultimate" water needs; and Bulletin 3 (1957), "The California Water Plan," plans for full practical development of California’s water resources, both by local projects and a major State project to meet the State's ultimate needs. (See brief addendum below “The Development of Boundaries for Hydrologic Studies for the Sacramento Valley Region”)DWR subdivided California into study areas for planning purposes. The largest study areas are the ten hydrologic regions (HR), corresponding to the State’s major drainage basins. The next levels of delineation are the Planning Areas (PA), which in turn are composed of multiple detailed analysis units (DAU). The DAUs are often split by county boundaries, so are the smallest study areas used by DWR.The DAU/counties are used for estimating water demand by agricultural crops and other surfaces for water resources planning. Under current guidelines, each DAU/County has multiple crop and land-use categories. Many planning studies begin at the DAU or PA level, and the results are aggregated into hydrologic regions for presentation.Since 1950 DWR has conducted over 250 land use surveys of all or parts of California's 58 counties. Early land use surveys were recorded on paper maps of USGS 7.5' quadrangles. In 1986, DWR began to develop georeferenced digital maps of land use survey data, which are available for download. Long term goals for this program is to survey land use more frequently and efficiently using satellite imagery, high elevation digital imagery, local sources of data, and remote sensing in conjunction with field surveys.There are currently 58 counties and 278 DAUs in California.Due to some DAUs being split by county lines, the total number of DAU’s identifiable via DAU by County is 782.ADDENDUMThe Development of Boundaries for Hydrologic Studies for the Sacramento Valley Region[Detailed Analysis Units made up of a grouping of the Depletion Study Drainage Areas (DSA) boundaries occurred on the Eastern Foothills and Mountains within the Sacramento Region. Other DSA’s were divided into two or more DAU’s; for example, DSA 58 (Redding Basin) was divided into 3 DAU’s; 143,141, and 145. Mountain areas on both the east and west side of the Sacramento River below Shasta Dam went from ridge top to ridge top, or topographic highs. If available, boundaries were set adjacent to stream gages located at the low point of rivers and major creek drainages.Later, as the DAU’s were developed, some of the smaller watershed DSA boundaries in the foothill and mountain areas were grouped. The Pit River DSA was split so water use in the larger valleys (Alturas area, Big Valley, Fall River Valley, Hat Creek) could be analyzed. A change in the boundary of the Sacramento Region mountain area occurred at this time when Goose Lake near the Oregon State Line was included as part of the Sacramento Region.The Sacramento Valley Floor hydrologic boundary was at the edge of the alluvial soils and slightly modified to follow the water bearing sediments to a depth of 200 feet or more. Stream gages were located on incoming streams and used as an exception to the alluvial soil boundary. Another exception to the alluvial boundary was the inclusion of the foothills between Red Bluff and the Redding Basin. Modifications of the valley floor exterior boundary were made to facilitate analysis; some areas at the northern end of the valley followed section lines or other established boundaries.Valley floor boundaries, as originally shown in Bulletin 2, Water Utilization and Requirements of California, 1955 were based on physical topographic features such as ridges even if they only rise a few feet between basins and/or drainage areas. A few boundaries were based on drainage canals. The Joint DWR-USBR Depletion Study Drainage Areas (DSA) used drainage areas where topographic highs drained into one drainage basin. Some areas were difficult to study, particularly in areas transected by major rivers. Depletion Study Drainage Areas containing large rivers were separated into two DAU’s; one on each side of the river. This made it easier to analyze water source, water supply, and water use and drainage outflow from the DAU.Many of the DAUs that consist of natural drainage basins have stream gages located at outfall gates, which provided an accurate estimate of water leaving the unit. Detailed Analysis Units based on political boundaries or other criteria are much more difficult to analyze than those units that follow natural drainage basins.]END ADDENDUM*

This table matches counties with their district in the California Courts of Appeal, with a record for each county matching it to the district it is in. Many counties make up each district, so there is a one to many relationship matching districts to counties.Working with California Courts Appeal Jurisdictions Download the data locally and join it to a county boundary layer based on County names.A CDT maintained California County Boundary and Identifiers layer can be found on the Geoportal for Download:https://gis.data.ca.gov/datasets/California::california-county-boundaries-and-identifiers/aboutA CDT maintained California County Boundary and Identifiers with Coastal Buffers layer can be found on the Geoportal for Download:https://gis.data.ca.gov/datasets/California::california-county-boundaries-and-identifiers-with-coastal-buffers/aboutJudicial Branch of California's webpage can be accessed at https://courts.ca.gov/policy-administration/judicial-councilPDF Maps provided by the Courts: https://courts.ca.gov/news-reference/reports-publications/maps For general Judicial Council questions please email JudicialCouncil@jud.ca.gov.For specific data related questions please email gis@state.ca.gov.This data was received from the Judicial Council on 9/2/25.Fields:District_Number: Text value for district number, including the word "District" - e.g. "District 2".

Description for i03_DAU_county_cnty2018 is as follows:Detailed Analysis Unit-(DAU) Convergence via County Boundary cnty18_1 for Cal-Fire, (See metadata for CAL-FIRE cnty18_1), State of California.The existing DAU boundaries were aligned with cnty18_1 feature class.Originally a collaboration by Department of Water Resources, Region Office personnel, Michael L. Serna, NRO, Jason Harbaugh - NCRO, Cynthia Moffett - SCRO and Robert Fastenau - SRO with the final merge of all data into a cohesive feature class to create i03_DAU_COUNTY_cnty24k09 alignment which has been updated to create i03_DAU_COUNTY_cnty18_1.This version was derived from a preexisting “dau_v2_105, 27, i03_DAU_COUNTY_cnty24k09” Detailed Analysis Unit feature class's and aligned with Cal-Fire's 2018 boundary.Manmade structures such as piers and breakers, small islands and coastal rocks have been removed from this version. Inlets waters are listed on the coast only.These features are reachable by County\DAU. This allows the county boundaries, the DAU boundaries and the State of California Boundary to match Cal-Fire cnty18_1.DAU BackgroundThe first investigation of California's water resources began in 1873 when President Ulysses S. Grant commissioned an investigation by Colonel B. S. Alexander of the U.S. Army Corps of Engineers. The state followed with its own study in 1878 when the State Engineer's office was created and filled by William Hammond Hall. The concept of a statewide water development project was first raised in 1919 by Lt. Robert B. Marshall of the U.S. Geological Survey.In 1931, State Engineer Edward Hyatt introduced a report identifying the facilities required and the economic means to accomplish a north-to-south water transfer. Called the "State Water Plan", the report took nine years to prepare. To implement the plan, the Legislature passed the Central Valley Act of 1933, which authorized the project. Due to lack of funds, the federal government took over the CVP as a public works project to provide jobs and its construction began in 1935.In 1945, the California Legislature authorized an investigation of statewide water resources and in 1947, the California Legislature requested that an investigation be conducted of the water resources as well as present and future water needs for all hydrologic regions in the State. Accordingly, DWR and its predecessor agencies began to collect the urban and agricultural land use and water use data that serve as the basis for the computations of current and projected water uses.The work, conducted by the Division of Water Resources (DWR’s predecessor) under the Department of Public Works, led to the publication of three important bulletins: Bulletin 1 (1951), "Water Resources of California," a collection of data on precipitation, unimpaired stream flows, flood flows and frequency, and water quality statewide; Bulletin 2 (1955), "Water Utilization and Requirements of California," estimates of water uses and forecasts of "ultimate" water needs; and Bulletin 3 (1957), "The California Water Plan," plans for full practical development of California’s water resources, both by local projects and a major State project to meet the State's ultimate needs. (See brief addendum below “The Development of Boundaries for Hydrologic Studies for the Sacramento Valley Region”)DWR subdivided California into study areas for planning purposes. The largest study areas are the ten hydrologic regions (HR), corresponding to the State’s major drainage basins. The next levels of delineation are the Planning Areas (PA), which in turn are composed of multiple detailed analysis units (DAU). The DAUs are often split by county boundaries, so are the smallest study areas used by DWR.The DAU/counties are used for estimating water demand by agricultural crops and other surfaces for water resources planning. Under current guidelines, each DAU/County has multiple crop and land-use categories. Many planning studies begin at the DAU or PA level, and the results are aggregated into hydrologic regions for presentation.Since 1950 DWR has conducted over 250 land use surveys of all or parts of California's 58 counties. Early land use surveys were recorded on paper maps of USGS 7.5' quadrangles. In 1986, DWR began to develop georeferenced digital maps of land use survey data, which are available for download. Long term goals for this program is to survey land use more frequently and efficiently using satellite imagery, high elevation digital imagery, local sources of data, and remote sensing in conjunction with field surveys.There are currently 58 counties and 278 DAUs in California.Due to some DAUs being split by county lines, the total number of DAU’s identifiable via DAU by County is 782.ADDENDUMThe Development of Boundaries for Hydrologic Studies for the Sacramento Valley Region[Detailed Analysis Units made up of a grouping of the Depletion Study Drainage Areas (DSA) boundaries occurred on the Eastern Foothills and Mountains within the Sacramento Region. Other DSA’s were divided into two or more DAU’s; for example, DSA 58 (Redding Basin) was divided into 3 DAU’s; 143,141, and 145. Mountain areas on both the east and west side of the Sacramento River below Shasta Dam went from ridge top to ridge top, or topographic highs. If available, boundaries were set adjacent to stream gages located at the low point of rivers and major creek drainages.Later, as the DAU’s were developed, some of the smaller watershed DSA boundaries in the foothill and mountain areas were grouped. The Pit River DSA was split so water use in the larger valleys (Alturas area, Big Valley, Fall River Valley, Hat Creek) could be analyzed. A change in the boundary of the Sacramento Region mountain area occurred at this time when Goose Lake near the Oregon State Line was included as part of the Sacramento Region.The Sacramento Valley Floor hydrologic boundary was at the edge of the alluvial soils and slightly modified to follow the water bearing sediments to a depth of 200 feet or more. Stream gages were located on incoming streams and used as an exception to the alluvial soil boundary. Another exception to the alluvial boundary was the inclusion of the foothills between Red Bluff and the Redding Basin. Modifications of the valley floor exterior boundary were made to facilitate analysis; some areas at the northern end of the valley followed section lines or other established boundaries.Valley floor boundaries, as originally shown in Bulletin 2, Water Utilization and Requirements of California, 1955 were based on physical topographic features such as ridges even if they only rise a few feet between basins and/or drainage areas. A few boundaries were based on drainage canals. The Joint DWR-USBR Depletion Study Drainage Areas (DSA) used drainage areas where topographic highs drained into one drainage basin. Some areas were difficult to study, particularly in areas transected by major rivers. Depletion Study Drainage Areas containing large rivers were separated into two DAU’s; one on each side of the river. This made it easier to analyze water source, water supply, and water use and drainage outflow from the DAU.Many of the DAUs that consist of natural drainage basins have stream gages located at outfall gates, which provided an accurate estimate of water leaving the unit. Detailed Analysis Units based on political boundaries or other criteria are much more difficult to analyze than those units that follow natural drainage basins.]END ADDENDUM*