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

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

This feature service includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations. BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES: additional clarifying information about the action. BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the BOE's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

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

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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally- recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2019, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs, delineated in 20 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

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.

This dataset contains the county boundaries that make up the Southern California Association of Governments service area. These county boundaries are consistent with the LAFCO city boundaries as of 08/2016 (Ver. 1.0).

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

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 =

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

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.

Except as provided in Section 366, bear may be taken only as follows:(a) Areas:(1) Northern California: In the counties of Del Norte, Humboldt, Plumas, Shasta, Siskiyou, Tehama and Trinity; and those portions of Lassen and Modoc counties west of the following line: Beginning at Highway 395 and the Sierra-Lassen county line; north on Highway 395 to the junction of Highway 36; west on Highway 36 to the junction of Highway 139; north on Highway 139 to Highway 299; north on Highway 299 to County Road 87; west on County Road 87 to Lookout-Hackamore Road; north on Lookout-Hackamore Road to Highway 139; north on Highway 139 to the Modoc-Siskiyou county line; north on the Modoc-Siskiyou county line to the Oregon border.(2) Central California: In the counties of Alpine, Amador, Butte, Calaveras, Colusa, El Dorado, Glenn, Lake, Mendocino, Nevada, Placer, Sacramento, Sierra, Sutter, Yolo and Yuba and those portions of Napa and Sonoma counties northeast of Highway 128.(3) Southern Sierra: That portion of Kern County west of Highway 14 and east of the following line: Beginning at the intersection of Highway 99 and the Kern-Tulare county line; south on Highway 99 to Highway 166; west and south on Highway 166 to the Kern-Santa Barbara county line; and those portions of Fresno, Madera, Mariposa, Merced, Stanislaus, Tulare and Tuolumne counties east of Highway 99.(4) Southern California: In the counties of Los Angeles, Santa Barbara and Ventura; that portion of Riverside County north of Interstate 10 and west of Highway 62; and that portion of San Bernardino County south and west of the following line: Beginning at the intersection of Highway 18 and the Los Angeles-San Bernardino county line; east along Highway 18 to Highway 247; southeast on Highway 247 to Highway 62; southwest along Highway 62 to the Riverside-San Bernardino county line.(5) Southeastern Sierra: Those portions of Inyo and Mono counties west of Highway 395; and that portion of Madera County within the following line: Beginning at the junction of the Fresno-Madera-Mono county lines; north and west along the Madera-Mono county line to the boundary of the Inyo-Sierra National Forest; south along the Inyo-Sierra National Forest boundary to the Fresno-Madera county line; north and east on the Fresno-Madera county line to the point of beginning. Also, that portion of Inyo county west of Highway 395; and that portion of Mono county beginning at the intersection of Highway 6 and the Mono county line; north along Highway 6 to the Nevada state line; north along the Nevada state line to the Alpine county line; south along the Mono-Alpine county line to the Mono-Tuolumne county line and the Inyo National Forest Boundary; south along the Inyo National Forest Boundary to the Inyo-Sierra Forest boundary; south along the Inyo-Sierra Forest boundary to the Fresno-Madera county line; north and east along the Fresno-Madera county line to the junction of the Fresno-Madera-Mono county line; south along the Mono-Fresno county line to the Mono-Inyo County line; east along the Mono-Inyo county line to the point of beginning.

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

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 data set maps and describes the geology of the Conejo Well 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 part of the northern Eagle Mountains and part of the 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 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 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 in the Eagle Mountains and an east-west trending system of high-angle dip- and left-slip faults. In and adjacent to the Conejo Well quadrangle, faults of the northwest-trending set displace Miocene sedimentary rocks and basalt deposited on the Tertiary erosion surface and 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 Conejo Well database was created using ARCVIEW and ARC/INFO, which are geographical information system (GIS) software products of Envronmental 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 point coverage containing line ornamentation, and (5) a scanned topographic base at a scale of 1:24,000. The coverages include 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.

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

Vector polygon map data of mile markers from the state of California containing 157892 features.

Mile marker GIS data consists of points along a linear feature, such as roads or railways. They serve as reference points to measure distances along these features. Mile markers are often labeled with numbers indicating their distance from a starting point, such as a highway's origin or a railway station.

These markers are invaluable for navigation, route planning, emergency response, and data collection. For example, they help drivers and emergency services identify their location precisely on a road. In transportation planning, mile markers aid in analyzing traffic patterns, determining optimal routes, and estimating travel times. Additionally, they facilitate maintenance activities by providing clear reference points for inspecting and repairing infrastructure.

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

This dataset contains the county boundaries that make up the Southern California Association of Governments service area. These county boundaries are consistent with the LAFCO city boundaries as of 08/2016 (Ver. 1.0).