GDB_HMS.HMSADMIN.rdsmall_arc
vector digital data
The Road Centerline data layer (TransRoad_RDS) 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 VCGI (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, RPCs, and VTrans. The 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 EmergencyE911_RDS data layer. The EmergencyE911_RDS road centerline layer maintained by Vermont's E911 Board as 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.
To provide high accuracy road centerlines and official road classification data for the State of Vermont.
19920101
20161231
ground condition
Annually
-117.499996
-42.500205
45.018391
-89.999991
ISO 19115 Topic Categories
transportation
structure
None
highways
roads
road centerlines
infrastructure
streets
Vermont
transportation
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
VTrans GIS Database Administrator
mailing and physical
One National Life Drive
Montpelier
Vermont
05633-5001
US
802-828-2600
802-828-2334
johnathan.croft@vermont.gov
Vermont Agency of Transportation (VTrans) - Mapping Section
Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.3.1.4959
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, RPC's and VCGI have 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 TransRoad_RDS 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 TransRoad_RDS data layer is currently being maintained by the Vermont Agency of Transportation (VTrans). The TransRoad_RDS 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 TransRoad_RDS data layer with input from the Regional Planning Commissions, municipalities and VCGI. The intention is that the TransRoad_RDS 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 TransRoad_RDS 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
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.
20121231
Vector
String
75169
NAD 1983 StatePlane Vermont FIPS 4400
0.9999642857142858
-72.5
42.5
500000.0
0.0
coordinate pair
0.0001
0.0001
meter
D North American 1983
GRS 1980
6378137.0
298.257222101
TransRoad_RDS
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; maintained by E911
E911 field - VTrans Mapping Section description
1
311067
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. DETAILS: 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
1
2419
STREETID
A unique number previously used by E911 for each road segment. Matches the content of the SEGMENTID field; incompletely populated in this release.
VTrans Mapping Section
1
253234
PD
Prefix road direction, previously named PRE.DIR; maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
N
North
Producer defined
NE
Northeast
Producer defined
E
East
Producer defined
SE
Southeast
Producer defined
S
South
Producer defined
SW
Southwest
Producer defined
W
West
Producer defined
NW
Northwest
Producer defined
PT
Prefix type. Maintained by E911; incompletely populated in this release
E911
Unknown
SN
Street name. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
ST
Street type. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
SD
Street direction. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
N
North
E911
E
East
E911
S
South
E911
W
West
E911
GEONAMEID
Geo Name ID number. Maintained by E911; incompletely populated in this release
E911
0
710091
USEGEONAMESALIASES
Use Geonames Aliases. 1 = Yes , 0 = No. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
0 = No. Maintained by E911; incompletely populated in this release
E911
1
1 = Yes. Maintained by E911; incompletely populated in this release
E911
0
1
PRIMARYNAME
Full Primary Road Segment Name. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
ALINAME
Alternate name. Maintained by E911; incompletely populated in this release
E911
Unknown
ALIAS1
Alternate road name 1. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
ALIAS2
Alternate road name 2; maintained by E911; incompletely populated in this release
E911
Unknown
ALIAS3
Alternate road name 3. Maintained by E911; incompletely populated in this release
E911
Unknown
ALIAS4
Alternate road name 4. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
ALIAS5
Alternate road name 5. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
COMMENTS
Free text field for miscellaneous comments. Maintained by E911; incompletely populated in this release
E911
Unknown
SURFACETYPE
The surface type of the road, previously named SURFACE maintained by: VTrans
Vermont Road Centerline Data Standard
1
Paved
Road Centerline Spatial Data Standard
2
Gravel
Road Centerline Spatial Data Standard
3
Soil or graded and drained earth
Road Centerline Data Standard
5
Unimproved/Primitive
Road Centerline Data Standard
6
Impassable or untravelled
Road Centerline Data Standard
9
Unknown
Road Centerline Data Standard
ONEWAY
Oneway street. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
N
No. Not a oneway street.
E911
Y
Yes. Oneway street in direction of arc.
E911
X
Yes. Oneway street in opposite direction of arc.
E911
ADDRESSLOCK
1 = Yes 0 = No. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
No
E911
1
Yes
E911
0
1
NO_MSAG
No definition included; maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
C1_EXCEPTION
No definition included. Maintained by E911; incompletely populated in this release
VTrans Mapping Section
0
542224
MCODE
Municipal code. Maintained by E911; incompletely populated in this release
E911
0
760
LESN
Left side-of-road Emergency Service Number. Maintained by E911; incompletely populated in this release
E911
-1
673
RESN
Right side-of-road Emergency Service Number. Maintained by E911; incompletely populated in this release
E911
-1
673
LTWN
The town to the left side of a road, based upon the road segment’s stored direction. Maintained by E911; incompletely populated in this release
VTrans Mapping Section
Unknown
RTWN
The town to the right side of a road, based upon the road segment’s stored direction. Maintained by E911; incompletely populated in this release
VTrans Mapping Section
Unknown
LLO_A
Low address for left side of road for the road segment based on the arc direction. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
127925
RLO_A
Low address for right side of road for the road segment based on the arc direction. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
127926
LHI_A
LHI_A
Low address value for the right side of the road for the road segment based on arc direction; maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
124267
RHI_A
High address value for the right side of the road for the road segment based on arc direction. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
124266
LZIP
ZIP code on the left side of the road using the stored line direction for placement. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
RZIP
ZIP code on the right side of the road using the stored line direction for placement. Maintained by: E911 incompletely populated in this release
VTrans Mapping Section
Unknown
LLO_T
LLO_T
Low address value for the left side of the road using the stored line direction for placement. Maintained by E911; incompletely populated in this release
VTrans Mapping Section
0
175392
RLO_T
Low address value for the right side of the road using the stored line direction for placement. Maintained by E911; incompletely populated in this release
VTrans Mapping Section
0
175392
LHI_T
High address value for the left side of the road using the stored line direction for placement. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
177747
RHI_T
High address value for the right side of the road using the stored line direction for placement. Maintained by E911; incompletely populated in this release
VTrans Mapping Section
0
177746
ADDRESRANGEID
Address range ID number. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
159772
ROUTEINCLUDE
1 = Yes 0 = No. Maintained by E911; incompletely populated in this release
E911
1
1 = Yes. Maintained by E911; incompletely populated in this release
E911
0
0 = No. Maintained by E911; incompletely populated in this release
E911
0
1
RTNAME
The 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". maintained by: VTrans Staff
VTrans Road Centerline Spatial Data User Guide
Alt US-
US Alternate Route
VTrans Road Centerline Spatial Data User Guide
BR I-
Interstate Business Route
VTrans Road Centerline Spatial Data User Guide
BR US-
U.S. Business Route
VTrans Road Centerline Spatial Data User Guide
BSp I-
Interstate Business Spur
VTrans Road Centerline Spatial Data User Guide
BSp US-
U.S. Business Spur
VTrans Road Centerline Spatial Data User Guide
Hist US-
Historic U.S. Route
VTrans Road Centerline Spatial Data User Guide
Hist VT-
Vermont Numbered Route - Historic Route
VTrans Road Centerline Spatial Data User Guide
I-
Interstate
VTrans Road Centerline Spatial Data User Guide
NF-
National Forest Highway
VTrans Road Centerline Spatial Data User Guide
NSH-
Named State Highway
VTrans Road Centerline Spatial Data User Guide
Old US-
Old US Route
VTrans Road Centerline Spatial Data User Guide
Old VT-
Vermont Numbered Route - Old Route
VTrans Road Centerline Spatial Data User Guide
S-
Other State Highway special case
VTrans Road Centerline Spatial Data User Guide
SF-
Dept. of Forests, Parks and Recreation Highway
VTrans Road Centerline Spatial Data User Guide
TH-
Town Highway
VTrans Road Centerline Spatial Data User Guide
US-
U.S. Route
VTrans Road Centerline Spatial Data User Guide
VT-
Vermont Numbered Route
VTrans Road Centerline Spatial Data User Guide
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 Road Centerline Spatial Data User Guide
Unknown
HWYSIGN
Alt US-
US Alternate Route
VTrans Road Centerline Spatial Data User Guide
BR I-
Interstate Business Route
VTrans Road Centerline Spatial Data User Guide
BR US-
U.S. Business Route
VTrans Road Centerline Spatial Data User Guide
BSp I-
Interstate Business Spur
VTrans Road Centerline Spatial Data User Guide
BSp US-
U.S. Business Spur
VTrans Road Centerline Spatial Data User Guide
Hist US-
Historic U.S. Route
VTrans Road Centerline Spatial Data User Guide
Hist VT-
Vermont Numbered Route - Historic Route
VTrans Road Centerline Spatial Data User Guide
I-
Interstate
VTrans Road Centerline Spatial Data User Guide
NF-
National Forest Highway
VTrans Road Centerline Spatial Data User Guide
NSH-
Named State Highway
VTrans Road Centerline Spatial Data User Guide
Old US-
Old US Route
VTrans Road Centerline Spatial Data User Guide
Old VT-
Vermont Numbered Route - Old Route
VTrans Road Centerline Spatial Data User Guide
S-
Other State Highway special case
VTrans Road Centerline Spatial Data User Guide
SF-
Dept. of Forests, Parks and Recreation Highway
VTrans Road Centerline Spatial Data User Guide
TH-
Town Highway
VTrans Road Centerline Spatial Data User Guide
US-
U.S. Route
VTrans Road Centerline Spatial Data User Guide
VT-
Vermont Numbered Route
VTrans Road Centerline Spatial Data User Guide
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
1
99
AOTCLASS
This item will hold 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 - 4
Class 1-4 town highway, undivided (see 11-19, 21-29 for divided)
VTrans - E911
5
State Forest Highway
VTrans - E911
6
National Forest Highway
VTrans - E911
7
Legal Trail
VTrans - E911
8
Private Road - No Show
VTrans - E911
9
Private Road
VTrans - E911
10
Driveway (put in driveway)
VTrans - E911
11-19
Town Highway Class 1, 11 = North Bound, 12 = South Bound, 13 = East Bound, 14 = West Bound, 15 = On/Off Ramp, 16 = Emergency U-Turn, 17 = Rest Area, 19 = Other
VTrans - E911
20
County Highway
VTrans - E911
21-29
Town Highway Class 2, 21 = North Bound, 22 = South Bound, 23 = East Bound, 24 = West Bound, 25 = On/Off Ramp, 26 = Emergency U-Turn, 27 = Rest Area, 29 = Other
VTrans - E911
30
State Highway, undivided centerline (most state highways)
VTrans - E911
31-39
State Highway, 31 = North Bound, 32 = South Bound, 33 = East Bound, 34 = West Bound, 35 = On/Off Ramp, 36 = Emergency U-Turn, 37 = Rest Area, 39 = Other
VTrans - E911
40
US Highway, undivided centerline (most US highways)
VTrans - E911
41-49
US Highway, 41 = North Bound, 42 = South Bound, 43 = East Bound, 44 = West Bound, 45 = On/Off Ramp, 46 = Emergency U-Turn, 47 = Rest Area, 49 = Other
VTrans - E911
50
Interstate Highway, undivided centerline (not currently used)
VTrans - E911
51-59
Interstate Highway, 51 = North Bound, 52 = South Bound, 53 = East Bound, 54 = West Bound, 55 = On/Off Ramp, 56 = Emergency U-Turn, 57 = Rest Area, 59 = Other
VTrans - E911
60
US Government Highway)
VTrans - E911
65
Ferry
VTrans - E911
70
Unconfirmed Legal Trail
VTrans - E911
71
Unidentified Corridor
VTrans - E911
80
Proposed Highway - Unknown Class
VTrans - E911
81-83
Proposed Class 1-3 Town Highway
VTrans - E911
84
Proposed State Highway
VTrans - E911
85
Proposed US Highway
VTrans - E911
86
Proposed Interstate Highway
VTrans - E911
87
Proposed Interstate Highway - Ramp
VTrans - E911
88
Proposed Non-Interstate Highway - Ramp
VTrans - E911
89
Proposed Private Road
VTrans - E911
91
New - Class Unknown
VTrans - E911
92
Military - No Public Access
VTrans - E911
93
Public - Class Unknown
VTrans - E911
95
Class Under Review
VTrans - E911
96
Discontinued Road
VTrans - E911
97
Discontinued Road - Now Private
VTrans - E911
98
Not a Road
VTrans - E911
99
Unknown
VTrans - E911
1
99
NUTS
Sections 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
Y
The highway is "Not Up to Standard" (The highway does NOT meet Class 3 standards)
VTrans Mapping Section
N
The highway is not "Not Up to Standard" (The highway meets Class 3 or better standards)
VTrans Mapping Section
NHS
National 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 Road Centerline Spatial Data User Guide
0
Not on NHS
VTrans Road Centerline Spatial Data User Guide
1
NHS - Interstate
VTrans Road Centerline Spatial Data User Guide
2
ISTEA High Priority Corridor
VTrans Road Centerline Spatial Data User Guide
3
Non-Interstate STRAHNET
VTrans Road Centerline Spatial Data User Guide
4
STRAHNET Connector
VTrans Road Centerline Spatial Data User Guide
5
ISTEA High Priority Corridor/Non-Interstate STRAHNET
VTrans Road Centerline Spatial Data User Guide
6
ISTEA High Priority/STRAHNET Connector
VTrans Road Centerline Spatial Data User Guide
7
NHS - Principal Arterial
VTrans Road Centerline Spatial Data User Guide
8
NHS - Intermodal Connector
VTrans Road Centerline Spatial Data User Guide
10
NHS MAP-21 Principal Connector
VTrans Road Centerline Spatial Data User Guide
0
10
FUNCL
Functional 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
0
Not part of Functional Classification System
VTrans
1
Interstate
VTrans
2
Principal Arterial - Other Freeways and Expressways
VTrans
3
Principal Arterial - Other
VTrans
4
Minor Arterial
VTrans
5
Major Collector
VTrans
6
Minor Collector
VTrans
7
Local
VTrans
0
7
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
Unknown
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. Please refer to pages 21 and 22 of the VTrans Road Centerline Spatial Data User Guide for a more readable explanation of the codes used in this field. Route ID used to identify "routed" roads. Assigned by VTrans. The ETE_LR can be broken down into the following components (or redefined items): Route Type, Route Number, Route # Modifier, Direction, Subtype, Numeric, and Alpha ID. Route Type (ETE_LR_TYP): I = Interstate, U = U.S. route, V = VT signed route, S = State highway (named, special cases, other routed roads), A = Alternate route, B = Business route. Route Number (ETE_LR_NUM): The numeric portion of the highway number (3 digits), right justified in characters 2-4. For Named State Highways, Major Collectors and Urban Collectors, 4-digit codes are used (in characters 2 -5). Route # Modifier (ETE_LR_MOD): Used for a letter or special modifier, if needed. Named State Highways, Major Collectors and Urban Collectors retain their full, 4-digit codes in common usage. For these, the Highway Number and Modifier are combined to form a 4-digit highway number. For the three separate sections of Alternate U.S. 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 U.S. 5); digit for a Named State Highway, Major or Urban Collector ' ' = <blank>, if no modifier is needed and no subsequent components are needed for the ETE_LR - = <dash>, if no modifier is needed but other ETE_LR components follow. Direction (ETE_LR_DIR): The direction character is included only if the highway is divided. However, it is NOT used for North/East bound mainline routes. The Direction character is only used with North/East bound Approaches, Connectors, Jughandles, Ramps, and Spurs Valid direction characters include: ' ' = <blank>, if route is undivided and there are no subsequent ETE_LR_RTE components W = Westbound (for divided routes), S = Southbound (for divided routes), E = Eastbound (for divided routes), N = Northbound (for divided routes). Examples: ETE_LR End-to-End Route 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 (ETE_LR_SUBT): This field describes sections of road that are not on the main line yet have defined lengths recognized by the Agency. Valid codes include: ' ' = <blank>, no subtype, A = Approach, C = Connector, J = Jughandle, R = Ramp, S = Spur, F = Facility and Rest Areas, Turn Outs, Access Roads. Numeric ID (ETE_LR_NID): 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 (ETE_LR_AID): This letter identifies ramps and spurs, as taken from the route logs except for two ramps at I 91, 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: ETE_LR End-to-End Route U004 = US 4 Eastbound Divided Highway, U004-W = US 4 Westbound Divided Highway, V100-NA010 = VT 100 Approach #10, B004-WJ010 = Business Rt US4 Westbound Jughandle #10, I089-SR009A = I 89 Southbound Exit 9 Ramp
VTrans Road Centerline Spatial Data User Guide
A
Alternate route
VTrans Road Centerline Spatial Data User Guide
B
Business route
VTrans Road Centerline Spatial Data User Guide
I
Interstate
VTrans Road Centerline Spatial Data User Guide
N
Named State Highway
VTrans Road Centerline Spatial Data User Guide
S
Special Route: a town highway that is a major or minor collector, or is an urban route
VTrans Road Centerline Spatial Data User Guide
U
US Route
VTrans Road Centerline Spatial Data User Guide
V
Vermont Signed Route
VTrans Road Centerline Spatial Data User Guide
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). See Appendix C of the VTrans Road Centerline Spatial Data User Guide for the CTCODE list.
VTrans
0101
1424
UA
Trans 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'. See Appendix D the VTrans Road Centerline Spatial Data User Guide for the codes.
VTrans Road Centerline Spatial Data User Guide
0
3
CTUA
CTCODE with UA Code, unique to all towns and Urban Areas in Vermont.
VTrans
Minimum value 0101-0, maximum value 1424-1
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
Minimum value 0101-0, maximum value 1424-1
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
0.000387
6.895
AOTMILES
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
0
6.60
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
0
9.474
UPDACT
Used for flagging the type of update made to an arc.
VTrans
A
Added arc (i.e., a new arc)
VTrans Road Centerline Spatial Data User Guide
M
Moved arc
VTrans Road Centerline Spatial Data User Guide
S
Split arc
VTrans Road Centerline Spatial Data User Guide
U
Unsplit arc
VTrans Road Centerline Spatial Data User Guide
LOCMETH
Method 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
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.
VTrans Road Centerline Spatial Data User Guide
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.
VTrans Road Centerline Spatial Data User Guide
3
Not clearly visible on the ortho, location estimated from State Forest maps.
VTrans Road Centerline Spatial Data User Guide
4
No indication of the road on the orthophoto; apparently a new road built since the orthophoto was taken. Location estimated from VTrans maps.
VTrans Road Centerline Spatial Data User Guide
5
Road centerlines drafted onto orthophotos from engineering drawings and the like.
VTrans Road Centerline Spatial Data User Guide
6
Invisible on the orthophoto, but located based on town or other local knowledge of the area.
VTrans Road Centerline Spatial Data User Guide
7
Digitized centerline of the parcel (tax map) road right-of-way.
VTrans Road Centerline Spatial Data User Guide
8
Screen digitized from drafting by town officials onto maps of approximately 1:15,000 to 1:20,000 scale.
VTrans Road Centerline Spatial Data User Guide
9
Coordinates captured via a GPS device utilizing "dead reckoning" with typical horizontal accuracy within 5 meters.
VTrans Road Centerline Spatial Data User Guide
1
10
SRCORG
Organization/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 Road Centerline Spatial Data User Guide
1
VCGI, original data (assigned Sept 1993)
VTrans Road Centerline Spatial Data User Guide
2
VCGI, updated location
VTrans Road Centerline Spatial Data User Guide
10
Addison County RPC
VTrans Road Centerline Spatial Data User Guide
11
Bennington County RC
VTrans Road Centerline Spatial Data User Guide
12
Central VT RPC
VTrans Road Centerline Spatial Data User Guide
13
Chittenden County RPC
VTrans Road Centerline Spatial Data User Guide
14
Northwest RPC
VTrans Road Centerline Spatial Data User Guide
15
Lamoille County PC
VTrans Road Centerline Spatial Data User Guide
16
Northeast VT Development Assoc.
VTrans Road Centerline Spatial Data User Guide
17
Rutland RPC
VTrans Road Centerline Spatial Data User Guide
18
Southern Windsor RPC (or its contractor)
VTrans Road Centerline Spatial Data User Guide
19
Two Rivers-Ottauquechee RPC
VTrans Road Centerline Spatial Data User Guide
20
Upper Valley-Lake Sunapee RPC
VTrans Road Centerline Spatial Data User Guide
21
Windham RPC
VTrans Road Centerline Spatial Data User Guide
22
microData, incorporated by CVRPC
VTrans Road Centerline Spatial Data User Guide
24
E9-1-1 GIS database development project (1996)
VTrans Road Centerline Spatial Data User Guide
23
Incorporated from municipal updates
VTrans Road Centerline Spatial Data User Guide
25
IVS Highway Mapping System Project
VTrans Road Centerline Spatial Data User Guide
26
VTrans HMS updates
VTrans Road Centerline Spatial Data User Guide
SCENICHWY
Highways 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
VTrans Mapping Section
1
Designated as Scenic Highway by local municipality
VTrans Mapping Section
2
Designated as Scenic Highway by VTrans
VTrans Mapping Section
SCENICBYWAY
Designated Scenic Byways
VTrans Mapping Section
0
Not a scenic byway
VTrans Mapping Section
100
Connecticut River Scenic Byway
VTrans Mapping Section
200
Lake Champlain Byway
VTrans Mapping Section
300
Molly Stark Trail: A Byway Through the Green Mountains
VTrans Mapping Section
400
Mad River Byway
VTrans Mapping Section
500
Stone Valley Byway
VTrans Mapping Section
600
Green Mountain Byway
VTrans Mapping Section
700
The Crossroad of Vermont
VTrans Mapping Section
800
Scenic Route 100 Byway
VTrans Mapping Section
900
The Shires of Vermont Byway
VTrans Mapping Section
1000
Northeast Kingdom Byway
VTrans Mapping Section
0
1000
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
Unknown
PROVISIONALYEAR
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
0
9999
ANCIENTROADYEAR
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
Unknown
TRUCKROUTE
Designated 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 - Vermont State Statute
0
Not a truck route
VTrans Mapping Section
100
National Network - Limited Access (no overall length limit)
VTrans Mapping Section
200
Brattleboro VT-9 between I-91 and New Hampshire
VTrans Mapping Section
300
Truck Network, 72-foot limit (no permit)
VTrans Mapping Section
400
US-4, Permit Required
VTrans Mapping Section
500
Urban Avoidance Route, Part of Truck Network, 72-foot limit (no permit)
VTrans Mapping Section
600
Network – Limited Access (no overall length limit)
VTrans Mapping Section
0
600
SPEEDLIMIT
Speed Limit Currently a place holder for future use.
VTrans Mapping Section
0
65
ROADCLOSED
Road Closed Status. Currently a place holder for future use. Maintained by E911; incompletely populated in this release
E911
Closed
Closed
E911 - VTrans
Closed_AVO
Closed-Authorized Vehicles Only
E911 - VTrans
Closed_LTO
Closed-Local Traffic Only
E911 - VTrans
Closed_W
Closed-Winter
E911 - VTrans
Normal_SR
Normal Service Requested
E911 - VTrans
Open
Open
E911 - VTrans
Open_CD
Open with Construction Delays
E911 - VTrans
Open_R
Open with Restrictions
E911 - VTrans
ISVISIBLE
Flag used by the Highway Mapping Sytem for cartographic purposes.
VTrans Mapping Section
0
Not visible
VTrans Mapping Section
1
Visible
VTrans Mapping Section
0
1
CERTYEAR
Year an arc was altered due to a change reflected on the Certificate of Highway Mileage
Towns Highway Certificates, VTrans Mapping Section
0
9999
MAPYEAR
Not defined; maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
UPDATESOURCE
The source of the information used to update the road segment. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
UPDATEDATE
The year the feature was last updated. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
Unknown
GPSUPDATE
GPS update. Maintained by E911; incompletely populated in this release
E911
Unknown
GlobalID
Not defined in this release
VTrans Mapping Section
Globally Unique Identifier or GUID
STATE
State in which the road segment appears; maintained by E911; incompletely populated in this release
E911
Unknown
GAP
No definition included. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
1
GAPMILES
Not defined. Maintained by E911; incompletely populated in this release
E911 field - VTrans Mapping Section description
0
0.349
GAPSTREETID
Not defined and incompletely populated in this release
E911
0
54579
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 Town Highway Maps
50001005
50027120
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.
VTrans Mapping Section
0
925
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
0
99999999
RDFLNAME
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
Unknown
ISVISIBLE_UC
Flag used by the VTrans Highway Mapping System for cartographic purposes.
VTrans Mapping Section
0
Not visible
VTrans Mapping Section
1
Visible
VTrans Mapping Section
0
1
Shape
Feature geometry.
Esri
Coordinates defining the features.
FAID_N
This field will be removed in future releases. See FAID for more information.
VTrans Mapping Section
500010050001
500271200851
FUNCL_OLD
Old 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
0
Not part of Functional Classification System
VTrans
1
Principal Arterial - Interstate
VTrans
2
Rural, Principal Arterial
VTrans
4
Rural, Principal Arterial - Other (not other freeway); not a standard federal code
VTrans
6
Rural, Minor Arterial
VTrans
7
Rural, Major Collector
VTrans
8
Rural, Minor Collector
VTrans
9
Rural, Local
VTrans
11
Urban, Principal Arterial-Interstate
VTrans
12
Urban, Principal Arterial-Other Freeway
VTrans
14
Urban, Principal Arterial-Other
VTrans
16
Urban, Minor Arterial
VTrans
17
Urban Collector
VTrans
19
Urban Local
VTrans
Urban_Code
Census urban code
VTrans
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.
VTrans (Census, adjustments approved by FHWA)
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.
VTrans (Census, adjustments approved by FHWA)
99999
Rural areas; all areas outside the adjusted Urbanized Area and Small Urban Area boundaries, for transportation planning purposes.
VTrans (Census, adjustments approved by FHWA)
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
500010050001
500271200875
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.
VTrans Mapping Section
Facility_Type
Facility_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.
FHWA
2
Two-Way Roadway -- Roadway that operates with traffic moving in both directions during non-peak period hours.
FHWA
4
Ramp -- Non-mainline junction or connector facility contained within a grade-separated interchange.
FHWA
5
Non Mainline -- All non-mainline facilities excluding ramps.
FHWA
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.
FHWA
7
Planned/Unbuilt -- Planned roadway that has yet to be constructed.
FHWA
CREATIONUSER
Added November 18, 2016 as one of four fields to be used for editor tracking. This field records the ArcSDE geodatabase user name of the user who created the arc.
VTrans Road Centerline Spatial Data User Guide
Unknown
DATECREATED
Added November 18, 2016 as one of four fields to be used for editor tracking. This field records the date and time the arc was created. The time is recorded in the database’s local time zone (Eastern Time).
VTrans Road Centerline Spatial Data User Guide
Unknown
LASTUSER
Added November 18, 2016 as one of four fields to be used for editor tracking. This field records the ArcSDE geodatabase user name of the user who last modified the record in any way.
VTrans Road Centerline Spatial Data User Guide
Unknown
DATEMODIFIED
Added November 18, 2016 as one of four fields to be used for editor tracking. This field records the date and time the record was modified in any way. The time is recorded in the database’s local time zone (Eastern Time).
VTrans Road Centerline Spatial Data User Guide
Unknown
Shape.STLength()
Automatically calculated length measurement of the arc in meters.
VTrans Mapping Section
Unknown
The entity and attribute information provided here describes the tabular data associated with the data set. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the data set.
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 Center for Geographic Information
VCGI
Staff
mailing and physical
One National Life Drive
Davis Building, 6th Floor
Montpelier
Vermont
05620-0501
US
802-828-3211
802-828-3383
accd.vcgiinfo@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.
Vector Digital Data Set (Polyline)
http://maps.vcgi.org/gisdata/vtrans/packaged_zips/TransRoad_RDS.zip
No charge when downloading from the internet, and when no custom processing is required.
20161231
Vermont Agency of Transportation (VTrans)
Johnathan Croft
VTrans GIS Database Administrator
mailing and physical
One National Life Drive
Montpelier
Vermont
05633-5001
US
802-828-2600
802-828-2334
johnathan.croft@vermont.gov
8:00am - 4:30pm, Monday - Friday, Eastern Time
FGDC Content Standard for Digital Geospatial Metadata
FGDC-STD-001-1998
local time