TransRoad_RDS

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: GIS Database Administrator
Publication_Date: 20081021
Publication_Time: Unknown
Title: TransRoad_RDS
Edition: 2008B
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: Road centerlines from RF 5000 Orthophotos and GPS
Issue_Identification: 2008B
Publication_Information:
Publication_Place: Montpelier, VT 05633
Publisher: GIS Database Administrator
Other_Citation_Details: Tile Structure - STATE
Online_Linkage:
<http://www.vcgi.org/techres/white_papers/rdsfaq/VT_roadcenterline_FAQ.pdf>
Online_Linkage: <http://www.aot.state.vt.us/>
Online_Linkage: <http://www.vcgi.org/dataware/default.cfm?layer=TransRoad_RDS>
Online_Linkage:
<http://www.vcgi.org/dataware/default.cfm?layer=TransRoad_RDS&mapit=yes>
Online_Linkage:
<http://maps.vcgi.org:8080/wmsconnector/com.esri.wms.Esrimap?servicename=DATAWARE_VTRANS&VERSION=1.1.1&request=getmap&BBOX=-72.78108248505863,44.28374275027345,-72.7204763913086,44.360521719023424&SRS=EPSG:4326&LAYERS=TRANS_RDS_LINE&WIDTH=300&HEIGHT=400&FORMAT=image/gif>
Description:
Abstract:
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 VT Agency of Transportation (VTrans) is now considered the steward of this data layer.
Updates have been performed over the years by VCGI, RPCs, and VTrans. The VT Agency of Transportation has taken over the update and maintenance of the road centerline data layer and has revised the layer to match "Official" highway mileage.
NOTE: TransRoad_RDS meets the requirements articulated in the VGIS Road Centerline Data Standard (<http://www.vcgi.org/techres/standards/>). 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 is not may not match perfectly with the EmergencyE911_RDS data layer. The EmergencyE911_RDS road centerline layer maintained by VT's E911 Board as the most up-to-date roadname information. It was originally based on TransRoad_RDS, and is therefore very similar. However, it includes all private roads and generally more reliable road name and address range information. Refer to the VT Road Centerline Data FAQ for more information about TransRoad_RDS and EmergencyE911_RDS.
FAQ - <http://www.vcgi.org/techres/white_papers/rdsfaq/VT_roadcenterline_FAQ.pdf>
Purpose:
To provide high accuracy road centerlines and official road classification data for the state of Vermont.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20081021
Time_of_Day: unknown
Currentness_Reference: publication date
Status:
Progress: In work
Maintenance_and_Update_Frequency: Annually
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -73.444232
East_Bounding_Coordinate: -71.466427
North_Bounding_Coordinate: 45.018336
South_Bounding_Coordinate: 42.722817
Keywords:
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: transportation
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: roads
Theme_Keyword: transportation
Theme_Keyword: infrastructure
Theme_Keyword: road centerlines
Theme_Keyword: streets
Theme_Keyword: highways
Theme_Keyword: roads
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Vermont
Temporal:
Temporal_Keyword_Thesaurus: None
Temporal_Keyword: 2007
Access_Constraints:
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.
Use_Constraints:
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.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Johnathan Croft
Contact_Organization: Vermont Agency of Transportation (VTrans) - Mapping Unit
Contact_Position: VTrans GIS Database Administrator
Contact_Address:
Address_Type: mailing and physical address
Address: VTrans - Policy & Planning Division
Address: One National Life Drive
City: Montpelier
State_or_Province: VT
Postal_Code: 05633-5001
Country: USA
Contact_Voice_Telephone: 802/828-2600
Contact_TDD/TTY_Telephone: None
Contact_Facsimile_Telephone: 802/828-2334
Contact_Electronic_Mail_Address: johnathan.croft@state.vt.us
Hours_of_Service: 8:00am - 4:30pm, M-F
Browse_Graphic:
Browse_Graphic_File_Name:
<http://maps.vcgi.org:8080/wmsconnector/com.esri.wms.Esrimap?servicename=DATAWARE_VTRANS&VERSION=1.1.0&request=getmap&BBOX=-72.78108248505863,44.28374275027345,-72.7204763913086,44.360521719023424&SRS=EPSG:4326&LAYERS=TRANS_RDS_LINE&WIDTH=300&HEIGHT=400&FORMAT=image/gif>
Browse_Graphic_File_Description: GIF
Browse_Graphic_File_Type: GIF
Data_Set_Credit: GIS Database Administrator
Security_Information:
Security_Classification_System: N/A
Security_Classification: Unclassified
Security_Handling_Description: No security considerations
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.780
Cross_Reference:
Citation_Information:
Originator: VTrans GIS Database Administrator
Publication_Date: 20081021
Publication_Time: Unknown
Title: VTrans "official" Town Highway Maps
Edition: 2008
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: Town Highway Maps
Issue_Identification: 2008
Publication_Information:
Publication_Place: Montpelier, VT 05633-5001
Publisher: VTrans GIS Database Administrator
Other_Citation_Details:
TransRoad_RDS is maintained by VTrans using the Town Highway Maping System (HMS)
Online_Linkage: <http://www.aot.state.vt.us/planning/MapGIS/Town_Maps1.htm>
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
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 RPCs. 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 attribution are reviewed and corrected, The data is reviewed and checked with multiple processes, but there may be errors that have yet to be 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.
Logical_Consistency_Report:
Subsequent to the original digitizing, RPCs/VCGI/VTrans has 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.
Completeness_Report:
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 VT Agency of Transportation (VTrans). The TransRoad_RDS data layer contains the spatial representation of the 15,500 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 define in the "VGIS Road Centerline Spatial Data Standards" (<http://www.vcgi.org/techres/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 Unit 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 is considerably better and continues to improve.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
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 Commission's 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. Please contact VTrans for a list of towns completed to date.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: 6 map units
Horizontal_Positional_Accuracy_Explanation: Overall accuracy estimation
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: VT Agency of Transportation
Publication_Date: 20081021
Publication_Time: Unknown
Title: Official Trans Town Highway Maps and VT 1:5000 orthophotos
Edition: 2008B
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: VTrans Highway maps and VT orthophotos
Issue_Identification: 2008B
Publication_Information:
Publication_Place: Montpelier, VT
Publisher: VTrans
Other_Citation_Details:
Town Highways Maps are produced based on the changes supplied by towns on the Mileage Certificates that are filed on or before February 10th of each year. The Maps show the highway network as of that date.
Online_Linkage: <http://www.aot.state.vt.us/planning/MapGIS/Town_Maps1.htm>
Source_Scale_Denominator: 5000
Type_of_Source_Media: analog and digital
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 19740000
Beginning_Time: unknown
Ending_Date: 20080000
Ending_Time: unknown
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: VTrans
Source_Contribution: VTrans
Process_Step:
Process_Description:
Original documentation completed. Operator - Steve Bower (VCGI)
Process_Date: 19920212
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 19920826
Process_Time: Unknown
Process_Step:
Process_Description:
Completion of roads corrections by VCGI staff for all tiles not previously available. Operator - Nate Dansereau (VCGI)
Process_Date: 19920916
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 19940119
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 19960202
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 19961212
Process_Time: Unknown
Process_Step:
Process_Description:
Data updated by VTrans contractor (Information Visualization Services, South Burlington, VT). Included spatial and attribute updates. Operator - Steve Sharp (VCGI)
Process_Date: 19970901
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 20001201
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 20010416
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 20010503
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 20011101
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 20021106
Process_Time: Unknown
Process_Step:
Process_Description:
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)
Process_Date: 20040830
Process_Time: Unknown
Process_Step:
Process_Description:
Preliminary cut of 2005 road centerline updates (HMS updates) sent to VCGI as 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)
Process_Date: 20051025
Process_Time: Unknown
Process_Step:
Process_Description:
Final 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.
Process_Date: 20071015
Process_Time: Unknown
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Johnathan Croft, Sara Moulton, and VTrans Mapping Unit Staff
Process_Step:
Process_Description:
VCGI downloaded a copy of VTrans 2007 road centerline data from their FTP site. The data has NOT been QA/QC by VCGI. Data has been integrated into the VGIS Data Warehouse for distribution.
Process_Date: 20071109
Process_Time: Unknown
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Steve Sharp
Contact_Organization: VCGI
Contact_Position: GIS Database Administrator
Process_Step:
Process_Description:
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.
Process_Date: 20081021
Process_Time: Unknown
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Johnathan Croft, Sara Moulton, and Michael Trunzo
Contact_Organization: VTrans Mapping Unit
Process_Step:
Process_Description:
VCGI downloaded a copy of VTrans 2008 road centerline data from their FTP site. The data has NOT been QA/QC by VCGI. Data has been integrated into the VGIS Data Warehouse for distribution. 2008A release.
Process_Date: 20080703
Process_Time: Unknown
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Steve Sharp
Contact_Organization: VCGI
Contact_Position: GIS Database Administrator
Process_Step:
Process_Description:
VCGI downloaded a revised version of VTrans' 2008 road centerline data from their FTP site. The data has NOT been QA/QC by VCGI. Data has been integrated into the VGIS Data Warehouse for distribution. 2008B release.
Process_Date: 20081106
Process_Time: Unknown
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Steve Sharp
Contact_Organization: VCGI
Contact_Position: GIS Database Administrator
Spatial_Data_Organization_Information:
Indirect_Spatial_Reference: Line
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 77001
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name: State Plane Coordinate System 1983
State_Plane_Coordinate_System:
SPCS_Zone_Identifier: 4400
Transverse_Mercator:
Scale_Factor_at_Central_Meridian: 0.999964
Longitude_of_Central_Meridian: -72.500000
Latitude_of_Projection_Origin: 42.500000
False_Easting: 500000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.010000
Ordinate_Resolution: 0.010000
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: Trans_RDS_line
Entity_Type_Definition: 1-D Linear representation
Entity_Type_Definition_Source: VTrans
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: RTNAME
Attribute_Definition:
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 LR_ETE. The RDNAME field refers to the roads common name (via a relate to the RDS.RDNAMES table). 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 23 (which is "Main Street" in the RDS.RDNAMES table). However, the same road could also be classified as "Vermont Route 100" (VT-100). In this case, the LR_ETE field would be populated with "V100". The ALTNAME field in the RDS.RDNAMES table could also be used to store this information. Note: Many cities and villages have named streets with no route numbers (mostly paved). There will be no entry for their route numbers even though they are official public roads. See AOTCLASS=93.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: I
Enumerated_Domain_Value_Definition: Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BR I-
Enumerated_Domain_Value_Definition: Interstate Business Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BSp I-
Enumerated_Domain_Value_Definition: Interstate Business Spur
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: US-
Enumerated_Domain_Value_Definition: U.S. route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Alt US-
Enumerated_Domain_Value_Definition: U.S. Alternate Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BR US-
Enumerated_Domain_Value_Definition: U.S. Business Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BSp US-
Enumerated_Domain_Value_Definition: U.S. Business Spur
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Old US-
Enumerated_Domain_Value_Definition: Old U.S. Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Hist US-
Enumerated_Domain_Value_Definition: Historic U.S. Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: VT-
Enumerated_Domain_Value_Definition: Vermont Numbered Route - Old Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Old VT-
Enumerated_Domain_Value_Definition: Vermont Numbered Route - Old Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Hist VT-
Enumerated_Domain_Value_Definition: Vermont Numbered Route - Historic Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TH-
Enumerated_Domain_Value_Definition: Town Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NSH-
Enumerated_Domain_Value_Definition: Named State Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: S-
Enumerated_Domain_Value_Definition: Other State Highway special cases
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: SF-
Enumerated_Domain_Value_Definition: Dept of Forest, Parks and Recreation Highway
Enumerated_Domain_Value_Definition_Source: Typically shown as SFH in the road centerline data.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NF-
Enumerated_Domain_Value_Definition: National Forest Highway
Enumerated_Domain_Value_Definition_Source: Typically shown as NFR in the road centerline data.
Attribute:
Attribute_Label: RTNO
Attribute_Definition:
Once updates are made to the RDS data layer, "post processing" routines are used to populate this field from the RTNAME field. Everything after the dash "-" in the RTNAME field is transferred to this field. This field is NEVER updated directly. It should always match RTNAME.
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Route Number
Codeset_Source: *Generated from RTNAME (includes everything after the "-")
Attribute:
Attribute_Label: HWYSIGN
Attribute_Definition:
The 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.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: I
Enumerated_Domain_Value_Definition: Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BR I-
Enumerated_Domain_Value_Definition: Interstate Business Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BSp I-
Enumerated_Domain_Value_Definition: Interstate Business Spur
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: US-
Enumerated_Domain_Value_Definition: U.S. route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Alt US-
Enumerated_Domain_Value_Definition: U.S. Alternate Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BR US-
Enumerated_Domain_Value_Definition: U.S. Business Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BSp US-
Enumerated_Domain_Value_Definition: U.S. Business Spur
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Old US-
Enumerated_Domain_Value_Definition: Old U.S. Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Hist US-
Enumerated_Domain_Value_Definition: Historic U.S. Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: VT-
Enumerated_Domain_Value_Definition: Vermont Numbered Route - Old Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Old VT-
Enumerated_Domain_Value_Definition: Vermont Numbered Route - Old Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Hist VT-
Enumerated_Domain_Value_Definition: Vermont Numbered Route - Historic Route
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TH-
Enumerated_Domain_Value_Definition: Town Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NSH-
Enumerated_Domain_Value_Definition: Named State Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: S-
Enumerated_Domain_Value_Definition: Other State Highway special cases
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: SF-
Enumerated_Domain_Value_Definition: Dept of Forest, Parks and Recreation Highway
Enumerated_Domain_Value_Definition_Source: Typically shown as SFH in the road centerline data.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NF-
Enumerated_Domain_Value_Definition: National Forest Highway
Enumerated_Domain_Value_Definition_Source: Typically shown as NFR in the road centerline data.
Attribute:
Attribute_Label: RPCCLASS
Attribute_Definition:
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 RPCCLASSes 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 will not be maintained in the roads data layer. RPCCLASS will be reset to equal AOTCLASS whenever AOTCLASS is updated. Two attributes for road class are therefore used: the RPCCLASS code can be modified as needed for regional/local mapping, while the AOTCLASS code maintains agreement with the VTrans town highway maps. Comparison of the RPCCLASS and AOTCLASS attributes will help to identify roads needing class updates by the 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 needed for state routes and class 1 and 2 town highways, as well as for interstates and US routes.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1-4
Enumerated_Domain_Value_Definition: Class 1-4 town highway, undivided (see 11-19, 21-29)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition: State forest highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition: National forest highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 7
Enumerated_Domain_Value_Definition: Legal trail
Enumerated_Domain_Value_Definition_Source:
Legal Trail Mileage Approved by Selectboard after the enactment of Act 178 (July 1, 2006)
Due to the introduction of Act 178, the Mapping Unit needed to differentiate between officially accepted and designated legal trail versus trails that had traditionally been shown on the maps. Towns have until 2015 to map all Class 1-4 and Legal Trails, based on new changes in VSA Title 19.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 8
Enumerated_Domain_Value_Definition:
Private road, but not for display on local maps. Some municipalities may prefer not to show certain private roads on their maps, but the roads may need to be maintained in the data for emergency response or other purposes.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 9
Enumerated_Domain_Value_Definition: Private road, for display on local maps
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 10
Enumerated_Domain_Value_Definition: Not used; use RPCCLASS = 1 for undivided Class 1 Town Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 11
Enumerated_Domain_Value_Definition: North bound (for divided centerlines)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 12
Enumerated_Domain_Value_Definition: South bound
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 13
Enumerated_Domain_Value_Definition: East bound
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 14
Enumerated_Domain_Value_Definition: West bound
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 15
Enumerated_Domain_Value_Definition: Entrance/Exit ramp, Approach, Jughandle
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 16
Enumerated_Domain_Value_Definition: Emergency U-turn
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 17
Enumerated_Domain_Value_Definition: Rest area
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 19
Enumerated_Domain_Value_Definition:
Other Class 1 Town Highway (weigh stations, maintenance areas, etc.)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 20
Enumerated_Domain_Value_Definition: Not used; use RPCCLASS = 2 for undivided Class 2 Town Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 21-29
Enumerated_Domain_Value_Definition: Class 2 Town Highway; same road types as for 11-19
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 30
Enumerated_Domain_Value_Definition:
Vermont State Highway, undivided centerline (most Vermont Highways)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 31-39
Enumerated_Domain_Value_Definition: Vermont State Highway; same road types as for 11-19
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 40
Enumerated_Domain_Value_Definition: US Highway, undivided centerline (most US Highways)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 41-49
Enumerated_Domain_Value_Definition: US Highway; same road types as for 11-19
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 50
Enumerated_Domain_Value_Definition: Interstate, undivided centerline (not currently used)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 51-59
Enumerated_Domain_Value_Definition: Interstate, same road types as for 11-19
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 81-83
Enumerated_Domain_Value_Definition: Proposed Class 1-3 Town Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 84
Enumerated_Domain_Value_Definition: Proposed State Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 85
Enumerated_Domain_Value_Definition: Proposed US Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 86
Enumerated_Domain_Value_Definition: Proposed Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 87
Enumerated_Domain_Value_Definition: Proposed ramp: Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 88
Enumerated_Domain_Value_Definition: Proposed ramp: non-Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 89
Enumerated_Domain_Value_Definition: Proposed private road
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 91
Enumerated_Domain_Value_Definition:
Driveway (not used) - driveways maintained as separate data layer DW
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 92
Enumerated_Domain_Value_Definition: Military road, no public access
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 93
Enumerated_Domain_Value_Definition:
Public road from VTrans map, for which the class could not be determined. Most of these are named streets in urban areas, which are mostly class 3. From the original road centerline data, any road with CLASS = 99 (unknown) but with a known SURFACE type was assigned RPCCLASS = 93
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 95
Enumerated_Domain_Value_Definition: Road class under special review, usually temporary
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 96
Enumerated_Domain_Value_Definition: Discontinued
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 97
Enumerated_Domain_Value_Definition: Not used (to avoid confusion with AOTCLASS = 97)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 98
Enumerated_Domain_Value_Definition:
Not considered a road based on local/regional review, but maintained in the data because it is on the VTrans town highway map
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 99
Enumerated_Domain_Value_Definition:
Unknown class (assumed private, but not originally coded as private) Class 4 roads on the VTrans maps include provisional class 4 roads. These are legally class 3, but have a class 4 level of service. They are shown as class 4 because the VTrans does not provide state aid for them.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 70
Enumerated_Domain_Value_Definition: Legal Trail - not yet approved
Enumerated_Domain_Value_Definition_Source:
Legal Trails not yet approved by Selectboard after the enactment of Act 178 (July 1, 2006)
Due to the introduction of Act 178, the Mapping Unit needed to differentiate between officially accepted and designated legal trails.
Trails in this category have been traditionally mapped by VTrans as legal trails, but have not been formally added to the Mileage Certificates by Towns. Under Act 178, Towns have until July 1, 2015 to do this.
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: RPCCLASS
Attribute_Value_Accuracy_Explanation:
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 CLASSes based on local and/or regional review; therefore, in some cases the RPCCLASS values may not agree with with current VTrans highway maps. Two attributes for road class are therfore used.. The RPCCLASS code can be modified as needed for regional/local mapping, while the AOTCLASS code maintains agreement with the VTrans town highway maps. Comparison of the RPCCLASS and AOTCLASS attributes will help to identify roads needing class updates by the 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 imbed the 'type' information in the CLASS 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 U.S. routes. Class 4 roads on the VTrans maps include provisional class 4 roads. These are legally Class 3, but are functionally Class 4 town highways. VTrans has withdrawn State Aid funds for these sections of downgraded sections. Municipalites have been notified of the situation and requested to upgrade or reclassify the sections.
Attribute:
Attribute_Label: AOTCLASS
Attribute_Definition:
This item will hold the official VTrans road class from the VTrans highway maps. See the discussion for item RPCCLASS. All arcs must be assigned RPCCLASS an AOTCLASS codes. AOTCLASS uses the same codes as the RPCCLASS item, except for code 98 (used only as a RPCCLASS code, for roads not shown on the VTrans highway maps). One additional AOTCLASS code is used: 97 Non-private road added based on local/regional review, but not yet shown on the VTrans town highway maps. For example, if an RPC adds a class 3 town highway that is not shown on the current VTrans town highway map, then the new road would be assigned RPCCLASS = 3 and AOTCLASS = 97. This attribute only applies to public roads, as the VTrans does not intend to show private roads on future VTrans highway maps. Any updates to the roads data should be made using current VTrans highway maps. The roads for each town are inventoried by the VTrans approximately every 10 years. Updates of official VTrans highway maps are made with each town's road inventory, or whenever the VTrans receives notification of changes to road classifications (local or state roads).
Attribute_Definition_Source: VGIS Road Centerline Data Standards
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: AOTCLASS
Attribute_Value_Accuracy_Explanation:
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 can not alter classification without justification. Act 178 of 2006 formally added Class 4 and Legal Trail mileage to the Mileage Certificates, prompting the need to distinquish 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.
Attribute:
Attribute_Label: FUNCL
Attribute_Definition:
Functional Class Code. Functional classification codes 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.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 0
Enumerated_Domain_Value_Definition: Not part of Functional Classification System
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: Rural, Principal Arterial - Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition: Rural, Principal Arterial
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 4
Enumerated_Domain_Value_Definition:
Rural, Principal Arterial - Other (not other freeway); not a standard federal code
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition: Rural, Minor Arterial
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 7
Enumerated_Domain_Value_Definition: Rural, Major Collector
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 8
Enumerated_Domain_Value_Definition: Rural, Minor Collector
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 9
Enumerated_Domain_Value_Definition: Rural, Local
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 11
Enumerated_Domain_Value_Definition: Urban, Principal Arterial-Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 12
Enumerated_Domain_Value_Definition: Urban, Principal Arterial-Other Freeway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 14
Enumerated_Domain_Value_Definition: Urban, Principal Arterial-Other
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 16
Enumerated_Domain_Value_Definition: Urban, Minor Arterial
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 17
Enumerated_Domain_Value_Definition: Urban Collector
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 19
Enumerated_Domain_Value_Definition: Urban Local
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: Functional Class Code
Attribute_Value_Accuracy_Explanation:
All efforts are being made to revised and correct any Functional Class Codes in the TransRoad_RDS data layer. Information from the VTrans Highway Research Unit is being incorporated into this dataset and being thoroughly checked. There have been several new additions and alterations that have been made to the functionally classed highways that are not reflected in the last series of Federal Urban Area Maps or the Functional Class Map of the State of Vermont. These maps will be updated using this Road Centerline data.
Attribute:
Attribute_Label: NHS
Attribute_Definition: National Highway System designation as defined by FHWA.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 0
Enumerated_Domain_Value_Definition: Not on NHS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition: ISTEA High Priority Corridor
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 3
Enumerated_Domain_Value_Definition: Non-Interstate STRAHNET
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 4
Enumerated_Domain_Value_Definition: STRAHNET Connector
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition: ISTEA High Priority Corridor/Non-Interstate STRAHNET
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition: ISTEA High Priority/STRAHNET Connector
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 7
Enumerated_Domain_Value_Definition: Other NHS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 8
Enumerated_Domain_Value_Definition: Intermodal Connector
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: NHS
Attribute_Value_Accuracy_Explanation:
The NHS code is newly added to the data. The RDS Standard does not contain documentation pertaining to the Intermodal Connector which 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.
Attribute:
Attribute_Label: SCENIC
Attribute_Definition:
Highways officially designated as "Scenic Highways" by VTrans or municipalities. The ability to designate a Scenic Highway is defined in Vermont Statute and documented on the Mileage Certificates. The VTrans Mapping & GIS Unit maintains the official listing of Scenic Highways within the State of Vermont.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 0
Enumerated_Domain_Value_Definition: Not designated as Scenic Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: Designated as Scenic Highway by local municipality
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition: Designated as Scenic Highway by VTrans
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: SCENIC
Attribute_Value_Accuracy_Explanation:
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.
Attribute:
Attribute_Label: SURFACE
Attribute_Definition:
Road surface type. Roads surface types are generally based on VTrans Town Highway Maps, or on regional/local review.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: Hard surface (pavement)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition: Gravel
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 3
Enumerated_Domain_Value_Definition: Soil or graded and drained earth
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition: Unimproved/Primitive
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition: Impassable or untravelled
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 9
Enumerated_Domain_Value_Definition: Unknown surface type
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: SURFACE
Attribute_Value_Accuracy_Explanation:
Roads surface types are generally based on VTrans Town Highway Maps, or on regional/local review. Little or no photo interpretation was done, but road shapes and distances were originally used to assign SURFACE codes. Some regional and local knowledge has been used to update SURFACE codes in updated datasets (see the updates listing). Legal trails and discontinued roads were all originally assigned SURFACE equals 9 (unknown). The surface types of some very short roads could not be determined from the VTrans maps, especially differentiating between gravel (2) and soil (3). Surface types for these arcs were coded 'unknown' (9), or a best judgement was made. The Town Highway Maps are being generated from the TransRoad_RDS data and require public highways to have surface code other than 9. The QA/QC process flags highways that don't comform and are corrected.
Attribute:
Attribute_Label: LR_ETE
Attribute_Definition:
Route ID used to identify "routed" roads. This item contains an "End-to-End" LRS identifier used to identify routed roads. The LR_ETE can be broken down into LR_ETE_TYPE, LR_ETE_NUM, LR_ETE_MOD, LR_ETE_DIR, LR_ETE_SUBT, LR_ETE_NID, LR_ETE_AID. Refer to the definintions outlined in the listings for the redefined items below.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: LR_ETE_TYP
Attribute_Definition: ETE ID type prefix
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: I
Enumerated_Domain_Value_Definition: Interstate
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: U
Enumerated_Domain_Value_Definition: US Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: V
Enumerated_Domain_Value_Definition: Vermont State Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: S
Enumerated_Domain_Value_Definition: State Named Highway
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: O
Enumerated_Domain_Value_Definition:
Other including Major Collectors, Minor Collectors, Urban routes
Attribute:
Attribute_Label: LR_ETE_NUM
Attribute_Definition: ETE ID Number
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 999
Attribute:
Attribute_Label: LR_ETE_MOD
Attribute_Definition: ETE ID Modifier
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Unrepresentable_Domain: Modifier can be a number or character (ex: B in V100B).
Attribute:
Attribute_Label: LR_ETE_DIR
Attribute_Definition: ETE ID direction specifier
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: N
Enumerated_Domain_Value_Definition: North
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: S
Enumerated_Domain_Value_Definition: South
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: E
Enumerated_Domain_Value_Definition: East
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: W
Enumerated_Domain_Value_Definition: West
Attribute:
Attribute_Label: LR_ETE_SUBT
Attribute_Definition: ETE ID Subtype
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: A
Enumerated_Domain_Value_Definition: Approach
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: C
Enumerated_Domain_Value_Definition: Connector
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: J
Enumerated_Domain_Value_Definition: Jughandle
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: R
Enumerated_Domain_Value_Definition: Ramp
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: S
Enumerated_Domain_Value_Definition: Spur
Attribute:
Attribute_Label: LR_ETE_NID
Attribute_Definition: ETE ID numeric ID
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 999
Attribute:
Attribute_Label: LR_ETE_AID
Attribute_Definition: ETE ID alpha ID
Attribute_Definition_Source: VTrans
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: A
Range_Domain_Maximum: Z
Attribute_Domain_Values:
Unrepresentable_Domain: Identifies ramps and spurs by a character letter.
Attribute:
Attribute_Label: CTCODE
Attribute_Definition:
County-Town code based on values defined by the Vermont Agency of Transportation, VTrans. The CTCODE is comprised of the first 2 digits being the County and the last 2 digits define the Town. 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. This field is generated by relating FIPS8 to a lookup table containing CTCODE values within the Highway Mapping System. The county-town code identifies the municipality in which each road falls. This field is NEVER updated directly. Post-processing routines will populate this field via the FIPS8 attribute. The CTCODE is evident on reference markers in the field, which include the CTCODE, route identifier and milemarker.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: CTCODE
Attribute_Value_Accuracy_Explanation:
The CTCODE is as accurate as the FIPS6 code for an arc. The FIPS code is used to link to a join table containing FIPS6 and CTCODE. The FIPS is auto defined based on the municipality being editted within the Highway Mapping System, the CTCODE is then autoloaded into the AAT file for each corresponding record. These values should be accurate and consistent for each municipality.
Attribute:
Attribute_Label: FAID_S
Attribute_Definition:
Similar to FAID, but without a space leading ARCID. This value is an all numeric value of FIPS8 with ARCID concatenated.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: UA
Attribute_Definition:
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 1-digit code is used in conjunction with the FIPS8 code to uniquely identify each urban area. Please refer to page 22 and 23 of the VGIS Road Centerline Data Standard for the codes. It should be noted that several villages have been merged with towns and the villages no longer exist. For mapping purposes, these villages may have become "urban compacts."
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Urban Area
Codeset_Source: Municipal boundaries and VTrans highway maps
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: UA
Attribute_Value_Accuracy_Explanation:
Currently the UA code has not been fully populated within the TransRoad_RDS data layer. As VTrans prepares a Town Highway Map for production, the UA codes are reviewed and corrected. Currently, only UA's have been updated for those towns with revised Town Highways from 2005 to the present. VTrans is moving forward with the update and correction of the UA codes. It should be noted that the remainder of Urban Compacts and Villages that have specific highway maps will require review and revision, this may require arcs to be split a the Urban Compact boundary to allow for proper mileage summaries.
Attribute:
Attribute_Label: RDNAME
Attribute_Definition:
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 used in the road centerline attribute table (RDS.AAT). Each named road will have a unique RDNAME value. Users should generally turn to the E911\RDS data layer when they need "official" road name information. During the spring of 2007, VTrans ran an assessment between the E911 RDS and the TransRoad_RDS and identified roads with different RDNAME values. These values were updated in the TransRoad_RDS data layer. There is still work to be done, but the RDNAME should better match the "official" values stored by E911.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: RDNAME
Enumerated_Domain_Value_Definition: Road Name Code
Enumerated_Domain_Value_Definition_Source: Region/Local
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: RDNAME
Attribute_Value_Accuracy_Explanation:
VTrans has evaluated and updated the RDNAME field with the RDNAME from the E911 RDS data layer. During 2006 or early 2007, E911 changed the numbering schema for the RDNAME. The TransRoad_RDS data layer was updated to match the current schema. 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.
Attribute:
Attribute_Label: RDFLNAME
Attribute_Definition:
Full road name This field contains the complete road name as defined in the NAME field of the RDS.RDNAMES table. This field is populated by relating the the RDS.RDNAMES field using RDNAME as the relate/link field. This field should NEVER be updated directly. Post-processing routines will create and update this field. 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.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: RDFLNAME
Enumerated_Domain_Value_Definition: Full Road Name
Enumerated_Domain_Value_Definition_Source: Generated from the NAME field in the RDS.RDNAMES table.
Attribute:
Attribute_Label: AOTMILES_CALC
Attribute_Definition:
Field used in the process of prorating AOTMILES, not for use outside of the Highway Mapping System
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: NUTS
Attribute_Definition:
Sections of highway deemed "Not Up To Standard", in short, sections of highway that do not meet Class 3 Standard at the time of inventory and are functionally classified as Class 4, but legally still Class 3. Contact VTrans for more information.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: NEARDIST
Attribute:
Attribute_Label: AOTSURFCL
Attribute_Definition: Used by the former HMS and no longer being updated.
Attribute:
Attribute_Label: LOCMETH
Attribute_Definition: Method used to locate/digitize the road segment (arc)
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition:
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 attribute.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition:
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 VTrans maps, adjoining roads and land features.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 3
Enumerated_Domain_Value_Definition:
Not clearly visible on the ortho, location estimated from State Forest maps.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 4
Enumerated_Domain_Value_Definition:
No indication of the road on the orthophoto; apparently a new road built since the orthophoto was taken. Location estimated from VTrans maps.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition:
Road centerlines drafted onto orthophotos from engineering drawings and the like.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition:
Invisible on the orthophoto, but located based on town or other local knowledge of the area.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 7
Enumerated_Domain_Value_Definition: Digitized centerline of the parcel (tax map) road right-of-way.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 8
Enumerated_Domain_Value_Definition:
Screen digitized from drafting by town officials onto maps of approximately 1:15,000 to 1:20,000 scale.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 9
Enumerated_Domain_Value_Definition:
Coordinates captured via a GPS device utilizing "dead reckoning" with typical horizontal accuracy within 5 meters
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: Line Accuracy Code
Attribute_Value_Accuracy_Explanation:
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 RDSACC 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 RDSACC 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 orthos may be moved to match the digital orthos. 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.
Attribute:
Attribute_Label: SRCORG
Attribute_Definition:
Organization/project which created/updated the road segement (arc). This attribute identifies the organization or project which digitized the 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".
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: VCGI, original data (assigned Sept 1993)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition: VCGI, updated location
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 10
Enumerated_Domain_Value_Definition: Addison County RPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 11
Enumerated_Domain_Value_Definition: Bennington County RC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 12
Enumerated_Domain_Value_Definition: Central VT RPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 13
Enumerated_Domain_Value_Definition: Chittenden County RPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 14
Enumerated_Domain_Value_Definition: Northwest RPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 15
Enumerated_Domain_Value_Definition: Lamoille County PC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 16
Enumerated_Domain_Value_Definition: Northeast VT Development Assoc.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 17
Enumerated_Domain_Value_Definition: Rutland RPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 18
Enumerated_Domain_Value_Definition: Southern Windsor RPC (or its contractor)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 19
Enumerated_Domain_Value_Definition: Two Rivers-Ottauquechee RPDC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 20
Enumerated_Domain_Value_Definition: Upper Valley-Lake Sunapee RPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 21
Enumerated_Domain_Value_Definition: Windham RPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 22
Enumerated_Domain_Value_Definition: microData, incorporated by CVRPC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 23
Enumerated_Domain_Value_Definition: Incorporated from municipal updates
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 24
Enumerated_Domain_Value_Definition: E9-1-1 GIS database development project (1996)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 25
Enumerated_Domain_Value_Definition: IVS Highway Mapping System Project
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 26
Enumerated_Domain_Value_Definition: VTrans HMS updates
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: Road Source
Attribute_Value_Accuracy_Explanation:
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.
Attribute:
Attribute_Label: FIPS8
Attribute_Definition:
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 (ex: 50 for Vermont) + FIPS6. Some short road sections in the data fall outside of Vermont. These are assigned the FIPS8 code of the associated town with the state FIPS code of the adjoining state. Therefore, a FIPS8 of 90027115 indicates an arc in New Hampshire associated with the town of Windsor (50027115).
Attribute_Definition_Source: VTrans Town Highway Maps
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: FIPS
Enumerated_Domain_Value_Definition: Federal Information Processing Standard
Enumerated_Domain_Value_Definition_Source: Federal Government
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: FIPS Code
Attribute_Value_Accuracy_Explanation:
FIPS6 codes were assigned by an overlay of the roads data with the BoundaryTown_TBHASH town boundaries layer [rev. 12/16/93]. BoundaryTown_TBHASH was developed with 'Best Available' town boundaries for this purpose (THBASH was archived on 7/2003 and replaced by BNDHASH). After the overlay, manual edits were made along with all town boundaries to assure agreement with VTrans highway maps. Therefore, the assigned FIPS6 codes did not always agree with the BoundaryTown_TBHASH boundaries, particularly where intersections or bends in the roads close to the town boundaries allowed for improved assignment of town codes based on the VTrans maps. However, most roads which had the same attributes on both sides of a town boundary will have had the FIPS6 code assigned as in BoundaryTown_TBHASH [including virtually all Interstate, US, and VT roads].
As noted, TBHASH was archived in 2003 and replaced by BNDHASH. However, the town boundaries reflected in BNDHASH's REGION.TOWNS subclass do not necessarily match the RDS layer as noted with TBHASH. VTrans makes adjustments to the FIPS6 coding based on the best available information at its disposal. VTrans maintains its own version of TBHASH/BNDHASH called TB_. TB_ has not been synchronized with BNDHASH as of 7/2003.
Attribute:
Attribute_Label: ARCID
Attribute_Definition:
Arc identifier, unique by town, city, grant, or gore. The ARCID is a unique arc identifier within each municipality (town, city, grant or gore). When combined with the FIPS8 codes, this provides a unique arc identifier statewide. A redefined item, FAID contains both FIPS8 and ARCID within the ArcInfo dataset.
Attribute_Definition_Source: VCGI
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: ARCID
Codeset_Source: VCGI, VTrans and data developers
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: ARCID
Attribute_Value_Accuracy_Explanation:
The ARCID is a unique arc identifier within each municipality (town, city, grant ,gore). When combined with the FIPS6 and UA codes, this provides a unique arc identifier statewide. The ARCID can be used for error reporting, and is used to aid in quality control of updated data. The ARCID for an arc should only be changed if the arc is moved or reshaped. Any new arcs must be assigned ARCIDs unique to their towns. If an arc is split, unique ARCIDs are assigned to the two new arcs (one ARCID can be the same as the original arc). In summary, any data updates must maintain unique ARCIDs within each municipality. Refer to the VGIS Handbook: "Road Centerline Spatial Data Standard for more information."
Attribute:
Attribute_Label: UPDACT
Attribute_Definition:
Used for flagging the type of update made to an arc. Updated data sets received by VCGI are compared against the original data set provided to the data developer, and a record of changes made to the data will be generated. To enable this process, data developers must record any changes made to the arc topology.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: A
Enumerated_Domain_Value_Definition: Added arc (i.e., a new arc)
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: M
Enumerated_Domain_Value_Definition:
Moved arc (by reshaping the arc, moving a node, moving or deleting a vertex, or
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: S
Enumerated_Domain_Value_Definition: Split arc (both new arcs are coded 'S')
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: U
Enumerated_Domain_Value_Definition: Unsplit arc (originally 2 arcs)
Attribute:
Attribute_Label: ARCMILES
Attribute_Definition:
Calculated mileage based on Arc attribute, LENGTH * .0006211371192 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 * .0006213711. It is not intended to reflect or duplicate actual or official VTrans mileage.
Attribute_Definition_Source: VGIS Road Centerline Data Standard
Attribute:
Attribute_Label: AOTMILES
Attribute_Definition:
The AOTMILES item 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. For those maps updated since 2005, the AOTMILES should be correct and complete. Those towns that have not had the maps updated, the AOTMILES values may be coarse and yet to be verified. VTrans expects to have this field fully updated in the next 5 years.
Attribute_Definition_Source: Calculated by the Highway Mapping System at VTrans
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy_Explanation:
AOTMILES are rounded to the nearest 100th of a mile on Town Highways and 1000th of a mile on State Highways
Attribute:
Attribute_Label: FAID
Attribute:
Attribute_Label: FIPS6
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: INSET
Attribute_Definition:
Field used by Highway Mapping System to flag arcs that fall within an inset on the Town Highway Maps.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: FORMER_RTNAME
Attribute_Definition:
Former Town Highway Number or Route Number for an arc. This is used primarily on Class 2 Transfers, or discontinuance of highways.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: ISVISIBLE
Attribute_Definition:
Flag used by the Highway Mapping Sytem for cartographic purposes.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: PROVISIONALYEAR
Attribute_Definition:
Year a road is added to the Map, based on town information. The road is considered by the Town as provisional and is this way until formally classified.
Attribute_Definition_Source: VTrans
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy_Explanation: Null values are allowed in this field.
Attribute:
Attribute_Label: TWN_LR
Attribute_Definition:
Town-based linear reference code used to generate the town-based Linear Reference System data layer. The TWN_LR is related to the LR_ETE field by adding the CTCODE.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: CTUA
Attribute_Definition: CTCODE with UA Code, unique to all towns and UA within Vermont
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: CERTCODE
Attribute_Definition:
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.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: ANCIENTROADYEAR
Attribute_Definition: Year a road that was considered an ancient road was added.
Attribute_Definition_Source: VTrans
Attribute:
Attribute_Label: TRUCKROUTE
Attribute_Definition: Designated Truck Routes
Attribute_Definition_Source: VTrans - Vermont State Statute
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: Not fully assessed or complete
Attribute:
Attribute_Label: SCENICBYWAY
Attribute_Definition: Designated Scenic Byways
Attribute_Definition_Source: VTrans
Attribute_Value_Accuracy_Information:
Attribute_Value_Accuracy: Not fully assessed or complete
Attribute:
Attribute_Label: SHAPE_Length
Attribute_Definition: Length of feature in internal units (meters).
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: VT Center for Geographic Information
Contact_Address:
Address_Type: Mailing and Physical Address
Address: 58 South Main Street, Suite 2
City: Waterbury
State_or_Province: VT
Postal_Code: 05676
Country: USA
Contact_Voice_Telephone: 802/882-3000
Contact_TDD/TTY_Telephone: None
Contact_Facsimile_Telephone: 802/882-3001
Contact_Electronic_Mail_Address: geowizard@vcgi.org
Hours_of_Service: 9am - 5pm, M-F
Resource_Description: TransRoad_RDS
Distribution_Liability:
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.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: SHP
Format_Specification: ESRI Shapefile format (compressed to ZIP format)
Format_Information_Content: geospatial data
File_Decompression_Technique: ZIP decompression software
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.vcgi.org/dataware/default.cfm?layer=TransRoad_RDS>
Access_Instructions: Download from web site.
Offline_Option:
Offline_Media: CD-ROM
Offline_Option:
Offline_Media: DVD
Fees:
No charge when downloading from the internet, and when no custom processing is required.
Ordering_Instructions:
Download from web site or mail-fax a copy of the VCGI 'Data Request Form' which is available from the VGIS web site <http://www.vcgi.org/dataware/order_forms>
Turnaround: About 5 days.
Custom_Order_Process:
Mail or Fax a copy of the VCGI 'Data Request Form' which is available from <http://www.vcgi.org/dataware/order_forms>
Technical_Prerequisites: ESRI Arc/Info, ArcView, or ArcExplorer software.
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20081021
Time_of_Day: unknown
Metadata_Reference_Information:
Metadata_Date: 20081021
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Johnathan Croft
Contact_Organization: Vermont Agency of Transportation (VTrans) - Mapping Unit
Contact_Position: VTrans GIS Database Administrator
Contact_Address:
Address_Type: mailing and physical address
Address: VTrans - Policy & Planning Division
Address: One National Life Drive
City: Montpelier
State_or_Province: VT
Postal_Code: 05633-5001
Country: USA
Contact_Voice_Telephone: 802/828-2600
Contact_TDD/TTY_Telephone: None
Contact_Facsimile_Telephone: 802/828-2334
Contact_Electronic_Mail_Address: johnathan.croft@state.vt.us
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Access_Constraints: None
Metadata_Use_Constraints: None
Metadata_Security_Information:
Metadata_Security_Classification_System: N/A
Metadata_Security_Classification: Unclassified
Metadata_Security_Handling_Description: No security considerations
Generated by mp version 2.9.5 on Wed May 13 13:48:45 2009