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.

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

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.

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

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. 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)State BoundaryWith Bay CutsWithout Bay Cuts 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, gis@state.ca.gov Field 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 San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these

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.

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

This web map displays the California Department of Education's (CDE) core set of geographic data layers. This content represents the authoritative source for all statewide public school site locations and school district service areas boundaries for the 2018-19 academic year. The map also includes school and district layers enriched with student demographic and performance information from the California Department of Education's data collections. These data elements add meaningful statistical and descriptive information that can be visualized and analyzed on a map and used to advance education research or inform decision making.

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 California Pettinga, J.R., Dudash, S.L., and Cossette, P.M., 2023, Preliminary Geologic Map of the Southern Santa Rosa Mountains and Borrego Badlands, San Diego County, Southern California: U.S. Geological Survey Open-File Report 2023–1076, scale 1:12,000, https://doi.org/10.3133/ofr20231076.

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

This digital dataset is comprised of two separate data files that contain total dissolved solids, well construction, and well identifying information for 1,131 petroleum wells used to map salinity in and around 31 southern and central California oil fields. Salinity mapping was done for 27 fields located in the southern San Joaquin Valley of Kern County (North Belridge, South Belridge, Canfield Ranch, North Coles Levee, South Coles Levee, Cymric, Edison, Elk Hills, Fruitvale, Greeley, Jasmin, Kern Bluff, Kern Front, Kern River, Lost Hills, Mount Poso, Mountain View, Poso Creek, Rio Bravo, Rosedale, Rosedale Ranch, Round Mountain, San Emidio Nose, Tejon, Ten Section, Wheeler Ridge, and Yowlumne), 3 fields in the Los Angeles (LA) Basin of Los Angeles County (Montebello, Santa Fe Springs, and Wilmington), and 1 field in the central coast area of Santa Barbara and San Luis Obispo Counties (Santa Maria Valley). Only petroleum wells that were located within the administrative boundaries ...

This map shows cases broken down by the county level and city level in Southern California.

Second edition. Shows the different temperature zones of the state by use of color. Also used as a promotional broadside for the Southern Pacific Railroad. Above the map reads "If You Intend To Travel Take The "Sunset Route" Of The Southern Pacific Company."

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 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".County: Text name of each county, without the word "County" - this field may be joined to the field "CDT_Name_Short" in the previously linked datasets.

This geodatabase contains all of the map information used to publish the Surficial Geologic Map of the Owlshead Mountains 30’ X 60’ Quadrangle,Inyo and San Bernardino Counties, California: U.S. Geological Survey Scientific Investigations Map SIM-3496. The geodatabase and associated map delineate primarily surficial geology and neotectonics structure across the entire extent of this quadrangle, which includes 32 complete 7.5’ quadrangles located in the Owlshead Mountains, southern Death Valley, and adjoining basins and highlands in the southwestern section of Inyo County and the northeastern part of San Bernardino County in eastern California. The datasets contained in this Scientific Investigation Map describe the surficial geology within the entire map area of the Owlshead Mountains (OM) 30' X 60' Quadrangle. The geodatabase and associated geologic map delineate primarily surficial geology and neotectonics structure across the entire extent of this quadrangle, which includes 32 complete 7.5' quadrangles located in the southwestern section of Inyo County and the northeastern part of San Bernardino County in eastern California. The map encompasses a sparsely populated area that includes the southeastern corner of Death Valley National Park (DVNP) and the northeastern corner of the Fort Irwin Military Reservation, with a complex intermixture of public lands, mostly with the U. S. Bureau of Land Management, interspersed with many small scattered private holdings (mostly ranch land) and the few small municipalities of Shoshone and Tecopa. The map area encompasses a complex and diverse physiographic area dominated by the prominent feature of southern Death Valley (SDV), which is a major wide, continuous, and deep topographic trough that curves south and southeastward through the center map before connecting into the broad lowland areas of Valjean and Silurian Valleys in the eastern and southeastern map corner. The SDV trough is bounded on the northeast by the mountainous crest of the southern Black Mountains which merges northeastward into a series of north- to northeast-trending ranges and intervening valleys including Tecopa, Chicago, and southern California Valleys and the southern Resting Springs and Nopah Ranges. To the west and southwest of SDV lie the southern highlands of the Panamint Range, and Owlshead, Avawatz, and northern Granite Mountains, surrounding the linear east-trending valley of Leach Lake basin on the southwest corner of the map. The map and geodatabase for the Owlshead Mountains quadrangle was generated entirely from data originated by the database authors based primarily on new systematic photointerpretation supported by field traverses in selected areas. The geodatabase catalogues the complex geology and tectonic features responsible for producing this complex terrain. The map emphasizes spatial patterns of Quaternary sedimentation, erosion, and active deformation affecting landscape evolution in the area. Key elements of the map are a complex suite of (a) over 170 aggradational single and composite surficial units classified by both geologic age and genetic process (e.g., alluvial- and debris-flow fan, wash, axial valley, eolian, playa, lacustrine, groundwater discharge, and mass-wasting deposits,) and (b) degradational units (pediment surfaces). The surficial units overlie a generalized set of pre-Quaternary map units recognized for their potential relevance to physical and genetic attributes of the Quaternary deposits. The map also identifies an array of faults and folds, including several fault-related folds, that are differentiated by geometry and (or) slip type. Map compilation efforts emphasized the systematic depiction of surficial units and structures essential to time-space interpretations of deposition and dissection, surface-drainage evolution, and neotectonic deformation across this region. The mapped distribution and age of alluvial and fluvial deposits clearly define spatial and temporal patterns of deposition, mainly concentrated in the central trough of SDV, that contrast with areas in adjoining highlands where drainage incision is persistent. These data provide input to time-space reconstructions of regional drainages such as the lower Amargosa River. Mapped traces of faults and folds define complex and widespread neotectonic deformation centered in SDV and areas to the south and west. Active deformation is characterized by: (a) three to four regional sets of commonly intersecting dextral and sinistral translational faults (including the SDV and eastern Garlock faults); (b) zones of contraction (thrust faults and associated folds, transpressive structures, and fold belts) and uplift commonly concentrated at major fault intersections, and (c) zones of downwarping and uplift that form many of the basinal troughs (e.g. SDV) and adjoining highlands.

This file contains the official subregional boundaries for the SCAG region (Ventura, Los Angeles, San Bernardino, Orange, Riverside and Imperial counties). The file has been updated as of 08/13 to incorporate changes in WRCOG and CVAG in County of Riverside. All subregional boundaries are consistent with the 2012 city boundaries whenever they overlap. The SCAG Data Services Program was initiated and organized starting in the late 1980s with the goal of being the preeminent source of information for the Southern California region. The purpose of the program is to derive and promote a model policy for distributing geospatial data and other information developed and maintained at SCAG. We believe so strongly in providing this service to stakeholders that we have incorporated this philosophy into our Ten Year Strategic Plan. Our services are available to government agencies and private businesses without any fees. Our information is used by local government, public agencies, consultants, academia, students and the general public. Our information is designed for use in plans, studies, analyses, and presentations.

The data set for the Porcupine Wash 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. The Porcupine Wash data set represents part of an ongoing effort to create a regional GIS geologic database for southern California. This regional digital database, in turn, is being developed as a contribution to the National Geologic Map Database of the National Cooperative Geologic Mapping Program of the USGS. The Porcupine Wash database has been prepared in cooperation with the National Park Service as part of an ongoing project to provide Joshua Tree National Park with a geologic map base for use in managing Park resources and developing interpretive materials.

The digital geologic map database for the Porcupine Wash quadrangle has been created as a general-purpose data set that is applicable to land-related investigations in the earth and biological sciences. Along with geologic map databases in preparation for adjoining quadrangles, the Porcupine Wash database has been generated to further our understanding of bedrock and surficial processes at work in the region and to document evidence for seismotectonic activity in the eastern Transverse Ranges. The database is designed to serve as a base layer suitable for ecosystem and mineral resource assessment and for building a hydrogeologic framework for Pinto Basin.

This data set maps and describes the geology of the Porcupine Wash 7.5 minute quadrangle, Riverside County, southern California. The quadrangle, situated in Joshua Tree National Park in the eastern Transverse Ranges physiographic and structural province, encompasses parts of the Hexie Mountains, Cottonwood Mountains, northern Eagle Mountains, and south flank of Pinto Basin. It is underlain by a basement terrane comprising Proterozoic metamorphic rocks, Mesozoic plutonic rocks, and Mesozoic and Mesozoic or Cenozoic hypabyssal dikes. The basement terrane is capped by a widespread Tertiary erosion surface preserved in remnants in the Eagle and Cottonwood Mountains and buried beneath Cenozoic deposits in Pinto Basin. Locally, Miocene basalt overlies the erosion surface. A sequence of at least three Quaternary pediments is planed into the north piedmont of the Eagle and Hexie Mountains, each in turn overlain by successively younger residual and alluvial deposits.

The Tertiary erosion surface is deformed and broken by north-northwest-trending, high-angle, dip-slip faults and an east-west trending system of high-angle dip- and left-slip faults. East-west trending faults are younger than and perhaps in part coeval with faults of the northwest-trending set.

The Porcupine Wash database was created using ARCVIEW and ARC/INFO, which are geographical information system (GIS) software products of Environmental Systems Research Institute (ESRI). The database consists of the following items: (1) a map coverage showing faults and geologic contacts and units, (2) a separate coverage showing dikes, (3) a coverage showing structural data, (4) a scanned topographic base at a scale of 1:24,000, and (5) attribute tables for geologic units (polygons and regions), contacts (arcs), and site-specific data (points). The database, accompanied by a pamphlet file and this metadata file, also includes the following graphic and text products: (1) A portable document file (.pdf) containing a navigable graphic of the geologic map on a 1:24,000 topographic base. The map is accompanied by a marginal explanation consisting of a Description of Map and Database Units (DMU), a Correlation of Map and Database Units (CMU), and a key to point-and line-symbols. (2) Separate .pdf files of the DMU and CMU, individually. (3) A PostScript graphic-file containing the geologic map on a 1:24,000 topographic base accompanied by the marginal explanation. (4) A pamphlet that describes the database and how to access it. Within the database, geologic contacts , faults, and dikes are represented as lines (arcs), geologic units as polygons and regions, 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.

Map nomenclature and symbols

Within the geologic map database, map units are identified by standard geologic map criteria such as formation-name, age, and lithology. The authors have attempted to adhere to the stratigraphic nomenclature of the U.S. Geological Survey and the North American Stratigraphic Code, but the database has not received a formal editorial review of geologic names.

Special symbols are associated with some map units. Question marks have been added to the unit symbol (e.g., QTs?, Prpgd?) and unit name where unit assignment based on interpretation of aerial photographs is uncertain. Question marks are plotted as part of the map unit symbol for those polygons to which they apply, but they are not shown in the CMU or DMU unless all polygons of a given unit are queried. To locate queried map-unit polygons in a search of database, the question mark must be included as part of the unit symbol.

Geologic map unit labels entered in database items LABL and PLABL contain substitute characters for conventional stratigraphic age symbols: Proterozoic appears as 'Pr' in LABL and as '<' in PLABL, Triassic appears as 'Tr' in LABL and as '^' in PLABL. The substitute characters in PLABL invoke their corresponding symbols from the GeoAge font group to generate map unit labels with conventional stratigraphic symbols.

This file contains the official subregional boundaries for the SCAG region. The file has been updated as of 08/13 to incorporate changes in WRCOG and CVAG in County of Riverside. All subregional boundaries are consistent with the 2012 city boundaries whenever they overlap.