(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 2015 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 records in this file allow users to map the parts of Urban Areas that overlap a particular county. After each decennial census, the Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2010.

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

County Foresters provide forest management and forest stewardship information, technical assistance, and outreach to landowners in Vermont. County Forester offices are conveniently located around the state. This layer displays their coverage area and contact information. If a problem exists in the coverage map, please check first with the Private Land Forestry Program.

(Link to Metadata) DemoCensus_CNTY2000 includes Census 2000 County boundaries and SF1 attributes. The data was downloaded (URL defunct) by VCGI from ESRI's Data website. The downloaded shapefiles were combined into a single shapefile and reprojected to VCS NAD83. A set of Census 2000 SF1 (URL defunct) attributes were joined to the shapefile. For more information go to (URL defunct)

(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) DemoCensus_CNTY1990 is derived from BoundaryCounty_CNTY250. BoundaryCounty_CNTY250 was derived from BoundaryTown_TB250 (TB250 was archived 6/2003 and has been replaced by BNDHASH. However, CNTY1990 has not been regenerated). Associated table documentation maps.vcgi.vermont.gov/gisdata/metadata/census1990_suppdoc.txt

(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) This metadata applies to the following collection area(s): Chittenden County 2004 3.2m and related ASPECT datasets. This metadata complies with the VT Geodata Portal format and applies to thematic layers with the same resolution (RESCLASS), e.g., 0p7m, 1m etc., and may include multiple data "collection" efforts. For the original vendor metadata containing specific details on each collections "point cloud" such as flight dates, nominal pulse spacing and RMSEz etc., see the "All Available Lidar" Product page: (http://vcgi.vermont.gov/warehouse/products/ALL-LDR_MIX_LIDAR_STATE_ALL). For an overview of the "Vermont Lidar Initiative" please see "VCGI.VERMONT.GOV/LIDAR".

description: (Link to Metadata) This metadata record describes the acquisition and production of 15 centimeter ground sample distance (GSD) natural color and color infrared digital ground orthoimagery covering a portion of Vermont State. The digital orthophotography and color infrared digital orthos are composed of 24 bit natural color digital orthos with a 0.15 meter GSD. Geographic extent is limited to specific buy-up areas in central Vermont including portions of Addison and Chittenden counties, approximately 30 total square miles. Poor weather and ground conditions precluded capture of all areas originally planned. Product: 15-centimeter color orthoimagery tiles (uncompressed GeoTIFF and compressed JPEG2000). Geographic Extent: The 15 centimeter buy-up areas were limited to specific areas in central Vermont within portions of Addison and Chittenden counties, approximately 30 total square miles. Dataset Description: The Vermont 2017 Imagery project called for the planning, acquisition, processing and derivative products of imagery data to be collected at an ground sample distance of 15 centimeters.Project specifications are based on the ASPRS Positional Accuracy Standards for Digital Geospatial Data. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane Coordinate System Vermont, meters. Raw imagery data was produced in 16-bit 4-band (RGB-IR) uncompressed format, then processed to create 24-bit 4-band (RGB-IR) orthorectified tiles. Compressed orthoimagery was produced in JPEG2000 format. An additional set of uncompressed GeoTIFF and compressed JPEG 2000 data was produced in black and white. A total of 97 of the originally planned 712 tiles were produced with a tile size of 900 meters x 900 meters. Tile names use the following naming convention "VT_(TILENUM)_(YYYYMMDD).(FileExtension)", where TILENUM = the 8-digit value of the TILENUM attribute in the master index files YYYYMMDD = the flight acquisition date (or majority date) for that particular tile. Ground Conditions: Imagery was collected in spring of 2017 during minimal shadow conditions. In order to post process the imagery data to meet task order specifications, Quantum Spatial utilized 2 checkpoints provided by the Bryant Associates, Inc. These checkpoints were established throughout the project area and used to check the accuracy of the data.; abstract: (Link to Metadata) This metadata record describes the acquisition and production of 15 centimeter ground sample distance (GSD) natural color and color infrared digital ground orthoimagery covering a portion of Vermont State. The digital orthophotography and color infrared digital orthos are composed of 24 bit natural color digital orthos with a 0.15 meter GSD. Geographic extent is limited to specific buy-up areas in central Vermont including portions of Addison and Chittenden counties, approximately 30 total square miles. Poor weather and ground conditions precluded capture of all areas originally planned. Product: 15-centimeter color orthoimagery tiles (uncompressed GeoTIFF and compressed JPEG2000). Geographic Extent: The 15 centimeter buy-up areas were limited to specific areas in central Vermont within portions of Addison and Chittenden counties, approximately 30 total square miles. Dataset Description: The Vermont 2017 Imagery project called for the planning, acquisition, processing and derivative products of imagery data to be collected at an ground sample distance of 15 centimeters.Project specifications are based on the ASPRS Positional Accuracy Standards for Digital Geospatial Data. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane Coordinate System Vermont, meters. Raw imagery data was produced in 16-bit 4-band (RGB-IR) uncompressed format, then processed to create 24-bit 4-band (RGB-IR) orthorectified tiles. Compressed orthoimagery was produced in JPEG2000 format. An additional set of uncompressed GeoTIFF and compressed JPEG 2000 data was produced in black and white. A total of 97 of the originally planned 712 tiles were produced with a tile size of 900 meters x 900 meters. Tile names use the following naming convention "VT_(TILENUM)_(YYYYMMDD).(FileExtension)", where TILENUM = the 8-digit value of the TILENUM attribute in the master index files YYYYMMDD = the flight acquisition date (or majority date) for that particular tile. Ground Conditions: Imagery was collected in spring of 2017 during minimal shadow conditions. In order to post process the imagery data to meet task order specifications, Quantum Spatial utilized 2 checkpoints provided by the Bryant Associates, Inc. These checkpoints were established throughout the project area and used to check the accuracy of the data.

(Link to Metadata) CNTY2010 contains a subset of attributes from Summary File 1 of the 2010 Decennial Census. The TIGER/Line Files are shapefiles and related database files (.dbf) that 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) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. States and equivalent entities are the primary governmental divisions of the United States. In addition to the fifty States, the Census Bureau treats the District of Columbia, Puerto Rico, and each of the Island Areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the U.S. Virgin Islands) as the statistical equivalents of States for the purpose of data presentation.

Digital bedrock Geologic Map of The Mount Snow and Readsboro quadrangles, Bennington and Windham counties Vermont. Abstract was not provided, for more information on this resource and accessibility options please see the links provided.

Digital Data from VG98-123A Walsh, G. J., 1998,�Digital and preliminary bedrock geologic map of the Vermont part of the Hartland quadrangle, Windsor County, Vermont: USGS Open-File Report 98-123A, 1 color plate and�text,�scale 1:24000. The bedrock geologic map data at a scale of 1:24,000 depicts types of bedrock underlying unconsolidated materials in Vermont. Data is created by mapping on the ground using standard geologic pace and compass techniques and/or GPS on a USGS 1:24000 topographic base map. Data may be organized by town, quadrangle or watershed. Each data bundle may includes point, line and polygon data and some or all of the following: 1) contacts (lithogic contacts), 2) fault_brittle, 3) fault_ductile, 4) fault_thrust, 5) fault_bed_plane (bedding plane thrust), 6) bedding, 7) bedding_graded (graded bedding) 8) bedding_overturn (overturned bedding), 9) bedding_select (selected points for published map), 10) foliation_n1, n2, n3 etc (foliation data), 11) outcrop (exposed outcrops), 12) field_station (outcrop and data collection point), 13) fold_axis, 14) axial_plane, 15) lamprophyre, 16) water_well_log (water well driller information), 16) linear_int (intersection lineation), 17) linear_str (stretching lineation) 18) x_section_line (line of cross-section), and photolinear (lineaments identified from air photos). Other feature classes may be included with each data bundle. (https://dec.vermont.gov/geological-survey/publication-gis/ofr).

Estimate of Median Household Income for Caledonia County, VT was 64229.00000 $ in January of 2023, according to the United States Federal Reserve. Historically, Estimate of Median Household Income for Caledonia County, VT reached a record high of 64229.00000 in January of 2023 and a record low of 24354.00000 in January of 1989. Trading Economics provides the current actual value, an historical data chart and related indicators for Estimate of Median Household Income for Caledonia County, VT - last updated from the United States Federal Reserve on July of 2025.

description: (Link to Metadata) This datalayer contains Vermont Population and Health data describing public health (1986-2000), by county, extracted from various sources, such as; the Vermont Department of Health, the Vermont Center for Justice Research, the National Institute on Alcohol Abuse & Alcoholism, et al. Development of this database is a continual effort. Periodically, more data will be added. Additional Public Health data can be found in the HealthStats_CTYHEAL1 database. Funding for much of this data was provided by the UVM - Center for Rural Studies. One may download Excel spreadsheets or comma-delimited ASCII textfiles of this data from the VGIS indicators webpage - http://vcgi.vermont.gov/indicators/; abstract: (Link to Metadata) This datalayer contains Vermont Population and Health data describing public health (1986-2000), by county, extracted from various sources, such as; the Vermont Department of Health, the Vermont Center for Justice Research, the National Institute on Alcohol Abuse & Alcoholism, et al. Development of this database is a continual effort. Periodically, more data will be added. Additional Public Health data can be found in the HealthStats_CTYHEAL1 database. Funding for much of this data was provided by the UVM - Center for Rural Studies. One may download Excel spreadsheets or comma-delimited ASCII textfiles of this data from the VGIS indicators webpage - http://vcgi.vermont.gov/indicators/

description: (Link to Metadata) This metadata applies to the following collection area(s): Windham County 2015 0.7m and related SLOPE datasets. Created using ArcGIS "SLOPE" command to produce change in elevation over the distance between the cell and its eight neighbors expressed in percent slope or percent grade, i.e., rise/run * 100. This metadata complies with the VT Geodata Portal format and applies to thematic layers with the same resolution (RESCLASS), e.g., 0p7m, 1m etc., and may include multiple data "collection" efforts. For the original vendor metadata containing specific details on each collections "point cloud" such as flight dates, nominal pulse spacing and RMSEz etc., see the "All Available Lidar" Product page: (http://vcgi.vermont.gov/data/products/ALL-LDR_MIX_LIDAR_STATE_ALL). For an overview of the "Vermont Lidar Initiative" please see "http://vcgi.vermont.gov/lidar".; abstract: (Link to Metadata) This metadata applies to the following collection area(s): Windham County 2015 0.7m and related SLOPE datasets. Created using ArcGIS "SLOPE" command to produce change in elevation over the distance between the cell and its eight neighbors expressed in percent slope or percent grade, i.e., rise/run * 100. This metadata complies with the VT Geodata Portal format and applies to thematic layers with the same resolution (RESCLASS), e.g., 0p7m, 1m etc., and may include multiple data "collection" efforts. For the original vendor metadata containing specific details on each collections "point cloud" such as flight dates, nominal pulse spacing and RMSEz etc., see the "All Available Lidar" Product page: (http://vcgi.vermont.gov/data/products/ALL-LDR_MIX_LIDAR_STATE_ALL). For an overview of the "Vermont Lidar Initiative" please see "http://vcgi.vermont.gov/lidar".

description: (Link to Metadata) This metadata applies to the following collection area(s): Windham County 2015 0.7m; Eastern VT 2014 0.7m; Rutland/GI Counties 2013 0.7m; and related Digital Surface Model (DSM) data. This metadata complies with the VT Geodata Portal format and applies to thematic layers with the same resolution (RESCLASS), e.g., 0p7m, 1m etc., and may include multiple data 'collection' efforts. For the original vendor metadata containing specific details on each collections 'point cloud' such as flight dates, nominal pulse spacing and RMSEz etc., see the 'All Available Lidar' Product page: (http://vcgi.vermont.gov/warehouse/products/ALL-LDR_MIX_LIDAR_STATE_ALL). For an overview of the 'VCGI Lidar Program' please see 'http://vcgi.vermont.gov/lidar'.; abstract: (Link to Metadata) This metadata applies to the following collection area(s): Windham County 2015 0.7m; Eastern VT 2014 0.7m; Rutland/GI Counties 2013 0.7m; and related Digital Surface Model (DSM) data. This metadata complies with the VT Geodata Portal format and applies to thematic layers with the same resolution (RESCLASS), e.g., 0p7m, 1m etc., and may include multiple data 'collection' efforts. For the original vendor metadata containing specific details on each collections 'point cloud' such as flight dates, nominal pulse spacing and RMSEz etc., see the 'All Available Lidar' Product page: (http://vcgi.vermont.gov/warehouse/products/ALL-LDR_MIX_LIDAR_STATE_ALL). For an overview of the 'VCGI Lidar Program' please see 'http://vcgi.vermont.gov/lidar'.

(Link to Metadata) COUSUB2010 contains a subset of attributes from Summary File 1 of the 2010 Decennial Census.The TIGER/Line Files are shapefiles and related database files (.dbf) that 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) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data, and they include legally minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the legal MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas is covered by county subdivisions. The boundaries of all 2010 Census legal MCDs are as of January 1, 2010 as reported through the Census Bureau's Boundary and Annexation Survey (BAS). For the 2010 Census, CCDs or their equivalents are delineated in 21 States. The boundaries of all 2010 Census statistical CCDs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP).