(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 LAYER IS CURRENTLY BETA.This dataset provides approximate point locations and associated public information collected by the Department of Taxes under 32 V.S.A. § 9606 for all property transferred by deed in Vermont beginning in January 2019 through present. The layer is updated weekly. In addition to the data fields provided by the Department of Taxes, VCGI has added the latitude, longitude, standardized town name (based on the townCode), town GEOID, and Match Method (see below). Questions about property transfer data can be directed to the Department of Taxes at tax.rett@vermont.gov.Multiple methods are used to geocode property locations, indicated in the 'MatchMethod' field and prioritized in the following order:Geocoded using the VCGI ESITE Geocoder with the property street and city. MatchMethod = Property Address (ESITE). If unmatched:Match on SPAN in the E911 Site Locations layer; geocode using the location of the ESITE. MatchMethod = SPAN (ESITE). If unmatched:Geocode using the VCGI Composite Geocoder with the property street and city. MatchMethod = Property Address (Composite). If unmatched:Match on the SPAN in the Standardized Parcel Data layer; geocode based on a point located within the parcel polygon. While the point will fall within the correct parcel it may still be distant from the actual property, particularly in large parcels, and is less precise than the methods above. MatchMethod = SPAN (Parcel centroid).Locations are approximate, and those geocoded using the Property Address (Composite) and SPAN (Parcel centroid) methods in particular are less precise. Records that could not be geocoded using the above methods, often because of an incomplete, missing, or otherwise invalid SPAN and/or property address, are retained in the table but do not include geometry or coordinates. For these records, MatchMethod = Unmatched.Data download limitationVCGI recommends the use of feature services and geodatabase downloads when possible. Please note that if downloading the data as a shapefile the entries in the following fields may be truncated due to character limits:prTxExDesc (property tax exemption as described under32 V.S.A. § 9603)LGTExDesc (land gain exemption description)addSellNam (additional seller names from PTT175)addSellLoc (additional seller locations from PTT175)addBuyrNam (additional buyer names from PTT175)addBuyrLoc (additional buyer locations from PTT175)

description: (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.; abstract: (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.

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.

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

(Link to Metadata) CadastralParcels_VTPARCELS includes standardized parcel data--with joined Grand List data--for Vermont municipalities. For information on the Statewide Property Parcel Mapping Program, go to https://vcgi.vermont.gov/data-and-programs/parcel-program.

The Digital Bedrock 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_bedrock_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_bedrock_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_bedrock_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_bedrock_geology_metadata.txt or mabi_bedrock_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).

(Link to Metadata) High resolution land cover dataset for Vermont. Eight land cover classes were mapped: (1) tree canopy, (2) grass/shrub, (3) bare earth, (4) water, (5) buildings, (6) roads, (7) other paved surfaces,and (8) railroads. The primary sources used to derive this land cover layer were 2013-2017 LiDAR data and 2016 NAIP imagery. Ancillary data sources included GIS data provided by the State of Vermont or created by the UVM Spatial Analysis Laboratory. Object-based image analysis techniques (OBIA) were employed to extract land cover information using the best available remotely sensed and vector GIS datasets. OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to insure that the end product is both accurate and cartographically pleasing. Following the automated OBIA mapping a detailed manual review of the dataset was carried out at a scale of 1:3000 and all observable errors were corrected.

(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) Large ownerships were identified and verified through a variety of sources.

The 2022 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. Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. The generalized BG boundaries in this release are based on those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

Northeastern United States Town Boundary data are intended for geographic display of state, county and town (municipal) boundaries at statewide and regional levels. Use it to map and label towns 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) The WaterHydro_DLGSW layer represents surface waters (hydrography) at a scale of RF 100000. WaterHydro_DLGSW was derived from RF100000 USGS Digital Line Graph (DLG). DLG's of map features are converted to digital form from maps and related sources. Refer to the USGS web site from more information on DLGs (http://www.usgs.gov)

description: (Link to Metadata) This coverage represents the results of an analysis of landscape diversity in Vermont. Polygons in the dataset represent as much as possible (in a limited area) of the physical diversity in each of the state's 8 biophysical regions (BPRs)-- hence the name "representative landscapes" (RLs). Units of physical diversity were based on elevation, bedrock type, surficial deposits, and landform. Numbers of unique landscape diversity unit labels occurring in the 8 BPRs ranged from 586 to 956. Percent of diversity units represented in the RL polygons in this dataset ranged from a low of 74% (in 25% of the Champlain Valley BPR) to 87% (in 23% of the Northern Piedmont BPR). The most efficient repesentations were in the Northeastern Highlands and the Champlain Valley, where 83% and 81% (respectively) of the landscape diversity units occurring in the BPRs were represented in 17% of the BPR area.; abstract: (Link to Metadata) This coverage represents the results of an analysis of landscape diversity in Vermont. Polygons in the dataset represent as much as possible (in a limited area) of the physical diversity in each of the state's 8 biophysical regions (BPRs)-- hence the name "representative landscapes" (RLs). Units of physical diversity were based on elevation, bedrock type, surficial deposits, and landform. Numbers of unique landscape diversity unit labels occurring in the 8 BPRs ranged from 586 to 956. Percent of diversity units represented in the RL polygons in this dataset ranged from a low of 74% (in 25% of the Champlain Valley BPR) to 87% (in 23% of the Northern Piedmont BPR). The most efficient repesentations were in the Northeastern Highlands and the Champlain Valley, where 83% and 81% (respectively) of the landscape diversity units occurring in the BPRs were represented in 17% of the BPR area.

THIS LAYER IS CURRENTLY BETA.This dataset provides approximate point locations and associated public information collected by the Department of Taxes under 32 V.S.A. § 9606 for all property transferred by deed in Vermont beginning in January 2019 through present. The layer is updated weekly. In addition to the data fields provided by the Department of Taxes, VCGI has added the latitude, longitude, standardized town name (based on the townCode), town GEOID, and Match Method (see below). Questions about property transfer data can be directed to the Department of Taxes at tax.rett@vermont.gov.Multiple methods are used to geocode property locations, indicated in the 'MatchMethod' field and prioritized in the following order:Geocoded using the VCGI ESITE Geocoder with the property street and city. MatchMethod = Property Address (ESITE). If unmatched:Match on SPAN in the E911 Site Locations layer; geocode using the location of the ESITE. MatchMethod = SPAN (ESITE). If unmatched:Geocode using the VCGI Composite Geocoder with the property street and city. MatchMethod = Property Address (Composite). If unmatched:Match on the SPAN in the Standardized Parcel Data layer; geocode based on a point located within the parcel polygon. While the point will fall within the correct parcel it may still be distant from the actual property, particularly in large parcels, and is less precise than the methods above. MatchMethod = SPAN (Parcel centroid).Locations are approximate, and those geocoded using the Property Address (Composite) and SPAN (Parcel centroid) methods in particular are less precise. Records that could not be geocoded using the above methods, often because of an incomplete, missing, or otherwise invalid SPAN and/or property address, are retained in the table but do not include geometry or coordinates. For these records, MatchMethod = Unmatched.Data download limitationVCGI recommends the use of feature services and geodatabase downloads when possible. Please note that if downloading the data as a shapefile the entries in the following fields may be truncated due to character limits:prTxExDesc (property tax exemption as described under32 V.S.A. § 9603)LGTExDesc (land gain exemption description)addSellNam (additional seller names from PTT175)addSellLoc (additional seller locations from PTT175)addBuyrNam (additional buyer names from PTT175)addBuyrLoc (additional buyer locations from PTT175)

(Link to Metadata) The EnvironMangareas_MAREA2000 data layers includes management area boundaries administered by the Green Mountain National Forest and partner organizations. EnvironMangareas_MAREA2000 is an updated version of EnvironMangareas_MAREA1999 including all lands acquired in 2000. All purchases (9 tracts) occurred on the Manchester District.

(Link to Metadata) The EnvironMangareas_MAREA2004 data layer includes management area boundaries administered by the Green Mountain National Forest and partner organizations. EnvironMangareas_MAREA2004 is an updated version of EnvironMangareas_MAREA2001 including all lands acquired as of 9/01/2004. Refer to ACQ_DATE field.

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