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.

In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata.A dataset was made available (approximately 2004) through CALFIRE - FRAP and the California Spatial Information Library (CaSIL), with additional updates throughout subsequent years. More recently, an effort was made to improve the coastal linework by using the previous interior linework from the 24k data, but replacing the coastal linework based on NOAA's ERMA coastal dataset (which used NAIP 2010). In this dataset, all bays (plus bay islands and constructed features) are merged into the mainland, and coastal features (such as islands and constructed features) are not included, with the exception of the Channel Islands which ARE included.This service represents the latest released version, and is updated when new versions are released. As of June, 2019 it represents cnty19_1.

This feature service includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations. BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; 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. 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 BOE'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).

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.

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, odsdataservices@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.

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 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 (this dataset)
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)
• 
  

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@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.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

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

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.

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

This digital map database represents the general distribution of bedrock and surficial geologic units, and related data in the Fonts Point and Seventeen Palms 7.5’ quadrangles, California. The database delineates map units that are identified by general age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. This investigation delineates the geologic framework of an area of 75 square kilometers (km2) located west of the Salton Sea in southern California. The study area encompasses the south flank of the Santa Rosa Mountains and the eastern part of the Borrego Badlands. In this study area, regionally important stratigraphic and structural elements collectively inform the late Cenozoic geologic evolution of the Anza-Borrego sector of the Salton Trough province. This geodatabase contains all of the map information used to publish the Preliminary Geologic Map of the Southern Santa Rosa Mountains and Borrego Badlands, San Diego County, Southern California Pettinga, J.R., Dudash, S.L., and Cossette, P.M., 2023, Preliminary Geologic Map of the Southern Santa Rosa Mountains and Borrego Badlands, San Diego County, Southern California: U.S. Geological Survey Open-File Report 2023–1076, scale 1:12,000, https://doi.org/10.3133/ofr20231076.

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 =

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.

Power Outages by County

This data set of polygon features represents Riverside County's Incorporated City Boundaries. Topology has been run and all gaps and overlaps have been fixed. The data has been adjusted to match Riverside County Parcel Boundaries. The city name field is used to represent the citys' name. Every polygon that represents an incorporated city must have a city name. Data was spatially adjusted in 2020. Maintained by Adam Grim, 12/2020

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 shows cases broken down by the county level and city level in Southern California.

The California Department of Fish and Game (CDFG) contracted with the California Native Plant Society (CNPS) and Aerial Information Systems (AIS) to produce an alliance-level, vegetation classification and map of Western Riverside County, California. The resulting classification and map products will be used to help establish a monitoring basis for the vegetation and habitats of the Western Riverside County Multi-Species Habitat Conservation Plan (MSHCP). The plan aims to conserve over 500,000 acres of land out of the 1.26 million acre total. This area is the largest MSHCP ever attempted and is an integral piece of the network of Southern California Habitat Conservation Plans and Natural Community Conservation Planning (Dudek 2001, Dudek 2003). Riverside County is one of the fastest growing counties in California, as well as one of the most biodiverse counties in the United States. A wide array of habitats are found within the non-developed lands in Western Riverside County, including coastal sage scrub, vernal pools, montane coniferous forest, chaparral, foothill woodland, annual grassland, and desert. In the CNPS contract, vegetation resources were assessed quantitatively through field surveys, data analysis, and final vegetation classification. Field survey data were analyzed statistically to come up with a floristically-based classification. Each vegetation type sampled was classified according to the National Vegetation Classification System to the alliance level (and association level if possible). The vegetation alliances were described floristically and environmentally in standard descriptions, and a final key was produced to differentiate among 101 alliances, 169 associations, and 3 unique stands (for final report, see http://maps.dfg.ca.gov/references/ds170 ). In a parallel but separate effort by AIS (as reported in this dataset), vegetation mapping was undertaken through interpretation of ortho-rectified, aerial photographs for vegetation signatur

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 data set maps and describes the geology of the San Bernardino Wash 7.5 minute quadrangle, Riverside County, southern California. The quadrangle, situated in Joshua Tree National Park in the eastern Transverse Ranges physiographic and structural province, encompasses parts of the northwestern Eagle Mountains, east-central Pinto Basin, and eastern Pinto Mountains. The quadrangle is underlain by a basement terrane comprising metamorphosed Proterozoic strata, Mesozoic plutonic rocks, and Jurassic and Mesozoic and (or) Cenozoic hypabyssal dikes. The basement terrane is capped by a widespread Tertiary erosion surface preserved in remnants in the Pinto and Eagle Mountains and buried beneath Cenozoic deposits in Pinto Basin. Locally, a cover of Miocene sedimentary deposits and basalt overlie the erosion surface. A sequence of at least three Quaternary pediments is planed into the north piedmont of the Eagle Mountains, each in turn overlain by successively younger residual and alluvial, surficial deposits. The Tertiary erosion surface is deformed and broken by north-northwest-trending, high-angle, dip-slip faults in the Pinto and Eagle Mountains and an east-west trending system of high-angle dip- and left-slip faults along the range fronts facing Pinto Basin. In and around the San Bernardino Wash quadrangle, faults of the north-northwest-trending set displace Miocene sedimentary rocks and basalt deposited on the Tertiary erosion surface and some of the faults may offset Pliocene and (or) Pleistocene deposits that accumulated on the oldest pediment. Faults of this system appear to be overlain by Pleistocene deposits that accumulated on younger pediments. East-west trending faults are younger than and perhaps in part coeval with faults of the northwest-trending set. The San Bernardino Wash database was created using ARCVIEW and ARC/INFO, which are geographical information system (GIS) software products of Envronmental Systems Research Institute (ESRI). The database comprises five coverages: (1) a geologic layer showing the distribution of geologic contacts and units; (2) a structural layer showing the distribution of faults (arcs) and fault ornamentation data (points); (3) a layer showing the distribution of dikes (arcs); a structural point data layer showing (4) bedding and metamorphic foliation attitudes, and (5) cartographic map elements, including unit label leaders and geologic unit annotation. The dataset also includes a scanned topographic base at a scale of 1:24,000. Within the database coverages, geologic contacts , faults, and dikes are represented as lines (arcs and routes), geologic units as areas (polygons and regions), and site-specific data as points. Polygon, region, arc, route, and point attribute tables uniquely identify each geologic datum and link it to descriptive tables that provide more detailed geologic information. The digital database is accompanied by two derivative maps: (1) A portable document file (.pdf) containing a navigable graphic of the geologic map on a 1:24,000 topographic base and (2) a PostScript graphic-file containing the geologic map on a 1:24,000 topographic base. Each of these map products is accompanied by a marginal explanation consisting of a Description of Map Units (DMU), a Correlation of Map Units (CMU), and a key to point and line symbols. The database is further accompanied by three document files: (1) a readme that lists the contents of the database and describes how to access it, (2) a pamphlet file that describes the geology of the quadrangle and (3) this metadata file.

The Yucaipa 7.5' quadrangle is located at the southeastern margin of the San Bernardino Basin, an extensional region situated within a right-step-over zone between the San Jacinto and San Andreas Fault zones. The quadrangle is traversed by several faults of the San Andreas system, including (from oldest to youngest) the Banning Fault and the Wilson Creek, Mission Creek, Mill Creek, and San Bernardino Strands of the San Andreas Fault. The Mill Creek Strand of the San Andreas Fault is the easternmost strand of the San Andreas in the Yucaipa quadrangle. It separates granitic and metamorphic rocks of the San Bernardino Mountains block from a thin slice of similar rocks on Yucaipa Ridge, and thus has only a small amount of strike-slip displacement. The Wilson Creek Strand traverses Yucaipa Ridge and converges toward the Mlll Creek Strand in the Santa Ana river Canyon. The fault has juxtaposed an igneous and metamorphic complex (Wilson Creek block) and overlying nonmarine sedimentary rocks (Mill Creek Formation of Gibson, 1971) against rocks of San Bernardino Mountains-type, and thus has significant strike-slip displacement. The Mission Creek Strand is inferred to lie beneath Quaternary surficial deposits along the southwestern base of the San Bernardino Mountains. This fault is the major strand of the San Andreas Fault zone, and has juxtaposed crystalline rocks of San Gabriel Mountains-type (including Pelona Schist overlain by the Vincent Thrust and associated upper-plate crystalline rocks) against the Wilson Creek block and the San Bernardino Mountains. The San Bernardino Strand defines the modern trace of the San Andreas Fault. The strand forms primary fault features in all but the youngest Quaternary surficial units, and is thought to have evolved in the last 125,000 years or so based on regional fault relations. Complications within the San Andreas Fault system over the last several hundred thousand years have created a landscape setting in which Quaternary surficial materials of the Yucaipa quadrangle have accumulated. Crustal extension throughout the San Bernardino Basin region led to uplift of the Crafton Hills block and down-dropping of the Yucaipa Valley region on faults of the Crafton Hills and Chicken Hill complex. Subsequent middle and late Quaternary streamflows deposited several generations of axial-valley and alluvial-fan sediment in the down-dropped lowlands. These deposits and the older San Timoteo beds they overlie record the history of Quaternary fault movements, and form reservoirs for ground water in the Yucaipa quadrangle. Digital Data: The geologic database of the Yucaipa 1:24,000-scale 7.5' quadrangle, San Bernardino and Riverside Counties, California, was prepared by the Southern California Areal Mapping Project (SCAMP), a regional geologic-mapping project sponsored jointly by the U.S. Geological Survey and the California Geological Survey. The database was created in ARC/INFO (Environmental Systems Research Institute, ESRI), and includes the following files: (1) a readme.txt file, (2) this metadata file, (3) coverages containing geologic data and station-location data, (4) associated INFO attribute data files, (5) a browse graphic (.pdf) of the geologic-map plot and map-marginal explanatory information, (6) a PostScript graphics file of the geologic-map plot with map-marginal explanatory information, and (7) .pdf text files describing the map units of the Yucaipa quadrangle (Description of Map Units) and their geologic age and correlation (Correlation of Map Units).