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

(Link to Metadata) CadastralParcels_VTPARCELS includes standardized parcel data for Vermont municipalities. For information on the Statewide Property Parcel Mapping Program, go to http://vcgi.vermont.gov/parcels.

The State of Vermont has a long history of acquiring properties for conservation and recreation purposes. Since the first official state forest (L.R. Jones State Forest) was acquired in 1909, the State has acquired over 345,000 acres of land in more than 200 towns across the state. In addition, the Agency has recently acquired conservation easements on over 44,000 acres of privately-owned forest land. These diverse holdings are managed by the Agency of Natural Resources and include state parks, state forests, wildlife management areas, and fishing access areas, pond sites, streambanks, fish culture stations, dams, and other miscellaneous properties.

Feature layer of locations corresponding to surveys that are produced by Vermont licensed land surveyors and submitted—as .pdf copies—to the Vermont Land Survey Library.Locations are attributed with information such as name of surveyor, date of survey, survey type (e.g., subdivision), and municipality. When the feature layer is opened in ArcGIS Online, the .pdf copies (as feature attachments) can be viewed/downloaded.Effective January 1, 2020 and as stated in27 V.S.A. § 341, surveys are required for property line changes in Vermont. Licensed land surveyors who produce the surveys are to submit a digital copy of them to the library in.pdf format (see27 V.S.A. §1401 and 27 V.S.A. §1403).The copies of surveys are for public reference only, with the originals that most often reside with the Municipality remaining the official documents. The purpose of the land survey library is to improve knowledge of who owns what lands where throughout Vermont.For more information about land surveying in Vermont, see theVermont Society of Land Surveyors (VSLS) and the Vermont Survey Law Manual (PDF).

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state but may extend across county and county subdivision boundaries. An incorporated place is usually a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs are often defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2024, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2024 BAS as well.

(Link to Metadata) Large ownerships were identified and verified through a variety of sources.

Northeastern United States County Boundary data are intended for geographic display of state and county boundaries at statewide and regional levels. Use it to map and label counties on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

(Link to Metadata) These data identify shorelines of lakes and ponds ten (10) acres and larger. The shorelines are classified according to their development status. Development is defined as human structures, roads, or railroads within 250 feet of the shore.

This parcels dataset is a spatial representation of tax lots for Union County, New Jersey that have been extracted from the NJ statewide parcels composite by the NJ Office of Information Technology, Office of GIS (NJOGIS). Parcels at county boundaries have been modified to correspond with the NJ county boundaries and the parcels in adjacent counties.Each parcel contains a field named PAMS_PIN based on a concatenation of the county/municipality code, block number, lot number and qualification code. Using the PAMS_PIN, the dataset can be joined to the MOD-IV database table that contains supplementary attribute information regarding lot ownership and characteristics. Due to irregularities in the data development process, duplicate PAMS_PIN values exist in the parcel records. Users should avoid joining MOD-IV database table records to all parcel records with duplicate PAMS_PINs because of uncertainty regarding whether the MOD-IV records will join to the correct parcel records. There are also parcel records with unique PAMS_PIN values for which there are no corresponding records in the MOD-IV database tables. This is mostly due to the way data are organized in the MOD-IV database.The polygons delineated in the dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such.The MOD-IV system provides for uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of the Division of Taxation. MOD-IV maintains and updates all assessment records and produces all statutorily required tax lists for property tax bills. This list accounts for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel. Tax List records were received as raw data from the Taxation Team of NJOIT which collected source information from municipal tax assessors and created the statewide table. This table was subsequently processed for ease of use with NJ tax parcel spatial data and split into an individual table for each county.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

The 2023 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The cartographic boundary files include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The generalized boundaries of most incorporated places in this file are based on those as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs are based on those delineated or updated as part of the the 2023 BAS or the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The 2022 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The cartographic boundary files include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The generalized boundaries of most incorporated places in this file are based on those as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs are based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

(Link to Metadata) The EcologicOther_ELT (Ecological Land Type) data layer was developed by the Green Mountain National Forest in the early 1980's from aerial photography. Using stereo-pairs of 1:42000 aerial photographs units were mapped using techniques similar to those used by soil scientists to delineate soil-series. After the initial mapping, fieldwork was done to 1) verify and adjust unit designations and 2) develop unit descriptions. To do this, sample plots were established on photos in locations that appeared to be representative of particular ELT's, or in locations where there were questions about the accuracy of the designations. Adjustments to the ELT boundaries were made in the field when data on vegetation and edaphic and topographic features were collected at sample plots. On the north half of the Green Mountain National Forest, 60 different elts have been mapped, and 320 sample plots established to validate and describe the units. Polygons were drawn onto 1:24000 USFS Topographic Maps sheets (mylar). In 1993 these maps were given to the University of Vermont's Spatial Analysis Lab for digitizing. Automation was completed in the fall of 1993. Ecological land classification (ELC) is a cartographic approach to forest land delineation that defines units of land at different spatial scales that are hierarchical, nested, and homogeneous in their environmental and late-successional vegetational characteristics. The ecological land classification system in use on the Green Mountain National Forest (GMNF) in Vermont conforms to the guidelines defined by the National Hierarchical Framework of Ecological Units established by the USDA Forest Service. This classification system is meant to assist managers by allowing them to delineate ecosystems, assess resources, conduct environmental analyses, establish desired future conditions, and manage and monitor resources. Units at the ecological land type (ELT) scale have been mapped on the GMNF. These units are designed to assist managers in site specific, project-level planning. Average unit size for ELT's on the north half of the GMNF is 267 acres. The units are identified by a four-digit code that is based on landtype association, geomorphic process, soil depth, and moisture (refer to ELTCODE documentation).

Abstract: This file contains Hydrologic Unit (HU) polygon boundaries for the United States, Puerto Rico, and the U.S. Virgin Islands. The data is a seamless National representation of HU boundaries from 2 to 14 digits compiled from U.S. Geological Survey (USGS) National Hydrography Dataset (NHD) and U.S. Department of Agriculture (USDA) National Resources Conservation Service (NRCS) Watershed Boundary Dataset (WBD) sources. Purpose: This data is intended primarily for geographic display and analysis of regional and national data, and can also be used for illustration purposes at intermediate or small scales (1:250,000 to 1:2,000,000).

The Digital Surficial Geologic-GIS Map of Marsh-Billings-Rockefeller National Historical Park and the Town Boundary of Woodstock, Vermont is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (mabi_surficial_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (mabi_surficial_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (mabi_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (mabi_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (mabi_surficial_geology_metadata_faq.pdf). Please read the mabi_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Vermont Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (mabi_surficial_geology_metadata.txt or mabi_surficial_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

This community revitalization program helps maintain or evolve small to medium-sized historic centers with existing civic and commercial buildings. The designation supports the historic center and targets training and financial incentives to bring additional public and private investment to spark village revitalization. If available, the data is submitted by the Regional Planning Commissions as Shapefiles otherwise the approved map is scanned and digitized or parcel boundaries are used to build the boundary. Learn more about the Vermont Designation Programs.

Vermont GIS Parcel Data (dataset name = CadastralParcels_VTPARCELS) is published as of a set of three data layers. It includes standardized statewide parcel data--with joined Grand List data--for Vermont municipalities; an intermediary intersection table and data layer are used to facilitate the join. Data is compiled from multiple sources by Vermont Center for Geographic Information. [Information on Statewide Property Parcel Mapping Program] [Full metadata, including field descriptions]Published Layers:Statewide Standardized Parcel Data - parcel polygons:(feature class name = Cadastral_VTPARCELS_poly_standardized_parcels)Active parcels (including unlanded buildings)--with joined Grand List data, public right-of-ways, trail right-of-ways (for trails identified on the VTrans General Highway Maps, AKA Town Highway Maps), and surface water areas that serve as property boundaries.This layer is a product of joining Grand List data to active parcels. It is a value-added layer with a schema that is based on Vermont GIS Parcel Data Standard 2.3 and the Grand List schema.For scenarios where a one-to-many relationship exists between land and Grand List records--e.g., land with unlanded buildings, this layer includes an individual polygon for each related Grand List record; such scenarios create a stacked-polygon effect. For example, when an identify tool is applied to a location that has fifteen mobile homes on a land parcel, sixteen identical polygons can be returned--one for the land-surface Grand List record and fifteen for each of the mobile-home Grand List records.Statewide Standardized Parcel Data - inactive parcel polygons:(feature class name = Cadastral_VTPARCELS_poly_standardized_inactive)Inactive parcels and their related active parcels. Schema is based on Vermont GIS Parcel Data Standard 2.3.Statewide Standardized Parcel Data - Data Status polygons:(feature class name = Cadastral_VTPARCELS_poly_DataStatus)Status of parcel data by municipality.Intermediary Intersection Table and Data Layer:TABLE_VTPARCELS_intersection:An intersection table that relates records of the Grand List which have active SPAN numbers to records in the Cadastral_VTPARCELS_poly_standardized_parcels feature class which represent parcel features (PROPTYPE = ‘PARCEL’). Supports bi-directional matching/reconciliation between the Grand List and the parcels feature class.Schema is based on Vermont GIS Parcel Data Standard 2.3.Cadastral_VTPARCELS_poly_standardized_NONJOINED_parcels:Geometry and GIS-attribute base of Cadastral_VTPARCELS_poly_standardized_parcels, without Grand-List join. Schema is based on Vermont GIS Parcel Data Standard 2.3.Update Frequency and Time Period of Content:Vermont GIS Parcel Data is generally updated weekly. The time period of its content varies by municipality.

The table below showcases the 10th, 25th, 50th, 75th, and 90th percentiles of assessed property values for each zip code in Derby Line, Vermont. It's important to understand that assessed property values can vary greatly and can change yearly.

This TNC Lands spatial dataset represents the lands and waters in which The Nature Conservancy (TNC) currently has, or historically had, an interest, legal or otherwise in Vermont. The system of record for TNC Lands is the Legal Records Management (LRM) system, which is TNC’s database for all TNC land transactions.TNC properties should not be considered open to the public unless specifically designated as being so. TNC may change the access status at any time at its sole discretion. It's recommended to visit preserve-specific websites or contact the organization operating the preserve before any planned visit for the latest conditions, notices, and closures. TNC prohibits redistribution or display of the data in maps or online in any way that misleadingly implies such lands are universally open to the public.The types of current land interests represented in the TNC Lands data include: Fields and Attributes included in the public dataset:Field NameField DefinitionAttributesAttribute Definitions Public NameThe name of the tract that The Nature Conservancy (TNC) Business Unit (BU) uses for public audiences.Public name of tract if applicableN/A TNC Primary InterestThe primary interest held by The Nature Conservancy (TNC) on the tractFee OwnershipProperties where TNC currently holds fee-title or exclusive rights and control over real estate. Fee Ownership can include TNC Nature Preserves, managed areas, and properties that are held for future transfer. Conservation EasementProperties on which TNC holds a conservation easement, which is a legally binding agreement restricting the use of real property for conservation purposes (e.g., no development). The easement may additionally provide the holder (TNC) with affirmative rights, such as the rights to monitor species or to manage the land. It may run forever or for an expressed term of years. Deed RestrictionProperties where TNC holds a deed restriction, which is a provision placed in a deed restricting or limiting the use of the property in some manner (e.g., if a property goes up for sale, TNC gets the first option). TransferProperties where TNC historically had a legal interest (fee or easement), then subsequently transferred the interest to a conservation partner. AssistProperties where TNC assisted another agency/entity in protecting. Management Lease or AgreementAn agreement between two parties whereby one party allows the other to use their property for a certain period of time in exchange for a periodic fee. Grazing Lease or PermitA grazing lease or permit held by The Nature Conservancy Right of WayAn access easement or agreement held by The Nature Conservancy. OtherAnother real estate interest or legal agreement held by The Nature Conservancy Fee OwnerThe name of the organization serving as fee owner of the tract, or "Private Land Owner" if the owner is a private party. If The Nature Conservancy (TNC) primary interest is a "Transfer" or "Assist", then this is the fee owner at the time of the transaction.Fee Owner NameN/A Fee Org TypeThe type of organization(s) that hold(s) fee ownership. Chosen from a list of accepted values.Organization Types for Fee OwnershipFED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest HolderThe name of the organization(s) that hold(s) a different interest in the tract, besides fee ownership or TNC Primary Interest. This may include TNC if the Other Interest is held or co-held by TNC. Multiple interest holders should be separated by a semicolon (;).Other Interest Holder NameN/A Other Interest Org TypeThe type of organization(s) that hold(s) a different interest in the tract, besides fee ownership. This may include TNC if the Other Interest is held or co-held by TNC. Chosen from a list of accepted values.Organization Types for interest holders:FED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest TypeThe other interest type held on the tract. Chosen from a list of accepted values.​Access Right of Way; Conservation Easement; Co-held Conservation Easement; Deed Restriction; Co-held Deed Restriction; Fee Ownership; Co-held Fee Ownership; Grazing Lease or Permit; Life Estate; Management Lease or Agreement; Timber Lease or Agreement; OtherN/A Preserve NameThe name of The Nature Conservancy (TNC) preserve that the tract is a part of, this may be the same name as the as the "Public Name" for the tract.Preserve Name if applicableN/APublic AccessThe level of public access allowed on the tract.Open AccessAccess is encouraged on the tract, trails are maintained, signage is abundant, and parking is available. The tract may include regular hours of availability.Open with Limited AccessThere are no special requirements for public access to the tract, the tract may include regular hours of availability with limited amenities.Restricted AccessThe tract requires a special permit from the owner for access, a registration permit on public land, or has highly variable times or conditions to use.Closed AccessNo public access is allowed on the tract.UnknownAccess information for the tract is not currently available.Gap CategoryThe Gap Analysis Project (GAP) code for the tract. Gap Analysis is the science of determining how well we are protecting common plants and animals. Developing the data and tools to support that science is the mission of the Gap Analysis Project (GAP) at the US Geological Survey. See their website for more information, linked in the field name.1 - Permanent Protection for BiodiversityPermanent Protection for Biodiversity2 - Permanent Protection to Maintain a Primarily Natural StatePermanent Protection to Maintain a Primarily Natural State3 - Permanently Secured for Multiple Uses and in natural coverPermanently Secured for Multiple Uses and in natural cover39 - Permanently Secured and in agriculture or maintained grass coverPermanently Secured and in agriculture or maintained grass cover4 - UnsecuredUnsecured (temporary easements lands and/or municipal lands that are already developed (schools, golf course, soccer fields, ball fields)9 - UnknownUnknownProtected AcresThe planar area of the tract polygon in acres, calculated by the TNC Lands geographic information system (GIS).Total geodesic area of polygon in acresProjection: WGS 1984 Web Mercator Auxiliary SphereOriginal Protection DateThe original protection date for the tract, from the Land Resource Management (LRM) system record.Original protection dateN/AStateThe state within the United States of America or the Canadian province where the tract is located.Chosen from a list of state names.N/ACountryThe name of the country where the tract is located.Chosen from a list of countries.N/ADivisionThe name of the TNC North America Region Division where the tract is located. Chosen from a list of TNC North America DivisionsN/A

The landscape Change Program is an archive of paired historic and recent photos of Vermont landscapes. The program is funded by the National Science Foundation to digitally document how the Vermont landscape has changed over time.

The landscape of Vermont has changed considerably since it first emerged from the ocean during the collision of huge tectonic plates. For a time, geologically speaking, sediments that became Vermont had been in a warm tropical sea at the equator. Slowly they had moved north. Mountains were born and began to erode. Massive glaciers more than a kilometer thick blanketed Vermont. Soon after the glaciers left, Native Americans inhabited the area. Colonial settlers moved in, clearing the land and leaving just a quarter of the total area forested, making way for agriculture, then sheep, then dairy. Hundreds of hill farms sprang up and many were later abandoned as western soils called. Now the Vermont landscape is mostly forested and yet increasingly developed. The face of Vermont has changed dramatically over time. The shared appreciation and acknowledgement of this rich landscape history is the goal of this project.

[Summary provided by the University of Vermont.]

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.