RDS\RDSALL

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: GIS Database Administrator

Publication_Date: 2001

Publication_Time: Unknown

Title: RDS\RDSALL

Edition: 2001

Geospatial_Data_Presentation_Form: map

Series_Information:

Series_Name: Master Road centerlines from RF 5000 Orthophotos (GPS)

Issue_Identification: 2001

Publication_Information:

Publication_Place: Burlington VT 05405

Publisher: GIS Database Administrator

Other_Citation_Details: Tile Structure - STATE

Online_Linkage: <http://www.aot.state.vt.us/>

Online_Linkage: <http://www.vcgi.org/dataware/?layer=RDS\RDSALL>

Online_Linkage: <http://www.vcgi.org/dataware/?layer=RDS\RDSALL&mapit=yes>

Online_Linkage:

ogc:WMS-1.0.0-http-get-map <http://maps.vcgi.org:8080/servlet/com.esri.wms.Esrimap?servicename=WMS_VCGI_OGC&WMTVER=1.0.0&request=map&BBOX=-73.45416,42.72279,-71.46528,45.018356&SRS=EPSG:4326&LAYERS=primary_layer_name_in_caps&WIDTH=300&HEIGHT=400&FORMAT=GIF> [Friendly layer name]

Online_Linkage:

<http://maps.vcgi.org:8080/servlet/com.esri.wms.Esrimap?servicename=WMS_VCGI_OGC&WMTVER=1.0.0&request=map&BBOX=-73.45416,42.72279,-71.46528,45.018356&SRS=EPSG:4326&LAYERS=RDS\RDSALL&WIDTH=300&HEIGHT=400&FORMAT=GIF>

Description:

Abstract:

The Master Road Centerline data layer contains arcs for all town and state highways, as well as many private roads. The centerlines were developed initially under contract by Greenhorne and O'Mara under the guidance of VCGI. A combination of paper and RC Kodak RF 5000 scale orthophotos were used to determine road locations as originally digitized. 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. Orthophoto flight years and the VTrans map updates are documented under Associated files. 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 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 for February 10, 2001.

Purpose:

To provide high accuracy road centerlines for the state of Vermont.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 20010210

Time_of_Day: Unknown

Currentness_Reference: publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: Annually

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -71.46558

East_Bounding_Coordinate: -73.47547

North_Bounding_Coordinate: 42.70496

South_Bounding_Coordinate: 45.04176

Keywords:

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: master roads

Place:

Place_Keyword_Thesaurus: None

Place_Keyword: Vermont

Place_Keyword: statewide

Temporal:

Temporal_Keyword_Thesaurus: None

Temporal_Keyword: 2001

Access_Constraints:

VCGI, VTrans and the State of Vermont make no representations of any kind 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_Organization_Primary:

Contact_Organization: VCGI

Contact_Person: GIS Database Administrator

Contact_Position: GIS Database Administrator

Contact_Address:

Address_Type: Mailing and Physical Address

Address: 58 South Main Street, Suite 2

City: Waterbury

State_or_Province: VT

Postal_Code: 05405

Country: USA

Contact_Voice_Telephone: 802/882-3000

Contact_TDD/TTY_Telephone: None

Contact_Facsimile_Telephone: 802/882-3001

Hours_of_Service: 9am - 5pm EST, M-F

Browse_Graphic:

Browse_Graphic_File_Name:

<http://maps.vcgi.org:8080/servlet/com.esri.wms.Esrimap?servicename=WMS_VCGI_OGC&WMTVER=1.0.0&request=map&BBOX=-73.45416,42.72279,-71.46528,45.018356&SRS=EPSG:4326&LAYERS=RDS\RDSALL&WIDTH=300&HEIGHT=400&FORMAT=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: ArcInfo

Cross_Reference:

Citation_Information:

Originator: GIS Database Administrator

Publication_Date: 20000210

Publication_Time: unknown

Title: RDSALL

Edition: VTrans

Geospatial_Data_Presentation_Form: map

Series_Information:

Series_Name: Road Centerlines by Town

Issue_Identification: 2000

Publication_Information:

Publication_Place: Burlington VT 05405

Publisher: GIS Database Administrator

Other_Citation_Details: RDSALL

Online_Linkage: <http://www.vcgi.org/warehouse/?layer=RDS\RDSALL>

Online_Linkage: <http://www.aot.state.vt.us/>

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

Proof plots were generated by the original contractor. 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 VAOT highway maps. Frequency files were generated from the final data to reveal unlikely and impossible attribute combinations. (e.g. a gravel US highway). 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 prior to submission to VCGI. VCGI also runs QA/QC review of the RDS data layer. 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, VCGI 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 RDS data layer, including moving arcs to match digital orthophotography, changing route numbers, adding records, and updating road names fields.

Completeness_Report:

The statewide Master RDS data layer is currently being maintained by the VT Agency of Transportation (VTrans) and comprises over 74,000 arcs or over 30 Megabytes. The RDS 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 RDS with input from the Regional Planning Commissions, municipalities and VCGI. The intention is that the RDS data be maintained in a Master , comprehensive layer from which other roads layers may be derived. All updates are made to the Master 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> --> Publications). 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 or other means for adding new roads and improving road locations. See the LOCMETH and SRCORG attributes for more detail.

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:

Line accuracy standards for the original data conversion 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 RDS, improving the spatial accuracy of the data. The accuracy of the centerline data has improved with the advent of digital orthophotography. Most arcs will fall within 3 to 5 meters of their true location. Some errors may exist, especially in counties where a thorough comparison to digital orthophotography has not taken place.

Quantitative_Horizontal_Positional_Accuracy_Assessment:

Horizontal_Positional_Accuracy_Value: 0.250 map units

Horizontal_Positional_Accuracy_Explanation: Fuzzy Tolerance

Quantitative_Horizontal_Positional_Accuracy_Assessment:

Horizontal_Positional_Accuracy_Value: 2.54 map units

Horizontal_Positional_Accuracy_Explanation: Dangle Length

Quantitative_Horizontal_Positional_Accuracy_Assessment:

Horizontal_Positional_Accuracy_Value: 0.005

Horizontal_Positional_Accuracy_Explanation: Maximum RMS

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: VT Agency of Transportation(comp.)

Publication_Date: 19930310

Publication_Time: unknown

Title: Master Road centerline from 1:5000 orthophotos.

Edition: 1993

Geospatial_Data_Presentation_Form: map

Series_Information:

Series_Name: VAOT Highway maps.

Issue_Identification: 1993

Publication_Information:

Publication_Place: Montpelier, VT

Publisher: VAOT

Online_Linkage: <http://www.aot.vt.state.us/>

Source_Scale_Denominator: 5000

Type_of_Source_Media: paper maps from VAOT and RC Kodak orthophotos

Source_Time_Period_of_Content:

Time_Period_Information:

Range_of_Dates/Times:

Beginning_Date: 19740000

Beginning_Time: Unknown

Ending_Date: 19990000

Ending_Time: Unknown

Source_Currentness_Reference: Ground Condition

Source_Citation_Abbreviation: VTrans

Source_Contribution:

VAOT VCGI

Process_Step:

Process_Description:

Original documentation completed. Operator - Steve Bower (OGIS)

Process_Date: 19920212

Process_Time: 00000000

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: 00000000

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: 00000000

Process_Step:

Process_Description:

This update includes major modifications to the RDS layer. The layer is now managed by VCGI as a statewide, seamless, fully edgematched master layer (RDSM). The tile structure has been changed from ORTHO64 to COUNTY, although 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 AOT highway maps (1989, 1990 or 1993). As well, any roads which had been deleted but which still appeared on the AOT 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: 00000000

Process_Step:

Process_Description:

Since the last RDSnn 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 E9-1-1.

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 E9-1-1 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: 00000000

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: 00000000

Process_Step:

Process_Description:

Data updated by VAOT contractor (Information Visualization Services, South Burlington, VT). Included spatial and attribute updates. Operator - Steve Sharp (VCGI)

Process_Date: 19970901

Process_Time: 00000000

Process_Step:

Process_Description:

Extensive updates and QA/QC performed by VAOT and VCGI. Data has been integrated into the VGIS Data Warehouse for distribution. Operator - Steve Sharp (VCGI)

Process_Date: 20001201

Process_Time: 00000000

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: 00000000

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 load data into VGIS Data Warehouse. Operator - Steve Sharp (VCGI)

Process_Date: 20010503

Process_Time: 00000000

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: 00000000

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: 00000000

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: Elliptical arc

Point_and_Vector_Object_Count: varies by town

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Point

Point_and_Vector_Object_Count: 266

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

False_Easting: 500000.000000

False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.001

Ordinate_Resolution: 0.001

Planar_Distance_Units: Meters

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1983

Ellipsoid_Name: Geodetic Reference System 80

Semi-major_Axis: 6378137

Denominator_of_Flattening_Ratio: 1 / 298.25722210

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: Line

Entity_Type_Definition: 1-D Linear representation

Entity_Type_Definition_Source: VTrans

Attribute:

Attribute_Label: RTNAME

Attribute_Definition:

The RTNAME town highway number/name corresponds to the official number on the VAOT 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. The following are valid prefix values: I- = Interstate BR I- = Interstate Business Route BSp I- = Interstate Business Spur US- = U.S. route Alt US- = U.S. Alternate Route BR US- = U.S. Business Route BSp US- = U.S. Business Spur Old US- = Old U.S. Route Hist US- = Historic U.S. Route VT- = Vermont Numbered Route Old VT- = Vermont Numbered Route - Old Route Hist VT- = Vermont Numbered Route - Historic Route TH- = Town Highway NSH- = Named State Highway S- = Other State Highway special cases SF- = Dept of Forest, Parks and Recreation Highway NF- = National Forest Highway 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 VAOT 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 VAOT. 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.

Type (C) Width (12) Decimals (0)

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: VTrans town number/highway number

Codeset_Source: VTrans Route Logs & Highway Maps

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.

Type (C) Width (4) Decimals (0)

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 VAOT; 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. The following are valid prefix values: I- = Interstate BR I- = Interstate Business Route BSp I- = Interstate Business Spur US- = U.S. route Alt US- = U.S. Alternate Route BR US- = U.S. Business Route BSp US- = U.S. Business Spur Old US- = Old U.S. Route Hist US- = Historic U.S. Route VT- = Vermont Numbered Route Old VT- = Vermont Numbered Route - Old Route Hist VT- = Vermont Numbered Route - Historic Route TH- = Town Highway NSH- = Named State Highway S- = Other State Highway special cases SF- = Dept of Forest, Parks and Recreation Highway NF- = National Forest Highway 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 VAOT in the “field”. RTNAME should be consistent with how the road is “marked” on the official VAOT Town Highway Maps. These don’t always match.

Type (C) Width: 12 Decimals (0}

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: Highway Sign Route Number

Codeset_Source: VTrans infomation from signage in the field

Attribute:

Attribute_Label: RPCCLASS

Attribute_Definition:

The RPCCLASS item indicates the road class, generally as shown on official VAOT 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 VAOT 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 master 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 VAOT town highway maps. Comparison of the RPCCLASS and AOTCLASS attributes will help to identify roads needing class updates by the VAOT. 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. RPCCLASS Content ---------------------------------------------------- 1-4 Class 1-4 town highway, undivided (see 11-19, 21-29) 5 State forest highway 6 National forest highway 7 Legal trail 8 Private road, but not for display on local maps. Some municipalities may prefer not to show certain private roads on their maps, but the roads may need to be maintained in the data for emergency response or other purposes. 9 Private road, for display on local maps 10 Not used; use RPCCLASS = 1 for undivided Class 1 Town Highway 11 North bound (for divided centerlines) 12 South bound 13 East bound 14 West bound 15 Entrance/Exit ramp, Approach, Jughandle 16 Emergency U-turn 17 Rest area 19 Other Class 1 Town Highway (weigh stations, maintenance areas, etc.) 20 Not used; use RPCCLASS = 2 for undivided Class 2 Town Highway 21-29 Class 2 Town Highway; same road types as for 11-19 30 Vermont State Highway, undivided centerline (most Vermont Highways) 31-39 Vermont State Highway; same road types as for 11-19 40 US Highway, undivided centerline (most US Highways) 41-49 US Highway; same road types as for 11-19 50 Interstate, undivided centerline (not currently used) 51-59 Interstate, same road types as for 11-19 81-83 Proposed Class 1-3 Town Highway 84 Proposed State Highway 85 Proposed US Highway 86 Proposed Interstate 87 Proposed ramp: Interstate 88 Proposed ramp: non-Interstate 89 Proposed private road 91 Driveway (not used) - driveways maintained as separate data layer DW 92 Military road, no public access 93 Public road from VAOT 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 95 Road class under special review, usually temporary 96 Discontinued 97 Not used (to avoid confusion with AOTCLASS = 97) 98 Not considered a road based on local/regional review, but maintained in the data because it is on the VAOT town highway map 99 Unknown class (assumed private, but not originally coded as private) Class 4 roads on the VAOT 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 VAOT does not provide state aid for them.

Type (N) Width (2) Decimals (0)

Attribute_Definition_Source: Regional Planning Commissions

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1

Range_Domain_Maximum: 99

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 VAOT 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 VAOT road class from the VAOT 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).

Type (I) Width (2) Decimals (0)

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1

Range_Domain_Maximum: 99

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.

Attribute:

Attribute_Label: FUNCL

Attribute_Definition:

Functional Class Code. Functional classification codes are based on a federal classification system in use by VAOT. 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. Rural & Urban Functional Class Codes 0 Not part of Functional Classification System 1 Rural, Principal Arterial - Interstate. 2 Rural, Principal Arterial. 4 Rural, Principal Arterial - Other (not other freeway); not a standard federal code 6 Rural, Minor Arterial. 7 Rural, Major Collector. 8 Rural, Minor Collector. 9 Rural, Local. 11 Urban, Principal Arterial-Interstate. 12 Urban, Principal Arterial-Other Freeway. 14 Urban, Principal Arterial-Other. 16 Urban, Minor Arterial. 17 Urban Collector. 19 Urban Local.

Type (N) Width (2) Decimals (0)

Attribute_Definition_Source: VTrans Highway Research Unit

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: FUNCL

Enumerated_Domain_Value_Definition: Functional Class Code

Enumerated_Domain_Value_Definition_Source: VTrans

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 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. 0 = Not on NHS 1 = Interstate 2 = ISTEA High Priority Corridor 3 = Non-Interstate STRAHNET 4 = STRAHNET Connector 5 = ISTEA High Priority Corridor/Non-Interstate STRAHNET 6= ISTEA High Priority/STRAHNET Connector 7 = Other NHS 8 = Intermodal Connector

Type (I) Width (1) Decimals (0)

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 0

Range_Domain_Maximum: 8

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. The codes are as follows- 0 = Not designated as Scenic Highway 1 = Designated as Scenic Highway by local municipality 2 = Designated as Scenic Highway by VTrans

Type (I) Width (1) Decimals (0)

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 0

Range_Domain_Maximum: 2

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. 1 Hard surface (pavement) 2 Gravel 3 Soil or graded and drained earth 5 Unimproved/Primitive 6 Impassable or untravelled 9 Unknown surface type Roads surface types are generally based on VTrans Town Highway Maps, or on regional/local review.

Type (I) Width (1) Decimals (0)

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1

Range_Domain_Maximum: 9

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 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 the following components (or redefined items) Route Type - 1 byte Route Number - 3 bytes Route # Modifier - 1 byte Direction - 1 byte Subtype - 1 byte Numeric ID - 3 bytes Alpha ID - 1 byte Each component of the LR_ETE and composition are described below

Route Type (LR_ETE_TYP) I = Interstate U = U.S. route V = VT signed route S = State highway (named, special cases, functionally class town highways, other routed roads) A = Alternate route B = Business route

Route Number (LR_ETE_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 (LR_ETE_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 LR_ETE - = <dash>, if no modifier is needed but other LR_ETE components follow

Direction (LR_ETE_DIR). The direction character is included only if the highway is divided. Valid direction characters include: ' ' = <blank>, if route is undivided and there are no subsequent LR_ETE_RTE components W = Westbound (for divided routes) S = Southbound (for divided routes) E = Eastbound (for divided routes) N = Northbound (for divided routes) Examples: LR_ETE End-to-End Route I089-N = 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 (LR_ETE_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

Numeric ID (LR_ETE_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 (LR_ETE_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: LR_ETE End-to-End Route U004-E = 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

Type (C) Width (11) Decimals (0)

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.

Type (C) Width (4) Decimals (0)

Attribute_Definition_Source: VTrans

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: UA

Attribute_Definition:

VTrans Urban Area Code. These Urban Area codes identify 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. Listed in order of FIPS6 codes, the UA codes include: FIPS6 UA RPC Urban Area 1015 1 AC Bristol Village 1055 1 AC Middlebury Urban Compact 3005 1 BC Arlington Urban Compact 3010 1 BC North Bennington Village 3010 2 BC Old Bennington Village 3010 3 BC Bennington Urban Compact 3025 1 BC Manchester Village 3025 2 BC Manchester Center Depot Urban Compact 5010 1 NV West Burke Village 5020 1 NV Groton Village 5025 1 NV Hardwick Village 5035 1 NV Lyndonville Village 5050 1 NV South Ryegate Village 5055 1 NV St. Johnsbury Urban Compact 7030 1 CC Essex Junction Village 7030 2 CC Essex Center Urban Compact 7045 1 CC Jericho Village 7050 1 CC Milton Village 9020 1 NV Island Pond Urban Compact 11020 1 NW Enosburg Falls Village 11060 1 NW Richford Village 11080 1 NW Swanton Village 13005 1 NW Alburg Village 15010 1 LC Cambridge Village 15010 2 LC Jeffersonville Village 15025 1 LC Hyde Park Village 15030 1 LC Johnson Village 15035 1 LC Morrisville Village 15040 1 LC Stowe Village 17005 1 TR Bradford Village 17035 1 TR Newbury Village 17035 2 TR Wells River Village 17045 1 TR Randolph Village 19005 1 NV Albany Village 19010 1 NV Barton Village 19010 2 NV Orleans Village 19035 1 NV Derby Center Village 19035 2 NV Derby Line Village 19085 1 NV North Troy Village 21010 1 RR Brandon Urban Compact 21035 1 RR Fair Haven Urban Compact 21085 1 RR Poultney Village 21090 1 RR Proctor Urban Compact 21125 1 RR Wallingford Urban Compact 21140 1 RR West Rutland Urban Compact 23020 1 CV Cabot Village 23045 1 CV Marshfield Village 23065 1 CV Northfield Village 23090 1 CV Waterbury Village 25010 1 WR Brattleboro Urban Compact 25010 2 WR West Brattleboro Urban Compact 25060 1 WR Newfane Village 25070 1 WR Bellows Falls Village 25070 2 WR Saxtons River Village 25080 1 WR Townshend Village 25095 1 WR North Westminster Village 25095 2 WR Westminster Village 25100 1 WR Jacksonville Village 27030 1 RR Proctor Urban Compact 27035 1 SW Chester-Chester Depot Urban Compact 27040 1 UV White River Junction Urban Compact 27040 2 UV Wilder Urban Compact 27050 1 SW Ludlow Village 27090 1 SW Springfield Urban Compact 27090 2 SW North Springfield Urban Compact 27100 1 SW Perkinsville VillageFips6 27115 1 SW Windsor Urban Compact 27120 1 TR Woodstock Village

Type (N) Width (1) Decimals (0)

Attribute_Definition_Source:

To be based on municipal boundaries and VTrans town highway maps

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: Urban Area

Codeset_Source: Municipal boundaries and AOT 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 RDS data layer. Only the prime arcs within Essex Junction Village have been coded with an UA code. 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 and proper coding.

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. NOTE: There currently isn't a mechanism for maintenance of this item. Users should generally turn to the E911\RDS data layer when they need "official" road name information. The RDS RDNAME code is usually only 3 digits in length. The E911 RDNAME values contains a unique town code as a 3 digit prefix, making the RDNAME unique statewide. These values may be incorporated at some point in the future into this RDNAME code.

Type (I) Width (6) Decimals (0)

Attribute_Definition_Source:

Regionally or Locally assigned and primarily from original E911 values

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:

The current RDNAME field should be considered somewhat suspect due to the data originally used to generate the RDS data layer. The Enhanced 911 Program populated the field with information as the E911 data was being developed. This initial data has not been checked or revised since that original data population. There is an initiative to evaluate and revise the RDNAME and RDFLNAME, with revisions occuring the upcoming future. The RDNAME was not cleared or zeroed out due to the chance that some of the names, even if erroneous may give some information or reference. This field will improve over time.

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 mechanism for maintenance of this item. Users should generally turn to the E911\RDS data layer when they need "official" road name information.

Type (C) Width (30) Decimals (0)

Attribute:

Attribute_Label: LOCMETH

Attribute_Definition:

Line Accuracy Code. 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 attribute. 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. 3 = Not clearly visible on the ortho, location estimated from State Forest maps. 4 = No indication of the road on the orthophoto; apparently a new road built since the orthophoto was taken. Location estimated from VAOT maps. 5 = Road centerlines drafted onto orthophotos from engineering drawings and the like. 6 = Invisible on the orthophoto, but located based on town or other local knowledge of the area. 7 = Digitized centerline of the parcel (tax map) road right-of-way. 8 = Screen digitized from drafting by town officials onto maps of approximately 1:15,000 to 1:20,000 scale. 9 = Coordinates captured via a GPS device utilizing "dead reckoning" with typical horizontal accuracy within 5 meters

Type (I) Width (2) Decimals (0)

Attribute_Definition_Source: 1:5000 scale Orthophotos, 1974-99

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1

Range_Domain_Maximum: 9

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". 1 VCGI, original data (assigned Sept 1993) 2 VCGI, updated location 10 Addison County RPC 11 Bennington County RC 12 Central VT RPC 13 Chittenden County RPC 14 Northwest RPC 15 Lamoille County PC 16 Northeast VT Development Assoc. 17 Rutland RPC 18 Southern Windsor RPC (or its contractor) 19 Two Rivers-Ottauquechee RPDC 20 Upper Valley-Lake Sunapee RPC 21 Windham RPC 22 microData, incorporated by CVRPC 23 Incorporated from municipal updates 24 E9-1-1 GIS database development project (1996) 25 IVS Highway Mapping System Project 26 VAOT HMS updates

Type (I) Width (2) Decimals (0)

Attribute_Definition_Source: Assigned when digitized, moved, or re-shaped

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1

Range_Domain_Maximum: 26

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).

Type (I) Width (8) Decimals (0)

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 TBHASH town boundaries layer [v. 12/16/93]. TBHASH was developed with 'Best Available' town boundaries for this purpose. After the overlay, manual edits were made along with all town boundaries to assure agreement with VTrans highway maps. Therefore, the assigned FIPS6 codes will not always agree with the 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 TBHASH [including virtually all Interstate, US, and VT roads].

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.

Type (I) Width (4) Decimals (0)

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 in the UPDACT field with the following code: UPDACT Action A Added arc (i.e., a new arc) M Moved arc (by reshaping the arc, moving a node, moving or deleting a vertex, or other action altering the shape of the arc) S Split arc (both new arcs are coded 'S') U Unsplit arc (originally 2 arcs)

Type (C) Width (1) Decimals (0)

Attribute_Definition_Source: Assigned by organization performing updates

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.

Type (N) Width (7) Decimals (3)

Attribute_Definition_Source: Assigned by organization performing updates

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 Highway Mapping System uses the numeric value of the annotation to prorate mileage across all arcs representing the "official" mileage for that section. AOTMILES is then calculated to represent the proper percentage of the "official" mileage. The year 1999 was the first year this process was enacted and there may be sections of highway that have not be flagged as having a mileage, thus making it and other AOTMILES values incorrect. This information will be refined over the course of time.

Type (N) Width (7) Decimals (3)

Attribute_Definition_Source: Calculated by the Highway Mapping System at VTRans

Attribute:

Attribute_Label: L_ADD_FROM

Attribute_Definition:

LEFT-FROM address range based on the E911 road centerline. The L_ADD_FROM item indicates the starting address on the left side of the road relative to the start position of the arc. NOTE: All values will be calced to 0 until a method is developed to transfer E911 information into the master RDS layer. Users should use the E911\RDS layer when address range information is needed.

Type (I) Width (7) Decimals (0)

Attribute:

Attribute_Label: L_ADD_TO

Attribute_Definition:

LEFT-TO address range based on the E911 road centerline. The L_ADD_TO item indicates the ending address on the left side of the road relative to the starting position of the arc. NOTE: All values will be calced to 0 until a method is developed to transfer E911 information into the master RDS layer. Users should use the E911\RDS layer when address range information is needed.

Type (I) Width (7) Decimals (0)

Attribute:

Attribute_Label: R_ADD_FROM

Attribute_Definition:

RIGHT-FROM address range based on the E911 road centerline. The R_ADD_FROM item indicates the starting address on the right side of the road relative to the starting position of the arc. NOTE: All values will be calced to 0 until a method is developed to transfer E911 information into the master RDS layer. Users should use the E911\RDS layer when address range information is needed.

Type (I) Width (7) Decimals (0)

Attribute:

Attribute_Label: R_ADD_TO

Attribute_Definition:

RIGHT-TO address range based on the E911 road centerline. The R_ADD_TO item indicates the ending address on the right side of the road relative to the starting position of the arc. NOTE: All values will be calced to 0 until a method is developed to transfer E911 information into the master RDS layer. Users should use the E911\RDS layer when address range information is needed.

Type (I) Width (7) Decimals (0)

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: geowiz@vcgi.org

Hours_of_Service: 9am - 5pm, M-F

Resource_Description: RDS\RDSALL

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: ARCE

Format_Specification: ArcInfo Export file

Format_Information_Content: ArcInfo Export File (WinZip self extracting format)

File_Decompression_Technique: WinZIP

Digital_Transfer_Option:

Online_Option:

Computer_Contact_Information:

Network_Address:

Network_Resource_Name: <http://www.vcgi.org/dataware/?layer=RDS\RDSALL>

Access_Instructions: Download from web site.

Offline_Option:

Offline_Media: CD-ROM

Offline_Option:

Offline_Media: 3-1/2 inch floppy disk

Offline_Option:

Offline_Media: 4 mm cartridge tape

Offline_Option:

Offline_Media: 8 mm cartridge tape

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: 20001023

Time_of_Day: 00000000

Metadata_Reference_Information:

Metadata_Date: 20001024

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: VT Center for Geographic Information

Contact_Person: GIS Database Administrator

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

Metadata_Standard_Name: FGDC Content Standards for Digital 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

Metadata_Extensions:

Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>

Profile_Name: ESRI Metadata Profile