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.

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The primary legal divisions of most States are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, and municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four States (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their States. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The 2010 Census boundaries for counties and equivalent entities are as of January 1, 2010, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

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

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. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

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

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 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.

The California Department of Fish and Wildlife (CDFW) Vegetation Classification and Mapping Program (VegCAMP) has created a fine-scale vegetation map of the Department''s mitigation lands in the northern portion of the Carrizo Plain, San Luis Obispo County, California. The mapping follows Survey of California Vegetation, Federal Geographic Data Committee (FGDC), and National Vegetation Classification (NVC) standards (FGDC 2008, Jennings et al. 2009). The map legend is based on the classification in Stout et al. (2013), with slight modifications as discussed in Appendix C of the project report, which is available here: https://nrm.dfg.ca.gov/FileHandler.ashx?DocumentID=92969. Reconnaissance-level sampling of vegetation stands in the project area was conducted in the spring of 2013. Polygons were drawn using heads-up digitizing using the July 2011 1-foot imagery acquired for San Luis Obispo County and downloaded from US Geological Survey (USGS) EarthExplorer as the map base. Supplemental imagery included National Agricultural Imagery Program (NAIP) true color and color infrared (CIR) 1-meter resolution data from 2010''2012, Bing imagery, and current and historical imagery from Google Earth. The minimum mapping unit (MMU) is ½ acre in order to capture small, remnant native stands of trees, shrubs, and bunch grasses. Mapping is to the NVC hierarchy Association, Alliance, or Group level based on the ability of the photointerpreters to distinguish types based on all imagery available and on the field data. Field verification data was collected in the spring of 2014 and corrections were made to the map based on that data to increase the final accuracy.

This data set maps and describes the geology of the San Bernardino North 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 containing geologic contacts and units, (2) 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, topography, cultural data, a Correlation of Map Units (CMU) diagram, a Description of Map Units (DMU), an index map, a regional geologic and structure map, and a key for point and line symbols; (2) PDF files of this Readme (including the metadata file as an appendix), Description of Map Units (DMU), and the graphic produced by the PostScript plot file. The geologic map covers a part of the southwestern San Bernardino Mountains and the northwestern San Bernardino basin. Granitic and metamorphic rocks underlie most of the mountain area, and a complex array of Quaternary deposits fill the basin. These two areas are separated by strands of the seismically active San Andreas Fault. Bedrock units in the San Bernardino Mountains are dominated by large Cretaceous and Jurassic granitic bodies, ranging in composition from monzogranite to monzodiorite, and include lesser Triassic monzonite. The younger of these granitic rocks intrude a complex assemblage of gneiss, marble, and granitic rock of probable early Mesozoic age; the relationship between these metemorphic rocks and the Triassic rocks is unknown. Spanning the Pleistocene in age, large and small alluvial bodies emerge from the San Bernardino Mountains, and and fill the San Bernardino basin. In the southwestern part of the quadrangle, Cajon Wash carries sediments from both the San Bernardino and San Gabriel Mountains, and Lytle Creek heads in the eastern San Gabriel Mountains. Limited bedrock areas showing through the Quaternary sediments of the basin consist exclusively of Mesozoic Pelona Schist locally intruded by Tertairy dikes. Youthful-appearing fault scarps discontinuously mark the traces of the San Andreas Fault along the southern edge of the San Bernardino Mountains. Unnamed Tertiary sedimentary rocks are bounded by two strands of the fault between Badger Canyon and the east edge of the quadrangle. Young and old high-angle faults cut bedrock units within the San Bernardino Mountains, and the buried, seismically active San Jacinto Fault traverses the southwestern part of the quadrangle. The geologic map database contains original U.S. Geological Survey data generated by detailed field observation and by interpretation of aerial photographs. This digital Open-File map superceeds an older analog Open-File map of the quadrangle, and includes extensive new data on the Quaternary deposits, and revises some fault and bedrock distribution within the San Bernardino Mountains. The digital map was compiled on a base-stable cronoflex copy of the San Bernardino North 7.5' topographic base and then scribed. This scribe guide was used to make a 0.007 mil blackline clear-film, which was scanned at 1200 DPI by Optronics Specialty Company, Northridge, California; minor hand-digitized additions were made at the USGS. Lines, points, and polygonswere subsequently edited at the USGS using standard ARC/INFO commands. Digitizing and editing artifacts significant enough to display at a scale of 1:24,000 were corrected. 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.

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.

In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands†from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore of Point Reyes map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and ph... Visit https://dataone.org/datasets/4ea5faf6-34e2-40b3-a127-73a8dbc14580 for complete metadata about this dataset.

In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands†from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore of Bolinas map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and photog... Visit https://dataone.org/datasets/0afb1a5f-3882-4195-bf7b-bb0ccf69bfbe for complete metadata about this dataset.

In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands†from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore of Tomales Point map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and ... Visit https://dataone.org/datasets/55cbf4ba-e03a-4904-a101-2a38a96a08ed for complete metadata about this dataset.

This part of DS 781 presents data for the faults for the geologic and geomorphic map of the Offshore of Monterey map area, California. The vector data file is included in "Faults_OffshoreMonterey.zip," which is accessible from http://dx.doi.org/10.3133/ofr20161110. The shelf north and east of the Monterey Bay Peninsula in the Offshore of Monterey map area is cut by a diffuse zone of northwest striking, steeply dipping to vertical faults comprising the Monterey Bay Fault Zone (MBFZ). This zone, originally mapped by Greene (1977, 1990), extends about 45 km across Monterey Bay (Map E on sheet 9). Fault strands within the MBFZ are mapped with high-resolution seismic-reflection profiles (sheet 8). Seismic-reflection profiles traversing this diffuse zone in the map area cross as many as 5 faults over a width of about 4 to 5 km (see, for example, figs. 3 and 5 on sheet 8). The zone lacks a continuous "master fault," along which deformation is concentrated. Fault length ranges up to about 20 km (based on mapping outside this map area), but most strands are only about 2- to 7-km long. Faults in this diffuse zone cut through Neogene bedrock and locally appear to minimally disrupt overlying inferred Quaternary sediments. The presence of warped reflections along some fault strands suggests that fault offsets may be both vertical and strike-slip. Specific offshore faults within the zone that are continuous with mapped onshore faults include the Navy Fault, Chupines Fault, and Ord Terrace Fault (Clark and others, 1997; Wagner and others, 2002). Carmel Canyon, a relatively straight northwest-trending arm of the Monterey Canyon system, extends through the southwestern part of the Offshore of Monterey map area. Carmel Canyon has three heads (Greene and others, 2002), two of which extend east and northeast into Carmel Bay within the map area; the third head extends southeast along the main canyon trend for about 3 km beyond the confluence with the heads in Carmel Bay. Carmel Canyon is aligned with and structurally controlled by the San Gregorio fault zone (Greene and others, 1991), an important structure in the distributed transform boundary between the North American and Pacific plates (see, for example, Dickinson and others, 2005). This Fault Zone is part of a regional fault system that is present predominantly in the offshore for about 400 km, from Point Conception in the south (where it is known as the Hosgri Fault; Johnson and Watt, 2012) to Bolinas and Point Reyes in the north (Bruns and others, 2002; Ryan and others, 2008). The San Gregorio Fault Zone in the map area is part of a 90-km-long offshore segment that extends northward from Point Sur (about 24 km south of the map area), across outer Monterey Bay to Point Año Nuevo (51 km north of the map area) (see sheet 9; see also, Weber and Lajoie, 1980; Brabb and others, 1998; Wagner and others, 2002). High-resolution seismic-reflection data collected across the canyon do not clearly image the San Gregorio Fault Zone, due largely to significant depth and steep canyon walls. Accordingly, we have mapped the 1,000- 1,300-m-wide fault zone largely on the presence of prominent, lengthy, geomorphic lineaments (sheets 1 and 2) and both geomorphic and lithologic contrasts across the fault. Faults were primarily mapped by interpretation of seismic reflection profile data (see OFR 2013-1071). The seismic reflection profiles were collected between 2007 and 2010. References Cited Bruns, T.R., Cooper, A.K., Carlson, P.R., and McCulloch, D.S., 2002, Structure of the submerged San Andreas and San Gregorio Fault zones in the Gulf of Farallones as inferred from high-resolution seismic-reflection data, in Parsons, T., ed., Crustal structure of the coastal and marine San Francisco Bay region, California: U.S. Geological Survey Professional Paper 1658, p. 77–117, available at http://pubs.usgs.gov/pp/1658/. Brabb, E.E., 1997, Geologic Map of Santa Cruz County, California: A digital database, US Geological Survey Open-File Report 97–489, 1:62,500. Clark, J.C., Dupre, W.R., and Rosenberg, L.L., 1997, Geologic map of the Monterey and Seaside 7.5–minute quadrangles, Monterey County, California–A digital database: U.S. Geological Survey Open-File Report 97-30, 2 sheets, scale 1:24,000, http://pubs.usgs.gov/of/1997/of97-030/ Dickinson, W.R., Ducea, M., Rosenberg, L.I., Greene, H.G., Graham, S.A., Clark, J.C., Weber, G.E., Kidder, S., Ernst, W.G., and Brabb, E.E., 2005, Net dextral slip, Neogene San Gregorio-Hosgri fault zone, coastal California: Geologic evidence and tectonic implications: Geological Society of America Special Paper 391, 43 p. Greene, H.G., Maher, N.M., and Paull, C.K., 2002, Physiography of the Monterey Bay National Marine Sanctuary and implications about continental margin development: Marine Geology, v. 181, p. 55–82. Greene, H.G., Clarke, S.H. and Kennedy, M.P., 1991. Tectonic Evolution of Submarine Canyons Along the California Continental Margin. From Shoreline to Abyss, in Osborne, R.H., ed., Society for Sedimentary Geology, Special Publication No. 46, p. 231–248. Greene, H.G., 1990, Regional tectonics and structural evolution of the Monterey Bay region, central California, in Garrison, R.E., Greene, H.G., Hicks, K.R., Weber, G.E., and Wright, T.L., eds., Geology and tectonics of the central California coastal region, San Francisco to Monterey: American Association of Petroleum Geologists, Pacific Section, Guidebook GB67, p. 31–56. Greene, H.G., 1977, Geology of the Monterey Bay region: U.S. Geological Survey Open-File Report 77–718, 347 p. Greene, H.G., 1990, Regional tectonics and structural evolution of the Monterey Bay region, central California, in Garrison, R.E., Greene, H.G., Hicks, K.R., Weber, G.E., and Wright, T.L., eds., Geology and tectonics of the central California coastal region, San Francisco to Monterey, Pacific Section American Association of Petroleum Geologists, Guidebook GB-67, p. 31–56. Johnson, S.Y., and Watt, J.T., 2012, Influence of fault trend, bends, and convergence on shallow structure and geomorphology of the Hosgri strike-slip fault, offshore Central California: Geosphere, v. 8, p. 1,632–1,656, doi:10.1130/GES00830.1. Ryan, H.F., Parsons, T., and Sliter, R.W., 2008. Vertical tectonic deformation associated with the San Andreas fault zone offshore of San Francisco, California: Tectonophysics, v. 429, p. 209–224, doi:10.1016/j.tecto.2008.06.011. Wagner, D.L., Greene, H.G., Saucedo, G.J., and Pridmore, C.L., 2002, Geologic Map of the Monterey 30' x 60' quadrangle and adjacent areas, California: California Geological Survey Regional Geologic Map Series, scale 1:100,000. Weber, G.E., and Lajoie, K.R., 1980, Map of Quaternary faulting along the San Gregorio fault zone, San Mateo and Santa Cruz Counties, California: U.S. Geological Survey Open-File Report 80–907, 3 sheets, scale 1:24,000, available at http://pubs.er.usgs.gov/publication/ofr80907.

description: This part of DS 781 presents data for the geologic and geomorphic map of the Offshore of Tomales Point map area, California. The vector data file is included in "Geology_OffshoreTomalesPoint.zip," which is accessible from http://pubs.usgs.gov/ds/781/OffshoreTomalesPoint/data_catalog_OffshoreTomalesPoint.html. The morphology and the geology of the offshore part of the Offshore of Tomales Point map area result from the interplay between tectonics, sea-level rise, local sedimentary processes, and oceanography. The map area is cut by the northwest-trending San Andreas Fault, the right-lateral transform boundary between the North American and Pacific tectonic plates. The San Andreas strikes through Tomales Bay, the northern part of a linear valley that extends from Bolinas through Olema Valley to Bodega Bay, separating mainland California from the Point Reyes Peninsula. Onshore investigations indicate that this section of the San Andreas Fault has an estimated slip rate of about 17 to 25 mm/yr (Bryant and Lundberg, 2002; Grove and Niemi, 2005). The devastating Great 1906 California earthquake (M 7.8) is thought to have nucleated on the San Andreas Fault about 50 kilometers south of this map area offshore of San Francisco (e.g., Bolt, 1968; Lomax, 2005), with the rupture extending northward through the Offshore of Tomales Point map area to the south flank of Cape Mendocino (Lawson, 1908; Brown and Wolfe, 1972). The Point Reyes Peninsula is bounded to the south and west in the offshore by the north- and east-dipping Point Reyes Thrust Fault (McCulloch, 1987; Heck and others, 1990), which lies about 20 km west of Tomales Point. Granitic basement rocks are offset about 1.4 km on this thrust fault offshore of Point Reyes (McCulloch, 1987), and this uplift combined with west-side-up offset on the San Andreas Fault (Grove and Niemi, 2005) resulted in uplift of the Point Reyes Peninsula, including Tomales Point and the adjacent continental shelf. Grove and others (2010) reported uplift rates of as much as 1 mm/yr for the south flank of the Point Reyes Peninsula based on marine terraces, but reported no datable terrace surfaces that could constrain uplift for the flight of 4-5 terraces exposed farther north along Tomales Point. Because of this Quaternary uplift and relative lack of sediment supply from coastal watersheds, there is extensive rugged, rocky seafloor beneath the continental shelf in the Offshore of Tomales Point map area. Granitic rocks (unit Kg) on the seafloor are mapped on the basis of massive character, roughness, extensive fractures, and high backscatter (see Backscattter A to D--Offshore of Tomales Point, California, DS 781, for more information). Neogene sedimentary rocks (units Tl and Tu) commonly form distinctive "ribs," created by differential seafloor erosion of dipping beds of variable resistance. The more massive offshore outcrops of unit Tu in the southern part of the map area are inferred to represent more uniform lithologies. Slopes on the granitic seafloor (generally 1 to 1.3 degrees) are greater than those over sedimentary rock (generally about 0.5 to 0.6 degrees). Sediment-covered areas occur in gently sloping (less than about 0.6 degrees) mid-shelf environments west and north of Tomales Point, and at the mouth of Tomales Bay. Sediment supply is local, limited to erosion from local coastal bluffs and dunes, small coastal watersheds, and sediment flux out of the mouth of Tomales Bay. Shelf morphology and evolution largely reflects eustacy; sea level has risen about 125 to 130 m over about the last 21,000 years (for example, Lambeck and Chappell, 2001; Peltier and Fairbanks, 2005), leading to broadening of the continental shelf, progressive eastward migration of the shoreline and wave-cut platform, and associated transgressive erosion and deposition. Given present exposure to high wave energy, modern nearshore to mid-shelf sediments are mostly sand (unit Qms) and a mix of sand, gravel, and cobbles (units Qmsc and Qmsd). These sediments are distributed between rocky outcrops at water depths of as much as 65 m (see below). The more coarse-grained sands and gravels (units Qmsc and Qmsd) are primarily recognized on the basis of bathymetry and high backscatter. Unit Qmsd forms erosional lags in scoured depressions that are bounded by relatively sharp contacts with bedrock or sharp to diffuse contacts with units Qms and Qmsc. These scoured depressions are typically a few tens of centimeters deep and range in size from a few 10's of sq m to more than one sq km. Similar unit Qmsd scour depressions are common along this stretch of the California coast (see, for example, Cacchione and others, 1984; Hallenbeck and others, 2012) where surficial offshore sandy sediment is relatively thin (thus unable to fill the depressions) due to both lack of sediment supply and to erosion and transport of sediment during large northwest winter swells. Such features have been referred to as rippled-scour depressions (see, for example, Cacchione and others, 1984) or sorted bedforms (see, for example, Goff and others, 2005; Trembanis and Hume, 2011). Although the general areas in which both unit Qmsd scour depressions and surrounding mobile sand sheets occur are not likely to change substantially, the boundaries of the individual Qmsd depressions are likely ephemeral, changing seasonally and during significant storm events. Unit Qmsf consists primarily of mud and muddy sand and is commonly extensively bioturbated. The location of the inboard contact at water depths of about 65 m is based on meager sediment sampling and photographic data and the inference that if must lie offshore of the outer boundary of coarse-grained units Qmsd and Qmsc. This is notably deeper than the inner contact of unit Qmsf offshore of the nearby Russian River (about 50 m; Klise, 1983) which could may reflect both increased wave energy and significantly decreased supply of muddy sediment. There are two areas of high-backscatter, rough seafloor at water depths of 65 to 70 m west of northern Tomales Point. These areas are notable in that each includes several small (less than about 20,000 sq m), randomly distributed to northwest-trending, irregular "mounds," with as much as 1 m of positive relief above the seafloor (unit Qsr). Seismic-reflection data (see field activity S-15-10-NC) reveal this lumpy material rests on several meters of latest Pleistoce to Holocene sediment and is thus not bedrock outcrop. Rather, it seems likely that this material is marine debris, possibly derived from one (or more) of the more than 60 shipwrecks that have occurred offshore of the Point Reyes Peninsula between 1849 and 1940 (National Park Service, 2012). It is also conceivable that this lumpy terrane consists of biological "hardgrounds" Units Qsw, Qstb, Qdtb, and Qsdtb comprise sediments in Tomales Bay. Anima and others (2008) conducted a high-resolution bathymetric survey of Tomales Bay and noted that strong tidal currents at the mouth of the bay had created a large field of sandwaves, dunes, and flats (unit Qsw). Unit Qkdtb is a small subaqueous sandy delta deposited at the mouth of Keys Creek, the largest coastal watershed draining into this northern part of Tomales Bay. Unit Qstb occurs south of units Qsw and Qdtb, and comprises largely flat seafloor underlain by mixed sand and silt. Unit Qdtb consists of depressions within the sedimentary fill of Tomales Bay. These depressions commonly occur directly offshore of coastal promontories, cover as much as 74,000 sq m, and are as deep as 9 m. Map unit polygons were digitized over underlying 2-meter base layers developed from multibeam bathymetry and backscatter data (see Bathymetry--Offshore of Tomales Point, California and Backscattter A to D--Offshore of Tomales Point, California, DS 781). The bathymetry and backscatter data were collected between 2006 and 2010. References Cited Anima, R. A., Chin, J.L., Finlayson, D.P., McGann, M.L., and Wong, F.L., 2008, Interferometric sidescan bathymetry, sediment and foraminiferal analyses; a new look at Tomales Bay, Califorina: U.S. Geological Survey Open-File Report 2008 - 1237, 33 p. Brown, R.D., Jr., and Wolfe, E.W., 1972, Map showing recently active breaks along the San Andreas Fault between Point Delgada and Bolinas Bay, California: U.S. Geological Survey Miscellaneous Investigations Map I-692, scale 1:24,000. Bryant, W.A., and Lundberg, M.M., compilers, 2002, Fault number 1b, San Andreas fault zone, North Coast section, in Quaternary fault and fold database of the United States: U.S. Geological Survey website, accessed April 4, 2013 at http://earthquakes.usgs.gov/hazards/qfaults. Cacchione, D.A., Drake, D.E., Grant, W.D., and Tate, G.B., 1984, Rippled scour depressions of the inner continental shelf off central California: Journal of Sedimentary Petrology, v. 54, p. 1,280-1,291. Grove, K., and Niemi, T.M., 2005, Late Quaternary deformation and slip rates in the northern San Andreas fault zone at Olema Valley, Marin County, California: Tectonophysics, v. 401, p. 231-250. Grove, K, Sklar, L.S., Scherer, A.M., Lee, G., and Davis, J., 2010, Accelerating and spatially-varying crustal uplift and its geomorphic expression, San Andreas fault zone north of San Francisco, California: Tectonophysics, v. 495, p. 256-268. Klise, D.H., 1984, Modern sedimentation on the California continental margin adjacent to the Russian River: M.S. thesis, San Jose State University, 120 p. Hallenbeck, T.R., Kvitek, R.G., and Lindholm, J., 2012, Rippled scour depressions add ecologically significant heterogeneity to soft-bottom habitats on the continental shelf: Marine Ecology Progress Series, v. 468, p. 119-133. Lambeck, K., and Chappell, J., 2001, Sea level change through the last glacial cycle: Science, v. 292, p. 679-686, doi: 10.1126/science.1059549. Lawson, A.C., ed., 1908, The California earthquake of April 18, 1906, Report of the State Earthquake Investigation Commission:

Groundwater Elevation Change Maps summarize the change in groundwater level measurements over time, collected from wells in the northern Sacramento Valley by the Department of Water Resources (DWR) Northern Region Office (NRO) and monitoring cooperators. Northern Sacramento Valley groundwater levels are measured seasonally, during the annual water year, as part of our ongoing data collection program. Many of the wells have over 30 years of monitoring history, with the longest active monitoring well dating back to 1921. Groundwater level data provides valuable information regarding seasonal fluctuations and long-term changes in groundwater level trends over time. The groundwater level data presented in these figures includes the Sacramento Valley and Redding groundwater basin portions of Shasta, Tehama, Butte, Colusa, Glenn, and Sutter counties and are organized by year, season, well depth, and period of change.

This data set maps and describes the geology of the Cucamonga Peak 7.5' quadrangle, San Bernardino County, California. Created using Environmental Systems Research Institute's ARC/INFO software, the database consists of the following items: (1) a map coverage containing geologic contacts and units, (2) a coverage containing site-specific structural data, (3) a coverage containing geologic-unit label leaders and their associated 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, topography, cultural data, a Correlation of Map Units (CMU) diagram, a Description of Map Units (DMU), an index map, a regional geologic and structure map, and a key for point and line symbols; (2) PDF files of this Readme (including the metadata file as an appendix) and the graphic produced by the PostScript plot file. The Cucamonga Peak quadrangle includes part of the boundary between two major physiographic provinces of California, the Transverse Ranges Province to the north and the Peninsular Ranges Province to the south. The north part of the quadrangle is in the eastern San Gabriel Mountains, and the southern part includes an extensive Quaternary alluvial-fan complex flanking the upper Santa Ana River valley, the northernmost part of the Peninsular Ranges Province. Thrust faults of the active Cucamonga Fault zone along the the south margin of the San Gabriel Mountains are the rejuvenated eastern terminus of a major old fault zone that bounds the south side of the western and central Transverse Ranges (Morton and Matti, 1993). Rejuvenation of this old fault zone, including the Cucamonga Fault zone, is apparently in response to compression in the eastern San Gabriel Mountains resulting from initiation of right-lateral slip on the San Jacinto Fault zone in the Peninsular Ranges. Within the northern part of the quadrangle are several arcuate-in-plan faults that are part of an antiformal, schuppen-like fault complex of the eastern San Gabriel Mountains. Most of these arcuate faults are reactivated and deformed older faults that probably include the eastern part of the San Gabriel Fault. The structural grain within the San Gabriel Mountains, as defined by basement rocks, is generally east striking. Within the Cucamonga Peak quadrangle, these basement rocks include a Paleozoic schist and gneiss sequence which occurs as large, continuous and discontinuous bodies intruded by Cretaceous granitic rocks. Most of the granitic rocks are of tonalitic composition, and many are mylonitic. South of the granitic rocks is a comple assemblage of Proterozoic(?) metamorphic rocks, at least part of which is metasedimentary. This assemblage is intruded by Cretaceous tonalite on its north side, and by charnockitic rocks near the center of the mass. The charnockitic rocks are in contact with no other Cretaceous granitic rocks. Consequently, their relative position in the intrusive sequence is unknown. The Proterozoic(?) assemblage was metamorphosed to upper amphibolite and lower granulite grade, and subsequently to a lower metamorphic grade. It is also intensely deformed by mylonitization characterized by an east-striking, north-dipping foliation, and by a pronounced subhorizontal lineation that plunges shallowly east and west. The southern half of the quadrangle is dominated by extensive, symmetrical alluvial-fan complexes, particularly two emanating from Day and Deer Canyons. Other Quaternary units ranging from early Pleistocene to recent are mapped, and represent alluvial-fan, landslide, talus, and wash environments. The geologic map database contains original U.S. Geological Survey data generated by detailed field observation and by interpretation of aerial photographs. This digital Open-File map supercedes an older analog Open-File map of the quadrangle, and includes extensive new data on the Quaternary deposits, and revises some fault and bedrock distribution within the San Gabriel Mountains. The digital map was compiled on a base-stable cronoflex copy of the Cucamonga Peak 7.5' topographic base and then scribed. This scribe guide was used to make a 0.007 mil blackline clear-film, from which lines and point were hand digitized. Lines, points, and polygons were subsequently edited at the USGS using standard ARC/INFO commands. Digitizing and editing artifacts significant enough to display at a scale of 1:24,000 were corrected. 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.

Regional boundaries for use by CA Nature to support activities related to Executive Order N-82-20. These include California's 30x30 effort, Climate Smart Land Strategies, and equitable access to open space. This layer is derived from the 4th California Climate Assessment regions, and enhanced using the California County Boundaries dataset (version 19.1) maintained by the California Department of Forestry and Fire Protection's Fire Resource Assessment Program, and the 3 Nautical Mile marine boundary for California sourced from the California Department of Fish and Wildlife.

https://gis.data.ca.gov/datasets/CaliforniaARB::california-air-district-boundaries/aboutThe air quality control board dataset represents the Northern Sonoma County Air Pollution Control District (a.k.a. NSCAPCD) and the Bay Area Air Quality Management District (a.k.a. BAAQMD). The Northern Sonoma County Air Pollution Control District set forth Rule 110 which states: rules and regulations are set forth to achieve and maintain such levels of air quality as will protect human health and safety; prevent injury to plant and animal life; avoid damage to property; and preserve the comfort, convenience and enjoyment of the natural attractions of the California North Coast Air Basin. The Bay Area Air Quality Management District is committed to achieving clean air to protect the public's health and the environment in the San Francisco Bay region. The Air District aims to: 1) attain and maintain air quality standards, 2) increase public awareness of positive air quality choices, and 3) develop and implement protocol and policies for environmental justice. It is the intent of all air pollution control districts and air quality management districts in the California North Coast Air Basin to adopt and enforce rules and regulations which assure that reasonable provision is made to achieve and maintain state and federal ambient air quality standards for the area under their jurisdiction and to enforce all applicable provisions of State law.