For a detailed description of the zoning districts referenced in this data, please refer to the City of Burlington, Vermont's webpage. Please be sure to review all recently adopted amendments. The city provided this information: The Burlington Comprehensive Development Ordinance is amended pretty frequently and on no particular schedule. All of the adopted amendments are posted online following each published version of the CDO. In other words, since the latest CDO publication April 25, 2018, all adopted amendments are shown on this webpage.The City of Burlington also has overlay districts which can be downloaded separately.

Digital data from VG09-1 Wright, S., S. Fuller, S. Jones, A. McKinney, S. Rupard, and S.D. Shaw, 2009,�Surficial geologic map of the Burlington, Vermont 7.5 minute quadrangle: Vermont Geological Survey Open-File Report VG09-1, 1 color plate plus text, scale 1:24000. Data may include surficial geologic contacts, isopach contours lines, bedrock outcrop polygons, bedrock geologic contacts, hydrogeologic units and more. The surficial geologic materials data at a scale of 1:24,000 depict types of unconsolidated surficial and glacial materials overlying bedrock 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. The materials data is selected from the Vermont Geological Survey Open File Report (OFR) publication (https://dec.vermont.gov/geological-survey/publication-gis/ofr). The OFR contains more complete descriptions of map units, cross-sections, isopach maps and other information that may not be included in this digital data set.

Links to NWS GIS data resources / GIS Viewer web application and BTV (Burlington, VT forecast office) 24-Hour Daily Climate Maps.

Zoning District Data for the City of South Burlington. Data corresponds to Land Development Regulations.Overlay districts can be found under South Burlington Overlay data.

These data provide an accurate high-resolution shoreline compiled from imagery of Lake Champlain, Burlington to Cumberland Head, VT-NY . This vector shoreline data is based on an office interpretation of imagery that may be suitable as a geographic information system (GIS) data layer. This metadata describes information for both the line and point shapefiles. The NGS attribution scheme 'Coast...

Models a municipality’s overlay district and related information.

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.

Data originally comes from an AGOL layer named Bike_Infrastructure_2019, updated by Nicole Losch July 2021.

Attributes: FHFEATURE - Values: Not Applicable, Zone A Floodplain, Zone AE Floodplain, Zone AE Floodway FHSUBDISTRICT - Values: Not Applicable, Special Flood Hazard Area FHNAME - Values: Lake Champlain, Not Applicable, Pine Street Barge Canal, Potash Brook, Winooski River

This layer contains a Vermont-only subset of block group level 2020 Decennial Census redistricting data as reported by the U.S. Census Bureau for all states plus DC and Puerto Rico. The attributes come from the 2020 Public Law 94-171 (P.L. 94-171) tables.Data download date: August 12, 2021Census tables: P1, P2, P3, P4, H1, P5, HeaderDownloaded from: Census FTP siteProcessing Notes:Data was downloaded from the U.S. Census Bureau FTP site, imported into SAS format and joined to the 2020 TIGER boundaries. Boundaries are sourced from the 2020 TIGER/Line Geodatabases. Boundaries have been projected into Web Mercator and each attribute has been given a clear descriptive alias name. No alterations have been made to the vertices of the data.Each attribute maintains it's specified name from Census, but also has a descriptive alias name and long description derived from the technical documentation provided by the Census. For a detailed list of the attributes contained in this layer, view the Data tab and select "Fields". The following alterations have been made to the tabular data:Joined all tables to create one wide attribute table:P1 - RaceP2 - Hispanic or Latino, and not Hispanic or Latino by RaceP3 - Race for the Population 18 Years and OverP4 - Hispanic or Latino, and not Hispanic or Latino by Race for the Population 18 Years and OverH1 - Occupancy Status (Housing)P5 - Group Quarters Population by Group Quarters Type (correctional institutions, juvenile facilities, nursing facilities/skilled nursing, college/university student housing, military quarters, etc.)HeaderAfter joining, dropped fields: FILEID, STUSAB, CHARITER, CIFSN, LOGRECNO, GEOVAR, GEOCOMP, LSADC, and BLOCK.GEOCOMP was renamed to GEOID and moved be the first column in the table, the original GEOID was dropped.Placeholder fields for future legislative districts have been dropped: CD118, CD119, CD120, CD121, SLDU22, SLDU24, SLDU26, SLDU28, SLDL22, SLDL24 SLDL26, SLDL28.P0020001 was dropped, as it is duplicative of P0010001. Similarly, P0040001 was dropped, as it is duplicative of P0030001.In addition to calculated fields, County_Name and State_Name were added.The following calculated fields have been added (see long field descriptions in the Data tab for formulas used): PCT_P0030001: Percent of Population 18 Years and OverPCT_P0020002: Percent Hispanic or LatinoPCT_P0020005: Percent White alone, not Hispanic or LatinoPCT_P0020006: Percent Black or African American alone, not Hispanic or LatinoPCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or LatinoPCT_P0020008: Percent Asian alone, Not Hispanic or LatinoPCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or LatinoPCT_P0020010: Percent Some Other Race alone, not Hispanic or LatinoPCT_P0020011: Percent Population of Two or More Races, not Hispanic or LatinoPCT_H0010002: Percent of Housing Units that are OccupiedPCT_H0010003: Percent of Housing Units that are VacantPlease note these percentages might look strange at the individual block group level, since this data has been protected using differential privacy.*VCGI exported a Vermont-only subset of the nation-wide layer to produce this layer--with fields limited to this popular subset: OBJECTID: OBJECTID GEOID: Geographic Record Identifier NAME: Area Name-Legal/Statistical Area Description (LSAD) Term-Part Indicator County_Name: County Name State_Name: State Name P0010001: Total Population P0010003: Population of one race: White alone P0010004: Population of one race: Black or African American alone P0010005: Population of one race: American Indian and Alaska Native alone P0010006: Population of one race: Asian alone P0010007: Population of one race: Native Hawaiian and Other Pacific Islander alone P0010008: Population of one race: Some Other Race alone P0020002: Hispanic or Latino Population P0020003: Non-Hispanic or Latino Population P0030001: Total population 18 years and over H0010001: Total housing units H0010002: Total occupied housing units H0010003: Total vacant housing units P0050001: Total group quarters population PCT_P0030001: Percent of Population 18 Years and Over PCT_P0020002: Percent Hispanic or Latino PCT_P0020005: Percent White alone, not Hispanic or Latino PCT_P0020006: Percent Black or African American alone, not Hispanic or Latino PCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or Latino PCT_P0020008: Percent Asian alone, not Hispanic or Latino PCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or Latino PCT_P0020010: Percent Some Other Race alone, not Hispanic or Latino PCT_P0020011: Percent Population of two or more races, not Hispanic or Latino PCT_H0010002: Percent of Housing Units that are Occupied PCT_H0010003: Percent of Housing Units that are Vacant SUMLEV: Summary Level REGION: Region DIVISION: Division COUNTY: County (FIPS) COUNTYNS: County (NS) TRACT: Census Tract BLKGRP: Block Group AREALAND: Area (Land) AREAWATR: Area (Water) INTPTLAT: Internal Point (Latitude) INTPTLON: Internal Point (Longitude) BASENAME: Area Base Name POP100: Total Population Count HU100: Total Housing Count *To protect the privacy and confidentiality of respondents, data has been protected using differential privacy techniques by the U.S. Census Bureau. This means that some individual block groups will have values that are inconsistent or improbable. However, when aggregated up, these issues become minimized.Download Census redistricting data in this layer as a file geodatabase.Additional links:U.S. Census BureauU.S. Census Bureau Decennial CensusAbout the 2020 Census2020 Census2020 Census data qualityDecennial Census P.L. 94-171 Redistricting Data Program

Polygon Attributes: REFERENCE: A, B, C, D, E, F, G, na = Polygon not part of Height overlayDefined as setbacks from City street right-of-way edge (see attribute Depth), or as a polygon. Reference is a map reference letter in code text.

Arcs coincident with street right-of-ways indicate where Shopfront facade Types are required. Arcs from parcel data street right-of-way arcs.

(Link to Metadata) Point data for emergency water supplies

Poly Attribute: ABBREV - District name abbreviationPoly Attribute: DISTRICT - District full name

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

(Link to Metadata) This metadata applies to the following collection area(s): Eastern VT 2014 0.7m 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/data/products/ALL-LDR_MIX_LIDAR_STATE_ALL). For an overview of the "Vermont Lidar Initiative" please see "VCGI.VERMONT.GOV/LIDAR".

Urban heat islands are small areas where temperatures are unnaturally high - usually due to dense buildings, expansive hard surfaces, or a lack of tree cover or greenspace. People living in these communities are exposed to more dangerous conditions, especially as daytime high and nighttime low temperatures increase over time. NOAA Climate Program Office and CAPA Strategies have partnered with cities around the United States to map urban heat islands. Using Sentinel-2 satellite thermal data along with on-the-ground sensors, air temperature and heat indexes are calculated for morning, afternoon, and evening time periods. The NOAA Visualization Lab, part of the NOAA Satellite and Information Service, has made the original heat mapping data available as dynamic image services.Dataset SummaryPhenomenon Mapped: heat indexUnits: degrees Fahrenheit Cell Size: 30 metersPixel Type: 32 bit floating pointData Coordinate Systems: WGS84 Mosaic Projection: WGS84 Extent: cities within the United StatesSource: NOAA and CAPA StrategiesPublication Date: September 20, 2021What can you do with this layer?This imagery layer supports communities' UHI spatial analysis and mapping capabilities. The symbology can be manually changed, or a processing template applied to the layer will provide a custom rendering. Each city can be queried.Related layers include Morning Heat Index and Evening Heat Index. Cities IncludedBoulder, CO Brooklyn, NY Greenwich Village, NY Columbia, SC Columbia, MO Columbus, OH Knoxville, TN Jacksonville, FL Las Vegas, NV Milwaukee, WI Nashville, TN Omaha, NE Philadelphia, PA Rockville, MD Gaithersburg, MD Takoma Park, MD San Francisco, CA Spokane, WA Abingdon, VA Albuquerque, NM Arlington, MA Woburn, MA Arlington, VA Atlanta, GA Charleston, SC Charlottesville, VA Clarksville, IN Farmville, VA Gresham, OR Harrisonburg, VA Kansas City, MO Lynchburg, VA Manhattan, NY Bronx, NY Newark, NJ Jersey City, NJ Elizabeth, NJ Petersburg, VA Raleigh, NC Durham, NC Richmond, VA Richmond, IN Salem, VA San Diego, CA Virginia Beach, VA Winchester, VA Austin, TX Burlington, VT Cincinnati, OH Detroit, MI El Paso, TX Houston, TX Jackson, MS Las Cruces, NM Miami, FL New Orleans, LA Providence, RI Roanoke, VA San Jose, CA Seattle, WA Vancouver, BC Canada Boston, MA Fort Lauderdale, FL Honolulu, HI Boise, ID Nampa, ID Los Angeles, CA Yonkers, NY Oakland, CA Berkeley, CA San Juan, PR Sacramento, CA San Bernardino, CA Victorville, CA West Palm Beach, FL Worcester, MA Washington, D.C. Baltimore, MD Portland, ORCities may apply to be a part of the Heat Watch program through the CAPA Strategies website. Attribute Table Informationcity_name: Afternoon Heat Index Observations in Floating-Point (°F)

The following Overlay District Data is included:Design Review OverlayInstitutional Core Campus OverlayRH Density Bonus OverlayNatural Resource Protection OverlayLarge Lot OverlayMouth of the River OverlayCentennial Woods OverlayParking Districts OverlayForm Based Code Height OverlaySouth End Innovation District OverlaySteep Slopes Overlay

For a detailed description of the overlay districts referenced in this data, please refer to the City of Burlington, Vermont's Zoning webpage. Please be sure to review all recently adopted amendments. The city provided this information: The Burlington Comprehensive Development Ordinance is amended pretty frequently and on no particular schedule. All of the adopted amendments are posted online following each published version of the CDO.

Overlay District data for the City of Burlington, Vermont. Data corresponds to the City of Burlington's Zoning Ordinance amended as of 10/23/23.

This data set defines both current and historic landfills/waste disposal storage sites for the State of Vermont. Historic landfills were identified with the publication of the Vermont Ground Water Pollution Source Inventory by the Agency of Environmental Conservation, Department of Water Resources and Environmental Engineering Water Quality Division, December 1980. Current landfill locations supplied by the Solid Waste Division of the Vermont Agency of Natural Resources, Department of Environmental Conservation.This dataset includes: active landfills - currently accepting waste, geo-located; closed landfills- ceased accepting waste and completed closure under solid waste regulations (post-1988), geo-located; historic landfills - ceased accepting waste prior to solid waste regulation implementation (pre-1988), locations obtained from a 1990 Vermont Groundwater Pollution Source Inventory completed by the Department of Waster Resources and Environmental Engineering Groundwater Management Section. The listing of historic landfills is likely incomplete.

Poly Attribute: DISTRICT - Downtown, Shared Use, Neighborhood Parking District polygons are combinations of Zoning Districts, with one exception in the Old North End (see metadata for zoning_overlay_parking_arc). Mapping of Zoning District Abbreviations to Parking Districts: Zoning District Abbreviation -> Parking District FD6 -> DOWNTOWN FD5 -> DOWNTOWN DW-PT -> DOWNTOWN ELM -> SHARED USE I -> SHARED USE NAC -> SHARED USE NAC-CR -> SHARED USE NAC-R -> SHARED USE NMU -> SHARED USE CIVIC -> NEIGHBORHOOD EAE -> NEIGHBORHOOD RCO-A -> NEIGHBORHOOD RCO-C -> NEIGHBORHOOD RCO-RG -> NEIGHBORHOOD RH -> NEIGHBORHOOD RL -> NEIGHBORHOOD RL-W -> NEIGHBORHOOD RM -> NEIGHBORHOOD RM-W -> NEIGHBORHOOD UR -> NEIGHBORHOOD