This layer shows workers by employer type (private sector, government, etc.) in Austin, Texas. This is shown by censustract and place boundaries. Tract data contains the most currently released American Community Survey (ACS) 5-year data for all tracts within Bastrop, Caldwell, Hays, Travis, and Williamson Counties in Texas. Place data contains the most recent ACS 1-year estimate for the City of Austin, Texas. Data contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis.To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023 (Tract), 2023 (Place)ACS Table(s): C24060 Data downloaded from: Census Bureau's API for American Community Survey Date of API call: February 12, 2025National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

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.

This feature class depicts the boundaries of Operable Unit 1 (OU1) within the Carson River Mercury Site (CRMS), including the four Area of Investigation boundaries. NDEP lead an initiative to refine the boundaries shown on maps identifying the Carson River Mercury Superfund Site (CRMS) from the initial site identification and description as the Carson River hydrographic basin beginning in Carson City, NV to its terminal points in Churchill County, NV. This description of the CRMS was used in many of the early site investigation studies and reports and continued to be used in all public education and long-term site management controls until approximately 2012. Using site contaminant fate and transport determinations from the CRMS OU1 Remedial Investigation (RI) and Conceptual Site Model (CSM), it seemed inappropriate to include the much larger area of the hydrographic basin as being potentially impacted by site contaminants of concern (CoC). NDEP created protocols to estimate areas that are likely to have been impacted by CoCs and created maps using these protocols to redraw the CRMS boundary limits. In the development of these protocols, NDEP used: Historic records and documentation of probable source areas; The 2012 archaeological mill site research and field study conducted by Broadbent and Associates to locate the historic source areas; Soil and sediment transport mechanisms identified in the CSM and general soil transport and sedimentology principals to predict areas where CoCs have likely been located at and downstream of the historic sources. The overall area of transport was estimated to be reasonably large to include possible anthropogenic activity as well as historic and future natural events such as flooding and channel migration. Additionally, NDEP added a "buffer” to extend the potential areas beyond the conservatively defined primary areas of potential contamination to further address unknown and future effects. These buffers have been identified separately from the primary areas of concern and labeled as such on maps using these protocols. These revisions were formalized in the 2013 Explanation of Significant Differences to the OU-1 Record of Decision (RoD) to adopt the new site definition and boundaries identified by NDEP as new estimates of the CRMS extents. NDEP identified four geographic areas of prime importance to the CRMS. Originally labeled by NDEP as "Risk Areas”, the intent of this terminology was to indicate these were the areas understood to have the most likely "risk” of contamination. Under consultation with EPA R9 risk assessment staff, the term has been changed to "Area of Investigation” to avoid confusion that any actual quantitative level of human or ecological risk has been determined for these areas. They are only estimates of potential contamination and new or additional information that contradicts these boundaries as being insufficient will be used to adopt new boundaries as appropriate. The four Areas of Investigation have become the foundation for the residential soil sampling program mandated by the OU-1 RoD. Summarized briefly; Investigation Area 1 (IA 1)- This includes all areas in the Carson River drainage basin from about the area of the historic settlement of Empire in Carson City, NV downstream to the existing or historic terminal points of the river at Carson Lake, Carson Sink, Indian Lakes and the Stillwater National Wildlife Refuge that lie outside the buffer zones of the other three Investigation Areas. It is least probable that CRMS CoCs will be located in these areas. It is unlikely that any sampling will be requested on areas developed within IA 1, but it might be requested in special circumstances, especially near and around the source areas of the contamination where historic activities could potentially have caused contamination beyond the typical boundaries as identified by the CSM. Investigation Area 2 (IA 2)- This area is defined as a buffer that lies 100 feet along a normal horizontal to the Investigation Area 3 boundary. For Comstock-era mill sites and isolated tailings piles, this translates to the area between 350 feet and 450 feet from the center point of the historic feature. For the 100-year FEMA floodplain and areas of irrigation, this is the area beginning at the limit of the flood plain boundary or irrigated land along a normal to 100 feet. Investigation Area 3 (IA 3)- This area is defined as a buffer that lies 100 feet along a normal horizontal to the Investigation Area 4 boundary for Comstock-era mills or isolated tailings piles. For Comstock-era mill sites and isolated tailings piles, this translates to the area between 250 feet and 350 feet from the center point of the historic feature. It is also defined as the limits of the FEMA 100-year floodplain or past or current flood irrigation practices. A tributary of the Carson River must have a Comstock-era mill site or tailings pile located along it to be mapped in IA3 and only the portion of the tributary downstream of the historic feature is included, not including the IA3 area and buffer drawn around the historic feature itself. If a tributary does not have FEMA 100-year flood plain defined, then IA3 has been defined as the area 100 feet along a normal to Investigation Area 4 boundary of that tributary. Investigation Area 4 (IA 4)- This area represents the highest likelihood of mercury contamination. Multiple steps were used to define the extent of this area, described below: The area within a 250 feet radius from the center point of a Comstock-era mill Comstock-era tailings pile polygon with a 250 ft buffer The centerline of the current channel of the Carson River enclosed in a polygon 100-feet wide (50 feet either side). Tributaries to the Carson River, where Comstock-era mills and tailings piles were located are enclosed in a polygon 50-feet wide (25 feet either side) from the approximate center of the tributary channel. Irrigation canals are enclosed in a polygon 20 feet wide (10 feet either side) from the approximate center of the ditch.

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

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

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

Aggregate statistics for registered storefronts in Designated Class One properties by identified geographic boundaries (Citywide, Borough, Council District).

(Link to Metadata) 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.

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 polygon feature class of the Urban Center boundaries within Miami-Dade County. To identify the boundary of urban centers within Miami-Dade County for mapping, application and analysis purposes.Updated: Annually The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

(Link to Metadata) 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.

This dataset is a representation of the boundaries of the original claims (or water-righted places of use) sourced from Pine Creek and tributaries, as identified by the Sixth Judicial District Court in the Barlett Decree of 1931, as well as Duckwater and Currant Creek and tributaries, as identified by the Fifth Judicial District Court in the Duckwater Decree of 1909 and 1910 and the Currant Creek Decree of 1921. These data are intended to assist in identifying the general locations of water-righted areas and their associated claim numbers. This mapping project was initiated in 2024 to assist in determining historical pumpage estimates for the demonstration basins, Pine Valley (053) and Railroad Valley (173B), where groundwater rights may be supplemental to surface water for the Nevada Water Initiative, with the final result being a feature class identifying the locations of each claim for the Pine, Duckwater and Currant Creek Decrees. This feature class is available on the Nevada Division of Water Resources (NDWR) Open Data site: https://data-ndwr.hub.arcgis.com/datasets/NDWR::nevada-water-initiative-decree-boundaries/about. This GIS layer exists only as a guide and starting point to identify the approximate locations of the water-righted areas in comparison to modern place of use boundaries. Further research is required to determine if a particular place of use originally had decreed water rights and whether it has retained those rights. Please contact the Division of Water Resources for more information.In order to produce a GIS depiction of the claims, the decree maps when available were georeferenced to the most up-to-date version of the Public Land Survey System (PLSS) dataset. If decree maps were not available, places of use were mapped based on subdivision descriptions found within the decrees. Each claim was then digitized from the boundaries shown on the georeferenced map and attributed with the assigned claim number and linked with associated information for each claim as described in the decree.This layer is strictly a visual representation, and it is important to note that acreages listed in this dataset may not match the decree for each claim. Assumptions were made regarding claims in the Barlett Decree where acreages overlapped within a subdivision resulting in combined acreage amounts across multiple years of priority or land classifications. In some cases, claims were not mapped because boundaries were not shown for a given subdivision on the georeferenced map. Changes in the PLSS for Railroad Valley (173B) were incorporated when mapping the subdivisions for the Duckwater Decree, as the modern boundaries varied from the decreed descriptions.Authors: McCartin, C.R., and Vergin, T.N.Initial Release: May 22, 2024

This layer was developed by the Natural Resources Department of the Atlanta Regional Commission. The dataset contains polygonal hydrographic features including lakes, ponds, reservoirs, swamps, and marshes in the Metropolitan North Georgia Water Planning District.Original data were captured from the NHDWaterbody geospatial data layer included in the High Resolution National Hydrography Dataset Plus (NHDPlus HR). Features in the NHDWaterbody geospatial layer that intersected the Georgia State boundary were selected and spatially joined to Georgia county boundaries and the WBDHU8 geospatial data layer found in the U.S. Geological Survey's Watershed Boundary Dataset. Layers were spatially joined using the Largest Overlap matching method. The spatial join was removed upon calculating values for the COUNTY_FIPS, COUNTY_NAME, HUC8_ID, and HUC8_SUBBASIN attributes. The CLASS attribute was created to identify Lakes equal to or larger than 10 acres as Major and less than 0.5 acres as Minor. Data in the HYDRO_CAT and RESERVOIR_TYPE attributes were sourced from values encoded in the Feature Code (FCode) field of the NHDWaterbody geospatial data layer.Attributes:FEATURE = Type of hydrologic featureCLASS = Class used to identify major and minor waterbodiesGNIS_ID = A permanent, unique number assigned by the Geographic Names Information System (GNIS) to a geographic feature name for the sole purpose of uniquely identifying that name application as a record in any information system database, dataset, file, or documentGNIS_NAME = The Geographic Names Information System (GNIS) assigned proper name, specific term, or expression by which a particular geographic entity is known.HUC8_ID = 8-digit hydrologic unit code used to identify subbasins in the hydrologic unit systemHUC8_SUBBASIN = Subbasin name of the 8-digit hydrologic unit code in the hydrologic unit systemCOUNTY_FIPS = County Federal Information Processing System (FIPS) codeCOUNTY_NAME = County nameHYDRO_CAT = Hydrographic feature categoryRESERVOIR_TYPE = Type of reservoirACRES = Area of the feature in acresELEVATION = The vertical distance from a given datumGlobalID = A type of UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is createdlast_edited_user = User to last edit featurelast_edited_date = Date feature was last editedShape = Feature geometryShape_Length = Length of the feature, which may differ from the field measured length due to differences in calculation. Units are map units.Shape_Area = Area of feature in map units squaredSource: U.S. Geological Survey, National Geospatial ProgramDate: 2023

This layer was developed by the Natural Resources Department of the Atlanta Regional Commission. The dataset contains polygonal hydrographic features including lakes, ponds, reservoirs, swamps, and marshes. Original data were captured from the NHDWaterbody geospatial data layer included in the High Resolution National Hydrography Dataset Plus (NHDPlus HR). Features in the NHDWaterbody geospatial layer that intersected the Georgia State boundary were selected and spatially joined to Georgia county boundaries and the WBDHU8 geospatial data layer found in the U.S. Geological Survey's Watershed Boundary Dataset. Layers were spatially joined using the Largest Overlap matching method. The spatial join was removed upon calculating values for the COUNTY_FIPS, COUNTY_NAME, HUC8_ID, and HUC8_SUBBASIN attributes. The CLASS attribute was created to identify Lakes equal to or larger than 10 acres as Major and less than 0.5 acres as Minor. Data in the HYDRO_CAT and RESERVOIR_TYPE attributes were sourced from values encoded in the Feature Code (FCode) field of the NHDWaterbody geospatial data layer.Attributes:FEATURE = Type of hydrologic featureCLASS = Class used to identify major and minor waterbodiesGNIS_ID = A permanent, unique number assigned by the Geographic Names Information System (GNIS) to a geographic feature name for the sole purpose of uniquely identifying that name application as a record in any information system database, dataset, file, or documentGNIS_NAME = The Geographic Names Information System (GNIS) assigned proper name, specific term, or expression by which a particular geographic entity is known.HUC8_ID = 8-digit hydrologic unit code used to identify subbasins in the hydrologic unit systemHUC8_SUBBASIN = Subbasin name of the 8-digit hydrologic unit code in the hydrologic unit systemCOUNTY_FIPS = County Federal Information Processing System (FIPS) codeCOUNTY_NAME = County nameHYDRO_CAT = Hydrographic feature categoryRESERVOIR_TYPE = Type of reservoirACRES = Area of the feature in acresELEVATION = The vertical distance from a given datumGlobalID = A type of UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is createdlast_edited_user = User to last edit featurelast_edited_date = Date feature was last editedShape = Feature geometryShape_Length = Length of the feature, which may differ from the field measured length due to differences in calculation. Units are map units.Shape_Area = Area of feature in map units squaredSource: U.S. Geological Survey, National Geospatial ProgramDate: 2023

NOTE: A more current version of the Protected Areas Database of the United States (PAD-US) is available: PAD-US 2.1 https://doi.org/10.5066/P92QM3NT. The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public land and voluntarily provided private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastre Theme (https://communities.geoplatform.gov/ngda-cadastre/). The PAD-US is an ongoing project with several published versions of a spatial database including areas dedicated to the preservation of biological diversity, and other natural (including extraction), recreational, or cultural uses, managed for these purposes through legal or other effective means. The database was originally designed to support biodiversity assessments; however, its scope expanded in recent years to include all public and nonprofit lands and waters. Most are public lands owned in fee; however, long-term easements, leases, agreements, Congressional (e.g. 'Wilderness Area'), Executive (e.g. 'National Monument'), and administrative designations (e.g. 'Area of Critical Environmental Concern') documented in agency management plans are also included. The PAD-US strives to be a complete inventory of public land and other protected areas, compiling “best available” data provided by managing agencies and organizations. The PAD-US geodatabase maps and describes areas with over twenty-five attributes in nine feature classes to support data management, queries, web mapping services, and analyses. NOTE: A more current version of the Protected Areas Database of the United States (PAD-US) is available: PAD-US 2.1 https://doi.org/10.5066/P92QM3NT This PAD-US Version 2.0 dataset includes a variety of updates and changes from the previous Version 1.4 dataset. The following list summarizes major updates and changes: 1) Expanded database structure with new layers: the geodatabase feature class structure now includes nine feature classes separating fee owned lands, conservation (and other) easements, management designations overlapping fee lands, marine areas, proclamation boundaries and various 'Combined' feature classes (e.g. 'Fee' + 'Easement' + 'Designation' feature classes); 2) Major update of the Federal estate including data from 8 agencies, developed in collaboration with the Federal Geographic Data Committee (FGDC) Federal Lands Working Group (FLWG, https://communities.geoplatform.gov/ngda-govunits/federal-lands-workgroup/); 3) Major updates to 30 States and limited additions to 16 other States; 4) Integration of The Nature Conservancy's (TNC) Secured Lands geodatabase; 5) Integration of Ducks Unlimited's (DU) Conservation and Recreation Lands (CARL) database; 6) Integration of The Trust for Public Land's (TPL) Conservation Almanac database; 7) The Nature Conservancy (TNC) Lands database update: the national source of lands owned in fee or managed by TNC; 8) National Conservation Easement Database (NCED) update: complete update of non-sensitive (suitable for publication in the public domain) easements; 9) Complete National Marine Protected Areas (MPA) update: from the NOAA MPA Inventory, including conservation measure ('GAP Status Code', 'IUCN Category') review by NOAA; 10) First integration of Bureau of Energy Ocean Management (BOEM) managed marine lands: BOEM submitted Outer Continental Shelf Area lands managed for natural resources (minerals, oil and gas), a significant and new addition to PAD-US; 11) Fee boundary overlap assessment: topology overlaps in the PAD-US 2.0 'Fee' feature class have been identified and are available for user and data-steward reference (See Logical_Consistency_Report Section). For more information regarding the PAD-US dataset please visit, https://usgs.gov/gapanalysis/PAD-US/. For more information about data aggregation please review the “Data Manual for PAD-US” available at https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-manual .

The Minnesota Department of Transportation (MnDOT) divides the state into eight administrative zonal areas referred to as construction districts. The boundaries of these districts are used to determine which district is responsible for construction activities on trunk highways, and for reporting purposes.
Construction Districts is a polygon feature class that represents an area that defines the portions of trunk highways and their junctions served by each of the eight districts.

The Minnesota Department of Transportation (MnDOT) divides the state into eight administrative zonal areas called Construction Districts. Some of these Construction Districts have been further sub-divided into Maintenance SubDistricts, which may identify a region for operational or administrative purposes. Maintenance SubDistricts is a polygon feature class that represents this area, and defines the portions of trunk highways and their junctions served by each SubDistrict. They are derived from the SubDistrict attribute field from the Maintenance Subareas feature class.

The Minnesota Department of Transportation (MnDOT) divides the state into eight administrative zonal areas call construction districts. Within each construction district, there are a varying number of maintenance subareas. These subareas represent which facility is responsible for maintenance activities on trunk highways, specifically winter maintenance. Note that summer maintenance activates may deviate substantially from these boundaries. Maintenance Subareas is a polygon feature class that represents the area, and defines the portions of trunk highways and their junctions served by each districts subarea.


Check other metadata records in this package for more information on MnDOT Boundaries

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

The CT Municipalities layer consists of individual polygons representing each of the 169 municipalities that make up the state of Connecticut. This feature class is based on the Towns layer originally created by CTDEEP from USGS maps. The towns from the CTDEEP data were dissolved to create 169 records (one for each town). Fields were added and deleted to create a generic schema.The CT Municipalities feature class was created in (municipality) alphabetical order. Fields were added to identify the municipality number and the CTDOT Municipality number, which differ from each other in some cases. In 1947 the town of Saybrook officially changed its name to Deep River. Other State agencies and municipalities changed their numbering systems to reflect this name change, however, most of what is now CTDOT kept their existing numbering system. This is why the CTDOT town number for Deep River is 122, the number formerly assigned to Saybrook.The square miles associated with each town are for their interior land mass area. Coastal communities have boundaries that extend into Long Island Sound. These town boundary extensions into Long Island Sound are not included in the square miles field.CTDOT has created and will maintain a cartographic rendering of the geometric shape of Municipal boundaries. Official Town and City designations as incorporated areas consisting of an authorized governing body are managed by CT's Office of Policy and Management (OPM).CTDOT has undertaken a good faith effort to represent the boundaries cartographically in a fair and equitable fashion, from the best available data compiled from existing state, regional, and local resources including - existing historical cartographic renderings of the boundary locations, supplemental survey information, and map submissions. Corrections can be submitted to the CTDOT for incorporation and correction where applicable.Attribution was assigned to designations managed by a variety of entities that strictly follow Municipal boundaries and additional designations will be added as requested by State, regional, and local partners.