VT Data - E911 Road Centerlines

THIS DATASET IS DEPRECATED. Beginning on June 24, 2026, this dataset is replaced with a next-generation E911 road centerlines layer--VT E911 Road Centerlines (RCL). RCL has a schema that is based on the National Emergency Number Association (NENA) Standard for NG9-1-1 GIS Data Model. THIS DATASET IS SCHEDULED TO BE REMOVED ON SEPTEMBER 8, 2026, to allow time for dependencies to be redirected to RCL. (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.cfm Field 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_T RLO_T LHI_T RHI_T RTNAME: Route name. RTNUMBER: Route number. HWYSIGN: Highway sign. RPCCLASS AOTCLASS: 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: No Y: Yes - Direction of arc X: Yes - Opposite direction of arc **AOTClass Domain: 1: Town Highway Class 1 - undivided 2: Town Highway Class 2 - undivided 3: Town Highway Class 3 - undivided 4: Town Highway Class 4 - undivided 5: State Forest Highway 6: National Forest Highway 7: 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 maps 10: Driveway (put in driveway) 11: Town Highway Class 1 - North Bound 12: Town Highway Class 1 - South Bound 13: Town Highway Class 1 - East Bound 14: Town Highway Class 1 - West Bound 15: Town Highway Class 1 - On/Off Ramp 16: Town Highway Class 1 - Emergency U-Turn 20: County Highway 21: Town Highway Class 2 - North Bound 22: Town Highway Class 2 - South Bound 23: Town Highway Class 2 - East Bound 24: Town Highway Class 2 - West Bound 25: Town Highway Class 2 - On/Off Ramp 30: State Highway 31: State Highway - North Bound 32: State Highway - South Bound 33: State Highway - East Bound 34: State Highway - West Bound 35: State Highway - On/Off Ramp 40: US Highway 41: US Highway - North Bound 42: US Highway - South Bound 43: US Highway - East Bound 44: US Highway - West Bound 45: US Highway - On/Off Ramp 46: US Highway - Emergency U-Turn 47: US Highway - Rest Area 50: Interstate Highway 51: Interstate Highway - North Bound 52: Interstate Highway - South Bound 53: Interstate Highway - East Bound 54: Interstate Highway - West Bound 55: Interstate Highway - On/Off Ramp 56: Interstate Highway - Emergency U-Turn 57: Interstate Highway - Rest Area 59: Interstate Highway - Other 65: Ferry 70: Unconfirmed Legal Trail 71: Unidentified Corridor 80: Proposed Highway Unknown Class 81: Proposed Town Highway Class 1 82: Proposed Town Highway Class 2 83: Proposed Town Highway Class 3 84: Proposed State Highway 85: Proposed US Highway 86: Proposed Interstate Highway 87: Proposed Interstate Highway - Ramp 88: Proposed Non-Interstate Highway - Ramp 89: Proposed Private Road 91: New - Class Unknown 92: Military - no public access 93: Public - Class Unknown 95: Class Under Review 96: Discontinued Road 97: Discontinued Now Private 98: Not a Road 99: Unknown ***GPSUpdate Domain: Y: Yes - Needs GPS Update N: No - Does not need GPS Update G: GPS Update Complete V: GPS Update Complete - New Road X: Unresolved Segment