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.

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.

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

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.

These are the counties in California. Included is the CalOES Region and Mutual Aid Region Information.

ECM Community Support Services tables for a Quarterly Implementation Report. Including the County and Plan Details for both ECM and Community Support.This Medi-Cal Enhanced Care Management (ECM) and Community Supports Calendar Year Quarterly Implementation Report provides a comprehensive overview of ECM and Community Supports implementation in the programs' first year. It includes data at the state, county, and plan levels on total members served, utilization, and provider networks.ECM is a statewide MCP benefit that provides person-centered, community-based care management to the highest need members. The Department of Health Care Services (DHCS) and its MCP partners began implementing ECM in phases by Populations of Focus (POFs), with the first three POFs launching statewide in CY 2022.Community Supports are services that address members’ health-related social needs and help them avoid higher, costlier levels of care. Although it is optional for MCPs to offer these services, every Medi-Cal MCP offered Community Supports in 2022, and at least two Community Supports services were offered and available in every county by the end of the year.

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

The California State County Boundary data.

This dataset offers high-resolution boundary definitions, which allow users to analyze and visualize California’s county limits within mapping and spatial analysis projects.

The shapefile is part of a ZIP archive containing multiple related files that together define and support the boundary data. These files include:

.shp (Shape): This is the core file containing the vector data for California’s boundary, representing the geographic location and geometry of the state outline.

.shx (Shape Index): A companion index file for the .shp file, allowing for quick spatial queries and efficient data access.

.dbf (Attribute Table): A database file that stores attribute data linked to the geographic features in the .shp file, such as area identifiers or classification codes, in a tabular format compatible with database applications.

.prj (Projection): This file contains projection information, specifying the coordinate system and map projection used for the data, essential for aligning it accurately on maps.

.cpg (Code Page): This optional file indicates the character encoding for the attribute data in the .dbf file, which is useful for ensuring accurate text representation in various software.

.sbn and .sbx (Spatial Index): These files serve as a spatial index for the shapefile, allowing for faster processing of spatial queries, especially for larger datasets.

.xml (Metadata): A metadata file in XML format, often following FGDC or ISO standards, detailing the dataset’s origin, structure, and usage guidelines, providing essential information about data provenance and quality.

This comprehensive set of files ensures compatibility with most GIS software and allows users to perform a wide range of spatial analyses with detailed information on California’s boundary as defined by the U.S. Census Bureau's 2023 MAF/TIGER database.

The USGS, in cooperation with the U.S. Bureau of Land Management (BLM), created a series of geospatial mapping products of the Scotts Creek Watershed in Lake County, California, using National Agriculture Imagery Program (NAIP) imagery from 2018, 2020 and 2022 and Open Street Map (OSM) from 2019. The imagery was downloaded from United States Department of Agriculture (USDA) - Natural Resources Conservation Service (NRCS) Geospatial Data Gateway (https://datagateway.nrcs.usda.gov/) and Geofabrik GmbH - Open Street Map (https://www.geofabrik.de/geofabrik/openstreetmap.html), respectively. The imagery was classified using Random Forest (RF) Modeling to produce land cover maps with three main classifications - bare, vegetation, and shadows. An updated roads and trails map for the Upper Scotts Creek Watershed, including the BLM Recreational Area, was created to estimate road and trail densities in the watershed. Separate metadata records for each product (Land_Cover_Maps_Scotts_Creek_Watershed_CA_2018_2020_2022_metadata.xml, and Roads_and_Trails_Map_Upper_Scotts_Creek_Watershed_CA _2022_metadata.xml) are provided on the ScienceBase page for each child item. Users should be aware of the inherent errors in remote sensing products.

Counties in California intended for the NEVI Map.

Final approved map by the 2020 California Citizens Redistricting Commission for California's United States Congressional Districts; the authoritative and official delineations of California's United States Congressional Districts drawn during the 2020 redistricting cycle. The Citizens Redistricting Commission for the State of California has created statewide district maps for the State Assembly, State Senate, State Board of Equalization, and United States Congress in accordance, with the provisions of Article XXI of the California Constitution. The Commission has approved the final maps and certified them to the Secretary of State.Line drawing criteria included population equality as required by the U.S. Constitution, the Federal Voting Rights Act, geographic contiguity, geographic integrity, geographic compactness, and nesting. Geography was defined by U.S. Census Block geometry.Each of the 52 Congressional districts apportioned to California have an ideal population of 760,066, and the Commission adhered to federal constitutional mandates by requiring a district population deviation of no more than +/- one person. These districts also posed some of the Commission’s biggest challenges, and, because of strict population equality requirements, resulted in many more splits of counties, cities, neighborhoods, and communities of interest compared to State Assembly or Senate plans.

The East Bay Regional Park District (EBRPD) initiated this project to map the topography, physical and biotic features, and diverse plant communities of the east bay region. This project was funded by the California Department of Forestry and Fire Protection (CAL FIRE), the California State Coastal Conservancy (SCC), and California Department of Fish and Wildlife (CDFW) grants. The mapping study area, consists of approximately 987,000 acres of Alameda and Contra Costa counties. This 115-class fine scale vegetation map was completed in May 2025 and contains 140,442 polygons. The map is based on summer 2020 National Aerial Imagery Program (NAIP) imagery. The map additionally contains lidar-derived information about stand height, canopy cover, and percentage of impervious cover as well as canopy mortality data for each polygon. The minimum mapping unit (MMU) for this project ranges from 1/5 to 1 acre depending on feature type, and is described in detail in the mapping report (Tukman Geospatial, 2025). Development of the Alameda and Contra Costa fine scale vegetation map was managed by EBRPD and staffed by personnel from Tukman Geospatial. Field surveys were completed by trained botanists from the California Native Plant Society (CNPS), who were assisted by botanists from Nomad Ecology Consulting. Data from these surveys, combined with older surveys from previous efforts, were analyzed by the CNPS Vegetation Program, with support from the CDFW Vegetation Classification and Mapping Program (VegCAMP) to develop a county-specific vegetation classification. The floristic classification follows protocols compliant with the Federal Geographic Data Committee (FGDC) and National Vegetation Classification Standards (NVCS). For more information on the field sampling and vegetation classification work, refer to the final report issued by CNPS and corresponding floristic descriptions (Sikes et al., 2025), which are bundled with the vegetation map published for BIOS here: https://filelib.wildlife.ca.gov/Public/BDB/GIS/BIOS/Public_Datasets/3200_3299/ds3206.zipThe foundation for this vegetation map is an enhanced lifeform map produced in 2023 with funding from CAL FIRE. This lifeform map was developed using fine scale segmentation in Trimble® Ecognition® with machine learning and further manual image interpretation. In 2023-2025, Tukman Geospatial and Nomad Ecology staff conducted countywide reconnaissance field work. Field-collected data was used to train automated machine learning algorithms, which produced a semi-automated countywide fine scale vegetation and habitat map. Throughout 2024 and 2025, Tukman Geospatial manually edited the fine scale maps, and Tukman Geospatial and Nomad Ecology went to the field for validation trips to inform and improve the manual editing process. In 2025, input from Alameda and Contra Costa counties’ community of land managers and by the funders of the project was used to further refine the map.Accuracy assessment plot data were collected in 2025. Accuracy assessment results were compiled and analyzed May of 2025. The overall accuracy of the vegetation map by lifeform is 97%. The overall accuracy of the vegetation map by fine scale vegetation map class is 80.8%, with an overall ‘fuzzy’ accuracy of 93.1%.For a complete datasheet of the product, click here. Map class definitions, as well as a dichotomous key for the map classes, can be found in the Alameda and Contra Costa Fine Scale Vegetation Map Key (https://vegmap.press/alcc_mapping_key). A key to map class abbreviations is also available (https://vegmap.press/alcc_vegmap_abbrevs).

Vector polygon map data covering property parcels from Orange County, California containing 699,877 features.

Parcel map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

Parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

Available for viewing and sharing in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

Final approved map by the 2020 California Citizens Redistricting Commission for the California State Assembly; the authoritative and official delineations of the California State Assembly drawn during the 2020 redistricting cycle. The Citizens Redistricting Commission for the State of California has created statewide district maps for the State Assembly, State Senate, State Board of Equalization, and United States Congress in accordance, with the provisions of Article XXI of the California Constitution. The Commission has approved the final maps and certified them to the Secretary of State.Line drawing criteria included population equality as required by the U.S. Constitution, the Federal Voting Rights Act, geographic contiguity, geographic integrity, geographic compactness, and nesting. Geography was defined by U.S. Census Block geometry.80 Assembly districts have an ideal population of around 500,000 people each, and in consideration of population equality, the Commission chose to limit the population deviation range to as close to zero percent as practicable. With these districts, the Commission was able to respect many local communities of interest and group similar communities; however, it was more difficult to keep densely populated counties, cities, neighborhoods, and larger communities of interest whole due to the district size and correspondingly smaller number allowable in the population deviation percentage.

Final approved map by the 2020 California Citizens Redistricting Commission for the California State Senate; the authoritative and official delineations of the California State Senate drawn during the 2020 redistricting cycle. The Citizens Redistricting Commission for the State of California has created statewide district maps for the State Assembly, State Senate, State Board of Equalization, and United States Congress in accordance, with the provisions of Article XXI of the California Constitution. The Commission has approved the final maps and certified them to the Secretary of State.Line drawing criteria included population equality as required by the U.S. Constitution, the Federal Voting Rights Act, geographic contiguity, geographic integrity, geographic compactness, and nesting. Geography was defined by U.S. Census Block geometry.Each of the 40 Senate districts has an ideal population of nearly one million people and represents the largest state legislative districts in the nation. In consideration of population equality, the Commission chose to limit the population deviation as close to zero percent as practicable. Per the California Constitution, the Commission strived to nest two Assembly districts where practicable. However, higher ranking criteria made this difficult in practice. While the size of the Senate districts allowed the Commission to recognize broadly shared interests, these interests did not always overlap exactly with the interests of smaller communities recognized in the related Assembly districts. Based on the large number of people in each district, there were a variety of different interests that were balanced and included.

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax jurisdictions. The boundaries are continuously being revised when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the Board of Equalization's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

California State Assembly district boundaries intended for the NEVI map.Data downloaded in October 2024 from https://gis.data.ca.gov/maps/b31d93f08c074753b89f8cbb0b8beed9/about.

Shapefile contains county boundaries for the five counties that are included in the Bay Area Regional Climate Action Planning Initiative Frontline Communities Map.

The original shapefile was downloaded from the California Air Resources Board, Geographical Information System (GIS) Library. The “Select Layer By Attribute” tool in ArcMap was used to select only those five counties that are part of the Bay Area Regional Climate Action Planning Initiative. No display filters were used to visualize the features in the final map. To learn more about the methodology behind the original dataset, please visit: https://ww2.arb.ca.gov/geographical-information-system-gis-library

The Frontline Communities Map is meant to help identify communities that are considered frontline communities for the purpose of the USEPA’s Climate Pollution Reduction Grant (CPRG) program’s planning effort, which is a five-county climate action planning process led by the Air District. USEPA refers to these communities as low-income and disadvantaged communities (LIDACs).