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

This 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

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.

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

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 =

Power Outages by County

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

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

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, the coastline is used to separate coastal buffers from 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 (this dataset)
   • Without Coastal Buffers
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

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 is SCAG's 2019 Annual Land Use (ALU v. 2019.1) at the parcel-level, updated as of February 2021. This dataset has been modified to include additional attributes in order to feed SCAG's Housing Element Parcel Tool (HELPR), version 2.0. The dataset will be further reviewed and updated as additional information is released. Please refer to the tables below for data dictionary and SCAG’s land use classification. Field Name Data TypeField DescriptionPID19Text2019 SCAG’s parcel unique IDAPN19Text2019 Assessor’s parcel numberCOUNTYTextCounty name (based on 2016 county boundary)COUNTY_IDDoubleCounty FIPS code (based on 2016 county boundary)CITYTextCity name (based on 2016 city boundary)CITY_IDDoubleCity FIPS code (based on 2016 city boundary)MULTIPARTShort IntegerMultipart feature (the number of multiple polygons; '1' = singlepart feature)STACKLong IntegerDuplicate geometry (the number of duplicate polygons; '0' = no duplicate polygons)ACRESDoubleParcel area (in acreage)GEOID20Text2020 Census Block Group GEOIDSLOPEShort IntegerSlope information1APN_DUPLong IntegerDuplicate APN (the number of multiple tax roll property records; '0' = no duplicate APN)IL_RATIODoubleRatio of improvement assessed value to land assessed valueLU19Text2019 existing land useLU19_SRCTextSource of 2019 existing land use2SCAGUID16Text2016 SCAG’s parcel unique IDAPNText2016 Assessor’s parcel numberCITY_GP_COText2016 Jurisdiction’s general plan land use designationSCAG_GP_COText2016 SCAG general plan land use codeSP_INDEXShort IntegerSpecific plan index ('0' = outside specific plan area; '1' = inside specific plan area)CITY_SP_COText2016 Jurisdiction’s specific plan land use designationSCAG_SP_COText2016 SCAG specific plan land use codeCITY_ZN_COText2016 Jurisdiction’s zoning codeSCAG_ZN_COText2016 SCAG zoning codeLU16Text2016 existing land useYEARLong IntegerDataset yearPUB_OWNShort IntegerPublic-owned land index ('1' = owned by public agency)PUB_NAMETextName of public agencyPUB_TYPETextType of public agency3BF_SQFTDoubleBuilding footprint area (in square feet)4BSF_NAMETextName of brownfield/superfund site5BSF_TYPETextType of brownfield/superfund site5FIREShort IntegerParcel intersects CalFire Very High Hazard Local Responsibility Areas or State Responsibility Areas (November 2020 version) (CalFIRE)SEARISE36Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)1 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)SEARISE72Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)2 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)FLOODShort IntegerParcel intersects with a FEMA 100 Year Flood Plain data from the Digital Flood Insurance Rate Map (DFIRM), obtained from Federal Emergency Management Agency (FEMA) in August 10, 2017EQUAKEShort IntegerParcel intersects with an Alquist-Priolo Earthquake Fault Zone (California Geological Survey; 2018) LIQUAFAShort IntegerParcel intersects with a Liquefaction Susceptibility Zone (California Geological Survey; 2016)LANDSLIDEShort IntegerParcel intersects with a Landslide Hazard Zone (California Geological Survey; 2016)CPADShort IntegerParcel intersects with a protected area from the California Protected Areas Database(CPAD) – www.calands.org (accessed April 2021)RIPARIANShort IntegerParcel centroid falls within Active River Areas(2010)or parcel intersects with a Wetland Area in the National Wetland Inventory(Version 2)WILDLIFEShort IntegerParcel intersects with wildlife habitat (US Fish & Wildlife ServiceCritical Habitat, Southern California Missing Linkages, Natural Lands & Habitat Corridors from Connect SoCal, CEHC Essential Connectivity Areas,Critical Coastal Habitats)CNDDBShort IntegerThe California Natural Diversity Database (CNDDB)includes the status and locations of rare plants and animals in California. Parcels that overlap locations of rare plants and animals in California from the California Natural Diversity Database (CNDDB)have a greater likelihood of encountering special status plants and animals on the property, potentially leading to further legal requirements to allow development (California Department of Fish and Wildlife). Data accessed in October 2020. HCPRAShort IntegerParcel intersects Natural Community & Habitat Conservation Plans Reserve Designs from the Western Riverside MHSCP, Coachella Valley MHSCP, and the Orange County Central Coastal NCCP/HCP, as accessed in October 2020WETLANDShort IntegerParcel intersects a wetland or deepwater habitat as defined by the US Fish & Wildlife Service National Wetlands Inventory, Version 2. UAZShort IntegerParcel centroid lies within a Caltrans Adjusted Urbanized AreasUNBUILT_SFDoubleDifference between parcel area and building footprint area expressed in square feet.6GRCRY_1MIShort IntegerThe number of grocery stores within a 1-mile drive7HEALTH_1MIShort IntegerThe number of healthcare facilities within a 1-mile drive7OPENSP_1MIShort IntegerQuantity of open space (roughly corresponding to city blocks’ worth) within a 1-mile drive7TCAC_2021TextThe opportunity level based on the 2021 CA HCD/TCAC opportunity scores.HQTA45Short IntegerField takes a value of 1 if parcel centroid lies within a 2045 High-Quality Transit Area (HQTA)JOB_CTRShort IntegerField takes a value of 1 if parcel centroid lies within a job centerNMAShort IntegerField takes a value of 1 if parcel centroid lies within a neighborhood mobility area. ABS_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within an absolute constraint area. See the Sustainable Communities Strategy Technical Reportfor details.VAR_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within a variable constraint area. See the Sustainable Communities Strategy Technical Reportfor details.EJAShort IntegerField takes a value of 1 if parcel centroid lies within an Environmental Justice Area. See the Environmental Justice Technical Reportfor details.SB535Short IntegerField takes a value of 1 if parcel centroid lies within an SB535 Disadvantaged Community area. See the Environmental Justice Technical Reportfor details.COCShort IntegerField takes a value of 1 if parcel centroid lies within a Community of Concern See the Environmental Justice Technical Reportfor details.STATEShort IntegerThis field is a rudimentary estimate of which parcels have adequate physical space to accommodate a typical detached Accessory Dwelling Unit (ADU)8. SBShort IntegerIndex of ADU eligibility according to the setback reduction policy scenario (from 4 to 2 feet) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SMShort IntegerIndex of ADU eligibility according to the small ADU policy scenario (from 800 to 600 square feet ADU) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)PKShort IntegerIndex of ADU eligibility according to parking space exemption (200 square feet) policy scenario (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SMShort IntegerIndex of ADU eligibility according to both the setback reduction and small ADU policy scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_PKShort IntegerIndex of ADU eligibility according to both the setback reduction and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SM_PKShort IntegerIndex of ADU eligibility according to both the small ADU policy and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SM_PKShort IntegerIndex of ADU eligibility according to the setback reduction, small ADU, and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)1. Slope: '0' - 0~4 percent; '5' - 5~9 percent; '10' - 10~14 percent; '15' = 15~19 percent; '20' - 20~24 percent; '25' = 25 percent or greater.2. Source of 2019 existing land use: SCAG_REF- SCAG's regional geospatial datasets;ASSESSOR- Assessor's 2019 tax roll records; CPAD- California Protected Areas Database (version 2020a; accessed in September 2020); CSCD- California School Campus Database (version 2018; accessed in September 2020); FMMP- Farmland Mapping and Monitoring Program's Important Farmland GIS data (accessed in September 2020); MIRTA- U.S. Department of Defense's Military Installations, Ranges, and Training Areas GIS data (accessed in September 2020)3. Type of public agency includes federal, state, county, city, special district, school district, college/university, military.4. Based on 2019 building footprint data obtained from BuildingFootprintUSA (except that 2014 building footprint data was used for Imperial County). Please note that 2019 building footprint data does not cover the entire SCAG region (overlapped with 83% of parcels in the SCAG Region).5. Includes brownfield/superfund site whose address information are matched by SCAG rooftop address locator. Brownfield data was obtained from EPA's Assessment, Cleanup and Redevelopment Exchange System (ACRES) database, Cleanups in my community (CIMC), DTSC brownfield Memorandum of Agreement (MOA). Superfund site data was obtained from EPA's Superfund Enterprise Management System (SEMS) database.6. Parcels with a zero value for building footprint area are marked as NULL to indicate this field is not reliable.7. These values are intended as a rudimentary indicator of accessibility developed by SCAG using 2016 InfoUSA business establishment data and 2017 California Protected Areas data. See documentation for details.8. A detailed study conducted by Cal Poly Pomona (CPP) and available hereconducted an extensive review of state and local requirements and development trends for ADUs in the SCAG region and developed a baseline set of assumptions for estimating how many of a jurisdiction’s parcels could accommodate a detached ADU. Please note that these estimates (1) do not include attached or other types of ADUs such as garage conversions or Junior ADUs, and (2)

CA School Districts for 2013-2014 as supplied by the US Census.

School Districts are geographic entities and single purpose governmental units that operate schools and provide public educational services at the local level. The Census Bureau collects school district boundaries to develop annual estimates of children in poverty to help the U.S. Department of Education determine the annual allocation of Title I funding to states and school districts. NCES also uses the school district boundaries to develop a broad collection of district-level demographic estimates from the Census Bureau’s American Community Survey. The Census Bureau updates school district boundaries, names, local education agency codes, grade ranges, and school district levels biennially based on information provided by state education officials.

© US Census, Institute of Education Sciences

This geologic map database for the El Mirage Lake area describes geologic materials for the dry lake, parts of the adjacent Shadow Mountains and Adobe Mountain, and much of the piedmont extending south from the lake upward toward the San Gabriel Mountains. This area lies within the western Mojave Desert of San Bernardino and Los Angeles Counties, southern California. The area is traversed by a few paved highways that service the community of El Mirage, and by numerous dirt roads that lead to outlying properties. An off-highway vehicle area established by the Bureau of Land Management encompasses the dry lake and much of the land north and east of the lake. The physiography of the area consists of the dry lake, flanking mud and sand flats and alluvial piedmonts, and a few sharp craggy mountains. This digital geologic map database, intended for use at 1:24,000- scale, describes and portrays the rock units and surficial deposits of the El Mirage Lake area. It was prepared as part of a water-resource assessments of the area, describing and interpreting surface geology that provides information to help understand distribution and extent of deeper groundwater-bearing units. The area mapped covers the Shadow Mountains SE and parts of the Shadow Mountains, Adobe Mountain, and El Mirage 7.5-minute quadrangles. The map database includes detailed geology of surface and bedrock deposits, which represent a significant update from previous bedrock geologic maps by Dibblee (1960) and Troxel and Gunderson (1970), and the surficial geologic map of Ponti and Burke (1980); it incorporates a fringe of the detailed bedrock mapping in the Shadow Mountains by Martin (1992).

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

The 2023 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some states and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

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