Class I and II surface water classification. The Clean Water Act requires that the surface waters of each state be classified according to designated uses. Florida has six classes with associated designated uses, which are arranged in order of degree of protection required: Class I - Potable Water Supplies Fourteen general areas throughout the state including: impoundments and associated tributaries, certain lakes, rivers, or portions of rivers, used as a drinking water supply. Class II - Shellfish Propagation or Harvesting Generally coastal waters where shellfish harvesting occurs. For a more detailed description of classes and specific waterbody designations, see 62-302.400.

Class I and II surface water classification boundaries. The Clean Water Act requires that the surface waters of each state be classified according to designated uses. Florida has six classes with associated designated uses, which are arranged in order of degree of protection required: Class I - Potable Water Supplies Fourteen general areas throughout the state including: impoundments and associated tributaries, certain lakes, rivers, or portions of rivers, used as a drinking water supply. Class II - Shellfish Propagation or Harvesting Generally coastal waters where shellfish harvesting occurs. For a more detailed description of classes and specific waterbody designations, see 62-302.400.

An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area. This data is intended for read-only use. These data were prepared to describe Forest Service administrative area boundaries. The purpose of the data is to provide display, identification, and analysis tools for determining current boundary information for Forest Service managers, GIS Specialists, and others. The Forest Service has multiple types of boundaries represented by different feature classes (layers): Administrative, Ownership and Proclaimed. 1) ADMINISTRATIVE boundaries (e.g. AdministrativeForest and RangerDistrict feature classes) encompass National Forest System lands managed by an administrative unit. These are dynamic layers that should not be considered "legal" boundaries as they are simply intended to identify the specific organizational units that administer areas. As lands are acquired and disposed, the administrative boundaries are adjusted to expand or shrink accordingly. Please note that ranger districts are sub units of National Forests. An administrative forest boundary can contain one or more Proclaimed National Forests, National Grasslands, Purchase Units, Research and Experimental Areas, Land Utilization Projects and various "Other" Areas. If needed, OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) should be reviewed along with these datasets to determine parcels that are federally managed within the administrative boundaries. 2) OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) represent parcels that are tied to legal transactions of ownership. These are parcels of Federal land managed by the USDA Forest Service. Please note that the BasicOwnership layer is simply a dissolved version of the SurfaceOwnership layer. 3) PROCLAIMED boundaries (e.g. ProclaimedForest and ProclaimedForest_Grassland) encompass areas of National Forest System land that is set aside and reserved from public domain by executive order or proclamation. Please note that the ProclaimedForest layer contains only proclaimed forests while ProclaimedForest_Grassland layer contains both proclaimed forests and proclaimed grasslands. For boundaries that reflect current National Forest System lands managed by an administrative unit, see the ADMINISTRATIVE boundaries (AdministrativeForest and RangerDistrict feature classes). For a visual comparison of the different kinds of USFS boundary datasets maintained by the USFS, see the Forest Service Boundary Comparison map at https://usfs.maps.arcgis.com/apps/CompareAnalysis/index.html?appid=fe7b9f56217949a291356f08cfccb119. USFS boundaries are often referenced in national datasets maintained by other federal agencies. Please note that variations may be found between USFS data and other boundary datasets due to differing update frequencies. PAD-US (Protected Areas Database of the United States), maintained by the U.S. Geological Survey, is a "best available" inventory of protected areas including data provided by managing agencies and organizations including the Forest Service. For more information see https://gapanalysis.usgs.gov/padus/data/metadata/. SMA (Surface Management Agency), maintained by the Bureau of Land Management, depicts Federal land for the United States and classifies this land by its active Federal surface managing agency. It uses data provided by the Forest Service and other agencies, combined with National Regional Offices collection efforts. For more information see https://landscape.blm.gov/geoportal/catalog/search/resource/details.page?uuid=%7B2A8B8906-7711-4AF7-9510-C6C7FD991177%7D.

An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area.

This data is intended for read-only use. These data were prepared to describe Forest Service administrative area boundaries. The purpose of the data is to provide display, identification, and analysis tools for determining current boundary information for Forest Service managers, GIS Specialists, and others.

The Forest Service has multiple types of boundaries represented by different feature classes (layers): Administrative, Ownership and Proclaimed. 1) ADMINISTRATIVE boundaries (e.g. AdministrativeForest and RangerDistrict feature classes) encompass National Forest System lands managed by an administrative unit. These are dynamic layers that should not be considered "legal" boundaries as they are simply intended to identify the specific organizational units that administer areas. As lands are acquired and disposed, the administrative boundaries are adjusted to expand or shrink accordingly. Please note that ranger districts are sub units of National Forests. An administrative forest boundary can contain one or more Proclaimed National Forests, National Grasslands, Purchase Units, Research and Experimental Areas, Land Utilization Projects and various "Other" Areas. If needed, OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) should be reviewed along with these datasets to determine parcels that are federally managed within the administrative boundaries. 2) OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) represent parcels that are tied to legal transactions of ownership. These are parcels of Federal land managed by the USDA Forest Service. Please note that the BasicOwnership layer is simply a dissolved version of the SurfaceOwnership layer. 3) PROCLAIMED boundaries (e.g. ProclaimedForest and ProclaimedForest_Grassland) encompass areas of National Forest System land that is set aside and reserved from public domain by executive order or proclamation. Please note that the ProclaimedForest layer contains only proclaimed forests while ProclaimedForest_Grassland layer contains both proclaimed forests and proclaimed grasslands. For boundaries that reflect current National Forest System lands managed by an administrative unit, see the ADMINISTRATIVE boundaries (AdministrativeForest and RangerDistrict feature classes). For a visual comparison of the different kinds of USFS boundary datasets maintained by the USFS, see the Forest Service Boundary Comparison map at https://usfs.maps.arcgis.com/apps/CompareAnalysis/index.html?appid=fe7b9f56217949a291356f08cfccb119. USFS boundaries are often referenced in national datasets maintained by other federal agencies. Please note that variations may be found between USFS data and other boundary datasets due to differing update frequencies. PAD-US (Protected Areas Database of the United States), maintained by the U.S. Geological Survey, is a "best available" inventory of protected areas including data provided by managing agencies and organizations including the Forest Service. For more information see https://gapanalysis.usgs.gov/padus/data/metadata/. SMA (Surface Management Agency), maintained by the Bureau of Land Management, depicts Federal land for the United States and classifies this land by its active Federal surface managing agency. It uses data provided by the Forest Service and other agencies, combined with National Regional Offices collection efforts. For more information see https://landscape.blm.gov/geoportal/catalog/search/resource/details.page?uuid=%7B2A8B8906-7711-4AF7-9510-C6C7FD991177%7D.

The BNDHASH dataset depicts Vermont villages, towns, counties, Regional Planning Commissions (RPC), and LEPC (Local Emergency Planning Committee) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) VILLAGES = Vermont villages 2) TOWNS = Vermont towns 3) COUNTIES = Vermont counties 4) RPCS = Vermont's Regional Planning Commissions 5) LEPC = Local Emergency Planning Committee boundaries 6) VTBND = Vermont's state boundary The master BNDHASH layer is managed as ESRI geodatabase feature dataset by VCGI. The dataset stores villages, towns, counties, and RPC boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/rpc boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the location of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line featue with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

WBDHU6: This geospatial dataset represents the 3rd level (6-digit) hydrologic unit boundaries of the Watershed Boundary Dataset (WBD) layer for Washington. It was created by dissolving boundaries from the finer resolution hydrologic units to create these broader boundaries. See metadata for the wbd_wa_poly feature class for a more complete description of the WBD. USGS Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD) located here: http://pubs.usgs.gov/tm/11/a3/pdf/tm11-a3.pdf

The Semantic Boundaries Dataset (SBD) is a dataset for predicting pixels on the boundary of the object (as opposed to the inside of the object with semantic segmentation). The dataset consists of 11318 images from the trainval set of the PASCAL VOC2011 challenge, divided into 8498 training and 2820 test images. This dataset has object instance boundaries with accurate figure/ground masks that are also labeled with one of 20 Pascal VOC classes.

WBDHU8: This geospatial dataset represents the 4th level (8-digit) hydrologic unit boundaries of the Watershed Boundary Dataset (WBD) layer for Oregon. It was created by dissolving boundaries from the finer resolution hydrologic units to create these broader boundaries. See metadata for the wbdhu12 feature class for a more complete description of the WBD. USGS Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD) located here: http://pubs.usgs.gov/tm/11/a3/pdf/tm11-a3.pdf

(Link to Metadata) The BNDHASH dataset depicts Vermont village, town, county, and Regional Planning Commission (RPC) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) BNDHASH_POLY_VILLAGES = Vermont villages 2) BNDHASH_POLY_TOWNS = Vermont towns 3) BNDHASH_POLY_COUNTIES = Vermont counties 4) BNDHASH_POLY_RPCS = Vermont's Regional Planning Commissions 5) BNDHASH_POLY_VTBND = Vermont's state boundary 6) BNDHASH_LINE = Lines on which all POLY feature classes are built The master BNDHASH data is managed as an ESRI geodatabase feature dataset by VCGI. The dataset stores village, town, county, RPC, and state boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/RPC/state boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the locations of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line feature with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

This polygon feature class represents the spatial extent of historical BLM Administrative Unit Boundaries (at the State, District, and Field Office levels).This state dataset may have published a dataset that is more current than the National dataset; there may be geometry variations between the state and national dataset which may have different results. The national dataset is updated following the data standard schedule

Accuracy assessment is one of the most important components of both applied and research-oriented remote sensing projects. For mapped classes that have sharp and easily identified boundaries, a broad array of accuracy assessment methods has been developed. However, accuracy assessment is in many cases complicated by classes that have fuzzy, indeterminate, or gradational boundaries, a condition which is common in real landscapes; for example, the boundaries of wetlands, many soil map units, and tree crowns. In such circumstances, the conventional approach of treating all reference pixels as equally important, whether located on the map close to the boundary of a class, or in the class center, can lead to misleading results. We therefore propose an accuracy assessment approach that relies on center-weighting map segment area to calculate a variety of common classification metrics including overall accuracy, class user’s and producer’s accuracy, precision, recall, specificity, and the F1 score. This method offers an augmentation of traditional assessment methods, can be used for both binary and multiclass assessment, allows for the calculation of count- and area-based measures, and permits the user to define the impact of distance from map segment edges based on a distance weighting exponent and a saturation threshold distance, after which the weighting ceases to grow. The method is demonstrated using synthetic and real examples, highlighting its use when the accuracy of maps with inherently uncertain class boundaries is evaluated.

This feature class represents the product of merge and dissolve operations in ArcGIS with the inputs being the individually submitted EIS boundary datasets. EIS boundaries were developed by each individual EIS in coordination with the Division of Decision Support, Planning and NEPA (WO 210). EIS boundary submissions occurred between Sept. 25th and Sept. 30th, 2013. No modifications to the source data have been made other than to add and calculate the "EIS Name" field. The following EIS boundaries are included in the dataset: 9-Plan, Bighorn Basin, Billings/Pompey's Pillar NM, Buffalo, HiLine, Idaho and SW Montana, Lander, Lewistown, Miles City, NW Colorado, Nevada and NE California, North Dakota, Oregon, South Dakota, Upper Missouri River Breaks NM, and Utah.

This digital, geographically referenced data set was developed to identify the county boundaries of the Des Moines 9 County Regional GIS community.This feature class is one many feature classes developed for and maintained by the Des Moines Area Regional GIS for the purpose of performing internal and external functions of the local government it covers.

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. Spatial data from field observation points and quantitative plots were used to edit the formation-level maps of Petersburg National Battlefield to better reflect vegetation classes. Using ArcView 3.3, polygon boundaries were revised onscreen over leaf-off photography. Units used to label polygons on the map (i.e. map classes) are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson (Anderson et al. 1976) Level II classification system. Each polygon on the Petersburg National Battlefield map was assigned to one of twenty map classes based on plot data, field observations, aerial photography signatures, and topographic maps. The mapping boundary was based on park boundary data obtained from Petersburg National Battlefield in May 2006. Spatial data depicting the locations of earthworks was obtained from the park and used to identify polygons of the cultural map classes Open Earthworks and Forested Earthworks. One map class used to attribute polygons combines two similar associations that, in some circumstances, are difficult to distinguish in the field. The vegetation map was clipped at the park boundary because areas outside the park were not surveyed or included in the accuracy assessment. Twenty map classes were used in the vegetation map for Petersburg National Battlefield. Map classes are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson (Anderson et al. 1976) Level II classification system.

One of the largest hydraulic mines (1.6 km2) is located in California’s Sierra Nevada within the Humbug Creek watershed and Malakoff Diggins State Historic Park (MDSHP). MDSHP’s denuded and dissected landscape is composed of weathered Eocene auriferous sediments susceptible to chronic rill and gully erosion whereas block failures and debris flows occur in more cohesive terrain. This data release includes a 2014 digital elevation model (DEM), a study area boundary, and a geomorphic map. The 2014 DEM was derived from an available aerial LiDAR dataset collected in 2014 by the California Department of Conservation. The geomorphic map was derived for the study area from using a multi-scale spatial analysis. A topographic position index (TPI) was created using focal statistics to compare the elevations across the study area. We calculated a fine-scale TPI using a circular neighborhood with a radius of 25-meters and large-scale TPI using a circular neighborhood with a radius of 100-meters. In the resulting raster positive TPI values are assigned to cells with elevations higher than the surrounding area and negative TPI values are assigned to cells with elevations lower than the surrounding area. The geomorphic map was then created using a nested conditional statement to apply classification thresholds on the basis the fine and large-scale TPI rasters and a slope raster. Ten geomorphic feature classes were defined and the map can be symbolized by feature class. The geomorphic map includes both channel and hillslope features and can be used to assess erosional and depositional processes at the landscape scale.

(Link to Metadata) The BNDHASH dataset depicts Vermont village, town, county, and Regional Planning Commission (RPC) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) BNDHASH_POLY_VILLAGES = Vermont villages 2) BNDHASH_POLY_TOWNS = Vermont towns 3) BNDHASH_POLY_COUNTIES = Vermont counties 4) BNDHASH_POLY_RPCS = Vermont's Regional Planning Commissions 5) BNDHASH_POLY_VTBND = Vermont's state boundary 6) BNDHASH_LINE = Lines on which all POLY feature classes are built The master BNDHASH data is managed as an ESRI geodatabase feature dataset by VCGI. The dataset stores village, town, county, RPC, and state boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/RPC/state boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the locations of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line feature with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

Spatial analysis and statistical summaries of the Protected Areas Database of the United States (PAD-US) provide land managers and decision makers with a general assessment of management intent for biodiversity protection, natural resource management, and recreation access across the nation. The PAD-US 4.0 Combined Fee, Designation, Easement feature class in the full geodatabase inventory (with Military Lands and Tribal Areas from the Proclamation and Other Planning Boundaries feature class) was modified to prioritize overlapping designations, avoiding massive overestimation in protected area statistics, and simplified by the following PAD-US attributes to support user needs for raster analysis data: Manager Type, Manager Name, Designation Type, GAP Status Code, Public Access, and State Name. The rasterization process prioritized overlapping designations previously identified (GAP_Prity field) in the Vector Analysis file (e.g. Wilderness within a National Forest) based upon their relative biodiversity conservation (e.g. GAP Status Code 1 over 2).The 30-meter Image (IMG) grid Raster Analysis Files area extents were defined by the Census state boundary file used to clip the Vector Analysis File, the data source for rasterization ("PADUS4_0VectorAnalysis_State_Clip_CENSUS2022") feature class from ("PADUS4_0VectorAnalysisFile_OtherExtents_ClipCENSUS2022.gdb"). Alaska (AK) and Hawaii (HI) raster data are separated from the contiguous U.S. (CONUS) to facilitate analyses at manageable scales. Note, the PAD-US inventory is now considered functionally complete with the vast majority of land protection types (with a legal protection mechanism) represented in some manner, while work continues to maintain updates, improve data quality, and integrate new data as it becomes available (see inventory completeness estimates at: http://www.protectedlands.net/data-stewards/ ). In addition, protection status represents a point-in-time and changes in status between versions of PAD-US may be attributed to improving the completeness and accuracy of the spatial data more than actual management actions or new acquisitions. USGS provides no legal warranty for the use of this data. While PAD-US is the official aggregation of protected areas ( https://ngda-portfolio-community-geoplatform.hub.arcgis.com/pages/portfolio ), agencies are the best source of their lands data.

This geospatial dataset represents the 2nd level (4-digit) hydrologic unit boundaries of the Watershed Boundary Dataset (WBD) layer for Washington. It was created by dissolving boundaries from the finer resolution hydrologic units to create these broader boundaries. See metadata for the wbd_wa_poly feature class for a more complete description of the WBD.