The "Create Buffers" analysis tool in ArcGIS Online can be used to identify areas within a given distance of existing features, be those points, lines or polygons.The distance used for the buffers can either be a fixed distance from all features, or could be taken from a numerical value within each features attributes.

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

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

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

Point of Contact

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

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated

This feature layer is generated from running the Buffer Features solution. Input from Water Distribution Sites were buffered by 1 Mile. This layer contains a buffer of water distribution sites used during the 2021 winter storm response. The distribution site were emergency shelter locations during the 2021 winter storm response. These locations can and will likely change depending on needs of future emergency activations. This data should be verified with Emergency Operation Center leadership. Last updated February 25, 2021

This dataset was developed from data produced by Rastermatics which was derived from 2008 ALS data. To be used in conjunction with the Wetland_Area Feature Class which identifies corresponding wetlands.

The Green Zones Ordinance was adopted by the Board of Supervisors on July 14, 2022. As stated in the summary memo: "The Green Zones Ordinance seeks to enhance public health and land use compatibility in the unincorporated communities that bear a disproportionate pollution burden and establish Countywide standards for recycling and waste management." For more information about the Green Zones Program, please visit our website here.Using the data layers for Sensitive Uses that were used in the Green Zones ordinance, these are the 500' buffers from sensitive uses within Green Zone Districts. Sensitive Uses include schools, dwelling units, playgrounds, nursing homes, hospitals and licensed day care facilities.UPDATE HISTORY:1/20/22 - Layer created6/1/22 - Layer was updated to remove non-conforming residential Assessor uses from within an industrial zone, which reduced some of the buffers within Avocado Heights, East Los Angeles, West Rancho Dominguez-Victoria, and Willowbrook.7/5/22 - Added one additional school that was missed previously (a High School and Charter School within SW Comm College in W. Athens), and added to the buffering there.

This orange layer shows a 250-meter turbidity buffer of the blue 45-meter growth buffer (blue layer called "SF Bay Eelgrass 45m Buffer") adjacent to the maximum extent eelgrass survey in the San Francisco Bay. When a dredging project’s footprint overlaps with this 250-meter buffer, indirect impacts to eelgrass are assessed and best management practices are required per the National Marine Fisheries Service's LTMS Programmatic Essential Fish Habitat consultation. Methods for creating this layer are as follows: Downloaded Bay-wide Eelgrass Surveys for 2003, 2009, and 2014 by Merkel & Associates, Inc. (Merkel) from SFEI. Obtained Richardson Bay 2019 eelgrass survey from Merkel. Loaded all layers into ArcGIS Pro © ESRI and re-projected all data to NAD 1983 UTM Zone 10N. Used Buffer tool to develop a single multipart shapefile with a 45-meter buffer of the 2003, 2009, 2014, and 2019 survey data . Imported the Pacific Marine and Estuarine Fish Habitat Partnership (PMEP) Estuary Extent layer and clipped the 45-meter buffer over terrestrial areas based on the PEMP Estuary Extent (this represents the 45-meter eelgrass buffer layer also found in this Web Application). To create the 250-meter turbidity buffer from there, the same methods were used as follows. Used Buffer tool to develop a single multipart shapefile with a 250-meter buffer from the 45-meter buffer layer. Clipped the 250-meter turbidity buffer over terrestrial areas based on the PEMP Estuary Extent. Some minor adjustments were made where the 250-meter turbidity buffer layer resulted in fragments on land or behind levees.

This layer is a 45-meter growth buffer surrounding the maximum extent of eelgrass (green layer called "SF Bay Eelgrass") surveyed in San Francisco Bay. Eelgrass beds are highly dynamic and the exact location and extent of eelgrass beds can change across seasons and years. Thus, the purpose of the 45-meter growth buffer, as described in the National Marine Fisheries Service's LTMS Programmatic Essential Fish Habitat consultation is to account for areas between eelgrass patches, temporal variation in bed extent, and potential bed expansion. In cases where a dredge project intersects with the 45-meter growth buffer direct impacts to eelgrass may occur and therefore assessment, minimization, and mitigation measures may be required on a project-by-project basis. A pre-dredge eelgrass area and density survey is required 30 days prior to the start of dredging and should be submitted to the LTMS permitting agencies. Methods for creating this layer are as follows: Downloaded Baywide Eelgrass Surveys for 2003, 2009, and 2014 by Merkel & Associates, Inc. (Merkel) from San Francisco Estuary Institute (SFEI) website. Obtained Richardson Bay 2019 eelgrass survey from Merkel. Loaded all layers into ArcGIS Pro © ESRI and re-projected all data to NAD 1983 UTM Zone 10N. Used Buffer tool to develop a single multipart shapefile with a 45-meter buffer of the input layers. Imported the Pacific Marine and Estuarine Fish Habitat Partnership (PMEP) Estuary Extent layer and clipped the 45-meter buffer over terrestrial areas based on the PEMP Estuary Extent. Some minor adjustments were made where the buffer layer resulted in fragments on land or behind levees.

The Tompkins County hydrology data set was used to create 100' polygon buffer of stream centerline of perennial streams

.5, 1, and 2 mile buffers around municipal and county parks. This web map is used in the Parks and Rec Dashboard and uses the Parks Buffer feature layer. This data was created as part of the Manager's Office Chatham County Performance Hub.

Connecticut Buffered Roads is 1:24,000-scale base map data. This layer is intended to be used with the Roads and Trails layer to reproduce the cartographic symbology established by the USGS for printing roads and trails on the 1:24,000-scale, 7.5-minute topographic quadrangle maps. Cartographically, the Buffered Roads layer is used to assign thin, black line symbology to the edges or curb lines of paved and unpaved roads on the quadrangle maps. Paved roads are symbolized with a narrow solid black line. Unpaved roads are symbolized with a narrow dashed black line. Complementing this symbology, the Roads and Trails layer is used to assign line symbology that 'fills in' the corresponding buffered road area with solid red or dashed red line work, depending on road class. Line symbology should be assigned to Roads and Trails features with AV_LEGEND attribute values equal to Primary Route (wide solid red), Secondary Route (wide dashed red), and Trail (narrow dashed black). Used in combination, Buffered Roads symbology outlines the centerline-based symbology applied to the Roads and Trails layer. For base map purposes, use this layer with other 1:24,000-scale base map data such as Hydrography, Railroads, Airports, and Towns. The Buffered Roads layer includes information within Connecticut and is derived from the Buffered Roads Master layer, which reproduces all buffered road features depicted on all of the U.S. Geological Survey (USGS) 7.5 minute topographic quadrangle maps that cover the State of Connecticut. This layer is a cartographic product and should only be printed on maps at 1:24,000 scale (1 inch = 2,000 feet.).

Connecticut Buffered Roads is a 1:24,000-scale, feature-based layer of paved and unpaved roads on the U.S. Geological Survey (USGS) 7.5 minute topographic quadrangle maps for the State of Connecticut. This layer only includes features located in Connecticut. This layer is cartographic in nature. It is designed to be used with maps printed at 1:24,000-scale that require road symbology similar to the standard established by the USGS for 1:24,000-scale, 7.5 minute topographic quadrangle maps. Two layers, the Buffered Roads layer and the Roads and Trails layer, are used together for this purpose. Buffered Roads features are linear and run parallel to the road (centerline) features of the Roads and Trails layer. Buffered Roads is a set of parallel lines 50 feet apart that result from a buffer on each side of the Road and Trail (centerline) features by a distance of 25 feet. A width of 50 feet is applied to all roads, regardless of road class, and does not reflect actual pavement width. The Buffered Roads layer does not include features on the topographic quadrangle maps that appear as single lines such as hiking trails, small private roads, and old railroad grades. These features are found in the more complete Roads and Trails layer. The Buffered Roads layer is derived from information from USGS topographic quadrangle maps published between 1969 and 1984 and does not represent the road network in Connecticut at any one particular point in time. The layer does not depict current conditions and excludes many roads that have been built, modified, or removed since the time these topographic quadrangle maps were published. The layer includes buffered centerlines for Interstate highways, US routes, state routes, local roads, unpaved roads, traffic circles, bridges, cul-de-sacs, etc. Trails are not included. Features are linear and approximate road curb lines at 1:24,000 scale. Attribute information is comprised of codes to cartographically represent (symbolize) paved and unpaved roads on a map. This layer was originally published in 1994. The 2005 edition includes the same road features published in 1994, but the attribute information has been slightly modified and made easier to use.

The Natural Filter Buffer Targeting layers identify riparian forest and grass buffer opportunities by county. Land use and hydrology characteristics were used to identify potential riparian buffer locations. These data are inputs into the Natural Filter Buffer Priorities for Water Quality models.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/Environment/MD_NaturalFilters/MapServer/0

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

Purpose

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

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

Related Layers

This dataset is part of a grouping of many datasets:

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

Point of Contact

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

Field and Abbreviation Definitions

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

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. Student safety zones are 1000' buffers around a school facility (Elementary, Middle and High school). Registered sex offenders are not permitted to live within these buffers. When a sex offender moves, they are required by law to register with the local law enforcement, who must verify that the address is not within a safety zone. Though the definition of a school safety zone could change with legislation, the parameters that were used to create this data were: A buffer of 1000’ from the parcel boundary of the school (versus just the centroid of the parcel, or from the building itself)Any K-12 school, public or private, should have a buffer. Teaching needs to occur in the building (i.e., not admin-only buildings)Preschools and day cares are excludedThis polygon feature class was originally created by buffering the Oakland County's Educational feature class. The key attributes include the facility Name, Address,Type (Elementary, Middle, High) and Access (Public, Private).

Shoreline Situation Reports (SSR) were first generated by VIMS in the 1970s to report the condition and status of the shore lands. The SSR series were published in hardcopy on a county by county basis for each of the Tidewater Virginia localities. The reports were intended to assist planners, managers, and regulators in decisions pertaining to management of coastal areas and natural resources therein. The techniques developed for Virginia's shoreline are used to create similar reports for the Maryland shoreline. Data collected describes conditions in the immediate riparian zone, the bank, and along the shore. These data should not be used for jurisdictional permit determinations beyond providing general shoreline condition or status information. These data have not been surveyed to property boundaries.This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Map Service Link: https://mdgeodata.md.gov/imap/rest/services/Hydrology/MD_ShorelineInventory/MapServer/4

Shoreline Situation Reports (SSR) were first generated by VIMS in the 1970s to report the condition and status of the shore lands. The SSR series were published in hardcopy on a county by county basis for each of the Tidewater Virginia localities. The reports were intended to assist planners, managers, and regulators in decisions pertaining to management of coastal areas and natural resources therein. The techniques developed for Virginia's shoreline are used to create similar reports for the Maryland shoreline. Data collected describes conditions in the immediate riparian zone, the bank, and along the shore. These data should not be used for jurisdictional permit determinations beyond providing general shoreline condition or status information. These data have not been surveyed to property boundaries.This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Map Service Link: https://mdgeodata.md.gov/imap/rest/services/Hydrology/MD_ShorelineInventory/MapServer/5

The pond polygons for the 2020 Cape Cod Pond Atlas were buffered 300 feet. The subdived polygons process was used to create two equal area halves of the buffer which were then marked in the gradient field as to up or down gradient. Elevation of polygon centroids on a surface of the water table were used to determine up/down.

Range polygons may include areas not currently occupied by a species and, conversely, may omit areas potentially used by a species. The boundary delineations are primarily based on ecoregion subsections (USDA F.S., Ecomap Subsections 2007), watersheds (USGS HUC12) and 10 Kilometer occurrence buffers. The ecoregions subsections and hucs were combined and will heretofore be referred to as "ecohuc"s. Criteria used to delineate range boundaries:Select all occupied ecohucs.Buffer species occurrences by 10 Kilometers (per maximum buffer distance suggested by scientific literature).If occurrence buffer extends outside a selected subsection, expand subsection boundary to incorporate buffer or ecohuc after assessing vegetational characteristics with subject matter experts.If non-selected subsection is surrounded by selected subsections, incorporate non-selected subsections into species range.Clip species range by California State boundary.Merge ecoregion subsections to create a seamless species range polygon.EcomapSubsections 2007 - MetadataThe Ecomap Subsections feature class contains ecological subsection polygons attributed with subsection names and descriptions. The EcomapSubsections 2007 data set describes the ecological subsections within the conterminous United States. It contains regional geographic delineations for analysis of ecological relationships across ecological units. ECOMAP is the term used for a USDA Forest Service initiative to map ecological units and encourage their use in ecosystem-based approaches to forest land conservation and management. This is a collaborative effort with many partners. It is coordinated at the national and regional levels by USDA Forest Service staff and implemented in cooperation with State forestry agencies and others. ECOMAP mapping criteria are outlined in the National Hierarchical Framework of Ecological Units (https://www.fs.usda.gov/Internet/FSE_DOCUMENTS/stelprdb5286434.pdf). The framework systematically divides the country into progressively smaller areas of land and water that have similar physical and biological characteristics and ecological processes. Note: The "EcomapSubSections_2007" was downloaded from the USDA Forest Service Clearing House website on January 17, 2023.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

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

Point of Contact

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

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

Contributing Area to Ponds (CAPs) - To be more protective of ponds, two areas, the Freshwater Recharge Area and the 300 foot buffer upgradient of a pond, were effectively combined on the RPP Data Viewer to yield Contributing Area to Ponds (CAPs). Upgradient Pond Buffer - These areas of the 300-ft buffer zone are delineated as significant based on groundwater contours and groundwater flow direction. To calculate and classify groundwater flow direction across ponds on Cape Cod, aspect rasters derived from interpolated water table surfaces and ½ foot elevation contours were used. Three-hundred-foot buffers around the ponds were added. Final output identified whether each side of the pond’s buffer zone is facing “up” or “down” in terms of water table gradient. The buffers were split in half, with the half of the buffer facing “up” as upgradient of the pond. Freshwater Recharge Areas - This layer identifies potential Priority Lands for Future Water Supply Development. The in-house analysis studied the natural, pervious land cover areas across Cape Cod and delineated places where at least one well & well protection buffer diameter could be reasonably placed based on the absense of certain conflicting land uses.