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.

Firm age class limits.

These data are a polygon feature class that represents the administrative boundaries of the US Forest Service Research and Development Stations. These territories consist of a collection of states' geographic areas, within which all research and development facilities and lands are managed by a station headquarters.

The metropolitan planning organization (MPO) polygon feature class provides California MPO legislative boundaries, primarily for regional planning applications.Data downloaded in February 2023 from https://gisdata-caltrans.opendata.arcgis.com/datasets/b3e0ef95520843ba8c1d3b9c0fa9a607_0/explore?location=36.748926%2C-119.524779%2C7.00.

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.

A feature class describing the spatial location of the administrative boundary of the lands managed by the Forest Supervisor's office. 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 dataset is derived from the USFS Southwestern Region ALP (Automated Lands Program) data Project. This is one of six layers derived from ALP for the purpose of supplying data layers for recourse GIS analysis and data needs within the Forest Service. The six layers are Surface Ownership, Administrative Forest Boundary, District Boundary, Townships, Sections, and Wilderness. There were some gapes in the ALP data so a small portion of this dataset comes from CCF (Cartographic Feature Files) datasets and the USFS Southwestern Region Core Data Project. ALP data is developed from data sources of differing accuracy, scales, and reliability. Where available it is developed from GCDB (Geographic Coordinate Data Base) data. GCDB data is maintained by the Bureau of Land Management in their State Offices. GCDB data is mostly corner data. Not all corners and not all boundaries are available in GCDB so ALP also utilizes many other data sources like CFF data to derive its boundaries. GCDB data is in a constant state of change because land corners are always getting resurveyed. The GCDB data used in this dataset represents a snapshot in time at the time the GCDB dataset was published by the BLM and may not reflect the most current GCDB dataset available. The Forest Service makes no expressed or implied warranty with respect to the character, function, or capabilities of these data. These data are intended to be used for planning and analyses purposes only and are not legally binding with regards to title or location of National Forest System lands.

GDB Version: ArcGIS Pro 3.3Additional Resources:Shapefile DownloadShapefile Download (Clipped to VIMS shoreline)Administrative Boundary Data Standard REST Endpoint (Unclipped) - REST Endpoint (Clipped)The Administrative Boundary feature classes represent the best available boundary information in Virginia. VGIN initially sought to develop an improved city, county, and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from an extraction of features from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the appropriate feature classes where locality data were a superior representation of boundaries. Administrative Boundary geodatabase and shapefiles are unclipped to hydrography features by default. The clipped to hydro dataset is included as a separate shapefile download below.

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

In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) data set (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the Process Step section of the Feature Class metadata. A data set named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 data set was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the data set to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has been renamed cnty24k09_1. Detailed documentation of changes is included in the Process Step section of the Feature Class metadata. This Geo database contains 3 feature classes representing California county boundaries (arc, polygon, and multipart-polygon feature classes) and also contains a polygon feature class representing the state boundary: 1. Line - can be useful for cartographic purposes, especially when different line symbology is needed for different boundaries (e.g. Coastline, Mexico, Nevada, etc). 2. Multipart - features from a common county are combined into a single record (equivalent to a region feature class in a coverage). May be useful for selections and overlays when all parts of a county are needed. 3. Poly - all county features are represented as individual polygons. 4. State Poly - state boundary polygon to be used for cartography or overlay analysis that requires a state polygon.

The same 20 features were measured for the in-graphs (representing the cellular structure associated with each boundary) and for the out-graphs (representing the corresponding areas in the background), giving 40 metrics in total.

Off-road image semantic segmentation is challenging due to the presence of uneven terrains, unstructured class boundaries, irregular features and strong textures.

The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.

© Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project

This layer is a component of Feature classes representing locality (county, city, and town) boundaries in the Commonwealth of Virginia..

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.

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.

(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 is a dataset for the 10-Regional Parks System as defined by Implementing Agencies that own and operate the regional parks and trails for the 7-county Twin Cities metropolitan area. This dataset contains the Regional Administrative Boundary feature classes in association with the Operating Agencies annual submission. These data have been modified to reflect current knowledge and provide necessary attribution need for the Parks Policy Plan maps. This dataset only contains the latest years data.

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

ESRI polygon feature class representing the City of Somerville, Massachusetts city boundary.

The dataset is a feature class showing the boundaries of 515 groundwater basins and subbasins as defined by the California Department of Water Resources as last modified by the Basin Boundary Emergency Regulation adopted on October 21, 2015 and subsequent modifications requested through the Basin Boundary Modification Request Process. This data is current as of December 9, 2022. The file is in ESRI geodatabase format and is intended for use with compatible GIS software. Groundwater basins are represented as polygon features and designated on the basis of geological and hydrological conditions - usually the occurrence of alluvial or unconsolidated deposits. When practical, large basins are also subdivided by political boundaries, as in the Central Valley. Basins are named and numbered per the convention of the Department of Water Resources.