20200501 vector digital data The Road Centerline data layer contains all town and state highways, as well as many private roads. The centerlines were originally developed under contract by Greenhorne and O'Mara under the guidance of the Vermont Center for Geographic Information (VCGI) in 1992. VCGI was the original steward of the road centerline data between 1992 and 2004. The Vermont Agency of Transportation (VTrans) is now the steward of this data layer.Updates have been performed over the years by VCGI, Regional Planning Commissions, and VTrans. VTrans has taken over the update and maintenance of the road centerline data layer and has revised the layer to match "Official" highway mileage. This layer is the most reliable source for official VTrans road class (AOTCLASS) information. However, this layer may not include every private road, and the road name information may not match the VT E911 Road Centerlines data layer. The VT E911 Road Centerlines road centerline layer maintained by Vermont's E911 Board has the most up-to-date roadname information. It is similar to this data layer, but it includes all private roads and generally has more reliable road name and address range information. There was a significant change in the schema in the June 2013 release as part of the effort between VTrans and E911 to merge their two datasets. The data layer includes the field structure agreed to by both entities, but many of the fields that are E911's have not been populated in this release. Due to software limitations, field attribute details are not included in the metadata imbedded in the dataset. Field attribute details are available in the XML file "TransRoad_RDS_20200501_metadata_FGDC.xml" and the document "VTrans Road Centerline Spatial Data User Guide" available online through the Vermont Open Geodata Portal (https://geodata.vermont.gov/datasets/VTrans::vt-road-centerline), the VTrans Mapping Section website (https://vtransmaps.vermont.gov/Maps/Publications/TransRoad_RDS_20200501_metadata_FGDC.xml, https://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide_20200501.pdf), or by contacting the VTrans Mapping Section. To provide high accuracy road centerlines and official road classification data for the State of Vermont. 19920101 20200501 ground condition In work Biannually -117.499996 -42.500205 45.018391 -89.999991 ISO 19115 Topic Category transportation structure None highways streets roads transportation infrastructure road centerlines Vermont None VCGI, VTrans and the State of Vermont 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.Although every effort has been made to assure the accuracy of features and their attributes for the road centerlines data layers, VCGI and VTrans are not accountable for any errors or misuse of the data. Vermont Agency of Transportation (VTrans) Johnathan Croft Mapping Section Chief Mailing and Physical

219 North Main Street

Barre Vermont 05641 US 802-828-2600 johnathan.croft@vermont.gov Vermont Agency of Transportation (VTrans) - Mapping Section Version 6.2 (Build 9200) ; Esri ArcGIS 10.5.1.7333 ORIGINAL 1992 DATA DEVELOPMENT NOTES: Proof plots were generated by the original contractor (1992). VCGI (then OGIS) staff verified the accuracy and attribute errors of all arcs. Corrections made by the contractor were spot checked by VCGI staff. Additional corrections were made directly by VCGI staff. All linework was checked by VCGI staff with translucent paper proof plots anchored to the source photos with 1000 meter tics. Attributes were checked against VTrans highway maps. Frequency files were generated from the final data to reveal unlikely and impossible attribute combinations. (e.g. a gravel US highway). UPDATES SINCE 1992: Between 1992 and 1999 all updates were managed by VCGI in cooperation with Vermont's Regional Planning Commissions (RPC's). VTrans has managed all updates since 1999. As roads are updated and revised by VTrans, internal Quality Control & Quality Assurance routines are run to assess any inaccurate or unlikely combination of attributes. Any questionable attributions are reviewed and corrected, The data is reviewed and checked with multiple processes, but there may be errors that were not detected. Due to the size of the statewide data layer and the level of complexity with the attribution, all reasonable care is taken to assure accuracy. Subsequent to the original digitizing, Regional Planning Commissions and the Vermont Center for Geographic Information (VCGI) made many minor corrections to road numbers, classes, and other attributes discovered while implementing new attributes and working with the data. VTrans has made major revisions to the VT Road Centerline data layer, including moving arcs to match digital orthophotography, changing route numbers, adding records, and updating road names fields. A combination of paper and RC Kodak RF 5000 scale orthophotos were used to determine road locations as originally digitized (1992). Road attributes 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 (and coded in the LOCMETH item). State forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 1250 orthophotos, or other means for adding new roads and improving road locations. See the LOCMETH arc attribute and the data updates listing for details. The statewide VT Road Centerline data layer is currently being maintained by the Vermont Agency of Transportation (VTrans). The data layer contains the spatial representation of the 14,000 plus miles of public highway within Vermont. This includes all Federal, State and Municipal highways and some State & National forest highways. There are also many private roads included in this data layer, but private roads are not necessarily complete and are not being maintained by VTrans in the same fashion as the public highways. VTrans is updating the VT Road Centerline data layer with input from the Regional Planning Commissions, municipalities and VCGI. The intention is that the VT Road Centerline data be maintained in a comprehensive layer from which other roads layers may be derived. All updates are made to the Road Centerline Data layer using the Highway Mapping System (HMS). The editing environment conforms with requirements defined in the "VGIS Road Centerline Spatial Data Standards" (http://vcgi.vermont.gov/resources/standards). HMS allows for feature tracking, recording of the update action (UPDACT) and management of the unique arc identifier (ARCID). If you have identified errors or changes, please contact staff at VTrans, (802) 828-2600. Some data updates have used RF 2500 or 1250 scale orthophotos, RF 5000 digital orthophotography, digital survey GPS, engineering CADD files, or other means for adding new roads and improving road locations. See the LOCMETH and SRCORG attributes for more detail. Since 2005, the VTrans Mapping Section has been updating the road centerline data layer in a single layer in ArcSDE and using this layer directly in the generation of the Town Highway Maps. This new environment has allowed for better integration with other data layers, new quality assurance methods, and more robust editing tools. The data has undergone much work, including alignments to the orthophotos, addition of roads, correction of mileage information, and the addition of new fields. The data is by no means complete or 100% accurate, but the data continues to improve. Line accuracy standards for the original data conversion (1992) were set as being within the confines of the visible road surface. All roads were checked for both line and attribute accuracy by VCGI. The linework was checked with translucent proof plots anchored to the source photos with 1000 meter tics. Most road centerlines are expected to fall within about 6 Meters of their true ground locations (except in cases where the wrong road was digitized/attributed, where orthophotos do not meet national map accuracy standards, or where road locations were not clearly visible on the photos). As noted by the Chittenden County RPC; "It is estimated that centerlines fall within the tax right-of-way 99% of the time." VTrans, as well as VCGI and the Regional Planning Commissions have made many adjustments and corrections to the VT Road Centerline data layer, improving the spatial accuracy of the data. The accuracy of the centerline data has improved with the advent of digital orthophotography. However, horizontal accuracy errors still exist, especially in counties where a thorough comparison to digital orthophotography has not taken place. VTrans is working toward updating the centerline to match the most current digital orthophotography, but has yet to complete this process. Quantitative_Horizontal_Positional_Accuracy_Assessment: Horizontal_Positional_Accuracy_Value: 6 map units Horizontal_Positional_Accuracy_Explanation: Overall accuracy estimation A formal accuracy assessment of the vertical positional information in the data set is not applicable. Original documentation completed. Operator - Steve Bower (VCGI) 19920212 RTNO attributes made left justified. Most RTNO values were previously right justified. A few corrections were made to arcs in the following tiles: 48,28,47,37,17,36,26,15,34,24,33,32,31,21. Preliminary lookup tables for road symbology have been placed in the RDS documentation directory. Operator - Nate Dansereau (VCGI) 19920826 Completion of roads corrections by VCGI staff for all tiles not previously available. Operator - Nate Dansereau (VCGI) 19920916 This update includes major modifications to the TransRoad_RDS layer. The layer is now managed by VCGI as a statewide, seamless, fully edgematched layer (RDSM). The tile structure has been changed from ORTHO64 to COUNTY, although TransRoad_RDS can be requested by TOWN as well as by COUNTY. Several new attributes have been added, including AOTCLASS, FUNCL, RDNAME, FIPS6 (town code), ARC_ID, RDSRC and RT_ID. The codes for attributes CLASS have been completely changed and expanded. SURFACE type 4 (graded and drained) has been eliminated and collapsed into soil (SURFACE=3). The FEDAID attribute has been dropped, although some codes were mapped onto the new FUNCL attribute. The attribute documentation has been generally improved, and describes in detail all changes made with this update. All unnecessary pseudo-nodes were removed. Updated data sets for Chittenden County and Southern Windsor RPCs have been integrated with the statewide layer. VCGI checked the data against the current VCGI version of the data, converted the attributes to new standard forms, then integrated the updated data with the rest of the statewide VCGI data. As well, functional class codes were conflated from Windham County RPC data to the current VCGI data. The Chittenden County data included many updates to the 1988 orthophotos, deletion of some roads of unknown class (CLASS=99), and some islands were removed at intersections. The Southern Windsor RPC data had been updated from preliminary release roads data, including many corrections to both attributes and linework. In some urban areas, roads were re-digitized to 1:2500 or 1:1250 orthophotos. Many attribute corrections were based on local review of proof plots. For both CCRPC and SWRPC, VCGI matched the new data to current VCGI data, identified arcs where the road class differed between the data sets, and, where needed, set AOTCLASS codes to be current with VTrans highway maps (1989, 1990 or 1993). As well, any roads which had been deleted but which still appeared on the VTrans maps were restored. The ORDATES.DBF and AOTDATES.DBF files have not yet been updated for Chittenden County and Southern Windsor RPCs. Operator - Steve Bower (VCGI) 19940119 Since the last TransRoad_RDS update, updated data sets have been provided by these RPCs: Southern Windsor (2 update sets), Chittenden County, Windham Regional, Central Vermont (2 update sets), Addison County, Rutland Regional and Two Rivers-Ottauquechee. In those and other regions, VCGI has made numerous updates, mainly to arc attributes. The number of updates varied by update set from minor to extensive. Details on individual update sets and updates are provided with digital files RDS.UPDSET and RDS.UPDTRX, and on file at VCGI. Extensive updates are expected during 1996 for a GIS data development project supporting the implementation of E911. In addition, several modifications have been made to the arc attributes. The format of the RDNAME attribute has changed, and will change again based on the E911 project. Item RTID was renamed (from RT_ID), and item ARCID was renamed (from ARC_ID). New values were added for other items, including new road classes. Operator - Steve Bower (VCGI) 19960202 E911 contractor updated data (topology and attributes). Added road name and address range information. Spatial updates performed using RF 5000 orthophotos and GPS field collection. Operator - Steve Sharp (VCGI) 19961212 Data updated by VTrans contractor (Information Visualization Services, South Burlington, VT). Included spatial and attribute updates. Operator - Steve Sharp (VCGI) 19970901 Extensive updates and QA/QC performed by VTrans and VCGI. Data has been integrated into the VGIS Data Warehouse for distribution. Operator - Steve Sharp (VCGI) 20001201 Final cut of 2000 data forwarded to VCGI as a single coverage by VTrans. Data has been integrated into the VGIS Data Warehouse for distribution. Operator - Steve Sharp (VCGI) 20010416 Implemented Sherburne to Killington name change by changing FIPS8 50021105 to 50021047. Renamed RDN21105 info file to RDN21047. Revised metadata and loaded data into VGIS Data Warehouse. Operator - Steve Sharp (VCGI) 20010503 Final cut of 2001 HMS updates. Data QA/QCed by VCGI and certified to meet VGIS Road Centerline Spatial Data Standards. Data has been integrated into the VGIS Data Warehouse for distribution. Operator - Steve Sharp (VCGI) 20011101 Final cut of 2002 HMS updates. Data QA/QCed by VCGI and certified to meet VGIS Road Centerline Spatial Data Standards. Data has been integrated into the VGIS Data Warehouse for distribution. Operator - Steve Sharp (VCGI) 20021106 Final cut of 2004 road centerline updates (HMS updates) sent to VCGI has a single coverage. A subset of 50 towns were QA/QCed by VCGI and certified to meet VGIS Road Centerline Spatial Data Standards. The remaining 205 towns have not been assessed by VCGI. Data has been integrated into the VGIS Data Warehouse for distribution. Operator - Steve Sharp (VCGI) 20040830 Preliminary cut of 2005 road centerline updates (HMS updates) sent to VCGI has a single coverage on 7/18/2005 by VTrans. The data has NOT been QA/QC by VCGI. Data has been integrated into the VGIS Data Warehouse for distribution. A final 2005 update will be released later this year. Operator - Steve Sharp (VCGI) 20051025 Primary cut of 2007 road centerlines with 2007 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. The data has not been QA/QC'd or assessed by VCGI. During 2006 and 2007, there has been a significant amount of work to the road centerline data layer to populate the AOTMILES for all towns with revised Town Highway Maps, accounting for 99 maps in 2007. As these towns are updated, effort has been extended to match the arcs to the orthophotography and to correct any issues with the data . In 2006, the Vermont Legislature passed Act 178 that required the alteration of the AOTCLASS 7 definition and the addition of a class 70. Several additional fields were also added to the road centerline data layer to accommodate more functionality within VTrans. Contact_Person: Johnathan Croft, Sara Moulton, and VTrans Mapping Unit Staff 20071015 Primary cut of 2008 road centerlines with 2008 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. The data has not been QA/QC'd or assessed by VCGI. Contact_Person: Johnathan Croft, Sara Moulton, and Michael Trunzo (VTrans) 20080625 Primary cut of 2009 road centerlines with 2009 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. The data has not been QA/QC'd or assessed by VCGI. Contact_Person: Johnathan Croft, Sara Moulton, and Michael Trunzo (VTrans) 20090101 Primary cut of 2010 road centerlines with 2010 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. The data has not been QA/QC'd or assessed by VCGI. This version incorporates a significant number of highway additions, based on compliance by towns with Act 178 of 2006, the "ancient roads act." Much work was performed to include accurate arcs and proper coding of the ancient roads. Each arc was assessed against the latest E911 road centerline data layer for matching road names, those that didn't match were updated for RDNAME and RDFLNAME. Some arcs were not updated due to the need to split an arc to match the E911 segmentation. It is expected that these arcs will be updated in the next cycle. Contact_Person: Sara Moulton (VTrans) 20110526 Primary cut of 2011 road centerlines with 2011 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. The data has not been QA/QC'd or assessed by VCGI. Contact_Person: Johnathan Croft, Sara Moulton, and Michael Trunzo (VTrans) 20110630 Primary cut of 2012 road centerlines with 2012 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. The data has not been QA/QC'd or assessed by VCGI. Contact_Person: Johnathan Croft, Sara Moulton, and Michael Trunzo (VTrans) 20120630 Year end cut of 2016 road centerlines with updates completed since 2010531. The fields "CREATIONUSER", "DATECREATED", "LASTUSER", "DATEMODIFIED" were added on 18 November 2016 to be used for editor tracking. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. Contact_Person: Johnathan Croft. Editing VTrans personnel: Sara Moulton, Michael Trunzo, Kerry Alley, Kevan Grimaldi, and Brian Lima. 20121231 Primary cut of 2013 road centerlines with 2012 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. The data has not been QA/QC'd or assessed by VCGI. VCGI loaded the data into the VGIS Data Warehouse for distribution, and integrated VTrans' metadata updates into the master metadata record for this dataset. Contact_Person: Johnathan Croft, Sara Moulton, and Michael Trunzo (VTrans) 20130630 VCGI received a copy of the 2013 RDS dataset on 20131024. VCGI ran a geometry check and removed 1 null geometry record. The data has otherwise not been QA/QC'd or assessed by VCGI. VCGI loaded the data into the VGIS Data Warehouse for distribution, and integrated VTrans' metadata updates into the master metadata record for this dataset. Contact_Person: Steve Sharp VCGI 20131028 VCGI received a copy of the latest RDS dataset (20131231) on 20140224. VCGI ran a geometry check and everything was clean. The data has otherwise not been QA/QC'd or assessed by VCGI. VCGI loaded the data into the VGIS Data Warehouse for distribution, and integrated VTrans' metadata updates into the master metadata record for this dataset. Contact_Person: Steve Sharp, VCGI 20140328 Primary cut of 2014 road centerlines with 2014 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Unit and corrections have been made. Contact_Person: Johnathan Croft, Sara Moulton, Michael Trunzo, and Kerry Alley (VTrans) 20140630 Primary cut of 2015 road centerlines with 2015 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. This release marks the sunset of Act 178 of 2006 and Act 158 of 2008 that made up the "Ancient Road Laws". July 1, 2015 is the date that "unidentified corridors" have been discontinued by Statute and municipalities were required to map all Class 1, 2, 3 and 4 town highways and legal trails. This dataset was used to generate the official 2015 Town Highway Maps. The highways in several villages were merged with their surrounding town and are no longer coded separately, specifically: Northfield Village/Northfield, Cabot Village/Cabot, and North Westminster Village/Westminster. The functional classification codes in the field "FUNCL" were updated to reflect the newly implemented Highway Functional Classification scheme released by the Federal Highway Administration (FHWA) in 2013. The new functional classification removes urban and rural delineation from the functional classification code. As a result, the fields "FUNCL_OLD” and "Urban_Code" were added to preserve the urban/rural categories and the old functional class values until such time as VTrans can complete a statewide functional class review. Additional information on the new functional classification criteria can be found in the FHWA publication, "Highway Functional Classification Concepts, Criteria and Procedures," 2013 edition, available online at: http://www.fhwa.dot.gov/planning/processes/statewide/related/highway_functional_classifications/fcauab.pdf Contact_Person: Johnathan Croft, Sara Moulton, Michael Trunzo, and Kerry Alley (VTrans Mapping Section) 20150630 Year end cut of 2015 road centerlines with updates completed since 20150630. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. Contact_Person: Johnathan Croft, Sara Moulton, Michael Trunzo, and Kerry Alley (VTrans) 20151230 Primary cut of 2016 road centerlines with 2016 updates completed and readied for sending to VCGI for posting. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. This dataset will be used to generate the official 2016 Town Highway Maps. The field "FAID" replaced the field "FAID_S". The field "FAID_N" is a transitional field and is likely to be removed in a future release. Johnathan Croft, Sara Moulton, Michael Trunzo, and Kerry Alley (VTrans Mapping Section) 20160531 Year end cut of 2016 road centerlines with updates completed since 2010531. The fields "CREATIONUSER", "DATECREATED", "LASTUSER", "DATEMODIFIED" were added on 18 November 2016 to be used for editor tracking. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. Contact_Person: Johnathan Croft. Editing VTrans personnel: Sara Moulton, Michael Trunzo, Kerry Alley, Kevan Grimaldi, and Brian Lima. 20161231 Primary cut of 2017 road centerlines with 2017 updates completed and readied for posting on the Vermont Open Data Portal. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. This dataset will be used to generate the official 2017 Town Highway Maps. The fields "DATECREATED_Converted", "DATEMODIFIED_Converted" were added in February 2017 to supersede "DATECREATED" and "DATEMODIFIED". Editing VTrans personnel: Johnathan Croft, Sara Moulton, Michael Trunzo, Kerry Alley, and Kevan Grimaldi. 20170531 Year-end cut of 2017 road centerlines with updates completed since 20170531. A significant amount of effort was put into improving the geometry of the road centerline data, from Mapping Section staff realigning highways to better match new 30 centimeter orthophotography, lidar data, and from Works Consulting, who was contracted to develop curve data from the road centerline geometry. The curve project required the geometry of the data to be reviewed and improved on local roads (FUNCL 7) with a priority to those with multiple crashes. About 85 functional class changes were made, primarily in Chittenden County with scattered changes throughout the rest of the state. These changes are reflected in the fields: FUNCL, TWN_LR, ETE_LR, Urban_Code, FED_AID, and Facility_Type. Two Federal Aid Urban Areas that extend into Vermont from neighboring states were added, including North Adams, MA extending the FAU into Pownal, and Walpole, NH extending into Rockingham. This required updates to the Urban_Code and applying splits to the data at the FAU boundaries. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. Due to software limitations, field attribute details are not included in the metadata associated with this release. Field attribute details are available in the "VTrans Road Centerline Spatial Data User Guide" available online through the Vermont Open Geodata Portal (http://geodata.vermont.gov/datasets/VTrans::vt-road-centerline), the VTrans Mapping Section website (http://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide.pdf), or by contacting the VTrans Mapping Section. Contact_Person: Johnathan Croft. Editing VTrans personnel: Sara Moulton, Michael Trunzo, Kerry Alley, and Kevan Grimaldi. 20171231 Primary cut of 2018 road centerlines with 2018 updates completed and readied for posting on the Vermont Open Geodata Portal. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. This dataset will be used to generate the official 2018 Town Highway Maps. Fields removed -- The following fields were removed in January 2018 after consultation with Jeremy McMullen, E911 Database Administrator: STREETID, COMMENTS, ALINAME, ADDRESSLOCK, NO_MSAG, C1_EXCEPTION, MCODE, LESN, RESN, LTWN, RTWN, LLO_A, RLO_A, LHI_A, RHI_A, LZIP, RZIP, LLO_T, RLO_T, LHI_T, RHI_T, ADDRESRANGEID, ROUTEINCLUDE, MAPYEAR, UPDATESOURCE, UPDATEDATE, GPSUPDATE, STATE, GAP, GAPMILES, GAPSTREETID. These fields were also removed as part of this release: FAID_N, DATECREATED_Converted, DATEMODIFIED_Converted. Fields added -- PENT, TOWNGEOID, StartNodeID, EndNodeID, Ownership. Existing TWN_LR Field Enhanced -- In this release, there was a significant addition of information in the existing field TWN_LR. In 2012, the Federal Highway Administration (FHWA) announced the requirement for State Departments of Transportation to submit a Linear Reference System (LRS) that included all public roads as part of their Highway Performance Monitoring System (HPMS) submittal. Prior to this, the requirement for an LRS applied only to highways that were Federal Aid routes. The new requirement is referred to as the All Road Network of Linear Referenced Data (ARNOLD). (https://www.fhwa.dot.gov/policyinformation/hpms/documents/arnold_reference_manual_2014.pdf) Due to software limitations, field attribute details are not included in the metadata associated with this release. Field attribute details are available in the "VTrans Road Centerline Spatial Data User Guide" available online through the Vermont Open Geodata Portal (http://geodata.vermont.gov/datasets/VTrans::vt-road-centerline), the VTrans Mapping Section website (http://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide.pdf), or by contacting the VTrans Mapping Section. Contact_Person: Johnathan Croft. Editing VTrans personnel: Johnathan Croft, Sara Moulton, Michael Trunzo, Kerry Alley, and Kevan Grimaldi. 20180531 Year-end cut of 2018 road centerlines with updates completed since 20180531. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. Due to software limitations, field attribute details are not included in the metadata associated with this release. Field attribute details are available in the "VTrans Road Centerline Spatial Data User Guide" available online through the Vermont Open Geodata Portal (http://geodata.vermont.gov/datasets/VTrans::vt-road-centerline), the VTrans Mapping Section website (http://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide.pdf), or by contacting the VTrans Mapping Section. Contact_Person: Johnathan Croft. Editing VTrans personnel: Sara Moulton, Michael Trunzo, Kerry Alley, and Kevan Grimaldi. 20181231 Year-end cut of 2019 road centerlines with updates completed since 20190531. The data has been internally QA/QC'd by the VTrans Mapping Section and corrections have been made. Due to software limitations, field attribute details are not included in the metadata associated with this release. Field attribute details are available in the "VTrans Road Centerline Spatial Data User Guide" available online through the Vermont Open Geodata Portal (http://geodata.vermont.gov/datasets/VTrans::vt-road-centerline), the VTrans Mapping Section website (https://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide_20191231.pdf), or by contacting the VTrans Mapping Section. Contact_Person: Johnathan Croft. Editing VTrans personnel: Sara Moulton, Michael Trunzo, and Kerry Alley. 20191231 Primary cut of 2020 road centerlines with updates from the 2020 Mileage Certificates plus other updates completed since 20191231. This dataset will be used to generate the official 2020 Town Highway Maps. The data has been internally QA/QC'd by the VTrans Mapping Section and posted on the Vermont Open Geodata Portal at https://geodata.vermont.gov/datasets/VTrans::vt-road-centerline . Due to software limitations, field attribute details are not included in the metadata associated with this release. Field attribute details are available in the "VTrans Road Centerline Spatial Data User Guide" available online through the Vermont Open Geodata Portal (https://geodata.vermont.gov/datasets/VTrans::vt-road-centerline ), the VTrans Mapping Section website (https://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide_20200501.pdf ), or by contacting the VTrans Mapping Section. Contact_Person: Johnathan Croft. Editing VTrans personnel: Sara Moulton, Michael Trunzo, and Kerry Alley. 20200501 Vector String 76407 NAD 1983 StatePlane Vermont FIPS 4400 0.9999642857142858 -72.5 42.5 500000.0 0.0 coordinate pair 0.0001 0.0001 meters D North American 1983 GRS 1980 6378137.0 298.257222101 VT Road Centerline OBJECTID Internal feature number. Esri Sequential unique whole numbers that are automatically generated. SEGMENTID A unique numeric value assigned by the software for each feature. E911 ARCID The ARCID is a unique arc identifier within each municipality (town, city, grant or gore). When combined with the FIPS8 code, this provides a unique arc identifier statewide. A redefined item, FAID contains both FIPS8 and ARCID within the road centerline dataset. The ARCID can be used for error reporting, and is used to aid in quality control of updated data. • New arcs must be assigned ARCIDs unique to their towns. • When an arc is split, both arcs will be assigned new ARCIDs. • When two (or more) arcs are joined, the resulting arc will be assigned a new ARCID. • If the FIPS8 code of an arc is changed (putting the arc into a new town), then the ARCID must be modified to make it unique with the arc’s new town. Care must be taken to assure that unique ARCID codes are maintained when editing near a town boundary. The ARCID is not changed when an arc is only moved or reshaped. New ARCID codes should be added in sequential order, starting with the next available ARCID (1 more than the current maximum for the given town). ARCIDs will never be reused. In summary, any data updates must maintain unique ARCIDs within each municipality. VTrans Mapping Section PDPrefix road direction, previously named PRE.DIR; incompletely populated in this release. E East Producer defined N North Producer defined NE Northeast Producer defined NW Northwest Producer defined S South Producer defined SE Southeast Producer defined SW Southwest Producer defined W West Producer defined PT Prefix type; incompletely populated in this release. E911 SN Street name; incompletely populated in this release. E911 ST Street type; incompletely populated in this release. E911 SDStreet direction; incompletely populated in this release.E911 E East Producer defined N North Producer defined S South Producer defined W West Producer defined GEONAMEID Geo Name ID number; incompletely populated in this release. E911 PRIMARYNAME Full primary road segment name; incompletely populated in this release. E911 ALIAS1 Alternate road name 1; incompletely populated in this release. E911 ALIAS2 Alternate road name 2; incompletely populated in this release. E911 ALIAS2 Alternate road name 2; incompletely populated in this release. E911 ALIAS3 Alternate road name 3; incompletely populated in this release. E911 ALIAS4 Alternate road name 4; incompletely populated in this release. E911 ALIAS5 Alternate road name 5; incompletely populated in this release. E911 SURFACETYPEThe surface type of the road; previously named SURFACE. Note: The surface type for some highways has not been reviewed or updated since the development of the road centerline data layer in the 1990’s and is based off the last field inventory to be performed on the highway. Surface types may have changed since this point, either being upgraded through maintenance or downgraded. VTrans seeks input regarding the quality and content of the surface type of the highway network. VTrans Mapping Section 1 Paved -- A road whose surface is bituminous concrete or other treated surface such as cement concrete, bricks, or cobblestone. Producer defined 2 Gravel -- A graded and drained road, the surface of which consists of gravel, broken stone, slag, slate and shale or other similar fragmental material coarser than sand. A gravel highway as applied to Town highways is defined as a highway having a gravel base and widths sufficient to provide reasonable transportation facilities at all times of the year, according to the classification of the highway. Producer defined 3 Soil or graded and drained earth -- A road which has been improved to provide more adequate traffic service by the addition of sand, coarse loam or light course of gravel, but not in sufficient amount to prevent a break-through in the spring, or a road of natural earth, aligned and graded to permit reasonably convenient use by motor vehicles. Producer defined 5 Unimproved/primitive -- An earth road consisting of the natural ground and which is maintained in a condition of bare passability, or an unimproved road on which there appears to be no public maintenance and which may or may not be traveled or passable. Producer defined 6 Impassable or untraveled -- A public highway in a primitive condition on which there appears to be no public travel and which is not maintained. Producer defined 9 Unknown Producer defined ONEWAYOne-way street.VTrans Mapping Section N Not a one-way street. Producer defined X One-way street in opposite direction of arc, Producer defined Y One-way street in direction of arc. Producer defined RTNAMEThe RTNAME town highway number/name corresponds to the official number on the VTrans highway maps with an added prefix (ex: "I-89", "VT-12A", "TH-3", "US-4", etc.). State and federal numbers will be unique for that highway for the entire state, while town-numbered highways will only be unique for that town. RTNAME = '-' is used for a blank (no data) value. The RTNAME field must not be empty. Where a route has two route numbers (as shown on road signs), the more local number (and prefix) is used - for example, a route having both a State route number and a town route number is assigned the town route number (as shown on the VTrans highway maps). The RTNAME field is not the same as RDNAME or ETE_LR. The RDNAME field refers to the road’s common name (defined by the E911 GEONAMEID field) - for example, Main Street may be considered Town Highway 5 (TH-5) by VTrans. In this situation the RTNAME would be "TH-5" and the RDNAME value would be 12519 (which is "Main Street" in the E911 data set). However, the same road could also be classified as "Vermont Route 12" (VT-12). In this case, the ETE_LR field would be populated with "V012".VTrans Mapping Section Alt US- US Alternate Route Producer defined BR I- Interstate Business Route Producer defined BR US- U.S. Business Route Producer defined BSp I- Interstate Business Spur Producer defined BSp US- U.S. Business Spur Producer defined Hist US- Historic U.S. Route Producer defined Hist VT- Vermont Numbered Route - Historic Route Producer defined I- Interstate Producer defined NF- National Forest Highway Producer defined NSH- Named State Highway Producer defined Old US- Old US Route Producer defined Old VT- Old Vermont Numbered Route Producer defined S- Other State Highway special case Producer defined SF- Department of Forests, Parks and Recreation Highway Producer defined TH- Town Highway Producer defined US- U.S. Route Producer defined VT- Vermont Numbered Highway Producer defined RTNUMBER This field is related to the RTNAME field. Everything after the dash "-" in the RTNAME field is transferred to this field. It should always match RTNAME. Previously known as RTNO. VTrans Mapping Section HWYSIGNThe HWYSIGN corresponds to how the road is signed in the field by VTrans, with an added prefix (ex: "I-89", "VT-12A", "TH-3", "US-4", etc.). State and federal numbers will be unique for that highway for the entire state, while town-numbered highways will only be unique for that town. HWYSIGN = '-' is used for a blank (no data) value. The HWYSIGN field must not be empty. The HWYSIGN field is not the same as RTNAME. HWYSIGN should be consistent with how the road is signed by VTrans in the field. RTNAME should be consistent with how the road is marked on the official VTrans Town Highway Maps. These don't always match.VTrans Mapping Section Alt US US Alternate Route Producer defined BR I- Interstate Business Route Producer defined BR US- U.S. Business Route Producer defined BSp I- Interstate Business Spur Producer defined BSp US- U.S. Business Spur Producer defined Hist US- Historic U.S. Route Producer defined Hist VT- Vermont Numbered Route - Historic Route Producer defined I- Interstate Producer defined NF- National Forest Highway Producer defined NSH- Named State Highway Producer defined Old US- Old US Route Producer defined Old VT- Old Vermont Numbered Route Producer defined S- Other State Highway special case Producer defined SF- Department of Forests, Parks and Recreation Highway Producer defined TH- Town Highway Producer defined US- U.S. Route Producer defined VT- Vermont Numbered Highway Producer defined RPCCLASS The RPCCLASS item indicates the road class, generally as shown on official VTrans highway maps. However, updates to the roads data have changed some road RPCCLASS codes based on local and/or regional review; therefore, in some cases the RPCCLASS values may not agree with current VTrans highway maps. NOTE: This field is for the convenience of end-users only. Changes made to this field by end-users are unofficial and may not be maintained in the roads data layer. RPCCLASS may be reset to equal AOTCLASS whenever AOTCLASS is updated. Two attributes for road class are therefore used: the RPCCLASS code, which can be modified as needed for regional/local mapping, and the AOTCLASS code, which maintains agreement with the VTrans town highway maps. Comparison of the RPCCLASS and AOTCLASS attributes will help to identify roads needing class updates by VTrans. All arcs must be assigned RPCCLASS and AOTCLASS codes. In addition to the road class, the RPCCLASS field is used to indicate the road 'type' (as for codes 11 to 19). Although this road type is not technically the road class, it is convenient to embed the 'type' information in the RPCCLASS code for generating maps with lookup tables. These 'type' codes are needed for state routes and class 1 and 2 town highways, as well as for interstates and US routes. (See also AOTCLASS for specific code descriptions.) VTrans Mapping Section AOTCLASSThis item holds the official VTrans road class from the VTrans highway maps (see also the description for RPCCLASS). All arcs must be assigned an AOTCLASS code. AOTCLASS generally uses the same codes as the RPCCLASS field, except for codes 8 and 9 - some RPCs use 8 to identify private roads not generally used by the public and 9 to identify private roads in general use by the public, while VTrans uses 8 to identify private roads not shown on the Town Highway Maps (most private roads) and 9 to identify private roads shown on the Town Highway Maps. These are usually short connectors between public highways or roads such as the Mount Mansfield Toll Road. VTrans follows a statutory process to define and reclassify town highways based on information provided from each town on their annual Mileage Certificate. This certificate is a record of total mileage in each classification of highway. Any changes require proper documentation and following of the statutory process. VTrans will make corrections based on the formal documentation, but cannot alter classification without justification. Act 178 of 2006 formally added class 4 and legal trail mileage to the Mileage Certificates, prompting the need to distinguish between formally approved legal trails. VTrans has added the class of 70 for legal trails that have yet to be approved, and leaving class 7 for those legal trails that have been approved by Selectboards.VTrans Mapping Section 1 Town Highway Class 1 – undivided Producer defined 2 Town Highway Class 2 – undivided Producer defined NUTSSections of highway deemed "Not Up To Standard"; in short, sections of highway that do not meet Class 3 standards at the time of inventory and are functionally classified as Class 4, but legally still Class 3. Contact VTrans for more information.VTrans Mapping Section N The highway is not "Not Up To Standard" (The highway meets Class 3 or better standards). Producer defined Y The highway is "Not Up To Standard" (The highway does NOT meet Class 3 standards). Producer defined NHSNational Highway System designation, as defined by FHWA. NOTE: The Intermodal Connector is a new addition. Several of this type of highway exist within Vermont, primarily connections of the NHS to bus stations, airports and railroad stations.VTrans Mapping Section 0 Not on NHS Producer defined 1 NHS – Interstate Producer defined 2 ISTEA High-Priority Corridor Producer defined 3 Non-Interstate STRAHNET Producer defined 4 STRAHNET Connector Producer defined 5 ISTEA High-Priority Corridor/Non-Interstate STRAHNET Producer defined 6 ISTEA High-Priority/STRAHNET Connector Producer defined 7 NHS – Principal Arterial Producer defined FUNCLFunctional Class Code. Functional classification codes are based on a federal classification system in use by VTrans. In earlier releases of TransRoad_RDS, functional classes were distinguished between rural and transportation-defined urban areas (8 in Vermont). This required road arcs to be split at the rural/urban boundaries. The current functional classification codes eliminated separate urban and rural classifications (please note the rural, small urban, and urbanized area designation is kept as a separate item, see the attribute Urban_Code). The Urban Collectors default to Major Collectors. In Vermont, there has previously not been a road functionally classified as both "urban" and "minor collector." In the upcoming functional classification review prompted by the coding changes, VTrans will evaluate roadways based on the 2013 edition of the Federal Highway Administration’s "Highway Functional Classification Concepts, Criteria, and Procedures," likely resulting in roadways functionally classified as minor collectors within the identified urban areas. The boundaries of the Urbanized Area and the Small Urban Areas (Census Urban Clusters with population >5,000 as specified by the Federal Highway Administration) were adjusted for transportation planning purposes in a collaborative process between VTrans and the appropriate regional planning partners. The adjusted urban area encompasses the entire urban area (of population >5,000) defined by the Census Bureau, in a single, contiguous entity, and is designed to include areas outside municipal boundaries that have urban characteristics with residential, commercial, industrial or national defense land uses consistent with or related to the development patterns of the Census-defined boundary. The adjusted urban area is also inclusive of large traffic generators near the urban area, and is designed so that its physical location can be easily discerned in the field based on physical characteristics such as roads, railroads, utility lines and water features. Lastly, the adjusted urban area was then evaluated for feature irregularities to minimize confusion. Information from the VTrans Highway Safety Data Unit has been incorporated into this dataset. NOTE: There have been several new additions and alterations which have been made to the functionally classed highways that were not reflected in the previous series of Federal Urban Area Maps or the Functional Class Map of the State of Vermont. These maps were updated in 2016 using the updated Functional Class road centerline data.VTrans Mapping Section 0 Not part of Functional Classification System Producer defined 1 Interstate Producer defined 2 Principal Arterial – other freeways and expressways Producer defined 3 Principal Arterial – other Producer defined 4 Minor Arterial Producer defined 5 Major Collector Producer defined 6 Minor Collector Producer defined 7 Local Producer defined TWN_LR Town-based linear reference code used to generate the town-based Linear Reference System data layer. The TWN_LR is related to the ETE_LR field but also includes the CTCODE. For example, the TWN_LR value for VT Route 12 in Montpelier is V012-1211 (ETE_LR = V012, CTCODE = 1211). VTrans Mapping Section ETE_LR Previously known as LR_ETE. It is used to identify "routed" roads, and is assigned by VTrans. This item contains an "end-to-end" LRS identifier used to identify routed roads. VTrans Mapping Section The ETE_LR can be broken down into the following components (or redefined items): - Route Type Field values: A = Alternate Route B = Business Route I = Interstate N = Named State Highway S = Special Route: a town highway that is a major or minor collector, or is an urban route U = US Route V = VT Signed Route - Route Number The numeric portion of the highway number (three digits), right-justified in characters 2-4. For Named State Highways, Major Collectors, and Urban Collectors, four-digit codes are used (in characters 2 -5). - Route # Modifier Used for a letter or special modifier, if needed. Named State Highways, Major Collectors, and Urban Collectors retain their full four-digit codes in common usage. For these, the Highway Number and Modifier are combined to form a four-digit highway number. For the three separate sections of Alternate US 5, the modifiers (1 to 3) are: A0051 = Alternate US 5, St. Johnsbury A0052 = Alternate US 5, Newport A0053 = Alternate US 5, Derby Valid Highway # Modifier characters include: [letter] = highway letter (e.g., the 'A' in Highway 2A) [digit] = special cases (e.g., Alternate US 5); digit for a Named State Highway, Major, or Urban Collector [blank] = cases where no modifier is needed and no subsequent components are needed for the ETE_LR [dash] = cases where no modifier is needed but other ETE_LR components follow - Direction The direction character is included only if the highway is divided. However, it is NOT used for northbound or eastbound mainline routes. The direction character is used only with northbound or eastbound approaches, connectors, jughandles, ramps, and spurs. Field values: ' ' = [blank] = undivided route with no subsequent ETE_LR components E = eastbound (for divided routes) N = northbound (for divided routes) S = southbound (for divided routes) W = westbound (for divided routes) Examples: I089 = I-89, northbound lane I089-S = I-89, southbound lane U002 = US-2, undivided portions U002-W = US-2, westbound portions (where divided) V003-NA020 = VT 3, approach 20 (approaches generally use the same direction as the parent road) - Subtype This field describes sections of road that are not on the main line, yet have defined lengths recognized by the Agency. Field values: ' ' = [blank] = no subtype A = approach C = connector F = facilities/rest areas, turnouts, access roads J = jughandle R = ramp S = spur - Numeric ID The ID number represents different things according to the subtype. Approaches and jughandles are numbered (initially) in ascending order from the start of the parent route in the primary direction. Numbers will increment by multiples of ten (ex: 10, 20, 30, 40, etc.). Gaps are left between numbers for future construction. For ramps and spurs, the number refers to the exit number for the parent route. A few ramps exit at locations that have no exit number; these have zeros in this field. Where no ID is required in this field, blanks are used. - Alpha ID This letter identifies ramps and spurs, as taken from the route logs (except for two ramps at I-91’s Exit 2, which were named A/B and C/D on the route logs. These have been renamed 'E' and 'F', respectively.) Where no ID is required in this field, a blank space is used. Examples: U004 = US-4 eastbound, divided highway U004-W = US-4 westbound, divided highway V100-NA002 = VT-100, Approach #2 B004-WJ001 = Business Route US-4 westbound, Jughandle #1 I089-SR009A = I-89 southbound, Exit 9 ramp CTCODE County-Town code based on values defined by the Vermont Agency of Transportation, VTrans. The CTCODE is comprised of the first two digits representing the County and the last two digits representing the Town in alphabetical order within the County. The counties are numbered sequentially starting with Addison County (01) and ending with Windsor County (14). Each town is then numbered sequentially within each county, producing a unique CTCODE. The county-town code identifies the municipality in which each road falls. The CTCODE is evident on reference markers in the field, which include the CTCODE, route identifier and mile marker. NOTE: The order of towns like Saint Albans (aka St. Albans) and Saint Johnsbury (aka St. Johnsbury) is based on the unabbreviated names - for example, in Caledonia County the CTCODE order for Saint Johnsbury places it between Ryegate and Sheffield (0310 Ryegate, 0311 Saint Johnsbury, 0312 Sheffield). NOTE: The CTCODE system was implemented before the Town of Sherburne changed its name to Killington - the name was changed, but the CTCODE was not (its CTCODE remained 1121, between 1120 Rutland Town and 1122 Shrewsbury). VTrans Mapping Section A list is available in Appendix C of the VTrans Road Centerline Spatial Data User Guide https://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide_20200501.pdf or at https://vtransmaps.vermont.gov/Maps/Publications/CTCODE_listing.pdf or https://vtransmaps.vermont.gov/Maps/Publications/CTCODE_listing_11x17.pdf UA VTrans Urban Area Code. The Urban Area code identifies villages and other urbanized areas within the Minor Civil Divisions specified by the FIPS8 codes. The codes include 'urban compacts' having separate VTrans Town Highway Maps. The one-digit code is used in conjunction with the FIPS8 code to uniquely identify each urban area. NOTE: Several villages have been merged with towns and the villages no longer exist. For mapping purposes, these villages may have become 'urban compacts'. VTrans Mapping Section A list is available in Appendix D of the VTrans Road Centerline Spatial Data User Guide https://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide_20200501.pdf CTUA CTCODE with UA Code, unique to all towns and Urban Areas in Vermont. VTrans Mapping Section See Appendiices C and D of the VTrans Road Centerline Spatial Data User Guide https://vtransmaps.vermont.gov/Maps/Publications/VTrans_Road_Centerline_User_Guide_20200501.pdf or at https://vtransmaps.vermont.gov/Maps/Publications/CTCODE_listing.pdf or https://vtransmaps.vermont.gov/Maps/Publications/CTCODE_listing_11x17.pdf CERTCODE Similar to CTUA, but unique only to the Mileage Certificates and towns that are autonomous for Highways. Urban Compacts and Villages not incorporated for highways carry the Town code. VTrans Mapping Section ARCMILES Calculated mileage based on Arc attribute [Shape.STLength()] * 0.0006214). The ARCMILES item indicates the mileage on each segment of road. ARCMILES is the primary basis for the RDNAME route system measurements. The ARCMILES item is necessary for rebuilding or remeasuring the RDNAME route system. The ARCMILES field is simply the product of the LENGTH * .0006214. It is not intended to reflect or duplicate actual or official VTrans mileage. VTrans Mapping Section AOTMILES The AOTMILES field indicates the "official" VTrans mileage on each segment of public highway. This includes all sections that are noted with mileage annotation on the Town Highway Map series. The AOTMILES are only for State Routes and Town Highways that are Class 1, 2, 3 or 4, and Legal Trails. If there is a mileage on the Town Highway Map, AOTMILES should be coded. The VTrans Mapping Unit uses AOTMILES to generate the mileage summaries and listings that are shown on the Town Highway Maps, prompting the need for accurate and complete mileage information. AOTMILES are rounded to the nearest 100th of a mile on Town Highways and 1000th of a mile on State Highways. VTrans Mapping Section AOTMILES_CALC Used internally by VTrans to prorate AOTMILES across specific road segments while editing. Not for use outside of the Highway Mapping System. VTrans Mapping Section UPDACTUsed for flagging the type of update made to an arc. NOTE: For S (split) and U (unsplit), the locations of the vertices may be unchanged. The shapes (and combined lengths) of the arcs may remain the same, but nodes may have been added, removed or moved along the arcs. Moving a pseudo node is sometimes required to modify the location where an attribute changes. For example, a pseudo node will need to be changed in response to a change in the location of a town boundary. All the attributes for the two arcs remain the same; only the location of the pseudo node has changed. This would entail splitting and unsplitting the two arcs, and therefore would be coded as ‘S’ and ‘U’. Sometimes an arc may be modified more than once, in which case either of the appropriate UPDACT codes can be assigned. For example, an arc might be reshaped and then split. In such a case, the arcs could be coded with an ‘S’ (split). Although it is not critical, it is preferable for the 'S' (split) code to take precedence over the ‘M’ code. Likewise, ‘A’ (added arc) takes precedence of other codes, so that if an added arc is later split. the UPDACT code should remain ‘A’. Routine cartographic realignments or subtle changes are generally not coded as a 'M' (move). UPDACT Hierarchy (from highest to lowest): 1. A (Addition), 2. S (Split), 3. U (Unsplit), 4. M (Move) It is not necessary to record changes to attributes.VTrans Mapping Section A Added arc (i.e., a new arc) Producer defined M Moved arc (by reshaping the arc, moving a node, moving or deleting a vertex, or other action altering the shape of the arc) Producer defined S Split arc (both new arcs are coded ‘S’) Producer defined U Unsplit arc (originally 2 or more arcs) Producer defined LOCMETHMethod used to locate/digitize a road segment (arc). Many Class 4 roads, legal trails, and other roads are difficult to locate with confidence on the orthophotos. For such roads, a road clearly visible on the orthophoto may have been digitized and assigned a value equal to 2 due to the uncertainty of it was the correct road. Code 4 was not in use at the beginning of the original digitizing contract. For northern parts of the state [approximately north of northing STP meters 216000], roads not appearing on the orthophotos may have been given a value equal to 2. Use of the digital orthophotos is improving the accuracy of the road centerlines and any roads not clearly visible on the paper orthophotos may be moved to match the digital orthophotos. If this process is performed, the LOCMETH will be altered to reflect the new location method. (Please refer to SRCORG for the organization making the location alteration or addition.)VTrans Mapping Section Producer defined Producer defined Producer defined Producer defined Producer defined Producer defined Producer defined 1 Visible on and digitized from a 1:5000 orthophoto (or better, as documented in the update record) with good degree of certainty as to location and correct RTNO (now known as RTNUMBER) attribute. Producer defined Producer defined 2 Road not clearly visible on the orthophoto, but it appears that it probably was there at the time the photo was taken. Location estimated from the AOT maps, adjoining roads, and land features. Producer defined 3 Not clearly visible on the orthophoto; location estimated from State Forest maps. Producer defined 4 No indication of the road on the orthophoto; apparently a new road built since the orthophoto was taken. Location estimated from VTrans maps. Producer defined 5 Road centerlines drafted onto orthophotos from engineering drawings and the like. Producer defined 6 Invisible on the orthophoto, but located based on town or other local knowledge of the area. Producer defined 7 Digitized centerline of the parcel (tax map) road right-of-way. Producer defined 8 Screen digitized from drafting by town officials onto maps of approximately 1:15000 to 1:20000 scale. Producer defined 9 Coordinates captured via a GPS device utilizing "dead reckoning" with typical horizontal accuracy within five meters. Producer defined SRCORGOrganization/project which created/updated a road segment (arc). This attribute identifies the organization or project which digitized an arc. When a road arc is digitized, moved, or reshaped, the SRCORG code should be updated. The SRCORG codes will serve as a record of “who did it". VTrans currently updates the SRCORG field with a code of 26 for each altered arc. This includes arcs moved to match the orthophotos, splits due to new roads, or unsplits due to same attribution. LOCMETH and UPDACT can also be viewed to give pedigree or tracking of the latest changes to an arc.VTrans Mapping Section 1 VCGI, original data (assigned Sept 1993) Producer defined 2 VCGI, updated location Producer defined 10 Addison County RPC Producer defined 11 Bennington County Regional Commission Producer defined 12 Central Vermont Regional Planning Commission Producer defined 13 Chittenden County Regional Planning Commission Producer defined 14 Northwest Regional Planning Commission Producer defined 15 Lamoille County Planning Commission Producer defined 16 Northeast Vermont Development Association Producer defined 17 Rutland Regional Planning Commission Producer defined 18 Southern Windsor Regional Planning Commission (or its contractor) Producer defined 19 Two Rivers-Ottauquechee Regional Planning Commission Producer defined 20 Upper Valley-Lake Sunapee Regional Planning Commission Producer defined 21 Windham Regional Commission Producer defined 22 microData Producer defined 23 Incorporated from municipal updates Producer defined 24 E911 GIS database development project (1996) Producer defined 25 IVS Highway Mapping System Project Producer defined 26 VTrans Highway Mapping System updates Producer defined SCENICHWYHighways officially designated as "Scenic Highways" by VTrans or municipalities. Previously known as SCENIC. The ability to designate a Scenic Highway is defined in Vermont Statute and documented on the Mileage Certificates. The VTrans Mapping Section maintains the official listing of Scenic Highways within the State of Vermont. NOTE: There have been some sections of Town Highway in Norwich that have been designated as Scenic Highway, but are not coded due to the Selectboard's request not to map or distribute information regarding the highway's locations. Due to this request, the coding for SCENIC is incomplete in the Town of Norwich. VTrans Mapping Section 0 Not designated as Scenic Highway Producer defined Designated as Scenic Highway by local municipality 1 Producer defined 2 Designated as Scenic Highway by VTrans Producer defined SCENICBYWAYDesignated Scenic Byways.VTrans Mapping Section 0 Not a scenic byway Producer defined 100 Connecticut River Scenic Byway Producer defined 200 Lake Champlain Byway Producer defined 300 Molly Stark Trail: A Byway through the Green Mountains Producer defined 400 Mad River Byway Producer defined 500 Stone Valley Byway Producer defined 600 Green Mountain Byway Producer defined 700 The Crossroad of Vermont Producer defined 800 Scenic Route 100 Byway Producer defined 900 The Shires of Vermont Byway Producer defined 1000 Northeast Kingdom Byway Producer defined FORMER_RTNAME Former Town Highway Number or Route Number for an arc. This is used primarily on Class 2 transfers, reclassifications of town highways to or from legal trails, or discontinuance of highways. VTrans Mapping Section PROVISIONALYEAR Year a provisional highway is added to the VTrans Town Highway Map, based on information supplied by the town as part of the Certificate of Highway Mileage process. According to Vermont Statute, 19 V.S.A. § 302. Classification of town highways (a)(3)(C), a highway not meeting the minimum standards for a class 3 town highway may be reclassified as a provisional class 3 highway if within five years of the determination, it will meet all class 3 highway standards. Null values are allowed in this field. VTrans Mapping Section ANCIENTROADYEAR Year a road that was considered an ancient road was added or most recently modified based on a change prompted by the Certificate of Highway Mileage process. This relates to Act 178 of 2006 and Act 158 of 2008 which sunset on July 1, 2015. VTrans Mapping Section TRUCKROUTEDesignated Truck Routes. These designations identified which routes allowed up to 72-foot long trucks with no permits required. These designations are now obsolete, but remain in the data for historical purposes. Please consult the Vermont Department of Motor Vehicles for current rules, routes, and permitting for commercial trucking.VTrans Mapping Section 0 Not a truck route Producer defined 100 National Network – Limited Access (no overall length limit) Producer defined 200 Brattleboro VT-9 between I-91 and New Hampshire Producer defined 300 Truck Network, 72-foot limit (no permit) Producer defined 400 US-4, Permit Required Producer defined 500 Urban Avoidance Route, Part of Truck Network, 72-foot limit (no permit) Producer defined 600 Network – Limited Access (no overall length limit) Producer defined SPEEDLIMIT Speed limit. Currently a place holder for future use. VTrans Mapping Section ROADCLOSEDRoad Closed status. Currently a placeholder for future use; incompletely populated in this release.VTrans Mapping Section Closed Road closed Producer defined Closed_AVO Road closed – passage restricted to authorized vehicles only Producer defined Closed_LTO Road closed – passage restricted to local traffic only Producer defined Closed_W Road closed for winter Producer defined Normal_SR Normal service requested Producer defined Open Road open Producer defined Open_CD Road open with construction delays Producer defined Open_R Road open with restrictions Producer defined ISVISIBLEFlag used by the Highway Mapping System for cartographic purposes.VTrans Mapping Section 0 Not visible Producer defined 1 Visible Producer defined CERTYEAR Year an arc was altered due to a change reflected on the Certificate of Highway Mileage. VTrans Mapping Section GlobalID Globally Unique Identifier or GUID; not defined in this release. VTrans Mapping Section FIPS8 Municipality (town, city, gore, grant) FIPS code. The FIPS8 code identifies the municipality in which each road falls, as shown on the VTrans Town Highway Maps. The FIPS8 code is a modified version of FIPS6 (as listed in the Geographic Area Codes Standard of the VGIS Handbook). FIPS8 includes the FIPS state code (for example: 50 for Vermont) + FIPS6. VTrans makes adjustments to the FIPS8 coding based on the best available information at its disposal. VTrans maintains its own version of the town boundaries, called townindex and townindex_arc. These data layers are sent to VCGI for review and inclusion of any pertinent changes into BNDHASH. VTrans Mapping Section RTNUMBER_N Similar to RTNUMBER, but in numeric format. Previously known as RTNO_N. It is used to have public highway listings display in numeric order instead of text order - for example, a listing based on RTNUMBER would be ordered as 1, 10, 11, 2, 20, 21, while a listing based on RTNUMBER_N would be ordered as 1, 2, 10, 11, 20, 21. The letter suffix in routes is assigned a decimal value. Examples: 100A = 100.10 100B = 100.20 100C = 100.30 US-ALT5 = 5.9 ALT VT-100 = 100.9 VTrans Mapping Section RDNAME Road name code. Road names are stored as an integer code, referencing look-up table RDS.RDNAMES. An integer code is used to minimize the space required in the road centerline attribute table. Each named road will have a unique RDNAME value and should reflect the "official" road name from E911, but there may have been some roads that either did not match in automated evaluation, or were missed. Users should generally turn to the E911\RDS data layer when they need "official" road name information and use the Trans_Road_RDS as a secondary name source. The current equivalent of RDNAME in E911RDS is GEONAMEID. Because GEONAMEID is incompletely populated in this release, VTrans continues its use of RDNAME until the VTrans and E911 road centerline data sets are merged. A value of 99999999 indicates that the RDFLNAME entered by VTrans is more correct than the E911 PRIMARYNAME for the arc at the time the arc was added or modified. VTrans Mapping Section RDFLNAME Full road name. VTrans has put an effort forward to correct the TransRoad_RDS data layer to reflect the "official" road names from E911, but there may have been some roads that either did not match in automated evaluation, or were missed. The E911 data should still be used as the "official" source and the Trans_Road_RDS as a secondary name source. NOTE: There currently isn't a reliable mechanism for maintenance of this item. Users should generally turn to the EmergencyE911_RDS data layer when they need "official" road name information. The current equivalent of RDFLNAME in E911RDS is PRIMARYNAME, but because PRIMARYNAME is incompletely populated in this release, VTrans will continue its use of RDFLNAME until the VTrans and E911 road centerline data sets are merged. VTrans Mapping Section ISVISIBLE_UCFlag used by the VTrans Highway Mapping System for cartographic purposes.VTrans Mapping Section 0 Not visible Producer defined 1 Visible Producer defined FUNCL_OLDOld Functional Class Code. These functional classification codes were used in the FUNCL field in data releases prior to 2015 and are based on a federal classification system in use by VTrans. Functional classes distinguish between rural and transportation-defined urban areas (8 in Vermont). Therefore, proper assignment of this attribute requires that road arcs be split at the rural/urban boundaries. NOTE: See FUNCL for the current Functional Classification codes. VTrans Mapping Section 0 Not part of Functional Classification System Producer defined 1 Principal arterial – Interstate Producer defined 2 Rural principal arterial Producer defined 4 Rural principal arterial – other (not other freeway); not a standard federal code Producer defined 6 Rural minor arterial Producer defined 7 Rural major collector Producer defined 8 Rural minor collector Producer defined 9 Rural local Producer defined 11 Urban principal arterial – Interstate Producer defined 12 Urban principal arterial – other freeway Producer defined 14 Urban principal arterial – other Producer defined 16 Urban minor arterial Producer defined 17 Urban collector Producer defined 19 Urban local Producer defined Urban_CodeCensus urban code.VTrans Mapping Section 11755 Five-digit code to uniquely identify the Census 2010 Urbanized Area (population greater than or equal to 50,000) of Burlington, VT, adjusted for transportation planning purposes by VTrans in conjunction with regional planning partners. Producer defined 99998 Small Urban area to identify the Census Urban Clusters with a population greater than or equal to 5,000 and less than 50,000, adjusted for transportation planning purposes by VTrans in conjunction with regional planning partners. Producer defined 99999 Rural areas; all areas outside the adjusted Urbanized Area and Small Urban Area boundaries, for transportation planning purposes Producer defined FAID Calculated field based on FIPS8 and ARCID. The first eight digits represent the FIPS8 value and the last four digits represent the ARCID value. VTrans Mapping Section FED_AID The Federal Aid Number for specific highway sections that are part of the Federal Aid Highway System or functionally classed as minor collectors. This number is used by VTrans in reporting on federal aid routes. Field values: 010-099 Arterial (rural and urban) 100-499 Rural Major Collector 500-999 Rural Minor Collector 1000-9002 Urban Collectors and Urban Minor Arterials 9420 Montpelier Junction State Highway (Major Collector) 9992 Morristown -- Alt VT-100 (Rural Minor Arterial) 9996 Newport City -- Alt-5 (Rural Minor Arterial) The “1000-9002 Urban Collectors and Urban Minor Arterials” are organized as follows: 1000-1063 Bennington 1200-1208 North Bennington Village 1402-1408 Old Bennington Village 1608-1625 Shaftsbury 2000-2048 Brattleboro 3000-3064 Rutland City 3113 Hartford - White River Junction 3200-3222 Rutland Town 3400-3409 West Rutland 3602-3604 Mendon 3200 Proctor 3810-3825 Proctor 5000-5072 Burlington City 5100-5113 Winooski City 5202-5228 South Burlington City 5300-5312 Essex Junction Village 5300 Essex Town 5402-5414 Essex Town 5504-5514 Williston 5600-5621 Colchester 5702-5722 Shelburne 5000 Milton 5802-5816 Milton 5900-5940 Middlebury 6000-6032 Barre City 6101-6119 Barre Town 6200-6208 Berlin 6300-6303 East Montpelier 6400-6434 Montpelier City 7000-7034 St. Johnsbury 8000-8034 St. Albans City 8200-8216 St. Albans Town 9000-9002 Newport City VTrans Mapping Section Facility_TypeFacility_Type has been added to allow for better summary of mileage for the Federal Highway Administration's Highway Performance Monitoring System (HPMS). This field represents the operational characteristics of a highway segment, based on the definitions in the HPMS Field Manual. A copy of this manual can be found on-line at the following link: http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/HPMS_2014.pdf; see also http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/chapter4b.cfm.VTrans Mapping Section 1 One-Way Roadway – Roadway that operates with traffic moving in a single direction during non-peak period hours Producer defined 2 Two-Way Roadway – Roadway that operates with traffic moving in both directions during non-peak period hours Producer defined 4 Ramp – Non-mainline junction or connector facility contained within a grade-separated interchange Producer defined 5 Non-Mainline – All non-mainline facilities excluding ramps. Producer defined 6 Non-Inventory Direction – Individual road/roads of a multi-road facility that is/are not used for determining the primary length for the facility. Producer defined 7 Planned/Unbuilt – Planned roadway that has yet to be constructed. Producer defined Shape Feature geometry. Esri Coordinates defining the features. PENTA highway or trail that is enclosed by the owner of the land during any part of the year, by erecting stiles, unlocked gates, and bars in the places designated, through permission from the governing body of the municipality and recorded in the town clerk’s office.VTrans Mapping Section Null Not coded Producer defined N Not designated as Pent Producer defined Y Designated as Pent Producer defined TOWNGEOID Town identifying code as defined and enumerated in the Vermont Center for Geographic Information (VCGI) “VT Geographic Area Codes Standard – State, County, Town, Village, and RPC Codes” http://vcgi.vermont.gov/sites/vcgi/files/VT_GIS_Geographic_Area_Codes_Standard.pdf VTrans Mapping Section StartNodeID Integer referencing the point feature from the VTrans “Nodes” feature class that uniquely represents the location of the first vertex of the arc’s geometry. Wherever the ends of two or more arcs intersect, those arcs will each have a StartNodeID value and/or EndNodeID value in common, depending on the direction of digitization. Loop features have StartNodeID value = EndNodeID value. VTrans Mapping Section EndNodeID Integer referencing the point feature from the VTrans “Nodes” feature class that uniquely represents the location of the last vertex of the arc’s geometry. Wherever the ends of two or more arcs intersect, those arcs will each have a StartNodeID value and/or EndNodeID value in common, depending on the direction of digitization. Loop features have StartNodeID value = EndNodeID value. VTrans Mapping Section OwnershipType of Governmental Ownership as defined in FHWA Model Inventory of Roadway Elements (MIRE) field 4 - https://safety.fhwa.dot.gov/rsdp/downloads/fhwasa17048.pdf.VTrans Mapping Section 1 State Highway Agency Producer defined 2 County Highway Agency Producer defined 3 Town or Township Highway Agency Producer defined 4 City or Municipal Highway Agency Producer defined 11 State Park, Forest, or Reservation Agency Producer defined 12 Local Park, Forest, or Reservation Agency Producer defined 21 Other State Agency Producer defined 25 Other Local Agency Producer defined 26 Private (other than Railroad) Producer defined 27 Railroad Producer defined 31 State Toll Authority Producer defined 32 Local Toll Authority Producer defined 40 Other Public Instrumentality (e.g. Airport, School, University) Producer defined 50 Indian Tribe Nation Producer defined 60 Other Federal Agency Producer defined 62 Bureau of Indian Affairs Producer defined 63 Bureau of Fish and Wildlife Producer defined 64 U.S. Forest Service Producer defined 66 National Park Service Producer defined 67 Tennessee Valley Authority Producer defined 68 Bureau of Land Management Producer defined 69 Bureau of Reclamation Producer defined 70 Corps of Engineers Producer defined 72 Air Force Producer defined 73 Navy/Marines Producer defined 74 Army Producer defined 80 Other Producer defined 99 Unknown Producer defined created_user This field records the ArcSDE geodatabase user name of the user who created the arc. The field was originally named CREATIONUSER and was one of four fields added for editor tracking on 2016-11-18. On 2018-09-25, The field name was changed to created_user because Esri changed the default names it uses in editor tracking. VTrans Mapping Section created_date This field records the date and time the arc was created. The time is recorded in Coordinated Universal Time (UTC). The field was originally named DATECREATED and was one of four fields added for editor tracking on 2016-11-18. On 2018-09-25, the field name was changed to created_date because Esri changed the default names it uses in editor tracking. VTrans Mapping Section last_edited_user This field records the ArcSDE geodatabase user name of the user who last modified the record. The field was originally named LASTUSER and was one of four fields added for editor tracking on 2016-11-18. On 2018-09-25, The field name was changed to last_edited_user because Esri changed the default names it uses in editor tracking. VTrans Mapping Section last_edited_date This field records the date and time the record was modified in any way. The time is recorded in Coordinated Universal Time (UTC). The field was originally named DATEMODIFIED and was one of four fields added for editor tracking on 2016-11-18. On 2018-09-25, the field name was changed to last_edited_date because Esri changed the default names it uses in editor tracking. VTrans Mapping Section UPDATENOTES Notes about an update to the road segment. VTrans Mapping Section Shape_Length Length of feature in internal units. Esri Positive real numbers that are automatically generated. Until the Esri Metadata Tool handles field attribute information reliably, the field attribute metadata will not be stored using the Esri metadata format. Information about the field attributes is available through the Vermont Agency of Transportation Mapping Section's "VTrans Road Centerline Spatial Data User Guide" and the metadata in XML format. These are available through the Vermont Open Data Portal. As of December 2018, the URL is http://geodata.vermont.gov/datasets/VTrans::vt-road-centerline The entity and attribute information was generated by the individual and/or agency identified as the originator of the data set. Please review the rest of the metadata record for additional details and information. Vermont Agency of Transportation (VTrans) Johnathan Croft Mapping Section Chief Mailing and Physical

219 North Main Street

Barre Vermont 05641 US 802-828-2600 johnathan.croft@vermont.gov VCGI and the State of Vermont 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. Digital Data https://geodata.vermont.gov/datasets/VTrans::vt-road-centerline No charge when downloading from the internet, and when no custom processing is required. 20200501 20200501 Vermont Agency of Transportation (VTrans) Johnathan Croft Mapping Section Chief Mailing and Physical

219 North Main Street

Barre Vermont 05641 US 802-828-2600 johnathan.croft@vermont.gov FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time