(Link to Metadata) Intersection points of the VAST trail network with intersection identifiers.

Vermont E911 Site locations (ESITEs) including buildings, facilities, and development sites; locations are represented by points. Points are attributed with addresses--composing an address points layer. Dataset is updated weekly.Field Descriptions:OBJECTID: Internal feature number. Auto-generated by Esri software.SEGMENTID: Unique segment ID.ESITEID: Unique ESITE ID.GEONAMEID: Ties ESITE to GEONAMEID (unique ID for each road name) in VT E911 Road Centerlines.PD: Prefix Direction, previously name PRE.DIR.PT: Prefix Type.SN: Street Name. Previously named STREET.ST: Street Type.SD: Suffix Direction, i.e., W for West, E for East etc.PRIMARYNAME: A concatenation of the street-name parts (PD, PT, SN, ST, SD).ALIAS1: Alternate road name.ALIAS2: Alternate road name.ALIAS3: Alternate road name.ALIAS4: Alternate road name.ALIAS5: Alternate road name.PRIMARYADDRESS: A concatenation of house number and street-name parts (PD, PT, SN, ST, SD).SITETYPE: Type of site. Uses SiteTypes domain*.TOWNNAME: Town name.MCODE: Municpal code.ESN: Emergency Service Number. Developed for each town that indicates a unique town code for each law, fire, and EMS provider. These providers are compared against the master list to determine if they are already present. If they are, the existing state code is used. If the provider is new, they are added to the state master list with the next unique provider number.ZIP: Zip code.PARCELNUM: Parcel number.GPSX: GPS X coordinate.GPSY: GPS Y coordinate.MAPYEAR: Date added to E911 data.UPDATEDATE: Update date.STATE: US State.FIPS8: Federal information processing standards codes.SPAN: Pulled from the VCGI parcel dataset via spatial join 1-3 times per year; NOT MAINTAINED DAILY.SUBTYPE: Field not in use.GlobalID_1: System-generated ID.UNITCOUNT: For commercial and residential, number of units in the site.PRIMARYADD1: Concatenation of house number, full street name, and E911 town. E911 TOWN (AKA E911 JBOUND) IS NOT ALWAYS THE SAME AS POSTAL TOWN NOR IS IT ALWAYS THE SAME AS TOWN DEFINED BY MUNICIPAL BOUNDARY. E911 TOWN (E911 JBOUND) was originally defined for the Master Street Address Guide (MSAG) Community; E911 JBOUND contains names chosen by towns for representing town names for 911 purposes.PRIMARYADD2: Concatenation of PRIMARYADD1 plus zip code.SITETYPE_MULTI1: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI2: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI3: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI4: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI5: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.COUNTY: County.COUNTRY: Country.SOURCEOFDATA: Source of data.DRIVEWAYID: Field not in use.ESZ: Emergency Service Zone--a defined area covered by four primary-response agencies.HOUSE_NUMBER: House number.HOUSE_NUMBERSUFFIX: For addresses not in compliance with standards (typically in urbanized areas where otherwise renumbering needs to occur). For example, a new house between 8 and 10 is built and the town calls it 8 1/2 or 8A instead of renumbering; the 1/2 or A would be in this field; there are approximately less than 300-400 of these cases.HOUSE_NUMBERPREFIX: For the three streets where alpha characters come before the house number (e.g., A20 or B12).FIPS: County FIPS number.Shape: Feature geometry.*SiteTypes Domain:ABANDONEDACCESS POINTACCESSORY BUILDINGAIR SUPPORT / MAINTENANCE FACILITYAIR TRAFFIC CONTROL CENTER / COMMAND CENTERAIRPORT TERMINALAMBULANCE SERVICEAUDITORIUM / CONCERT HALL / THEATER / OPERA HOUSEBANKBOAT RAMP / DOCKBORDER CROSSINGBORDER PATROLBUS STATION / DISPATCH FACILITYCAMPCAMPGROUNDCEMETERYCITY / TOWN HALLCOAST GUARDCOLLEGE / UNIVERSITYCOMMERCIALCOMMERCIAL CONSTRUCTION SERVICECOMMERCIAL FARMCOMMERCIAL GARAGECOMMERCIAL W/RESIDENCECOMMUNICATION BOXCOMMUNICATION TOWERCOMMUNITY / RECREATION FACILITYCOURT HOUSECULTURALCUSTOMS SERVICEDAY CARE FACILITYDEVELOPMENT SITEEBS TOWEREDUCATIONALEMERGENCY PHONE / CALLBOXFAIR / EXHIBITION/ RODEO GROUNDSFERRY TERMINAL / DISPATCH FACILITYFIRE STATIONFISH FARM / HATCHERYFITNESS FACILITYFOOD DISTRIBUTION CENTERGAS STATIONGATED W/BUILDINGGATED W/O BUILDINGGOLF COURSEGOVERNMENTGRAVEL PITGREENHOUSE / NURSERYGROCERY STOREHARBOR / MARINAHAZARDOUS MATERIALS FACILITYHAZARDOUS STORAGE FACILITYHEALTH CLINICHELIPAD / HELIPORT / HELISPOTHISTORIC SITE / POINT OF INTERESTHOSPITAL / MEDICAL CENTERHOUSE OF WORSHIPHYDROELECTRIC FACILITYICE ARENAINDUSTRIALINSTITUTIONAL RESIDENCE / DORM / BARRACKSLANDFILLLAW ENFORCEMENTLIBRARYLODGINGLOOKOUT TOWERLUMBER MILL / SAW MILLMANUFACTURING FACILITYMINEMOBILE HOMEMORGUEMULTI-FAMILY DWELLINGMUSEUMNATIONAL GUARD / ARMORYNUCLEAR FACILITYNURSING HOME / LONG TERM CAREOFFICE BUILDINGOFFICE OF EMERGENCY MANAGEMENTOIL / GAS FACILITYOTHEROTHER COMMERCIALOTHER RESIDENTIALOUTPATIENT CLINICPARK AND RIDE / COMMUTER LOTPHARMACYPICNIC AREAPOST OFFICEPRISON / CORRECTIONAL FACILITYPRIVATE AND EXPRESS SHIPPING FACILITYPSAPPUBLIC BEACHPUBLIC GATHERINGPUBLIC TELEPHONEPUBLIC WATER SUPPLY INTAKEPUBLIC WATER SUPPLY WELLPUMP STATIONRACE TRACK / DRAGSTRIPRADIO / TV BROADCAST FACILITYRAILROAD STATIONRESIDENTIAL FARMREST STOP / ROADSIDE PARKRESTAURANTRETAIL FACILITYRV HOOKUPSCHOOLSEASONAL HOMESINGLE FAMILY DWELLINGSKI AREA / ALPINE RESORTSOLAR FACILITYSPORTS ARENA / STADIUMSTATE CAPITOLSTATE GARAGESTATE GOVERNMENT FACILITYSTATE PARKSTORAGE UNITSSUBSTATIONSUGARHOUSETEMPORARY STRUCTURETOWN GARAGETOWN OFFICETRAILHEADTRANSFER STATIONUNKNOWNUS FOREST FACILITYUS GOVERNMENT FACILITYUTILITYUTILITY POLE W/PHONEVETERINARY HOSPITAL / CLINICVISITOR / INFORMATION CENTERWAREHOUSEWASTE / BIOMASS FACILITYWASTEWATER TREATMENT PLANTWATER TANKWATER TOWERWIND FACILITY / WIND TOWERYOUTH CAMP

(Link to Metadata) EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) were taken from the official VT Agency of Transportation (VTrans) highway maps. New roads not appearing on the photos were digitized with locations approximated from the VTrans highway maps. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. https://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfmField Descriptions:OBJECTID: Internal feature number, automatically generated by Esri software.SEGMENTID: Unique segment ID.ARCID: Arc identifier, unique statewide. The ARCID is a unique identifier for every ARC in the EmergencyE911_RDS data layer.PD: Prefix Direction, previously name PRE.DIR.PT: Prefix Type.SN: Street Name. Previously named STREET.ST: Street Type.SD: Suffix Direction, i.e., W for West, E for East, etc.GEONAMEID: Unique ID for each road name.PRIMARYNAME: Primary name.ALIAS1: Alternate road name 1.ALIAS2: Alternate road name 2.ALIAS3: Alternate road name 3.ALIAS4: Alternate road name 4.ALIAS5: Alternate road name 5.COMMENTS: Free text field for miscellaneous comments.ONEWAY: One-way street. Uses the Oneway domain*.NO_MSAG:MCODE: Municipal code.LESN: Left side of road Emergency Service Number.RESN: Right side of road Emergency Service Number.LTWN: Left side of road town.RTWN: Right side of road town.LLO_A: Low address for left side of road.RLO_A: Low address for right side of road.LHI_A: High address for left side of road.RHI_A: High address for right side of road.LZIP: Left side of road zip code.RZIP: Right side of road zip code.LLO_TRLO_TLHI_TRHI_TRTNAME: Route name.RTNUMBER: Route number.HWYSIGN: Highway sign.RPCCLASSAOTCLASS: Agency of Transportation class. Uses AOTClass domain**.ARCMILES: ESRI ArcGIS miles.AOTMILES: Agency of Transportation miles.AOTMILES_CALC:UPDACT:SCENICHWY: Scenic highway.SCENICBYWAY: Scenic byway.FORMER_RTNAME: Former route name.PROVISIONALYEAR: Provisional year.ANCIENTROADYEAR: Ancient road year.TRUCKROUTE: Truck route.CERTYEAR:MAPYEAR:UPDATEDATE: Update date.GPSUPDATE: Uses GPSUpdate domain***.GlobalID: GlobalID.STATE: State.GAP: Gap.GAPMILES: Gap miles.GAPSTREETID: Gap street ID.FIPS8:FAID_S:RTNUMBER_N:LCOUNTY:RCOUNTY:PRIMARYNAME1:SOURCEOFDATA: Source of data.COUNTRY: Country.PARITYLEFT:PARITYRIGHT:LFIPS:RFIPS:LSTATE:RSTATE:LESZ:RESZ:SPEED_SOURCE: Speed source.SPEEDLIMIT: Speed limit.MILES: Miles.MINUTES: Minutes.Shape: Feature geometry.Shape_Length: Length of feature in internal units. Automatically computed by Esri software.*Oneway Domain:N: NoY: Yes - Direction of arcX: Yes - Opposite direction of arc**AOTClass Domain:1: Town Highway Class 1 - undivided2: Town Highway Class 2 - undivided3: Town Highway Class 3 - undivided4: Town Highway Class 4 - undivided5: State Forest Highway6: National Forest Highway7: Legal Trail. Legal Trail Mileage Approved by Selectboard after the enactment of Act 178 (July 1, 2006). Due to the introduction of Act 178, the Mapping Unit needed to differentiate between officially accepted and designated legal trail versus trails that had traditionally been shown on the maps. Towns have until 2015 to map all Class 1-4 and Legal Trails, based on new changes in VSA Title 19.8: Private Road - No Show. Private road, but not for display on local maps. Some municipalities may prefer not to show certain private roads on their maps, but the roads may need to be maintained in the data for emergency response or other purposes.9: Private road, for display on local maps10: Driveway (put in driveway)11: Town Highway Class 1 - North Bound12: Town Highway Class 1 - South Bound13: Town Highway Class 1 - East Bound14: Town Highway Class 1 - West Bound15: Town Highway Class 1 - On/Off Ramp16: Town Highway Class 1 - Emergency U-Turn20: County Highway21: Town Highway Class 2 - North Bound22: Town Highway Class 2 - South Bound23: Town Highway Class 2 - East Bound24: Town Highway Class 2 - West Bound25: Town Highway Class 2 - On/Off Ramp30: State Highway31: State Highway - North Bound32: State Highway - South Bound33: State Highway - East Bound34: State Highway - West Bound35: State Highway - On/Off Ramp40: US Highway41: US Highway - North Bound42: US Highway - South Bound43: US Highway - East Bound44: US Highway - West Bound45: US Highway - On/Off Ramp46: US Highway - Emergency U-Turn47: US Highway - Rest Area50: Interstate Highway51: Interstate Highway - North Bound52: Interstate Highway - South Bound53: Interstate Highway - East Bound54: Interstate Highway - West Bound55: Interstate Highway - On/Off Ramp56: Interstate Highway - Emergency U-Turn57: Interstate Highway - Rest Area59: Interstate Highway - Other65: Ferry70: Unconfirmed Legal Trail71: Unidentified Corridor80: Proposed Highway Unknown Class81: Proposed Town Highway Class 182: Proposed Town Highway Class 283: Proposed Town Highway Class 384: Proposed State Highway85: Proposed US Highway86: Proposed Interstate Highway87: Proposed Interstate Highway - Ramp88: Proposed Non-Interstate Highway - Ramp89: Proposed Private Road91: New - Class Unknown92: Military - no public access93: Public - Class Unknown95: Class Under Review96: Discontinued Road97: Discontinued Now Private98: Not a Road99: Unknown***GPSUpdate Domain:Y: Yes - Needs GPS UpdateN: No - Does not need GPS UpdateG: GPS Update CompleteV: GPS Update Complete - New RoadX: Unresolved Segment

(Link to Metadata) EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) were taken from the official VT Agency of Transportation (VTrans) highway maps. New roads not appearing on the photos were digitized with locations approximated from the VTrans highway maps. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. http://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfm

(Link to Metadata) EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) were taken from the official VT Agency of Transportation (VTrans) highway maps. New roads not appearing on the photos were digitized with locations approximated from the VTrans highway maps. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. https://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfmField Descriptions:OBJECTID: Internal feature number, automatically generated by Esri software.SEGMENTID: Unique segment ID.ARCID: Arc identifier, unique statewide. The ARCID is a unique identifier for every ARC in the EmergencyE911_RDS data layer.PD: Prefix Direction, previously name PRE.DIR.PT: Prefix Type.SN: Street Name. Previously named STREET.ST: Street Type.SD: Suffix Direction, i.e., W for West, E for East, etc.GEONAMEID: Unique ID for each road name.PRIMARYNAME: Primary name.ALIAS1: Alternate road name 1.ALIAS2: Alternate road name 2.ALIAS3: Alternate road name 3.ALIAS4: Alternate road name 4.ALIAS5: Alternate road name 5.COMMENTS: Free text field for miscellaneous comments.ONEWAY: One-way street. Uses the Oneway domain*.NO_MSAG:MCODE: Municipal code.LESN: Left side of road Emergency Service Number.RESN: Right side of road Emergency Service Number.LTWN: Left side of road town.RTWN: Right side of road town.LLO_A: Low address for left side of road.RLO_A: Low address for right side of road.LHI_A: High address for left side of road.RHI_A: High address for right side of road.LZIP: Left side of road zip code.RZIP: Right side of road zip code.LLO_TRLO_TLHI_TRHI_TRTNAME: Route name.RTNUMBER: Route number.HWYSIGN: Highway sign.RPCCLASSAOTCLASS: Agency of Transportation class. Uses AOTClass domain**.ARCMILES: ESRI ArcGIS miles.AOTMILES: Agency of Transportation miles.AOTMILES_CALC:UPDACT:SCENICHWY: Scenic highway.SCENICBYWAY: Scenic byway.FORMER_RTNAME: Former route name.PROVISIONALYEAR: Provisional year.ANCIENTROADYEAR: Ancient road year.TRUCKROUTE: Truck route.CERTYEAR:MAPYEAR:UPDATEDATE: Update date.GPSUPDATE: Uses GPSUpdate domain***.GlobalID: GlobalID.STATE: State.GAP: Gap.GAPMILES: Gap miles.GAPSTREETID: Gap street ID.FIPS8:FAID_S:RTNUMBER_N:LCOUNTY:RCOUNTY:PRIMARYNAME1:SOURCEOFDATA: Source of data.COUNTRY: Country.PARITYLEFT:PARITYRIGHT:LFIPS:RFIPS:LSTATE:RSTATE:LESZ:RESZ:SPEED_SOURCE: Speed source.SPEEDLIMIT: Speed limit.MILES: Miles.MINUTES: Minutes.Shape: Feature geometry.Shape_Length: Length of feature in internal units. Automatically computed by Esri software.*Oneway Domain:N: NoY: Yes - Direction of arcX: Yes - Opposite direction of arc**AOTClass Domain:1: Town Highway Class 1 - undivided2: Town Highway Class 2 - undivided3: Town Highway Class 3 - undivided4: Town Highway Class 4 - undivided5: State Forest Highway6: National Forest Highway7: Legal Trail. Legal Trail Mileage Approved by Selectboard after the enactment of Act 178 (July 1, 2006). Due to the introduction of Act 178, the Mapping Unit needed to differentiate between officially accepted and designated legal trail versus trails that had traditionally been shown on the maps. Towns have until 2015 to map all Class 1-4 and Legal Trails, based on new changes in VSA Title 19.8: Private Road - No Show. Private road, but not for display on local maps. Some municipalities may prefer not to show certain private roads on their maps, but the roads may need to be maintained in the data for emergency response or other purposes.9: Private road, for display on local maps10: Driveway (put in driveway)11: Town Highway Class 1 - North Bound12: Town Highway Class 1 - South Bound13: Town Highway Class 1 - East Bound14: Town Highway Class 1 - West Bound15: Town Highway Class 1 - On/Off Ramp16: Town Highway Class 1 - Emergency U-Turn20: County Highway21: Town Highway Class 2 - North Bound22: Town Highway Class 2 - South Bound23: Town Highway Class 2 - East Bound24: Town Highway Class 2 - West Bound25: Town Highway Class 2 - On/Off Ramp30: State Highway31: State Highway - North Bound32: State Highway - South Bound33: State Highway - East Bound34: State Highway - West Bound35: State Highway - On/Off Ramp40: US Highway41: US Highway - North Bound42: US Highway - South Bound43: US Highway - East Bound44: US Highway - West Bound45: US Highway - On/Off Ramp46: US Highway - Emergency U-Turn47: US Highway - Rest Area50: Interstate Highway51: Interstate Highway - North Bound52: Interstate Highway - South Bound53: Interstate Highway - East Bound54: Interstate Highway - West Bound55: Interstate Highway - On/Off Ramp56: Interstate Highway - Emergency U-Turn57: Interstate Highway - Rest Area59: Interstate Highway - Other65: Ferry70: Unconfirmed Legal Trail71: Unidentified Corridor80: Proposed Highway Unknown Class81: Proposed Town Highway Class 182: Proposed Town Highway Class 283: Proposed Town Highway Class 384: Proposed State Highway85: Proposed US Highway86: Proposed Interstate Highway87: Proposed Interstate Highway - Ramp88: Proposed Non-Interstate Highway - Ramp89: Proposed Private Road91: New - Class Unknown92: Military - no public access93: Public - Class Unknown95: Class Under Review96: Discontinued Road97: Discontinued Now Private98: Not a Road99: Unknown***GPSUpdate Domain:Y: Yes - Needs GPS UpdateN: No - Does not need GPS UpdateG: GPS Update CompleteV: GPS Update Complete - New RoadX: Unresolved Segment

INTROThis dataset--UtilityTransmit_VEC, includes 2 Vermont Electric Cooperative, Inc. (VEC) layers. 1) Primary Overhead and Underground Distribution Lines (Utility_VEC_DISTLINES_line). 2) Poles (Utility_VEC_POLES_point).Distribution lines were drawn from pole to pole based on GPS pole locations.VEC’s poles were collected via submeter accurate GPS starting in 2000. More recent locations are being collected via consumer and submeter accurate GPS. Pole locations and attribute data are updated throughout time as poles are changed, or lines are added or retired. Attributes are updated in the office and through inspections in the field.PURPOSEGeneral planning. HISTORYLines were submitted to VCGI for posting to data portal in 2015 and were re-posted w/ updates multiple times between 2015 and 2019 (last post on 2019-03-15).On 2020-10-20, VEC sumitted pole data to VT Dept. of Public Service for posting to VT Open Geodata Portal. In posting, this dataset was renamed from UtilityTransmit_VECDISTLINES to UtilityTransmit_VEC. It's line layer was renamed from Utility_VECDISTLINES_line to Utility_VEC_DISTLINES_line. The poles layer was added named Utility_VEC_POLES_point.DISCLAIMERVCGI, VEC, and the State of VT make no representations of any kind, including but not limited to the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the data. LINE FIELD DESCRIPTIONSGS_SUBTYPE: Distribution line sub-type category. 1 = Overhead. 3 = Underground.GS_PHASE: Distribution line phase. 1 = Single phase. 2 = Two phase. 3 = Three phase.POINT FIELD DESCRIPTIONSThe list below depicts the relationships between the fields in this layer and the fields defined in the Vermont Utility Pole data standard. List items follow a

Digital data from VG09-3 De Simone, D. and Gale, M., 2009,�Surficial geology and hydrogeology of Dorset, Vermont: Vermont Geological Survey Open-File Report VG09-3, 9 color plates, scale 1:24,000 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.

This dataset represents high-water mark observations made following widespread flooding in Vermont on July 10-11 and December 18, 2023. Sites visited following flood recession are part of a long-term floodplain monitoring network maintained by the University of Vermont. Immediately after the floods, field teams flagged high water marks, took photos, and marked the locations with smart phone GPS. Subsequently a survey team revisited the sites with an RTK-GPS to more precisely capture the location and elevation and post-processed through NOAA's OPUS.

Data quality is noted based on the following: Field Rating: Based on initial site visits. Field personnel noted their confidence level in the indicators of the high water marks. High confidence are noted as "Good", and lower confidence points are noted as "Fair" or "Poor" GPS Quality: Based on RTK-GPS survey quality. More information can be found in accompanying txt file.