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.

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 map depicts Bald Eagle nesting sites, based on nest surveys conducted in 2022 in the state of Maine. This map depicts intact Bald Eagle nests in Maine with a 330' and 660' buffer zone established around each site that correspond with protection guidelines in the USFWS National Bald Eagle Management Guidelines. These locations were identified by an aerial survey during the nesting season and were last updated in 2023. There may be new nest locations in your area since the last survey. Thus further surveys are recommended for proposed projects. You must "zoom in" to the nest locations for the actual nest sites to appear. For more information, please contact the USFWS Maine Ecological Services Field Office. Contact information can be found here.

This feature represents the entire area considered as the U.S.-Mexico border region for the U.S.-Mexico Border Program. The extent of the area was agreed upon between the United States and Mexico under the 1983 La Paz Agreement. The framework of this agreement stated that the border area is defined as "the area situated 62 miles (100 kilometers) on either side of the inland and maritime boundaries". This layer was generated by buffering the Homeland Infrastructure Foundation-Level Data (HIFLD) "Mexico and US Border" layer (https://hifld-geoplatform.opendata.arcgis.com/datasets/geoplatform::mexico-and-us-border/about) by [60] Miles. These data support the U.S.-Mexico Border Program Map, which highlights the projects funded through the U.S.-Mexico Border Program (2013-2020) in both Region 9 and Region 6 of the U.S. EPA, including U.S. Federally recognized Tribal communities and states of Texas, New Mexico, Chihuahua, Nuevo Leon, Tamaulipas, Coahuila, California, Baja California, Sonora, and Arizona within 62 miles (100 kilometers) of the U.S.-Mexico Border. The projects stem from the Border 2020 framework that has five goals to reduce air pollution, improve access to clean water, promote materials and waste management, improve emergency preparedness, and enhance environmental stewardship, and fundamental strategies that includes children's health and environmental education and outreach. For more information about Border 2020 and/or current U.S.-Mexico Border program visit this website: https://www.epa.gov/usmexicoborder

Polygon features 200 foot buffers around rivers and streams within Dedham, MA. Waterbodies were collected planimetric data collected in April 2004. Some updates from the City of Boston collected in 2011 are included.

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

This feature class represents combined 200ft and 1000ft beach buffers derived from Intertidal_PL. The process for creating this combined buffer is as follows: Select from Intertidal_PL where Description in ( 'CHK' , 'INT', 'EST', 'UIT' ) and buffer it 1000 ft, then dissolve all, so it's just a big ol' blob. Use the same selected set from Intertidal_PL and buffer it 200 feet, then dissolve all.Then select from Intertidal_PL where Description in ( 'CHK' , 'SW', 'EST' ) and erase those areas from the big buffered blobs. (I do not erase the INT areas because that might leave gaps and slivers along the shoreline above the water.)Add a field called Buff1000ft to the 1000 foot buffer and populate it with 'Y'. Add a field called Buff200ft to the 200 foot buffer and populate it with 'Y'. Identity the 200 ft buffer onto the 1000 ft buffer.Select where the field Buff200ft is blank and populate it with 'N'. (This would be the area within the 1000 ft buffer that falls outside of the 200 ft buffer.)The resulting buffer polygons can end up being wider than 1000ft or 200ft respectively in some places (beach…etc), but the intent of the polygons is to go landward 1000ft/200ft – the additional width is due to the beach/island/peninsula type stuff. The reason I originally started choosing to buffer CHK, INT, EST, and UIT was because I was concerned that buffering only INT might lead to odd gaps.

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

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.

This is a polygon layer of 200-feet buffer area around signalized intersections operated and maintained by the City of Dallas.

This polygon layer represents the buffer zone established by city/county ordinance for the waterways in Newport News and other nearby localities. The City of Newport News complies with the Chesapeake Bay Preservation Act in order to protect the quality of water in the Bay. The Chesapeake Bay is one of the most important and productive estuarine systems in the world, providing economic and social benefits to the citizens of Newport News and the Commonwealth of Virginia. Portions of Newport News are designated as Chesapeake Bay Preservation Areas.Buffer zone means an area of natural or established vegetation managed to protect other components of a resource protection area and state waters from significant degradation due to land disturbances. This buffer area consists of three (3) trophic layers: trees, shrubs and ground cover.According to Newport News City Code: "a buffer area not less than one hundred (100) feet in width, located adjacent to and landward of the components listed in subsections a. through c. above, and along both sides of any water body with perennial flow. The full buffer area shall be designated as the landward component of the resource protection area notwithstanding the presence of permitted uses, encroachments and permitted vegetation clearing in compliance with section 37.1-51".

This is a polygon data set representing Boise Parks and Recreation data. A park is generally an area of land in a largely natural state, sometimes with grass, trees, paths, sports fields, playgrounds, picnic areas and other facilities, that is set aside and managed specifically for recreation use and enjoyment by the public. The features included in this polygon feature class are; parks, reserves, city maintained cemeteries, city maintained road rights-of-ways and greenbelt areas. This data set was created from a combination of Boise Parks and Recreation park and facility files and the Ada County Parcel records. This dataset was created by POWER Engineer's, Inc. and will be maintained by the City of Boise. This data set is updated at the request of Boise Parks and Recreation staff as changes to the park data occur. It is current to the date it was published.

This data set contains parcel polygon, tax block polygon, and leasehold polygon features classes, as well as several object classes (tables), for Cook County, Illinois, including a PIN table, a Ref_PIN table, a condo table, and a condo miscellaneous table. The cadastral data for Cook County have previously not been digital nor automated. This project is the initial automation for this information. This database was designed to represent a continuous, non-overlapping spatial database accounting for all land area in Cook County.

Taupō District Electricity Transmission Line 32m buffer polygon as identified within the Taupō District Plan, resulting from Plan Change 29 (Taupō and Centennial Industrial Environments), operative from 20 March 2015. Transmission line features can be downloaded from the LINZ Data Service or from the Transpower open data site.The Taupō District Plan has been operative since 2007. Selected datasets from the Taupō District Plan have been made available for download to allow for better public access to the data underlying the plan. Note that some features mapped for district plan purposes may have changed over time. Taupō District Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the District Plan data released for public download. The data provided is indicative only and does not purport to be a complete database of all information in Taupō District Council's possession or control. Taupō District Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data. While you are free to crop, export and repurpose the data, we ask that you attribute the Taupō District Council and clearly state that your work is a derivative and not the authoritative data source. Please include this statement when distributing any work derived from this data:This work is a derivative of the Taupō District Plan. You can view the full Taupō District E-Plan here: https://taupo.isoplan.co.nz/eplan/

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.

Polygon layer of emergency management siren signal radius buffers for Jefferson, Bullitt, Oldham & Shelby County. View detailed metadata.

Environmentally critical area layer used as an overlay for the City of Seattle Zone Development Capacity Model. Areas represent the ECAs that would reduce the amount of development on a development site. This layer is for analytical purposes only and does not represent actual regulatory areas or development regulation, rather an approximation of the potential impact on a development site.These areas include:Steep Slopes (40% or greater)Remove all steep slope polygons less than 1,000 square feet in size For remaining steep slope polygons:Treat areas within steep slope ECAs as if only 30% is developable. For example, on a 10,000 square foot site where half is in a steep slope ECA, we would treat it like at 6,500 square foot site (5,000100% + 5,00030%)Riparian CorridorsIgnore riparian corridors where the creek is in a culvertFor other riparian corridors:Assume there will be no development in that riparian corridor and a buffer of 50 feet for streams without salmon and 75 feet for streams with salmonAssume 30% of regular development potential in remainder of a 100 feet buffer from the riparian corridor (i.e. the next 50 feet for streams without salmon and the next 25 feet for streams with salmon).WetlandsRemove all wetlands polygons less than 1,000 square feet in sizeFor all other wetland polygons:For all wetland polygons greater than or equal to an acre, put a 200 foot buffer around them and assume no development will occur in the wetland or the bufferFor all wetlands less than an acre, put an 80 foot buffer around them and assume no development in wetland or buffer. Wetlands other than category I have a variety of buffers, but in general we see about half have 50 foot buffers and the other half have 110 foot buffers (with an average of 80 feet)Supporting Documentation

The Walk to a Park initiative focuses on increasing access to parks and open spaces, concentrating on areas of the city that are under-resourced and where residents are living further than a walk to a park. NYC Parks calculates the number of New Yorkers within walking distance of a park and reports on this as part of the Mayor’s Management Report. “Walking distance” is defined as a 1/4-mile or less for sites such as small playgrounds and sitting areas; or a 1/2-mile or less for larger parks that serve a wider region, typically over 8 acres or situated on the waterfront. Certain properties in NYC Parks' portfolio, such as cemeteries, community gardens, or sites with no recreational equipment were not included in this analysis. Similarly, some parks and open-space amenities not under the jurisdiction of NYC Parks were included in this analysis, as they provide recreational value.

This dataset includes two ESRI shapefiles of access points, one for sites that get a 1/4-mile buffer and one for sites that get a 1/2-mile buffer. It also includes an ESRI shapefile of the combined polygon that is the output of this analysis. This polygon represents the total area within walking distance of a park. To generate the number of New Yorkers within that distance, the polygon is compared with data from the U.S. Census.

This information is only current as of the publication date. For more information about this analysis and the Walk to a Park Initiative, visit: https://www.nycgovparks.org/planning-and-building/planning/walk-to-a-park

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 excluded

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

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. The digital aerial photos for Tonto NM were evaluated in ArcGIS (ESRI) to define and delimit distinct vegetation structural characteristics at what will hereafter be termed the “formation” level. Formations were defined by a combination of structural properties, including height, texture, color, and the relative percent cover of tree, shrub, and herbaceous vegetation. For Tonto NM, polygons (a closed line encompassing an area) were hand-digitized in ArcMap 9.0 (ESRI) around each visibly distinct formation across the entire park area, including a ~100-m buffer at the park boundary. Polygon lines were drawn such that homogeneity of visible characteristics was maximized within each polygon while minimizing the amount and size of structurally different inclusions of less than 0.5 hectares (1.24 ac) in size (Figure 2-2). Other spatial data were used to assist in this process, including digital elevation models (DEM) and contour lines. A minimum mapping unit of 0.5 hectares was observed, as set forth in the NVC standards. Distinct areas smaller than 0.5 hectares had to be included in an adjacent or enveloping polygon. All polygons were drawn such that adjacent polygon boundaries were shared, (i.e., there were no gaps between polygons) and complete coverage of the study area was achieved. The classification work led to the identification of 23 different vegetation types at the association level, attributed to 82 polygons.