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.

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.PurposeCity boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal Buffers (this dataset)Counties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal 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_CITY: CDTFA incorporated city nameCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections. Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor.CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information.CDTFA's source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is regularly updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. Purpose 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 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)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The 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, 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

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

Purpose

County 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, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• 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
• Place Name: CDTFA incorporated (city) or county name
• 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.
• Legal 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.
• 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 System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_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.

Accuracy

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. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

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.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal Buffers (this dataset)Without Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections. Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor.CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information.CDTFA's source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into

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

California State Lands Commission Offshore Oil Leases in the vicinity of Santa Barbara, Ventura, and Orange County.The polygons in this layer show the position of Offshore Oil Leases as documented by former State Lands Senior Boundary Determination Officer, Cris N. Perez and as reviewed and updated by GIS and Boundary staff.Background: This layer represents active offshore oil and gas agreements in California waters, which are what remain of the more than 60 originally issued. These leases were issued prior to the catastrophic 1969 oil spill from Platform A in federal waters off Santa Barbara County, and some predate the formation of the Commission. Between 2010 and 2014, the bulk of the approximately $300 million generated annually for the state's General Fund from oil and gas agreements was from these offshore leases.In 1921, the Legislature created the first tidelands oil and gas leasing program. Between 1921 and 1929, approximately 100 permits and leases were issued and over 850 wells were drilled in Santa Barbara and Ventura Counties. In 1929, the Legislature prohibited any new leases or permits. In 1933, however, the prohibition was partially lifted in response to an alleged theft of tidelands oil in Huntington Beach. It wasn't until 1938, and again in 1955, that the Legislature would allow new offshore oil and gas leasing. Except for limited circumstances, the Legislature has consistently placed limits on the areas that the Commission may offer for lease and in 1994, placed the entirety of California's coast off-limits to new oil and gas leases. Layer Creation Process:In 1997 Cris N. Perez, Senior Boundary Determination Officer of the Southern California Section of the State Lands Division, prepared a report on the Commission’s Offshore Oil Leases to:A. Show the position of Offshore Oil Leases. B. Produce a hard copy of 1927 NAD Coordinates for each lease. C. Discuss any problems evident after plotting the leases.Below are some of the details Cris included in the report:I have plotted the leases that were supplied to me by the Long Beach Office and computed 1927 NAD California Coordinates for each one. Where the Mean High Tide Line (MHTL) was called for and not described in the deed, I have plotted the California State Lands Commission CB Map Coordinates, from the actual field surveys of the Mean High Water Line and referenced them wherever used. Where the MHTL was called for and not described in the deed and no California State Lands Coordinates were available, I digitized the maps entitled, “Map of the Offshore Ownership Boundary of the State of California Drawn pursuant to the Supplemental Decree of the U.S. Supreme Court in the U.S. V. California, 382 U.S. 448 (1966), Scale 1:10000 Sheets 1-161.” The shore line depicted on these maps is the Mean Lower Low Water (MLLW) Line as shown on the Hydrographic or Topographic Sheets for the coastline. If a better fit is needed, a field survey to position this line will need to be done.The coordinates listed in Cris’ report were retrieved through Optical Character Recognition (OCR) and used to produce GIS polygons using Esri ArcGIS software. Coordinates were checked after the OCR process when producing the polygons in ArcMap to ensure accuracy. Original Coordinate systems (NAD 1927 California State Plane Zones 5 and 6) were used initially, with each zone being reprojected to NAD 83 Teale Albers Meters and merged after the review process.While Cris’ expertise and documentation were relied upon to produce this GIS Layer, certain polygons were reviewed further for any potential updates since Cris’ document and for any unusual geometry. Boundary Determination Officers addressed these issues and plotted leases currently listed as active, but not originally in Cris’ report. On December 24, 2014, the SLA boundary offshore of California was fixed (permanently immobilized) by a decree issued by the U.S. Supreme Court United States v. California, 135 S. Ct. 563 (2014). Offshore leases were clipped so as not to exceed the limits of this fixed boundary. Lease Notes:PRC 1482The “lease area” for this lease is based on the Compensatory Royalty Agreement dated 1-21-1955 as found on the CSLC Insider. The document spells out the distinction between “leased lands” and “state lands”. The leased lands are between two private companies and the agreement only makes a claim to the State’s interest as those lands as identified and surveyed per the map Tract 893, Bk 27 Pg 24. The map shows the State’s interest as being confined to the meanders of three sloughs, one of which is severed from the bay (Anaheim) by a Tideland sale. It should be noted that the actual sovereign tide and or submerged lands for this area is all those historic tide and submerged lands minus and valid tide land sales patents. The three parcels identified were also compared to what the Orange County GIS land records system has for their parcels. Shapefiles were downloaded from that site as well as two centerline monuments for 2 roads covered by the Tract 893. It corresponded well, so their GIS linework was held and clipped or extended to make a parcel.MJF Boundary Determination Officer 12/19/16PRC 3455The “lease area” for this lease is based on the Tract No. 2 Agreement, Long Beach Unit, Wilmington Oil Field, CA dated 4/01/1965 and found on the CSLC insider (also recorded March 12, 1965 in Book M 1799, Page 801).Unit Operating Agreement, Long Beach Unit recorded March 12, 1965 in Book M 1799 page 599.“City’s Portion of the Offshore Area” shall mean the undeveloped portion of the Long Beach tidelands as defined in Section 1(f) of Chapter 138, and includes Tract No. 1”“State’s Portion of the Offshore Area” shall mean that portion of the Alamitos Beach Park Lands, as defined in Chapter 138, included within the Unit Area and includes Tract No. 2.”“Alamitos Beach Park Lands” means those tidelands and submerged lands, whether filled or unfilled, described in that certain Judgment After Remittitur in The People of the State of California v. City of Long Beach, Case No. 683824 in the Superior Court of the State of California for the County of Los Angeles, dated May 8, 1962, and entered on May 15, 1962 in Judgment Book 4481, at Page 76, of the Official Records of the above entitled court”*The description for Tract 2 has an EXCEPTING (statement) “therefrom that portion lying Southerly of the Southerly line of the Boundary of Subsidence Area, as shown on Long Beach Harbor Department {LBHD} Drawing No. D-98. This map could not be found in records nor via a PRA request to the LBHD directly. Some maps were located that show the extents of subsidence in this area being approximately 700 feet waterward of the MHTL as determined by SCC 683824. Although the “EXCEPTING” statement appears to exclude most of what would seem like the offshore area (out to 3 nautical miles from the MHTL which is different than the actual CA offshore boundary measured from MLLW) the 1964, ch 138 grant (pg25) seems to reference the lands lying seaward of that MHTL and ”westerly of the easterly boundary of the undeveloped portion of the Long Beach tidelands, the latter of which is the same boundary (NW) of tract 2. This appears to then indicate that the “EXCEPTING” area is not part of the Lands Granted to City of Long Beach and appears to indicate that this portion might be then the “State’s Portion of the Offshore Area” as referenced in the Grant and the Unit Operating Agreement. Section “f” in the CSLC insider document (pg 9) defines the Contract Lands: means Tract No. 2 as described in Exhibit “A” to the Unit Agreement, and as shown on Exhibit “B” to the Unit Agreement, together with all other lands within the State’s Portion of the Offshore Area.Linework has been plotted in accordance with the methods used to produce this layer, with record lines rotated to those as listed in the descriptions. The main boundaries being the MHTL(north/northeast) that appears to be fixed for most of the area (projected to the city boundary on the east/southeast); 3 nautical miles from said MHTL on the south/southwest; and the prolongation of the NWly line of Block 50 of Alamitos Bay Tract.MJF Boundary Determination Officer 12-27-16PRC 4736The “lease area” for this lease is based on the Oil and Gas Lease and Agreement as found on the CSLC insider and recorded August 17, 1973 in BK 10855 PG 432 Official Records, Orange County. The State’s Mineral Interests are confined to Parcels “B-1” and “B-2” and are referred to as “State Mineral Lands” comprising 70.00 Acres. The lessee each has a right to certain uses including but not limited to usage of utility corridors, 110 foot radius parcels surrounding well-sites and roads. The State also has access to those same roads per this agreement/lease. Those uses are allowed in what are termed “State Lands”-Parcel E and “Leased Lands” which are defined as the “South Bolsa Lease Area”-Parcel C (2 parcels) and “North Bolsa Lease Area”-Parcel D. The “State Lands”-Parcel E are actually 3 parcels, 2 of which are within road right-of-ways. MJF Boundary Determination Officer 12-28-16

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

IntroductionThis metadata is broken up into different sections that provide both a high-level summary of the Housing Element and more detailed information about the data itself with links to other resources. The following is an excerpt from the Executive Summary from the Housing Element 2021 – 2029 document:The County of Los Angeles is required to ensure the availability of residential sites, at adequate densities and appropriate development standards, in the unincorporated Los Angeles County to accommodate its share of the regional housing need--also known as the Regional Housing Needs Allocation (RHNA). Unincorporated Los Angeles County has been assigned a RHNA of 90,052 units for the 2021-2029 Housing Element planning period, which is subdivided by level of affordability as follows:Extremely Low / Very Low (<50% AMI) - 25,648Lower (50 - 80% AMI) - 13,691Moderate (80 - 120% AMI) - 14,180Above Moderate (>120% AMI) - 36,533Total - 90,052NOTES - Pursuant to State law, the projected need of extremely low income households can be estimated at 50% of the very low income RHNA. Therefore, the County’s projected extremely low income can be estimated at 12,824 units. However, for the purpose of identifying adequate sites for RHNA, no separate accounting of sites for extremely low income households is required. AMI = Area Median IncomeDescriptionThe Sites Inventory (Appendix A) is comprised of vacant and underutilized sites within unincorporated Los Angeles County that are zoned at appropriate densities and development standards to facilitate housing development. The Sites Inventory was developed specifically for the County of Los Angeles, and has built-in features that filter sites based on specific criteria, including access to transit, protection from environmental hazards, and other criteria unique to unincorporated Los Angeles County. Other strategies used within the Sites Inventory analysis to accommodate the County’s assigned RHNA of 90,052 units include projected growth of ADUs, specific plan capacity, selected entitled projects, and capacity or planned development on County-owned sites within cities. This accounts for approximately 38 percent of the RHNA. The remaining 62 percent of the RHNA is accommodated by sites to be rezoned to accommodate higher density housing development (Appendix B).Caveats:This data is a snapshot in time, generally from the year 2021. It contains information about parcels, zoning and land use policy that may be outdated. The Department of Regional Planning will be keeping an internal tally of sites that get developed or rezoned to meet our RHNA goals, and we may, in the future, develop some public facing web applications or dashboards to show the progress. There may even be periodic updates to this GIS dataset as well, throughout this 8-year planning cycle.Update History:1/7/25 - Following the completion of the annexation to the City of Whittier on 11/12/24, 27 parcels were removed along Whittier Blvd which contained 315 Very Low Income units and 590 Above Moderate units. Following a joint County-City resolution of the RHNA transfer to the city, 247 Very Low Income units and 503 Above Moderate units were taken on by Whittier. 10/16/24 - Modifications were made to this layer during the updates to the South Bay and Westside Area Plans following outreach in these communities. In the Westside Planning area, 29 parcels were removed and no change in zoning / land use policy was proposed; 9 Mixed Use sites were added. In the South Bay, 23 sites were removed as they no longer count towards the RHNA, but still partially changing to Mixed Use.5/31/22 – Los Angeles County Board of Supervisors adopted the Housing Element on 5/17/22, and it received final certification from the State of California Department of Housing and Community Development (HCD) on 5/27/22. Data layer published on 5/31/22.Links to other resources:Department of Regional Planning Housing Page - Contains Housing Element and it's AppendicesHousing Element Update - Rezoning Program Story Map (English, and Spanish)Southern California Association of Governments (SCAG) - Regional Housing Needs AssessmentCalifornia Department of Housing and Community Development Housing Element pageField Descriptions:OBJECTID - Internal GIS IDAIN - Assessor Identification Number*SitusAddress - Site Address (Street and Number) from Assessor Data*Use Code - Existing Land Use Code (corresponds to Use Type and Use Description) from Assessor Data*Use Type - Existing Land Use Type from Assessor Data*Use Description - Existing Land Use Description from Assessor Data*Vacant / Nonvacant – Parcels that are vacant or non-vacant per the Use Code from the Assessor Data*Units Total - Total Existing Units from Assessor Data*Max Year - Maximum Year Built from Assessor Data*Supervisorial District (2021) - LA County Board of Supervisor DistrictSubmarket Area - Inclusionary Housing Submarket AreaPlanning Area - Planning Areas from the LA County Department of Regional Planning General Plan 2035Community Name - Unincorporated Community NamePlan Name - Land Use Plan Name from the LA County Department of Regional Planning (General Plan and Area / Community Plans)LUP - 1 - Land Use Policy from Dept. of Regional Planning - Primary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 1 (% area) - Land Use Policy from Dept. of Regional Planning - Primary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*LUP - 2 - Land Use Policy from Dept. of Regional Planning - Secondary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 2 (% area) - Land Use Policy from Dept. of Regional Planning - Secondary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*LUP - 3 - Land Use Policy from Dept. of Regional Planning - Tertiary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 3 (% area) - Land Use Policy from Dept. of Regional Planning - Tertiary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*Current LUP (Description) – This is a brief description of the land use category. In the case of multiple land uses, this would be the land use category that covers the majority of the parcel*Current LUP (Min Density - net or gross) - Minimum density for this category (as net or gross) per the Land Use Plan for this areaCurrent LUP (Max Density - net or gross) - Maximum density for this category (as net or gross) per the Land Use Plan for this areaProposed LUP – Final – The proposed land use category to increase density.Proposed LUP (Description) – Brief description of the proposed land use policy.Prop. LUP – Final (Min Density) – Minimum density for the proposed land use category.Prop. LUP – Final (Max Density) – Maximum density for the proposed land use category.Zoning - 1 - Zoning from Dept. of Regional Planning - Primary Zone (in cases where there are more than one zone category present)*Zoning - 1 (% area) - Zoning from Dept. of Regional Planning - Primary Zone (% of parcel covered in cases where there are more than one zone category present)*Zoning - 2 - Zoning from Dept. of Regional Planning - Secondary Zone (in cases where there are more than one zone category present)*Zoning - 2 (% area) - Zoning from Dept. of Regional Planning - Secondary Zone (% of parcel covered in cases where there are more than one zone category present)*Zoning - 3 - Zoning from Dept. of Regional Planning - Tertiary Zone (in cases where there are more than one zone category present)*Zoning - 3 (% area) - Zoning from Dept. of Regional Planning - Tertiary Zone (% of parcel covered in cases where there are more than one zone category present)*Current Zoning (Description) - This is a brief description of the zoning category. In the case of multiple zoning categories, this would be the zoning that covers the majority of the parcel*Proposed Zoning – Final – The proposed zoning category to increase density.Proposed Zoning (Description) – Brief description of the proposed zoning.Acres - Acreage of parcelMax Units Allowed - Total Proposed Land Use Policy UnitsRHNA Eligible? – Indicates whether the site is RHNA Eligible or not. NOTE: This layer only shows those that are RHNA Eligible, but internal versions of this layer also show sites that were not-RHNA eligible, or removed during the development of this layer in 2020 – 2022.Very Low Income Capacity - Total capacity for the Very Low Income level as defined in the Housing ElementLow Income Capacity - Total capacity for the Low Income level as defined in the Housing ElementModerate Income Capacity - Total capacity for the Moderate Income level as defined in the Housing ElementAbove Moderate Income Capacity - Total capacity for the Above Moderate Income level as defined in the Housing ElementRealistic Capacity - Total Realistic Capacity of parcel (totaling all income levels). Several factors went into this final calculation. See the Housing Element (Links to Other Resources above) in the following locations - "Sites Inventory - Lower Income RHNA" (p. 223), and "Rezoning - Very Low / Low Income RHNA" (p231).Income Categories - Income Categories assigned to the parcel (relates to income capacity units)Lot Consolidation ID - Parcels with a unique identfier for consolidation potential (based on parcel ownership)Lot Consolidation Notes - Specific notes for consolidationConsolidation - Adjacent Parcels - All adjacent parcels that are tied to each lot consolidation IDsShape_Length - Perimeter (feet)Shape_Area - Area (sq feet)*As it existed in 2021

This map presents a tour of the City of Redlands, California using the detailed map of Redlands included in the community basemap. The City of Redlands is located in Southern California, about 65 miles east of Los Angeles. The map tour highlights some of the unique features in the history of Redlands as well as several of the places and events that make it a very livable community today.The map features a detailed basemap for the City of Redlands, California, including buildings, parcels, vegetation, land use, landmarks, streets, and more. The map features special detail for areas of high interest within the City, including local parks, landmarks, and the ESRI campus.The map references detailed GIS data provided by the City of Redlands, Department of Innovation and Technology, GIS Division. The map was authored using map templates available from ESRI, including:Topographic Map Template - Large ScalesCampus Basemap TemplateThe map was published as part of ESRI's Community Maps Program and is one of several detailed maps of cities and counties in the World Topographic Map.

Important Note:The metadata description below mentions the Regional Housing Needs Assessment (or RHNA). Part of meeting RHNA Eligibility is satisfying a list of criteria set by the State of California that needs to be met in order to qualify. This dataset contains both RHNA Eligible and non-RHNA Eligible sites. Non-RHNA Eligible sites are those that didn't quite meet the eligibility criteria set by the state, but will be still eligible for Rezoning per Department of Regional Planning guidelines, and thus represents a full picture of ALL sites that are eligible for Rezoning. The official Housing Element Rezoning layer that was certified by the State of California is located here, but it should be noted that this layer only contains sites that are RHNA Eligible.IntroductionThis metadata is broken up into different sections that provide both a high-level summary of the Housing Element and more detailed information about the data itself with links to other resources. The following is an excerpt from the Executive Summary from the Housing Element 2021 – 2029 document:The County of Los Angeles is required to ensure the availability of residential sites, at adequate densities and appropriate development standards, in the unincorporated Los Angeles County to accommodate its share of the regional housing need--also known as the Regional Housing Needs Allocation (RHNA). Unincorporated Los Angeles County has been assigned a RHNA of 90,052 units for the 2021-2029 Housing Element planning period, which is subdivided by level of affordability as follows:Extremely Low / Very Low (<50% AMI) - 25,648Lower (50 - 80% AMI) - 13,691Moderate (80 - 120% AMI) - 14,180Above Moderate (>120% AMI) - 36,533Total - 90,052NOTES - Pursuant to State law, the projected need of extremely low income households can be estimated at 50% of the very low income RHNA. Therefore, the County’s projected extremely low income can be estimated at 12,824 units. However, for the purpose of identifying adequate sites for RHNA, no separate accounting of sites for extremely low income households is required. AMI = Area Median IncomeDescriptionThe Sites Inventory (Appendix A) is comprised of vacant and underutilized sites within unincorporated Los Angeles County that are zoned at appropriate densities and development standards to facilitate housing development. The Sites Inventory was developed specifically for the County of Los Angeles, and has built-in features that filter sites based on specific criteria, including access to transit, protection from environmental hazards, and other criteria unique to unincorporated Los Angeles County. Other strategies used within the Sites Inventory analysis to accommodate the County’s assigned RHNA of 90,052 units include projected growth of ADUs, specific plan capacity, selected entitled projects, and capacity or planned development on County-owned sites within cities. This accounts for approximately 38 percent of the RHNA. The remaining 62 percent of the RHNA is accommodated by sites to be rezoned to accommodate higher density housing development (Appendix B).Caveats:This data is a snapshot in time, generally from the year 2021. It contains information about parcels, zoning and land use policy that may be outdated. The Department of Regional Planning will be keeping an internal tally of sites that get developed or rezoned to meet our RHNA goals, and we may, in the future, develop some public facing web applications or dashboards to show the progress. There may even be periodic updates to this GIS dataset as well, throughout this 8-year planning cycle.Update History:12/18/24 - Following the completion of the annexation to the City of Whittier on 11/12/24, 27 parcels were removed along Whittier Blvd which contained 315 Very Low Income units and 590 Above Moderate units. Following a joint County-City resolution of the RHNA transfer to the city, 247 Very Low Income units and 503 Above Moderate units were taken on by Whittier. 10/23/24 - Modifications were made to this layer during the updates to the South Bay and Westside Area Plans following outreach in these communities. In the Westside Planning area, 29 parcels were removed and no change in zoning / land use policy was proposed; 9 Mixed Use sites were added. In the South Bay, 23 sites were removed as they no longer count towards the RHNA, but still partially changing to Mixed Use.5/31/22 – Los Angeles County Board of Supervisors adopted the Housing Element on 5/17/22, and it received final certification from the State of California Department of Housing and Community Development (HCD) on 5/27/22. Data layer published on 5/31/22.Links to other resources:Department of Regional Planning Housing Page - Contains Housing Element and it's AppendicesHousing Element Update - Rezoning Program Story Map (English, and Spanish)Southern California Association of Governments (SCAG) - Regional Housing Needs AssessmentCalifornia Department of Housing and Community Development Housing Element pageField Descriptions:OBJECTID - Internal GIS IDAIN - Assessor Identification Number*SitusAddress - Site Address (Street and Number) from Assessor Data*Use Code - Existing Land Use Code (corresponds to Use Type and Use Description) from Assessor Data*Use Type - Existing Land Use Type from Assessor Data*Use Description - Existing Land Use Description from Assessor Data*Vacant / Nonvacant – Parcels that are vacant or non-vacant per the Use Code from the Assessor Data*Units Total - Total Existing Units from Assessor Data*Max Year - Maximum Year Built from Assessor Data*Supervisorial District (2021) - LA County Board of Supervisor DistrictSubmarket Area - Inclusionary Housing Submarket AreaPlanning Area - Planning Areas from the LA County Department of Regional Planning General Plan 2035Community Name - Unincorporated Community NamePlan Name - Land Use Plan Name from the LA County Department of Regional Planning (General Plan and Area / Community Plans)LUP - 1 - Land Use Policy from Dept. of Regional Planning - Primary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 1 (% area) - Land Use Policy from Dept. of Regional Planning - Primary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*LUP - 2 - Land Use Policy from Dept. of Regional Planning - Secondary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 2 (% area) - Land Use Policy from Dept. of Regional Planning - Secondary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*LUP - 3 - Land Use Policy from Dept. of Regional Planning - Tertiary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 3 (% area) - Land Use Policy from Dept. of Regional Planning - Tertiary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*Current LUP (Description) – This is a brief description of the land use category. In the case of multiple land uses, this would be the land use category that covers the majority of the parcel*Current LUP (Min Density - net or gross) - Minimum density for this category (as net or gross) per the Land Use Plan for this areaCurrent LUP (Max Density - net or gross) - Maximum density for this category (as net or gross) per the Land Use Plan for this areaProposed LUP – Final – The proposed land use category to increase density.Proposed LUP (Description) – Brief description of the proposed land use policy.Prop. LUP – Final (Min Density) – Minimum density for the proposed land use category.Prop. LUP – Final (Max Density) – Maximum density for the proposed land use category.Zoning - 1 - Zoning from Dept. of Regional Planning - Primary Zone (in cases where there are more than one zone category present)*Zoning - 1 (% area) - Zoning from Dept. of Regional Planning - Primary Zone (% of parcel covered in cases where there are more than one zone category present)*Zoning - 2 - Zoning from Dept. of Regional Planning - Secondary Zone (in cases where there are more than one zone category present)*Zoning - 2 (% area) - Zoning from Dept. of Regional Planning - Secondary Zone (% of parcel covered in cases where there are more than one zone category present)*Zoning - 3 - Zoning from Dept. of Regional Planning - Tertiary Zone (in cases where there are more than one zone category present)*Zoning - 3 (% area) - Zoning from Dept. of Regional Planning - Tertiary Zone (% of parcel covered in cases where there are more than one zone category present)*Current Zoning (Description) - This is a brief description of the zoning category. In the case of multiple zoning categories, this would be the zoning that covers the majority of the parcel*Proposed Zoning – Final – The proposed zoning category to increase density.Proposed Zoning (Description) – Brief description of the proposed zoning.Acres - Acreage of parcelMax Units Allowed - Total Proposed Land Use Policy UnitsRHNA Eligible? – Indicates whether the site is RHNA Eligible or not. Very Low Income Capacity - Total capacity for the Very Low Income level as defined in the Housing ElementLow Income Capacity - Total capacity for the Low Income level as defined in the Housing ElementModerate Income Capacity - Total capacity for the Moderate Income level as defined in the Housing ElementAbove Moderate Income Capacity - Total capacity for the Above Moderate Income level as defined in the Housing ElementRealistic Capacity - Total Realistic Capacity of parcel (totaling all income levels). Several factors went into this final calculation. See the Housing Element (Links to Other Resources above) in the following locations - "Sites Inventory - Lower Income RHNA" (p. 223), and "Rezoning - Very Low / Low Income RHNA" (p231).Income Categories - Income Categories assigned to the parcel (relates

This is the zoning layer for UNINCORPORATED areas of Los Angeles County. It does not draw at all scales because there are lots of records (so basically for speed and performance), so it is scale dependent. Also, why only for UNINCORPORATED areas? Because there are 88 cities in L.A. County and they each manage their zoning and land use information separately.

For more complete information, see Title 22 (Planning and Zoning) of the Los Angeles County Code, or visit the Department of Regional Planning's website here.

PLEASE NOTE: Santa Catalina Island is not included in this dataset. It is in a separate data layer since Catalina has specific zoning categories that differ from the Countywide zoning categories found in Title 22. The Department of Regional Planning performs all land use planning functions for the UNINCORPORATED areas of Los Angeles County. Our services include long range planning, land development counseling, project/case intake and processing, environmental review and zoning enforcement for each of our County UNINCORPORATED communities.What is an UNINCORPORATED area of Los Angeles County?There are 88 incorporated cities within Los Angeles County, each with its own city council. The areas that are NOT part of these cities are considered to be UNINCORPORATED County territory. More than 65 percent of Los Angeles County is UNINCORPORATED. For the approximately 1 million people living in these areas, the Board of Supervisors and County departments provide the municipal services.LAST UPDATED: 4/9/25 for several zone changes related to the South Bay, West San Gabriel, and Westside Area Plan updates. These updates took effect on 4/10/25.NEED MORE FUNCTIONALITY? If you are looking for more layers or advanced tools and functionality, then try our suite of GIS Web Mapping Applications.

Historic Preservation in Santa Monica websiteThe local preservation movement began in earnest as the City of Santa Monica responded to the increased development pressures taking place in Southern California cities during the 1960s and 1970s. The City Council, following the community interest in preserving local landmarks, adopted the Landmarks and Historic District Ordinance on March 24, 1976. City staff works closely with the Landmarks Commission to:Designate Historic Resources at the local levelMaintain a comprehensive Historic Resources Inventory Implement state guidelines regarding historic propertiesDistribute information on Benefits & Tax Incentives for LandmarksReview applications for Certificate of Appropriateness, Certificate of Administrative Approval, Certificate of Exemption, and Certificate of Economic HardshipTypes of DesignationsA historic resource may be a building, structure, site, object, district, or landscape that may be associated with historic events; associated with important historical persons; represent a rare type of historic property; or has architectural quality or importance.Local level designations are handled by the Landmarks Commission. The City’s Landmarks Commission decides whether a property should be a designated Structure of Merit, or Landmark, and makes a recommendation to City Council on Historic District designation, based on certain required findings contained in the Landmarks Ordinance. These official designations are for resources that are considered locally significant historic sites or areas.Historic Resources may also be designated at Federal or State levels. Federal designation is managed by the National Register of Historic Places. Information on State level designations may be obtained through the Office of Historic Preservation.LandmarksLandmarks are considered to have the highest level of individual historical or architectural significance. Therefore, along with contributing buildings located within historic districts, Landmarks are offered the highest protection with respect to alterations and demolitions.Structures of MeritStructures of Merit are historic resources with a more limited degree of individual significance. This designation requires special review for demolition permits.Historic DistrictsHistoric Districts are geographic areas or non-contiguous groupings of thematically related properties significant in that they contribute to the historic character of the area at a local level. Any area in the city can be designated a Historic District subject to the approval of City Council.

This map visualizes Primary Care Shortage Areas (PCSAs) across Los Angeles and Orange Counties, using data from the California Department of Health Care Access and Information (HCAI). PCSAs are defined as regions with insufficient primary care access, determined by a Total Score (0–10) calculated as the sum of two components: Poverty Score and Provider Score (clinician availability). Regions are classified by a Total Score (0–10) as follows:0–2 (Green): No shortage3–4 (Light Green/Yellow): Moderate shortage5–6 (Orange): Officially designated PCSA7–10 (Red): Severe shortageThe map also includes the locations of City of Hope (COH) campuses for reference. This enables analysis of potential correlations between care accessibility gaps and the distribution of major medical facilities.The goal of this map is to support health policy planning, equity analysis, and resource allocation decisions by identifying underserved communities within Southern California.📎 Data SourcesPrimary Care Shortage Area (PCSA) data: California Department of Health Care Access and Information (HCAI), accessed via CHHS Open Data Portal https://data.chhs.ca.gov/.COH Campus Locations: Provided by City of Hope.

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.