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 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

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.

The Viewshed analysis layer is used to identify visible areas. You specify the places you are interested in, either from a file or interactively, and the Viewshed service combines this with Esri-curated elevation data to create output polygons of visible areas. Some questions you can answer with the Viewshed task include:What areas can I see from this location? What areas can see me?Can I see the proposed wind farm?What areas can be seen from the proposed fire tower?The maximum number of input features is 1000.Viewshed has the following optional parameters:Maximum Distance: The maximum distance to calculate the viewshed.Maximum Distance Units: The units for the Maximum Distance parameter. The default is meters.DEM Resolution: The source elevation data; the default is 90m resolution SRTM. Other options include 30m, 24m, 10m, and Finest.Observer Height: The height above the surface of the observer. The default value of 1.75 meters is an average height of a person. If you are looking from an elevation location such as an observation tower or a tall building, use that height instead.Observer Height Units: The units for the Observer Height parameter. The default is meters.Surface Offset: The height above the surface of the object you are trying to see. The default value is 0. If you are trying to see buildings or wind turbines add their height here.Surface Offset Units: The units for the Surface Offset parameter. The default is meters.Generalize Viewshed Polygons: Determine if the viewshed polygons are to be generalized or not. The viewshed calculation is based upon a raster elevation model which creates a result with stair-stepped edges. To create a more pleasing appearance, and improve performance, the default behavior is to generalize the polygons. This generalization will not change the accuracy of the result for any location more than one half of the DEM's resolution.By default, this tool currently works worldwide between 60 degrees north and 56 degrees south based on the 3 arc-second (approximately 90 meter) resolution SRTM dataset. Depending upon the DEM resolution pick by the user, different data sources will be used by the tool. For 24m, tool will use global dataset WorldDEM4Ortho (excluding the counties of Azerbaijan, DR Congo and Ukraine) 0.8 arc-second (approximately 24 meter) from Airbus Defence and Space GmbH. For 30m, tool will use 1 arc-second resolution data in North America (Canada, United States, and Mexico) from the USGS National Elevation Dataset (NED), SRTM DEM-S dataset from Geoscience Australia in Australia and SRTM data between 60 degrees north and 56 degrees south in the remaining parts of the world (Africa, South America, most of Europe and continental Asia, the East Indies, New Zealand, and islands of the western Pacific). For 10m, tool will use 1/3 arc-second resolution data in the continental United States from USGS National Elevation Dataset (NED) and approximately 10 meter data covering Netherlands, Norway, Finland, Denmark, Austria, Spain, Japan Estonia, Latvia, Lithuania, Slovakia, Italy, Northern Ireland, Switzerland and Liechtenstein from various authoritative sources.To learn more, read the developer documentation for Viewshed or follow the Learn ArcGIS exercise called I Can See for Miles and Miles. To use this Geoprocessing service in ArcGIS Desktop 10.2.1 and higher, you can either connect to the Ready-to-Use Services, or create an ArcGIS Server connection. Connect to the Ready-to-Use Services by first signing in to your ArcGIS Online Organizational Account:Once you are signed in, the Ready-to-Use Services will appear in the Ready-to-Use Services folder or the Catalog window:If you would like to add a direct connection to the Elevation ArcGIS Server in ArcGIS for Desktop or ArcGIS Pro, use this URL to connect: https://elevation.arcgis.com/arcgis/services. You will also need to provide your account credentials. ArcGIS for Desktop:ArcGIS Pro:The ArcGIS help has additional information about how to do this:Learn how to make a ArcGIS Server Connection in ArcGIS Desktop. Learn more about using geoprocessing services in ArcGIS Desktop.This tool is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks.

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.

Areas managed as WILDERNESSwithin Glacier National Park. This mapping was compiled in 2014, implementing NPS Director's Order 41 (2013), which provides guidelines to NPS units for delineating wilderness boundaries. The two main criteria provided by DO-41 are that boundaries 1) must be easily identifiable on the ground, and 2) standard boundary setbacks from roads, paved or unpaved, should be 100-feet either side of centerline. Included in this mapping are areas EXCLUDED from wilderness, which generally fall within 100-feet of road centerline or are part of the park's Visitor Service Zone (GMP, 1999). Additional areas categorized as 'Excluded from wilderness' include lands designated as part of the Visitor Service Zone (VSZ), documented in the GLAC Commercial Serices Plan (2004). Developed area footprints were mapped and then buffered 300-feet. Utility corridors and point locations were mapped and buffered 25-feet. Also, large lakes with existing commercial services were included in the VSZ and thus were categorized as Excluded.POTENTIAL WILDERNESS AREAS (PWA) are the 3rd map class; these lands are currently in private ownership, providing access to private ownership, or are small fragmented areas (i.e. not easily identified on the ground and difficult to manage as wilderness due to size and surrounding land uses) between areas excluded from wilderness (e.g. utility corridors and lands between utility corridors and other excluded areas).Chronology of edits:Begin edits 11/8/13 to implement DO-41. Update layer March 4, 2014 - create version 3 with the following edits - based on 3/3/14 meeting with GLAC Leadership Team (Kym Hall):1. Camas Cr patrol cabin, include 100-ft buffer of cabin + 100-ft buffer of roadway from Inside Rd.2. Bowman CG area: extend 'excluded' area from admin road to creek edge to accommodate admin road/trail (to bridge) not yet mapped. Also inlcude 100-ft buffered trail and 100-ft buffered buildings due east of bridge. 3. Kintla CG - same changes as Bowman, using standard 100-ft buffer of road/cabins4. Belly River enclave is added to the data set.-----------Update layer January 24, 2014 with these edits:1. Add Marias Pass 'excluded' area; 100-ft buffer of RR turnaround.2. Extend HQ area 'excluded' polygon to river /park bdy3. Create Dev Area footprints for Road Camp & Packer's Roost; buffer 300-ft and add to 'excluded'.----------Update layer January 13, 2014 with these edits:1. Bowman CG - add admin road missed, 2. Walton - remove exclusion area between road buffer and boundary, and 3. Swiftcurrent - include Swiftcurrent+Josephine Lakes as excluded, plus bump-out areas for boat storage and creek used to ferry supplies from Swift. Lake to Josephine Lake.---------Update layer April 15-18, 2014 with these additions/edits:1. Create developed area for Apgar Lookout; buffer 300-ft.2. Create developed area for 1913 Ranger Station (St Mary); buffer 300-ft.3. Add 2 monitoring wells in St Mary Flats (foot of lake south of GTSR); buffer 25-ft and connect to 'excluded area' polygon4. Add water source point for Many Glacier winter cabin (north of MG road near hotel jct; buffer 25-ft and add to 'excluded area' polygon5. Buffer McCarthy Homestead structures 100-ft and add to Excluded Area polygon for Inside North Fork Rd6. Buffer Ford Creek cabin structures 100-ft and add to Excluded Area polygon for Inside North Fork Rd7. Buffer Baring Crek cabin structures 100-ft and add to Excluded Area polygon Going to the Sun Rd8. Add to Excluded Area a strip of land 60-ft south of the International Boundary (per 1974 Wilderness proposal & MOU with GLAC and Int'l Boundary Comm).---------Updated layer 5/27/2014 - add approx. 2 acres to 'Excluded fro mWilderness' near the St Mary River bridge along GTSR. This sliver of land was included to utilize the river bank as a visible and distinguishable boundary in the field.

© NPS, Glacier NP GIS Program

This layer is a component of Glacier National Park.

This map service provides layers covering a variety of different datasets and themes for Glacier National Park. It is meant to be consumed by internet mapping applications and for general reference. It is for internal NPS use only. Produced November 2014.

© Denver Service Center Planning Division, IMR Geographic Resources Division, Glacier National Park

This feature class is a derivative of the 2012 planimetric water layer. It was Generalized using the Cartographic Generalization tool, Simplify Polygon with the Bend Simplify option and a Minimal Allowable Offset tolerance of 5 feet. Additionally the land feature(s) was removed. A collection of vector polygon features for water bodies within the Urban Development Boundary (UDB) and outside the UDB, approximately 938 square miles. The planimetric layer for Miami-Dade County was previously updated in 2007 by Woolpert. Aerial Cartographics of America's update is comprised of two individual updates: inside the UDB (542 square miles) performed using a on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience; and outside of the UDB (396 square miles) using on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience. Personnel that collected this data are either photogrammetrists trained in stereo collection or editors trained in ortho-photography based collection. Items included in the feature class: WATER BODIES (Polygons) Water lines and water under the bridge. Definition of particular fields in the Water feature class: Water = {0,1} where 0 = Feature does not represent water; 1 = Water feature. Type = 'C' = canal, 'L' = Lake and 'B' = BayUpdated: Biennially The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

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

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".

GIS spatial data for World Heritage Sites and their Buffer Zones, where existing, as inscribed by the World Heritage Committee of UNESCO. World Heritage Sites and their Buffer Zones are defined by a polygon defining the extent of the protected area.

A World Heritage Site is a site on a list of properties maintained by the World Heritage Committee of UNESCO and called the World Heritage List "forming part of the cultural heritage and natural heritage...which it considers as having outstanding universal value in terms of such criteria as it shall have established".

Data updated as required.

This feature class is a derivative of the 2012 planimetric water layer. It was Generalized using the Cartographic Generalization tool, Simplify Polygon with the Bend Simplify option and a Minimal Allowable Offset tolerance of 5 feet. A collection of vector polygon features for water bodies within the Urban Development Boundary (UDB) and outside the UDB, approximately 938 square miles. The planimetric layer for Miami-Dade County was previously updated in 2007 by Woolpert. Aerial Cartographics of America's update is comprised of two individual updates: inside the UDB (542 square miles) performed using a on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience; and outside of the UDB (396 square miles) using on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience. Personnel that collected this data are either photogrammetrists trained in stereo collection or editors trained in ortho-photography based collection. Items included in the feature class: WATER BODIES (Polygons) Water lines and water under the bridge. Definition of particular fields in the Water feature class: Water = {0,1} where 0 = Feature does not represent water; 1 = Water feature. Type = {'', 'B'} where B = Water under the bridge. Possible combinations of these fields are: 0,''; 1,'';1, 'B'Updated: Biennially The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

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.

The portion of Lake Huron within one (1) mile from shore and delineated by the following landmarks: St. Martin's Bay zone - from Rabbit Back Point north and east to Brulee Point. Regulations: The waters described above, shall be the Sault Tribe Tribal zone only during the salmon seasons. At all other times, these waters shall be part of the Northern Lake Huron Inter-Tribal Fishing Zone. Bay Mills fishers shall not fish in the portion of this zone described above. Fishing for salmon by the Tribal commercial fishers is limited to the Sault Tribe Tribal Zone described above. Salmon fishing shall be permitted from August 1 through October 15 in the St. Martin's Bay zone. Nets may be fished at the surface at any time during the specified salmon seasons in the areas described above. Outside the specified salmon season, commercial fishing for salmon is prohibited except for incidental harvest. The Tribes shall prohibit the retention of more than two hundred (200) pounds round weight per vessel per day of salmon caught as incidental catch in gill nets in waters and seasons not open to salmon fishing, and shall prohibit any retention of salmon caught in trap nets. Maps for general reference only: refer to text of Consent Decree 2000 for exact locations and provisions.Created a new polyline shapefile in ArcGIS 8.1. Copied selected features (as outlined in the Consent Decree 2000 documentation) of the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer into new shapefile. A one mile buffer was then generated from the polyline shapefile using the buffer wizard tool in Arc Map. Created a new polygon shapefile in ArcGIS 8.1. Copied selected features (as outlined in the Consent Decree 2000 documentation) of the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer into new shapefile. The new polygon feature was then commbined with the one mile buffer created earlier. The desired features were then selected and exported as a new shapefile. Created a new polygon shapefile in ArcGIS 8.1. The new pollygon layer was created using the snapping tool in ArcMap. Snapping to an adjacent layer and heading in a clockwise direction extending the polygon boundaries beyond the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer to encorporate the target area outlined in the Consent Decree 2000 documentation. The new polygon feature was then clipped to the exported polgon created earlier. A point was located on the USGS Mackinac county 1:24,000 DRG as outlined in the Consent Decree 2000 documentation. A one mile buffer was then generated from the point shapefile using the buffer wizard tool in Arc Map. The new buffer was then commbined with the copied polygon generated from the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected and exported as a new shapefile. The new polygon feature was commbined with the clipped polygon using the union tool from the geoprocessing wizard inArcMap. The desired features were then selected and exported as a new shapefile. Created a new polygon shapefile in ArcGIS 8.1. Snapped to the exported polygon layer created above to smooth out intersection. The desired features were then selected, merged as new layer in ArcMap, exported as a new shapefile, and reprojected from Michigan georef to Decimal Degrees to create the final St. Martin's Bay Zone layer.The boundaries represented on consent decree maps are approximations based on the text contained in the 2000 Consent Decree. For legal descriptions of geographic extent or details pertaining to regulations for these representations refer to the original 2000 Consent Decree Document.

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.

A polygon feature representing either an intermittent stream or a wetland that does not satisfy the criteria of an RPA. This identification is mandated through the Chesapeake Bay Program requirements and the City's Environmental Management Ordinance (Article XIII). This represents a 50 foot requirement for a natively vegetated buffer adjacent these sensitive areas. Impervious surfaces are prohibited in this buffer area except under special circumstances.

This dataset consists of polygons that indicate areas of mutual regulatory concern between 2 or more Water Management Districts in the state of Florida and as designated by referenced Memorandum of Understanding (MOU) or Memorandum of Agreement (MOA):SWFWMD_SJRWMD_5MI: This polygon dataset is a 5mi buffer of the shared edge extent between the SWFWMD and SJRWMD derived from the Detailed County boundaries (24K) dataset. SFWMD_SJRWMD: This polygon dataset is a 5mi buffer of the shared edge extent between the SFWMD and SJRWMD and all of Osceola and Orange Counties - derived from the Detailed County boundaries (24K) dataset.CFWI_10MileBuffer: This layer represents a 10-mile buffer around the Central Florida Water Initiative area (CFWI).MARION_CO_10MI: This polygon dataset is a 10-mile buffer of the Marion County, Fl extent derived from the Detailed County boundaries (24K) dataset. All these MOU boundaries were created for use by SJRWMD Regulatory staff.

Polygons encompassing recent northern Idaho Ground squirrel detections from Idaho Department of Fish & Game standardized surveys, presence surveys, exploratory surveys, and incidental observations. Polygon boundaries modified to encompass new detections in 2019 based on actual locations (adjusted for distance and side of survey line). Polygon boundaries typically not reduced in size until multiple years of no data.

Source datasets: MassDEP Hydrography 1:25K Ponds & Streams https://www.mass.gov/info-details/massgis-data-massdep-hydrography-125000 (last updated 2019); MassDEP Wetlands (2005) publ 2017: https://www.mass.gov/info-details/massgis-data-massdep-wetlands-2005 All geoprocessing work was performed in ArcPro by the Martha's Vineyard Commission. 300ft buffer applied to the compiled resource area (ponds & wetlands). The stream area within the resource area had already been buffered 1ft to convert the arc topology to a polygon (for inclusion in the polygon resource area dataset). Therefore, the stream resource area was buffered an additional 299ft. That 299ft stream buffer was merged into the larger 300ft resource area buffer.Edgartown Wetlands Protection Bylaw

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.

Reason for Selection Low-urban historic landscapes indicate significant cultural landscapes whose cultural context has been less impacted by urban development. Cultural landscapes are “properties [that] represent the combined works of nature and of man” (UNESCO 2012). Loss of natural habitat within these cultural landscapes reduces their overall historic and cultural value.Input Data Southeast Blueprint 2023 subregions: CaribbeanSoutheast Blueprint 2023 extent2020 LANDFIRE Existing Vegetation Type (EVT) (v2.2.0) for Puerto Rico and the U.S. Virgin Islands; access the data for U.S. Insular AreasThe following The National Register of Historic Places data for Puerto Rico provided by Eduardo Cancio, Information Systems Specialist with the Puerto Rico State Historic Preservation Office (SHPO) on 2-21-2023 (contact ecancio@prshpo.pr.gov for more information):NRHP_PR_individual_properties.shpNRHP_PR_lineal_districts.shpNRHP_PR_polygonal_districts.shp The National Register of Historic Places reflects what Americans value in their historic built environment. It is the collection of our human imprint on the landscape that records through time our changing relationship with the landscape, bridging between modern life and our history by providing, as closely as possible, experiences that evoke our empathy and understanding of previous eras. OpenStreetMap data “multipolygons” layer, accessed 3-14-2023 A polygon from this dataset is considered a historic site if the “historic” tag is not null. In OpenStreetMap, a historic feature refers to “features that still exist or of which traces are observable, and that are of historic interest, or where the feature class is generally of historical interest”. We only used historic polygons if the name tag is also not null. OpenStreetMap® is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more on the OSM copyright page.Select USVI historic districts: Polygon boundaries for the Christiansted National Historic District on St. Thomas and Charlotte Amalie Historic and Architectural Historic District on St. Croix, provided by Nikita Beck with the University of the Virgin Islands on 3-6-2023 (contact nikita.beck@uvi.edu for more information)Mapping Steps Identify urban areas using the following classes from 2020 LANDFIRE EVT: Developed-High Intensity, Developed-Low Intensity, Developed-Medium Intensity, Developed-Open Space, Developed-Roads. Classify all urban pixels as 1 and all other pixels as 0.Calculate the percent urban in a 270 m radius circle for each pixel using the Focal Statistics tool in ArcGIS. Since the LANDFIRE data resolution is 30 m, 270 m (9 pixels) approximates a 250 m radius. Retain all pixels that are <50% urban within a 270 m radius. Create a historic places layer by combining the following vector datasets as follows:Buffer National Register point data from the Puerto Rico SHPO by 100 m.Combine National Register polygons from the Puerto Rico SHPO, select USVI historic districts, and OpenStreetMap polygons. Only use OpenStreetMap polygons if both the historic and name columns are null. Buffer the polygons by 30 m.Buffer line data from the Puerto Rico SHPO by 30 m.Merge all buffered point, polygon, and line data into one layer and convert to a 30 m raster representing historic places.Use the historic places raster to remove areas that fall outside of the historic places.Reclassify the above raster into 3 classes, seen in the final indicator values below.Clip to the Caribbean Blueprint 2023 subregion.As a final step, clip to the spatial extent of Southeast Blueprint 2023. Note: For more details on the mapping steps, code used to create this layer is available in the Southeast Blueprint Data Download under > 6_Code.Final indicator valuesIndicator values are assigned as follows:2 = Historic place with nearby low-urban buffer1 = Historic place with nearby high-urban buffer0 = Not identified as a historic placeKnown IssuesThere are likely spatial mapping errors for some of the historic areas. Some historic areas with cultural importance are not captured in the National Register of Historic Places.The approach to measuring urban development doesn’t capture degradation to historic places that were historically in larger cities (e.g., courthouses and other downtown buildings). It also doesn’t distinguish between historic places that have always been urban and historic places that used to be low-urban.This layer likely underrepresents some historic areas in the U.S. Virgin Islands compared to Puerto Rico because we were unable to incorporate historic places data from the USVI SHPO during the timeline of this Blueprint update. As a result, some sites on the National Register of Historic Places are not depicted in this indicator.OpenStreetMap is a crowdsourced dataset. While members of the OpenStreetMap community often verify map features to check for accuracy and completeness, there is the potential for spatial errors (e.g., misrepresenting the boundary of a historic site) or incorrect tags (e.g., labelling an area as a historic site that does not have historic value). However, using a crowdsourced dataset gives on-the-ground experts, Blueprint users, and community members the power to fix errors and add new historic sites to improve the accuracy and coverage of this indicator in the future.Because open water is considered a non-urban landcover for the purposes of this analysis, this indicator is likely overprioritizing some urbanized historic areas that are close to water, such as marinas and bridges.Disclaimer: Comparing with Older Indicator VersionsThere are numerous problems with using Southeast Blueprint indicators for change analysis. Please consult Blueprint staff if you would like to do this (email hilary_morris@fws.gov).Literature CitedOpenStreetMap. Historic. Data extracted through Geofabrik downloads. Accessed March 14, 2023. [https://wiki.openstreetmap.org/wiki/Key:historic].LANDFIRE, Earth Resources Observation and Science Center (EROS), U.S. Geological Survey. Published August 1, 2022. LANDFIRE 2020 Existing Vegetation Type (EVT) Puerto Rico US Virgin Islands. LF 2020, raster digital data. Sioux Falls, SD. [https://www.landfire.gov].UNESCO (2012) Operational Guidelines for the Implementation of the World Heritage Convention [1]. UNESCO World Heritage Centre. Paris. Page 14. [https://whc.unesco.org/archive/opguide12-en.pdf].