TransRoad_RTLOGPTS2012

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: VCGI GIS Database Administrator

Publication_Date: 20121231

Title: TransRoad_RTLOGPTS2012

Edition: 2012

Geospatial_Data_Presentation_Form: vector digital data

Series_Information:

Series_Name:

VTrans 2012 Route Log intersection and LRS calibration point layer

Issue_Identification: 2012

Publication_Information:

Publication_Place: Montpelier, VT 05633

Publisher: GIS Database Administrator

Other_Citation_Details: Tile Structure - STATE

Description:

Abstract:

The RTLOGPTS2012 data layer consists of VTrans Route Log intersection and LRS calibration points.

Purpose:

This data layer is used with VTran's Integrated Route Log System (IRA). It is used to calibrate the TransRoad_LRS2012 route systems, including the End-to-End and Town-based LRSs.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 20121231

Currentness_Reference: publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -73.434729

East_Bounding_Coordinate: -71.506363

North_Bounding_Coordinate: 45.014127

South_Bounding_Coordinate: 42.723476

Keywords:

Theme:

Theme_Keyword_Thesaurus: ISO 19115 Topic Category

Theme_Keyword: transportation

Theme:

Theme_Keyword_Thesaurus: None

Theme_Keyword: road

Theme_Keyword: intersection

Theme_Keyword: calibration

Theme_Keyword: LRS

Theme_Keyword: linear referencing system

Theme_Keyword: route

Theme_Keyword: route log system

Place:

Place_Keyword_Thesaurus: None

Place_Keyword: Vermont

Access_Constraints:

VCGI and the State of VT 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: None.

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

Address: Drawer 33

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

Data_Set_Credit: VTrans

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

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report: Please refer to Logical Consistency Report below.

Logical_Consistency_Report:

2012 UPDATE: No documentation available from VTrans for this update.
2011 UPDATE: No documentation available from VTrans for this update.
2010 UPDATE: No documentation available from VTrans for this update.
2009 UPDATE: No documentation available from VTrans for this update.
2007 UPDATE: VTrans moved data into ArcSDE and worked on matching the intersecting road points to match the road centerline nodes. Correction to the road alignments was performed to correct any issues and the route log points were subsequently moved. VTrans ran a routine to identify missing and moved points and made the necessary corrections. Some points may still require correction to match the roads, or the roads require proper alignment. Road names coding - RDNAME was updated to match the new E911 format and many points were linked to their corresponding arcs in the TransRoad_RDS data layer.
2006 UPDATE: VTrans identified missing points and added these features. Mileage values, road names, and other attribute data were updated as necessary.
2005 UPDATE: VTrans provided VCGI with the latest copy of RTLOGPTS for use during the development of LRS2005. VCGI identified and corrected numerous errors. Updates also included A: Verified that there was a point at least every two miles tagged as a calibration point for every TWN/ETE route (USEFORCAL = Y within RTLOGPTS2005). Tagged additional RTLOGPTS2005 points as needed. If a point was not available for tagging (USEFORCAL = Y), VCGI wrote the FROM_MM/TO_MM and Route ID (ETE_LR/TWN_LR) for the given section to a "linear event table". VTrans provided VCGI a file which included LRS and milemarker information for bridges on interstate, US, and state highways. VCGI wrote a python script which snagged points from VTrans bridge data which were in the identified areas which did not meet the 2 mile specification. All of these procedures added over 2000 points to the coverage.
2004 UPDATE: VTrans provided VCGI with the latest copy of RTLOGPTS for use during the development of LRS2004. VCGI identified and corrected numerous errors. VCGI added two attributes to the PAT called UPDACT (update action) and UPDCOMMENTS. These two attributes document the updates made by VCGI. Additional edits were made by VTrans, however, these have not been documented.
HISTORICAL: The information below describes the creation of RTLOGPTS2002, which was the original release of RTLOGPTS. RTLOGPTS2002 was developed through a three phase data integration and QA/QC process (managed by VCGI). PHASE 1 - RTLOGPTS points were derived from two primary sources; RDS\CPTS2000 (existing calibration point coverage) and a VTran's Route Log intersection database (event table - IntersectingRoads.mdb provided by Johnathan Croft 2005 - VTrans). The route log event table was converted into a point coverage using dynamic segmentation (applied against RDS\LRS2000). A Visual Basic program (which called an AML) was used to combine these two coverages into a single data layer. The program looked for points in the route log intersection coverage (RTLOGPTS) which matched points in the calibration coverage (CPTS2000). Those that were within 15 meters, had the same LR_TWN value, and had the same LRTWN_MI value (within a tolerance of 0.01 miles) were tagged as matches. Some of the key CPTS2000 attributes were then carried into the RTLOGPTS coverage. The remaining points in CPTS2000 which did not match any of the points in RTLOGPTS were then put to RTLOGPTS. VCGI checked to make sure that every calibration point originally present in CPTS2000 had a representation in the RTLOGPTS coverage. There was a one to one match. All of the points in RTLOGPTS (the combined coverage) were snapped to RDS\RDSALL (2002 release) nodes within 20 meters. Mileages were derived from VTrans Route Logs and other sources (refer to MILE_SRC). PHASE 2 - This phase included moving all intersection points to match the "true" intersection location based on 5K VT digital orthophotography. This was done for all route log intersection points. STATION numbers were also verified against hardcopy VTrans Route Logs. In a few cases STATION numbers had to be corrected. In these cases the LRTWN_MI (MILEAGE) value was also updated. VCGI verified that FIPS6, CTCODE, and TOWNNAME values were consistent. Spatial consistency of FIPS6 with TBHASH was also checked, but there are many cases in which TBHASH isn't very accurate. In these cases VCGI used the VTrans Route Logs to determine the correct FIPS6. Points have been flagged to indicate whether they they should be used for calibration of VTrans' LRS coverage (USEFORCAL) or for VTrans' Route Log system (USEFORRTLG). There are cases in which points can be used for both. Also flagged route log intersections which did not match (not within 5 meters) the master RDSALL road centerline intersection nodes. Adjusted mileages for South and West bound sections of divided highways which had been using DMI based mileages to match North and East bound lanes (I089-S,I091-S,I093-S,U004-W). RDFLNAME values were verified against E911\RDS data using automated procedures. However, only 440 points of out of 6404 route log intersection stations could be verified. These were assigned the E911\RDS road name and RDNAME value. All other RDFLNAME values need to be manually verified (QC_FLAG = 2), which is beyond the scope of the "Calibration and Route Log Points Data Development Project" between VTrans and VCGI. RTNAME values were verified against the "master" RDS\RDSALL (RDSnnnnn) coverage (2005 release). VCGI was able to verify 3745 points ouf of 6404 route log intersection stations. All other RTNAME values need to be manually verified (QC_FLAG = 1), which is beyond the scope of the project. If both RTNAME and RDFLNAME need to be manually verified they have been flagged with QC_FLAG = 3. PHASE 3 - The final phase included two primary tasks; 1) Refreshing of ETE_LR and ETE_MM by porting TWN_LR and TWN_MM, and 2) final attribute consistency checking. First VCGI recalced all TWN_MM = TWN_ST / 5280. VCGI refreshed ETE_LR and ETE_MM values by dumping the RTLOGPTS2002.PAT to a dBase IV file then using a FoxPro program (developed by Jim Mossman VTrans 1999) to "port" TWN_MM values to ETE_MM. The refreshed values were then loaded back into the RTLOGPTS20122005.PAT using a table join. VCGI ran a final check to make sure FIPS6, CTCODE, and TOWNNAME values were consistent. VCGI also verified that all points tagged as calibration points (USEFORCAL = Y) had start/end mileages matching MRDTABLE2005.DBF (both ETE and TWN).

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:

There has been substantial work correcting the road centerlines to match the orthophotography. Some of the intersections may not fully match the node locations in the RDS data layer.
In 2005, VCGI had snapped all points to match intersections in the master road centerline coverage (RDS\RDSALL). All route log intersection points (USEFORRTLOG = Y) were verified against VT's 5K digital orthos. Those points not within 5 meters of the road centerline intersection were flagged with FIXRDS = Y (meaning these road intersections in the master RDS\RDSALL data need to be verified). NOTE: VTrans personnel may conclude that some of these are erroneous.
Since the data has been moved into ArcSDE, and significant work has taken place on the road centerlines, some of the intersections may not match the roads. Much effort has gone into correcting the intersecting road and calibration points, but the data has not been universally reviewed. Review has occurred on a town by town basis to date.

Vertical_Positional_Accuracy:

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: VTrans

Publication_Date: 20121231

Publication_Time: Unknown

Title:

VTrans 2012 Route Log intersection and LRS calibration point layer (RTLOGPTS2012)

Geospatial_Data_Presentation_Form: database

Publication_Information:

Publication_Place: Montpelier, VT

Publisher: VTrans

Source_Scale_Denominator: NA

Type_of_Source_Media: paper

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 20121231

Time_of_Day: unknown

Source_Currentness_Reference: publication date

Source_Citation_Abbreviation: TransRoad_RTLOGPTS2012

Source_Contribution: VTrans

Process_Step:

Process_Description:

VTrans submitted a copy of RTLOGPTS2012 (limited metadata provided) to VCGI in February 2014. VCGI adjusted RTLOGPTS2011 metadata to create this metadata and loaded the data into VGIS Data Warehouse.

Process_Date: 20140401

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

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Entity point

Point_and_Vector_Object_Count: 16002

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

Attribute:

Attribute_Label: FAID_S

Attribute_Definition: Unique Identifier from the TransRoad_RDS data layer

Attribute_Definition_Source: VTrans & Highway Mapping System

Attribute_Value_Accuracy_Information:

Attribute_Value_Accuracy:

Not fully coded in the data and only related to the intersecting roads

Attribute:

Attribute_Label: SHAPE

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

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

Attribute_Definition: Update Action flag. Reflects changes since the last release.

Attribute_Definition_Source: VCGI/VTrans

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: A

Enumerated_Domain_Value_Definition: point added

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: C

Enumerated_Domain_Value_Definition: one or more attributes changed

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: M

Enumerated_Domain_Value_Definition: point moved

Attribute:

Attribute_Label: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: PERIMETER

Attribute_Definition: Perimeter of feature in internal units.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Perimeter is always zero for point coverages. Values are automatically generated.

Attribute:

Attribute_Label: POINTID

Attribute_Definition: Unique point identifier

Attribute:

Attribute_Label: TWN_ST

Attribute_Definition: VTrans Route Log station number

Attribute:

Attribute_Label: TWN_LR

Attribute_Definition: Town-based route identifier

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Unrepresentable_Domain: Refer to LRS2000.MRDTABLE for list of values

Attribute:

Attribute_Label: TWN_MM

Attribute_Definition: TWN mileage at this point.

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1

Range_Domain_Maximum: 9999

Attribute:

Attribute_Label: ETE_LR

Attribute_Definition: End-to-End route identifier

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Unrepresentable_Domain: Refer to MRDTABLE2012 for list of values

Attribute:

Attribute_Label: ETE_MM

Attribute_Definition: ETE mileage at this point.

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1

Range_Domain_Maximum: 9999

Attribute:

Attribute_Label: RDFLNAME

Attribute_Definition: Full road name

Attribute:

Attribute_Label: RTNAME

Attribute_Definition: Town Highway name or route number

Attribute:

Attribute_Label: SIDEOFROAD

Attribute_Definition: Side of road for which the intersecting road hits

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: R

Enumerated_Domain_Value_Definition: Right side of road

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: L

Enumerated_Domain_Value_Definition: Left side of road

Attribute:

Attribute_Label: PT_TYPE

Attribute_Definition: Point type. Yet to be defined by VTrans.

Attribute:

Attribute_Label: ETEPT_TYPE

Attribute_Definition: Type of ETE calibration point

Attribute_Definition_Source: VCGI

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 0

Enumerated_Domain_Value_Definition: Regular calibration point

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 1

Enumerated_Domain_Value_Definition: Start (of route) calibration point

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 2

Enumerated_Domain_Value_Definition: End (of route) calibration point

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 3

Enumerated_Domain_Value_Definition: Gap calibration point (gaps in route)

Attribute:

Attribute_Label: TWNPT_TYPE

Attribute_Definition: Type of TWN calibration point

Attribute_Definition_Source: VCGI

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 0

Enumerated_Domain_Value_Definition: Regular calibration point

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 1

Enumerated_Domain_Value_Definition: Start (of route) calibration point

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 2

Enumerated_Domain_Value_Definition: End (of route) calibration point

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 3

Enumerated_Domain_Value_Definition: Gap calibration point (gaps in route)

Attribute:

Attribute_Label: TURNAZIMUTH

Attribute_Definition: Turn azimuth.

Attribute_Definition_Source: Has not been populated yet.

Attribute:

Attribute_Label: TURNANGLE

Attribute_Definition: Turn angle.

Attribute_Definition_Source: VTrans

Attribute_Value_Accuracy_Information:

Attribute_Value_Accuracy_Explanation:

Turn angles are approximate and related to the angle on the Route Logs and not the actual geometry of the intersection

Attribute:

Attribute_Label: USEFORCAL

Attribute_Definition: Use this point for calibration

Attribute_Definition_Source: VCGI

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Y

Enumerated_Domain_Value_Definition: Yes, use point for calibration

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: N

Enumerated_Domain_Value_Definition: No, do not use this point for calibration

Attribute:

Attribute_Label: USEFORRTLG

Attribute_Definition: Use for VTrans Route Log System

Attribute_Definition_Source: VTrans

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Y

Enumerated_Domain_Value_Definition: Yes, use point in Route Log System

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: N

Enumerated_Domain_Value_Definition: No, do not use point in Route Log System

Attribute:

Attribute_Label: LOCMETH

Attribute_Definition: Method used to locate and digitize point

Attribute_Definition_Source: VCGI

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 1

Enumerated_Domain_Value_Definition: Digitized from RF5000 scale orthophotos

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 2

Enumerated_Domain_Value_Definition:

Dynseged from VTrand route intersection database (IntersectingRoads.mdb)

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 3

Enumerated_Domain_Value_Definition: Intersection of RF5000 scale road data (RDS\RDSALL)

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 4

Enumerated_Domain_Value_Definition: Collected in the field using GPS

Attribute:

Attribute_Label: MILE_SRC

Attribute_Definition: Source of mileage info (LRTWN_MI and LRETE_MI)

Attribute_Definition_Source: VCGI

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 1

Enumerated_Domain_Value_Definition: VTrans Route Logs

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 2

Enumerated_Domain_Value_Definition: VTrans Pavement Management System

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 3

Enumerated_Domain_Value_Definition: VTrans AADT

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 4

Enumerated_Domain_Value_Definition: Calculated - estimated

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 5

Enumerated_Domain_Value_Definition: GIS calculated

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 6

Enumerated_Domain_Value_Definition: Field collected DMI measurements

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 7

Enumerated_Domain_Value_Definition: Unknown

Attribute:

Attribute_Label: FIPS6

Attribute_Definition: Municipality (town, city, gore, grant) FIPS code.

Attribute_Definition_Source: VGIS Geographic Area Codes Standard

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.

Attribute_Definition_Source: VTrans

Attribute:

Attribute_Label: TOWNNAME

Attribute_Definition: Name of town

Attribute:

Attribute_Label: RDSNODE_ID

Attribute_Definition:

Master road coverage node ID number (RDS\RDSnnnnn). No longer used or kept current

Attribute:

Attribute_Label: FIXRDS

Attribute_Definition: Flag indicating whether RDS\RDSnnnnn needs to be fixed.

Attribute_Definition_Source: VCGI/VTrans

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Y

Enumerated_Domain_Value_Definition: Yes, RDS\RDSnnnnn intersection needs to be fixed

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: N

Enumerated_Domain_Value_Definition: No, RDS\RDSnnnnn intersection does NOT need to be fixed

Attribute:

Attribute_Label: QC_FLAG

Attribute_Definition: Quality control flag

Attribute_Definition_Source: VCGI/VTrans

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 1

Enumerated_Domain_Value_Definition: Could not find RTNAME match in RDS\RDSnnnnn data

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 2

Enumerated_Domain_Value_Definition: Could not find RDFLNAME match in E911\RDS data

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 3

Enumerated_Domain_Value_Definition:

Could not find RDFLNAME match in E911\RDS data or RTNAME match in RDS\RDSnnnnn data

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 4

Enumerated_Domain_Value_Definition: Other problem with data. Refer to NOTES field.

Attribute:

Attribute_Label: NOTES

Attribute_Definition: Data notes

Attribute_Definition_Source: VCGI/VTrans

Attribute:

Attribute_Label: UPDCOMMENTS

Attribute_Definition:

Update comments. Augments UPDACT flag with additional detail as to change made.

Attribute:

Attribute_Label: UPDNAME

Attribute_Definition: Name assigned by VTrans or VCGI to identify update sets.

Attribute:

Attribute_Label: RTLOGPTS20122005_

Attribute:

Attribute_Label: RTLOGPTS20122005_ID

Attribute:

Attribute_Label: RDNAME

Attribute:

Attribute_Label: CTCODE_REDEF

Attribute:

Attribute_Label: POLYGONID

Attribute:

Attribute_Label: AOTCLASS

Attribute_Definition:

The AOTCLASS item indicates the road class, generally as shown on official VTrans highway maps.

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

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

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:

Attribute_Label: SCALE

Attribute:

Attribute_Label: ANGLE

Attribute:

Attribute_Label: AREA

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: info@vcgi.uvm.edu

Hours_of_Service: 9am - 5pm, M-F

Resource_Description: RTLOGPTS2012

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://maps.vcgi.org/gisdata/vtrans/packaged_zips/TransRoad_RTLOGPTS2012.zip>

Access_Instructions: Download from web site.

Offline_Option:

Offline_Media: USB Thumb Drive

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://vcgi.vermont.gov/warehouse/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://vcgi.vermont.gov/warehouse/order_forms>

Technical_Prerequisites: ESRI Arc/Info, ArcView, or ArcExplorer software.

Available_Time_Period:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 20121231

Time_of_Day: unknown

Metadata_Reference_Information:

Metadata_Date: 20121231

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