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

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

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

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

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

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

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

Point of Contact

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

Field and Abbreviation Definitions

• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

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

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

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

This dataset is one from a series of district layers pertaining to California Congressional Districts, that are derived from the California State Senate information. All data layers are reprojected in UTM projection. The following district layer is included in the series: congressional districts: Current California Congressional Districts based on the new district boundaries enacted into state law on September 13, 2001, and signed into law on September 26, 2001 for use with the March 2002 primary election. The boundary has been updated as of 11/2011

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

The following data is provided as a public service, for informational purposes only. This data should not be construed as legal advice. Users of this data should independently verify its determinations prior to taking any action under the California Environmental Quality Act (CEQA) or any other law. The State of California makes no warranties as to accuracy of this data.This zoning data was collected from 535 of California"s 539 jurisdictions. An effort was made to contact each jurisdiction in the state and request zoning data in whatever form available. In the event that zoning maps were not available in a GIS format, maps were converted from PDF or image maps using geo-referencing techniques and then transposing map information to parcel geometries sourced from county assessor data. Collection efforts began in late 2021 and were mostly finished in late 2022. Some data has been updated in 2023. Sources and dates are documented in the "Source" and "Date" columns with more detail available in the accompanying sources table.Individual zoning maps were combined for this statewide dataset. As part of the aggregation process, contiguous areas with identical zone codes, within jurisdictions, were merged or dissolved. Some features representing roads with right-of-way or Null zone designations were removed from this data. Features less than 4 square meters in area were also removed.

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

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

The data set for the Butler Peak quadrangle has been prepared by the Southern California Areal Mapping Project (SCAMP), a cooperative project sponsored jointly by the U.S. Geological Survey and the California Division of Mines and Geology, as part of an ongoing effort to utilize a Geographical Information System (GIS) format to create a regional digital geologic database for southern California. This regional database is being developed as a contribution to the National Geologic Map Data Base of the National Cooperative Geologic Mapping Program of the USGS. Development of the data set for the Butler Peak quadrangle has also been supported by the U.S. Forest Service, San Bernardino National Forest.

The digital geologic map database for the Butler Peak quadrangle has been created as a general-purpose data set that is applicable to other land-related investigations in the earth and biological sciences. For example, the U.S. Forest Service, San Bernardino National Forest, is using the database as part of a study of an endangered plant species that shows preference for particular rock type environments. The Butler Peak database is not suitable for site-specific geologic evaluations at scales greater than 1:24,000 (1 in = 2,000 ft).

This data set maps and describes the geology of the Butler Peak 7.5' quadrangle, San Bernardino County, California. Created using Environmental Systems Research Institute's ARC/INFO software, the data base consists of the following items: (1) a map coverage showing geologic contacts and units,(2) a scanned topographic base at a scale of 1:24,000, and (3) attribute tables for geologic units (polygons), contacts (arcs), and site-specific data (points). In addition, the data set includes the following graphic and text products: (1) A PostScript graphic plot-file containing the geologic map on a 1:24,000 topographic base accompanied by a Description of Map Units (DMU), a Correlation of Map Units (CMU), and a key to point and line symbols; (2) PDF files of the DMU and CMU, and of this Readme, and (3) this metadata file.

The geologic map data base contains original U.S. Geological Survey data generated by detailed field observation and by interpretation of aerial photographs. The map was created by transferring lines from the aerial photographs to a 1:24,000 mylar orthophoto-quadrangle and then to a base-stable topographic map. This map was then scribed, and a .007 mil, right-reading, black line clear film made by contact photographic processes.The black line was scanned and auto-vectorized by Optronics Specialty Company, Northridge, CA. The non-attributed scan was imported into ARC/INFO, where the database was built. Within the database, geologic contacts are represented as lines (arcs), geologic units as polygons, and site-specific data as points. Polygon, arc, and point attribute tables (.pat, .aat, and .pat, respectively) uniquely identify each geologic datum and link it to other tables (.rel) that provide more detailed geologic information.

In 2012, the CPUC ordered the development of a statewide map that is designed specifically for the purpose of identifying areas where there is an increased risk for utility associated wildfires. The development of the CPUC -sponsored fire-threat map, herein "CPUC Fire-Threat Map," started in R.08-11-005 and continued in R.15-05-006.

A multistep process was used to develop the statewide CPUC Fire-Threat Map. The first step was to develop Fire Map 1 (FM 1), an agnostic map which depicts areas of California where there is an elevated hazard for the ignition and rapid spread of powerline fires due to strong winds, abundant dry vegetation, and other environmental conditions. These are the environmental conditions associated with the catastrophic powerline fires that burned 334 square miles of Southern California in October 2007. FM 1 was developed by CAL FIRE and adopted by the CPUC in Decision 16-05-036.

FM 1 served as the foundation for the development of the final CPUC Fire-Threat Map. The CPUC Fire-Threat Map delineates, in part, the boundaries of a new High Fire-Threat District (HFTD) where utility infrastructure and operations will be subject to stricter fire‑safety regulations. Importantly, the CPUC Fire-Threat Map (1) incorporates the fire hazards associated with historical powerline wildfires besides the October 2007 fires in Southern California (e.g., the Butte Fire that burned 71,000 acres in Amador and Calaveras Counties in September 2015), and (2) ranks fire-threat areas based on the risks that utility-associated wildfires pose to people and property.

Primary responsibility for the development of the CPUC Fire-Threat Map was delegated to a group of utility mapping experts known as the Peer Development Panel (PDP), with oversight from a team of independent experts known as the Independent Review Team (IRT). The members of the IRT were selected by CAL FIRE and CAL FIRE served as the Chair of the IRT. The development of CPUC Fire-Threat Map includes input from many stakeholders, including investor-owned and publicly owned electric utilities, communications infrastructure providers, public interest groups, and local public safety agencies.

The PDP served a draft statewide CPUC Fire-Threat Map on July 31, 2017, which was subsequently reviewed by the IRT. On October 2 and October 5, 2017, the PDP filed an Initial CPUC Fire-Threat Map that reflected the results of the IRT's review through September 25, 2017. The final IRT-approved CPUC Fire-Threat Map was filed on November 17, 2017. On November 21, 2017, SED filed on behalf of the IRT a summary report detailing the production of the CPUC Fire-Threat Map(referenced at the time as Fire Map 2). Interested parties were provided opportunity to submit alternate maps, written comments on the IRT-approved map and alternate maps (if any), and motions for Evidentiary Hearings. No motions for Evidentiary Hearings or alternate map proposals were received. As such, on January 19, 2018 the CPUC adopted, via Safety and Enforcement Division's (SED) disposition of a Tier 1 Advice Letter, the final CPUC Fire-Threat Map.

Additional information can be found here.

The data set for the Porcupine Wash quadrangle has been prepared by the Southern California Areal Mapping Project (SCAMP), a cooperative project sponsored jointly by the U.S. Geological Survey and the California Division of Mines and Geology. The Porcupine Wash data set represents part of an ongoing effort to create a regional GIS geologic database for southern California. This regional digital database, in turn, is being developed as a contribution to the National Geologic Map Database of the National Cooperative Geologic Mapping Program of the USGS. The Porcupine Wash database has been prepared in cooperation with the National Park Service as part of an ongoing project to provide Joshua Tree National Park with a geologic map base for use in managing Park resources and developing interpretive materials.

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

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

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

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

Map nomenclature and symbols

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

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

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

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