Shapefile contains county boundaries for the five counties that are included in the Bay Area Regional Climate Action Planning Initiative Frontline Communities Map.

The original shapefile was downloaded from the California Air Resources Board, Geographical Information System (GIS) Library. The “Select Layer By Attribute” tool in ArcMap was used to select only those five counties that are part of the Bay Area Regional Climate Action Planning Initiative. No display filters were used to visualize the features in the final map. To learn more about the methodology behind the original dataset, please visit: https://ww2.arb.ca.gov/geographical-information-system-gis-library

The Frontline Communities Map is meant to help identify communities that are considered frontline communities for the purpose of the USEPA’s Climate Pollution Reduction Grant (CPRG) program’s planning effort, which is a five-county climate action planning process led by the Air District. USEPA refers to these communities as low-income and disadvantaged communities (LIDACs).

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

This digital map database provides an areally continuous representation of the Quaternary surficial deposits of the San Francisco Bay region merged from the database files from Knudsen and others (2000) and Witter and others (2006). The more detailed mapping by Witter and others (2006) of the inner part of the region (compiled at a scale of 1:24,000), is given precedence over the less detailed mapping by Knudsen and others (2000) of the outer part of the area (compiled at a scale of 1:100,000). The Quaternary map database is accompanied by a list of the map-unit names represented by polygon identities, a digital map index of the 1:24,000-scale topographic quadrangles of the region, and a figure illustrating the contents of the database. The Quaternary map database includes line work and the identity of the Quaternary map units, but no further description of the map units or how they were mapped. Use of the database should thus be accompanied by consultation with the original reports, which describe the map units and mapping procedures: citation of this database should be accompanied by citation of those original reports. As with all such digital maps, use of this database should attend to the compilation scales involved and not try to extract spatial detail or accuracy beyond those limits. Database layers: SFBQuat-lns: Quaternary map database: unit boundaries and their attributes SFBQuat-pys: Quaternary map database: polygons and their attributes SFBIndex-lns: Boundaries of 7.5-minute quadrangles for the map area, distinguishing those that form boundaries of 15-minute and 30x60-minute quadrangles SFBIndex-pys: 7.5-minute quadrangles, and for those within map area, their names and the names of the 30x60-minute quadrangles that contain them. The liquefaction ratings presented in the original reports for the various Quaternary map units remain valid and can be assigned to the units in this database if desired, with ratings of Witter and others (2006) given precedence. Assembly of the Quaternary map database involved stripping out all the information from the source maps that dealt with liquefaction, a major component of the original reports, and adjusting line work at the common boundary between the two source maps to produce a nearly seamless spatial database. The common boundary between the two sources is retained. Mismatches remaining at that common boundary are of two types: (1) contrasts in the degree of subdivision of the deposits resulting from the different compilation scales, and (2) terminations of narrow bands of water and artificial fill and levees at quadrangle boundaries that resulted from differences in details shown on the 1:24,000-scale topographic maps used as a source of mapping information in the original reports. The illustrative figure accompanying the database shows the content of the database plotted at a scale of 1:275,000, with the different map units distinguished by color and the different types of lines distinguished by symbol and color. An index map in that figure shows the 165 7½-minute quadrangles covering the region and the areas of the two source maps. Knudsen, K.L., Sowers, J.M., Witter, R.C., Wentworth, C.M., Helley, E.J., Nicholson, R.S., Wright, H.M., and Brown, K.M., 2000, Preliminary maps of Quaternary deposits and liquefaction susceptibility, nine-county San Francisco Bay region, California: a digital database: U.S. Geological Survey Open File Report 00-444. http://pubs.usgs.gov/of/2000/of00-444/ Witter, R.C., Knudsen, K.L, Sowers, J.M., Wentworth, C.M., Koehler, R.D., Randolph, C. E., Brooks, S.K., and Gans, K.D., 2006, Maps of Quaternary Deposits and Liquefaction Susceptibility in the Central San Francisco Bay Region, California: U.S. Geological Survey Open-File Report 06-1037 (http://pubs.usgs.gov/of/2006/1037)

County boundaries for the San Francisco Bay Region, clipped to remove major coastal and bay water areas. Features were extracted from, and clipped using, California 2020 TIGER/Line shapefiles by the Metropolitan Transportation Commission. The 2020 TIGER/Line Shapefiles reflect available governmental unit boundaries of the counties and equivalent entities as of May 28, 2021.Counties and equivalent entities are primary legal divisions of states. In most states, these entities are termed “counties.” Each county or statistically equivalent entity is assigned a 3-character FIPS code that is unique within a state.

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

The regional flooding and shoreline overtopping analysis maps provided in the ART Bay Shoreline Flood Explorer website capture permanent and temporary flooding impacts from sea level rise scenarios from 0- to 108-inches above MHHW (mean higher high water) and storm surge events from the 1-year to the 100-year storm surge. The process used to develop the maps included discussions with key stakeholders in each county, who reviewed the preliminary maps and provided on-the-ground verification and supplemental data to improve the accuracy of the maps. The maps and information produced through this effort can inform adaptation planning, assist in managing climate change risks, and help identify trigger points for implementing adaptation strategies to address sea level rise and flooding hazards, at both local and regional scales. The Flood Explorer maps were produced using the latest LiDAR topographic data sets, water level outputs from the FEMA San Francisco Bay Area Coastal Study (which relied in hydrodynamic modeling using MIKE21) and the San Francisco Tidal Datums Study. The 2010/2011 LIDAR applied (collected by USGS and NOAA at a 1-m resolution) was further refined through the stakeholder review process and integration of additional elevation data where available. The Flood Explorer also includes the regional shoreline delineation developed by the San Francisco Estuary Institute to represent coastal flooding and overtopping throughout the Bay Area. In sum, the maps include: 1) Flooding at ten total water levels that capture over 90 combinations of future sea level rise and storm surge scenarios; 2) Shoreline overtopping maps for all ten total water levels that depict where the Bay may overtop the shoreline and its depth of overtopping at that specific location. Coupled with the flood maps, the overtopping data can help identify vulnerable shoreline locations and their respective flow paths that could lead to inland flooding, and; 3) Hydraulically disconnected low-lying areas that represent areas that may be vulnerable to flooding due to their low elevation. These areas are not directly within flooding locations, but could be connected to flood waters through culverts and storm drains that are not captured in this analysis.

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

This layer includes 9 annotation features for the county labels for the San Francisco Bay Water Quality Improvment Fund (SFBWQIF) area of interest These features are incorporated in the San Francisco Bay Water Quality Improvement Fund Story Map, an interactive series of maps and QlikSense graphics highlighting the competitive grant program which supports projects to protect and restore San Francisco Bay. The application can be found on the EPA GeoPlatform at: "https://epa.maps.arcgis.com/apps/MapSeries/index.html?appid=db223d22741140b9b10baf7e91815271" "https://epa.maps.arcgis.com/apps/MapSeries/index.html?appid=db223d22741140b9b10baf7e91815271" The story map is also embedded in the following EPA web page: "https://www2.epa.gov/sfbay-delta/sf-bay-water-quality-improvement-fund-interactive-project-map" https://www2.epa.gov/sfbay-delta/sf-bay-water-quality-improvement-fund-interactive-project-map

Shapefile contains census tracts identified as disadvantaged in the Climate and Economic Justice Screening Tool (CEJST) for the five counties that are included in the Bay Area Regional Climate Action Planning Initiative Frontline Communities Map.

The original shapefile was downloaded from the The White House Council on Environmental Quality, Climate and Economic Justice Screening Tool (CEJST), Methodology & Data webpage.. The “Clip” tool in ArcMap was used to select only those features which are located within the boundaries of the five Bay Area counties included in the Frontline Communities Map. Only those census tracts where SN_C column is equal to 1 are displayed. Where, SN_C is defined as "Identified as disadvantaged" in the original codebook and 1 is equivalent to a true statement. To learn more about the methodology behind the original dataset, please visit: https://screeningtool.geoplatform.gov/en/methodology#3/33.47/-97.5

The Frontline Communities Map is meant to help identify communities that are considered frontline communities for the purpose of the USEPA’s Climate Pollution Reduction Grant (CPRG) program’s planning effort, which is a five-county climate action planning process led by the Air District. USEPA refers to these communities as low-income and disadvantaged communities (LIDACs).

As outlined in Executive Order 14008 on Tackling the Climate Crisis at Home and Abroad, the Climate and Economic Justice Screening Tool (CEJST) is a geospatial mapping tool designed to identify disadvantaged communities that are marginalized and overburdened by pollution and underinvestment, for the purposes of Justice40 Initiative.

This digital map database, compiled from previously published and unpublished data, and new mapping by the authors, represents the general distribution of bedrock and surficial deposits in the mapped area. Together with the accompanying text file (nesfmf.ps, nesfmf.pdf, nesfmf.txt), it provides current information on the geologic structure and stratigraphy of the area covered. The database delineates map units that are identified by general age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. The scale of the source maps limits the spatial resolution (scale) of the database to 1:62,500 or smaller.

Shapefile contains census tracts identified as Equity Priority Communities by MTC as part of the Plan Bay Area 2050 process for the five counties that are included in the Bay Area Regional Climate Action Planning Initiative Frontline Communities Map.

The original shapefile was downloaded from the Metropolitan Transportation Commission (MTC), Equity Priority Communities webpage. The “Clip” tool in ArcMap was used to select only those features which are located within the boundaries of the five Bay Area counties included in the Frontline Communities Map. Only those census tracts where epc_2050 column is equal to 1 are displayed. Where, epc_2050 is defined as "Equity Priority Community PBA 2050" in the original codebook and 1 is equivalent to a true statement. To learn more about the methodology behind the original dataset, please visit: https://opendata.mtc.ca.gov/datasets/MTC::equity-priority-communities-plan-bay-area-2050/about

The Frontline Communities Map is meant to help identify communities that are considered frontline communities for the purpose of the USEPA’s Climate Pollution Reduction Grant (CPRG) program’s planning effort, which is a five-county climate action planning process led by the Air District. USEPA refers to these communities as low-income and disadvantaged communities (LIDACs).

Formerly called “Communities of Concern,” Equity Priority Communities are census tracts that have a significant concentration of underserved populations. The Equity Priority Communities framework helps MTC make decisions on investments that meaningfully reverse the disparities in access to transportation, housing and other community services.

The Equity Priority Communities (tract geography) dataset is based upon eight demographic variables: • People of Color (70% threshold) • Low-Income (28% threshold) • Limited English Proficiency (12% threshold) • Seniors 75 Years and Over (8% threshold) • Zero-Vehicle Households (15% threshold) • Single Parent Families (18% threshold) • People with a Disability (12% threshold) • Rent-Burdened Households (14% threshold)

A tract is considered an Equity Priority Community: 1. If a tract exceeds both threshold values for BOTH Low-Income AND People of Color, or 2. If a tract exceeds the threshold value for Low-Income AND exceeds the threshold values for three or more of the six remaining variables

This dataset is intended for researchers, students, and policy makers for reference and mapping purposes, and may be used for basic applications such as viewing, querying, and map output production, or to provide a basemap to support graphical overlays and analysis with other spatial data.

Alameda County is located at the northern end of the Diablo Range of Central California. It is bounded on the north by the south flank of Mount Diablo, one of the highest peaks in the Bay Area, reaching an elevation of 1173 meters (3,849 ft). San Francisco Bay forms the western boundary, the San Joaquin Valley borders it on the east and an arbitrary line from the Bay into the Diablo Range forms the southern boundary. Alameda is one of the nine Bay Area counties tributary to San Francisco Bay. Most of the country is mountainous with steep rugged topography. Alameda County is covered by twenty-eight 7.5' topographic Quadrangles which are shown on the index map (alq_quad or Sheet 2). The Quaternary deposits in Alameda County comprise three distinct depositional environments. One, forming a transgressive sequence of alluvial fan and fan-delta facies, is mapped in the western one-third of the county. The second, forming only alluvial fan facies, is mapped in the Livermore Valley and San Joaquin Valley in the eastern part of the county. The third, forming a combination of Eolian dune and estuarine facies, is restricted to the Alameda Island area in the northwestern corner of the county.

In 1984, the General Assembly enacted the Chesapeake Bay Critical Area Act to regulate development, manage land use and conserve natural resources on land in those areas designated as Critical Area. For this document, the Critical Area is all land and water areas within 1,000 feet of the tidal waters' edge or from the landward edge of adjacent tidal wetlands and the lands under them. Georeferenced digital data files of the critical Area have been produced for Baltimore City and the 16 Maryland counties with land located within the Critical Area. The digital maps produced for each jurisdiction are polygons depicting the Critical Area and the land use classifications recognized by the Chesapeake Bay Critical Area Commission (CBCAC). Each jurisdiction is a separate file. The data were produced from hard copy parcel maps originally submitted by the counties as part of the requirements for developing their Critical Area Program. For the purpose of the Mdimap web service the Critical Area Data is displayed by two data layers, one general layer and one layer showing the available critical area data for local towns.This data set represents the Department of Natural Resources interpretation of the location and extent of the Critical Area; however, the digital maps are not recognized as the "official" maps. In accordance with Subsection 8-1807(a) of the Critical Area Act, the Critical Area consists of (1) All waters and lands under the Chesapeake Bay and its tributaries to the head of tide as indicated on the State wetland maps, and all State and private wetlands designated under Environment Article, Title 16, annotated Code of Maryland; (2) All land and water areas within 1,000 feet beyond the landward boundaries of State or private wetlands and the of tides designated under Environment Article, Article 16, Annotated Code of Maryland; and (3) Modification to these areas through inclusions or exclusions proposed by local jurisdictions and approved by Commission as specified in Natural Resources Article, Subsection 8-1807, annotated Code of Maryland. These maps are hard copy maps that cannot be exactly replicated in a digital format; therefore, some interpretation was necessary to create the digital line. Hard copy maps depicting the official Critical Area boundary line are available for review at the Chesapeake Bay Critical Area Commission, and at most local planning and zoning departments. The Department of Natural Resources makes no warranty, expressed or implied, as to the use or appropriateness of Spatial Data, and there are no warranties of merchantability or fitness for a particular purpose or use. The intended use is for general information and planning purposes. It is not intended to be used to determine the exact location of the Critical Area boundary on a specific parcel or to determine the acreage within the Critical Area on a specific site. The information contained in Spatial Data is from publicly available sources, but no representation is made as to the accuracy or completeness of Spatial Data. The Department of Natural Resources shall not be subject to liability for human error, error due to software conversion, defect, or failure of machines, or any material used in the connection with the machines, including tapes, disks, CD-ROMs or DVD-ROMs and energy. The Department of Natural Resources shall not be liable for any lost profits, consequential damages, or claims against the Department of Natural Resources by third parties. The liability of the Department of Natural Resources for damage regardless of the form of the action shall not exceed any distribution fees that may have been paid in obtaining Spatial Data.There were many parties involved in producing Maryland's Critical Area data and the key parties will be listed. Each county and city (listed below) produced a hard copy map and submitted the map to the Chesapeake Bay Critical Area Commission (CBCAC) for approval. Through Coastal Zone Management grants, CBCAC digit

The San Francisco Bay Region Jurisdictions feature set was developed by the Metropolitan Transportation Commission so tables containing values for both incorporated and unincorporated areas could be joined to a spatial feature set for mapping and analysis. County-level, 2020 TIGER/Line shapefiles, current as of May 28, 2021, were used to develop this feature set. Incorporated places (cities and towns) were erased from the county shapefile for the region. The remaining county areas (unincorporated lands) were then added to the incorporated places to produce a full, incorporated-unincorporated feature set for the region. For the final processing step, major water features were clipped from the jurisdiction feature set so only land areas remained.

This raster dataset depicts a final version of the Coarse Filter Vegetation Map as a 30 meter grid with 61 cover types, 51 of which are natural or semi-natural land cover, for the nine county San Francisco Bay Area Region, California. See Resource Details for detailed data compilation description. This data was compiled from data sourced from the United States Department of Agriculture Forest Service, The Nature Conservancy and the California Department of Forestry and Fire.

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

This map shows the potential of widespread slope failures, in terms of landslide probability, triggered by a M7.0 scenario earthquake on the Hayward Fault in the 10-county area surrounding the San Francisco Bay region, California. The likelihood of landsliding was evaluated using an equation developed by Jibson and others (2000) that estimates landslide probability as a function of predicted Newmark displacement. Based on this equation, four landslide probability categories are established with their corresponding percent likelihood and displacement ranges: Low (0-2%; 0-1 cm), Moderate (2-15%; 1-5 cm), High (15-32%; 5-15 cm), and Very High (>32%; >15 cm).The seismic-landslide probability map covers the counties of Alameda, Contra Costa, Marin, Napa, San Francisco, San Mateo, Santa Clara, Santa Cruz, Solano, and Sonoma. The slope failures are triggered by a hypothetical earthquake with a moment magnitude of 7.0 occurring on April 18, 2018, at 4:18 p.m. on the Hayward Fault in the east bay part of California’s San Francisco Bay region.

Contra Costa County is located at the northern end of the Diablo Range of Central California. It is bounded on the north by Carquinez Strait, through which flows 27 percent of California's surface water runoff. San Francisco Bay forms the western boundary, the San Joaquin Valley borders it on the east and the Livermore Valley forms the southern boundary. Contra Costa is one of the nine Bay Area counties with streams that are tributaries to San Francisco Bay. Most of the county is mountainous with steep rugged topography. Mount Diablo, in the center of the county, is one of the highest peaks in the Bay Area, reaching an elevation of 1173 meters (3,849 ft). Contra Costa County is covered by twenty-five 7.5' topographic Quadrangles shown on the index map (ccq_quad or Sheet 2). However, two of the quadrangles (Hayward and Petaluma Point) contain no Quaternary deposits in Contra Costa County, and so are not discussed herein. The Quaternary deposits in Contra Costa County comprise two distinct depositional environments. One, forming a transgressive sequence of alluvial fan and fan-delta deposits, is mapped in the western four-fifths of the county. The second, forming a combination of eolian dune and river delta deposits, is mapped in the San Joaquin Valley in the eastern part of the county.

This polygon shapefile displays Census tracts for the San Francisco Bay Area in California based on entity boundaries established on January 1, 1990. Census tracts are small, relatively permanent statistical subdivisions of a county (or statistical equivalent of a county), and are defined by local participants as part of the U.S. Census Bureau's Participant Statistical Areas Program. The U.S. Census Bureau delineated the census tracts in situations where no local participant existed or where local or tribal governments declined to participate. This layer is part of the Bay Area Metropolitan Transportation Commission (MTC) GIS Maps and Data collection.