Emergency911_RDS

Metadata also available as

Metadata:
Identification_Information:
Citation:
Citation_Information:
Originator: Database Administrator
Publication_Date: 20081002
Publication_Time: unknown
Title: Emergency911_RDS
Edition: 2008
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: E911 Road center lines from 1:5000 orthophotos and GPS
Issue_Identification: 2008
Publication_Information:
Publication_Place: Montpelier, VT 05620-6501
Publisher: Database Administrator
Other_Citation_Details: Tile Structure - STATE
Online_Linkage:
<http://www.vcgi.org/dataware/default.cfm?layer=EmergencyE911_RDS>
Description:
Abstract:
WARNING! When using E911 data it is imperative that you understand the inter-relationships between the various E911 data sets to avoid erroneous interpretations of the data. The best way to avoid this is to thoroughly read the metadata for each data set you are working with. Please see the Use_Constraints section below for more information on data issues identified by VCGI, Inc. in the quality control/quality assurance effort conducted for the E911 board.

See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. <http://www.vcgi.org/techres/?page=./white_papers/default_content.cfm>

EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) 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. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier.

Purpose: E911 Road center lines from RF 5000 orthophotos and GPS
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20080915
Time_of_Day: unknown
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Continually
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -73.423273
East_Bounding_Coordinate: -71.466476
North_Bounding_Coordinate: 45.016647
South_Bounding_Coordinate: 42.727173
Keywords:
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: emergency
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: E911 Road center lines from 1:5000 orthophotos and GPS
Theme_Keyword: transportation
Theme_Keyword: roads
Theme_Keyword: emergency management
Theme_Keyword: infrastructure
Theme_Keyword: streets
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Vermont
Access_Constraints:
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.
Use_Constraints:
Warning! The data was developed and designed for Enhanced 9-1-1 purposes only. The user should understand that the nature of Enhanced 9-1-1 data layers means they are never complete and all analysis and cartographic output based on this data should be adequately prefaced. Data layers are continually being updated with information including existing features being imported and with features that get created every day, e.g., new houses, driveways etc. Certain information comes from individual towns and cannot be integrated properly until provided by the Town. Historically, the largest issue with 9-1-1 data has been the "Grand-fathered" towns with incomplete or missing features. These are towns that had their addressing scheme approved by the Enhanced 9-1-1 Board and/or participated in the Board's GIS assistance project in 1997-1998. The "zero address values" in the SITES.SHP are related mostly to those towns that requested GIS assistance but did not indicate the grand-fathered address for that site. Exceptions would be new SITE features added in the field where no address was readily available and for fire hydrants. "Zero address values" in grand-fathered towns will require follow-up with the municipalities to resolve. "Zero-length ranges" in ROADS.SHP pertain to grand-fathered towns that have not provided the Enhanced 9-1-1 Board road segment range information. Mapping efforts by microData, Inc. in 2003 to collect data for towns without data, including some "grand-fathered" towns, has largely minimized "data holes", but again, efforts to fully integrate this information are an ongoing process.
Browse_Graphic:
Browse_Graphic_File_Name:
<http://maps.vcgi.org:8080/wmsconnector/com.esri.wms.Esrimap?servicename=DATAWARE_VCGI&VERSION=1.1.0&request=getmap&BBOX=-72.78108248505863,44.28374275027345,-72.7204763913086,44.360521719023424&SRS=EPSG:4326&LAYERS=EMERGENCY_RDS_LINE&WIDTH=300&HEIGHT=400&FORMAT=image/gif>
Browse_Graphic_File_Description: GIF
Browse_Graphic_File_Type: A GIF file
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.4.1420
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Proof plots were generated by the original contractor and checked by the 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 line work was checked by VCGI staff with translucent paper proof plots anchored to the source photos with 1000 meter tics. Attributes were checked against VTrans highway maps. Frequency files were generated from the final data to reveal unlikely and impossible attribute combinations (e.g., a gravel US highway). 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. See the VGIS Standard on 'Updating the Road Centerline Data Layer' (see VGIS Handbook) for details on quality control measures used for regional data updates. CHANGES MADE BY E911 CONTRACTOR; E911 updates performed via the Enhanced 9-1-1 Addressing project (1996-1997) were verified for consistency per the VGIS Standard on 'Updating the Road Centerline Data Layer'. The consistency of geo-coding (addressing) was also checked. Updates performed after October 1997 have not been QA/QCed by VCGI.
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: 0.0 inches
Attribute_Accuracy_Explanation: Resolution
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: 0.005
Attribute_Accuracy_Explanation: Max. RMS
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: 0.250 map units
Attribute_Accuracy_Explanation: Fuzzy Tolerance
Logical_Consistency_Report:
OVERVIEW; The EmergencyE911_RDS coverage was derived from Vermont's "master" Road Centerline Data Layer (RDSnn). E911's primary contractor updated RDSnn, modified its attribute structure (added and dropped attributes), removed unwanted pseudo nodes, and created the resulting EmergencyE911_RDS coverage. The EmergencyE911_RDS coverage is designed for use within E911's emergency response system. It is maintained independently from the RDSnn data layer. ORIGINAL DATA; The original RDSnn data layer included all roads appearing on the official VT Agency of Transportation (VTrans) highway maps, with most road locations determined from RF 5000 orthophotos (or better). When road locations were not clear from the orthophotos, an accuracy code (RDSACC) was used to record uncertainty in the location. In cases where roads were built after the orthophotos were flown, locations were generally approximated based on VTrans maps. The accuracy of some road locations were improved in the EmergencyE911_RDS through the use of GPS technology (Enhanced 9-1-1 Addressing Project; microDATA 1996-1998). The original digitizing of the road centerline data was done by Greenhorne & O'Mara Inc., Deluth GA, 1991-92 using Arc/Info (VAX). Many subsequent updates have been made by Regional Planning Commissions, their contractors and VCGI using various digitizing techniques. MAINTENANCE; The original RDSnn data was historically maintained by VCGI (about 30 MB and 65,000 arcs statewide), with updates being performed by Regional Planning Commissions, their contractors, and VCGI. The intention is that the RDSnn data be maintained in a 'master', comprehensive layer from which other roads layers may be derived. VTrans will take on management responsibility for the layer in 1999. The EmergencyE911_RDS data layer has been "split off" from RDSnn and has become and independent coverage maintained by Vermont's Enhanced 911 Board. VTrans attributes in the EmergencyE911_RDS coverage (such as RTNO and CLASS) may not reflect "official" VTrans information. Users requiring the latest RTNO, CLASS, and other VTrans attributes should utilize RDSnn. Users who want road name and address range information should use EmergencyE911_RDS. Again, these two data layers are being maintained independently and therefore may not align spatially, even though they generally will in many cases (since they are based on the same original data set). The EmergencyE911_RDS data should not be clipped to a town boundary, since some attributes near the boundary will likely be improperly clipped. Instead, the MCODE or FIPS6 (added by VCGI) town code attribute can be used to extract arcs by town. Refer to E911\TBPOLY for a lookup table matching FIPS6 to MCODE and TOWNAME. E911 CONTRACTOR UPDATES; Updates to the data via the Enhanced 9-1-1 project have affected "private" roads. According to E-911 standards, a road coded as "private" in the RDS data will be considered a "private road" if it leads to 3 or more buildings (emergency sites - EmergencyE911_ESITE). However, if a road coded as "private" leads to two buildings or less, its considered a "driveway" and therefore has been moved to the EmergencyE911_DW (driveways) coverage. Driveways were not added to the EmergencyE911_RDS coverage because it would have split existing ARCs in too many places.
Completeness_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 line work 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, where road locations were not clearly visible on the photos, or roads that have been built since the orthophotos were taken). As noted by Chittenden County "It is estimated that centerlines fall within the tax right-of-way 99% of the time." Road arcs were edgematched at the orthophoto boundaries with a complex algorithm, based on the distance between arc endpoints in adjoining photos, and on the arc attributes. Adjustments were made at photo edges (both automatically and manually) when needed, so minimal line error may have been introduced at the photo edges in some cases. Also, short road sections (generally less than 1 cm equals 50 meters on the ground) were added when needed at the corners of the photos without reference to the source maps, but only in cases where the road location was obvious. CHANGES MADE BY E911 CONTRACTOR; The Enhanced 911 program's primary contractor collected new road locations and corrected inaccuracies in the old centerlines using GPS receivers in the field. These centerlines are generally expected to be within 5 meters of its true location, but variations in GPS data collection quality can create variable results. Last Update Was: 9/15/08
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 line work 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, where road locations were not clearly visible on the photos, or roads that have been built since the orthophotos were taken). As noted by Chittenden County "It is estimated that centerlines fall within the tax right-of-way 99% of the time." Road arcs were edgematched at the orthophoto boundaries with a complex algorithm, based on the distance between arc endpoints in adjoining photos, and on the arc attributes. Adjustments were made at photo edges (both automatically and manually) when needed, so minimal line error may have been introduced at the photo edges in some cases. Also, short road sections (generally less than 1 cm equals 50 meters on the ground) were added when needed at the corners of the photos without reference to the source maps, but only in cases where the road location was obvious. CHANGES MADE BY E911 CONTRACTOR; The Enhanced 911 program's primary contractor collected new road locations and corrected inaccuracies in the old centerlines using GPS receivers in the field. These centerlines are generally expected to be within 5 meters of its true location, but variations in GPS data collection quality can create variable results.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Database Administrator
Publication_Date: 19980823
Publication_Time: unknown
Title: RDSnn
Edition: 1999
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: Road centerlines from RF 5000 orthophotos and GPS
Issue_Identification: 1999
Publication_Information:
Publication_Place: Waterbury, VT 05620-6501
Publisher: Database Administrator
Other_Citation_Details: RDSnn
Online_Linkage: <http://www.aot.state.vt.us/>
Source_Scale_Denominator: 5000
Type_of_Source_Media: Digital media, GPS & paper maps.
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20080915
Time_of_Day: unknown
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: RDSnn
Source_Contribution: Vermont Agency of Transportation (VTrans)
Process_Step:
Process_Description: N/A
Process_Date: 19990000
Process_Time: Unknown
Process_Step:
Process_Description: Updated shapefile provided by contractor
Process_Date: 20000513
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20010320
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20010430
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20010626
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20010926
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20011025
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20011218
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20020416
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20020722
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20020823
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20021021
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE & TOWN. Operator - Mike Brouillette, VCGI
Process_Date: 20021209
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20030211
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20030415
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20030606
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20030910
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20031111
Process_Time: Unknown
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20040204
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20040406
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20040629
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20041101
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20050111
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20050309
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20050523
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20050923
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20060103
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20070125
Process_Step:
Process_Description:
Action; Bi-monthly QAQC of revised shapefile provided by E911 contractor. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20070312
Process_Step:
Process_Description:
Action; Posting of intermediary data architecture until the 9-1-1 database is "flattened" in summer of 2008. Update documentation for maintenance release. Data is tiled by STATE. Operator - Mike Brouillette, VCGI
Process_Date: 20080212
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\DOCUME~1\MIKEB~1.VCG\LOCALS~1\Temp\xml5B6.tmp
Spatial_Data_Organization_Information:
Indirect_Spatial_Reference: LINE
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 62877
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.000000
Longitude_Resolution: 0.000000
Geographic_Coordinate_Units: Decimal degrees
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: 0.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: EmergencyE911_RDS
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: AT_ID
Attribute:
Attribute_Label: UPDTSRC
Attribute_Definition: Person who last updated the record.
Attribute_Definition_Source: e911 maintainer system
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: UPDTDT
Attribute_Definition: Date of last update.
Attribute_Definition_Source: e911 maintainer system
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: ONEWAY
Attribute_Definition:
0 or - or (blank) = not one way, Y = one way in the direction of the arc. X = One way in the opposite direction of the arc.
Attribute_Definition_Source: microDATA
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: RTNO
Attribute_Definition:
Primary route number. The RTNO route number corresponds to the official number on the VAOT highway maps. State and federal numbers will be unique for that highway for the entire state, while town numbered highways will only be unique to that town. '-' is used for a blank (no data) value. The RTNO field must not be empty. Where a route has two route numbers (as shown on road signs), the more local number is used. For example, a route having both a State route number and a town route number is assigned the town route number (as shown on the VTrans highway maps). Use the RDSnn coverage for the latest "official" VTrans road attributes.
Attribute_Definition_Source: VT Agency of Transportation highway maps
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: ROUTE
Attribute:
Attribute_Label: ARCID
Attribute_Definition:
Arc identifier, unique statewide. The ARCID is a unique identifier for every ARC in the EmergencyE911_RDS data layer.
Attribute_Definition_Source: Assigned by E911
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: RDNAME
Attribute_Definition:
Road name number (match to ROADNAMES.DBF). Road names are stored as an integer code in RDNAME, referencing look-up table E911\OTHER--> ROADNAMES.DBF. An integer code is used to minimize the space required for the road centerline attribute table. Its also minimizes the potential of misspellings from one arc to the next. Each named road will have a unique RDNAME. The RDNAME number has the following format --- MCODE + UNIQUE_ROADNAME_NUMBER
Attribute_Definition_Source: Assigned by E911
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: MCODE
Attribute_Definition: Municipal town code.
Attribute_Definition_Source: microDATA
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: SURFACE
Attribute_Definition: Attribute may not be maintained.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: Hard Surface (paved)
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition: Gravel
Enumerated_Domain:
Enumerated_Domain_Value: 3
Enumerated_Domain_Value_Definition: Soil or drained earth
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition: Unimproved/Primitive
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition: Impassable/Untraveled
Enumerated_Domain:
Enumerated_Domain_Value: 9
Enumerated_Domain_Value_Definition: Unknown
Attribute:
Attribute_Label: STREETCLASS
Attribute:
Attribute_Label: GPSUPDT
Attribute_Definition: Field GPS effort needed.
Attribute:
Attribute_Label: LR
Attribute_Definition: Lower Right
Attribute:
Attribute_Label: MILES
Attribute:
Attribute_Label: LLO
Attribute_Definition: Low address for left side of road.
Attribute_Definition_Source: Various
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: LHI
Attribute_Definition: High address for left side of road.
Attribute_Definition_Source: Various
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: RLO
Attribute_Definition: Low address for right side of road.
Attribute_Definition_Source: Various
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: RHI
Attribute_Definition: High address for right side of road.
Attribute_Definition_Source: Various
Attribute_Domain_Values:
Unrepresentable_Domain: n/a
Attribute:
Attribute_Label: SEQ
Attribute:
Attribute_Label: GF
Attribute_Definition: Grand Fathered.
Attribute:
Attribute_Label: STREET
Attribute:
Attribute_Label: LESN
Attribute_Definition: Left Emergency Service Zone number.
Attribute:
Attribute_Label: RESN
Attribute_Definition: Right Emergency Service Zone number.
Attribute:
Attribute_Label: RTWN
Attribute_Definition: Right Town.
Attribute:
Attribute_Label: LTWN
Attribute_Definition: Left Town.
Attribute:
Attribute_Label: RZIP
Attribute_Definition: Right Zip code
Attribute:
Attribute_Label: LZIP
Attribute_Definition: Left Zip Code.
Attribute:
Attribute_Label: FROMRIGHT
Attribute:
Attribute_Label: FROMLEFT
Attribute:
Attribute_Label: TORIGHT
Attribute:
Attribute_Label: TOLEFT
Attribute:
Attribute_Label: RCITY
Attribute:
Attribute_Label: LCITY
Attribute:
Attribute_Label: PD
Attribute_Definition: Prefix Direction, previously name PRE.DIR.
Attribute:
Attribute_Label: PT
Attribute_Definition: Prefix Type
Attribute:
Attribute_Label: SN
Attribute_Definition: Street Name. Previously named STREET
Attribute:
Attribute_Label: ST
Attribute_Definition: Street Type
Attribute:
Attribute_Label: SD
Attribute_Definition: Suffix Direction, i.e., W for West, E for East etc.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: JOINID
Attribute:
Attribute_Label: Shape_Length
Attribute_Definition: Length of feature in internal units.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Positive real numbers that are automatically generated. Overview_Description:
Entity_and_Attribute_Overview:
Data layers derived from or associated with the RDS data have all been named EmergencyE911_RDSn.
Entity_and_Attribute_Detail_Citation: n/a
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: EmergencyE911_RDS
Distribution_Liability:
VCGI and the State of Vermont make no representations of any kind, including but not limited to the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the data.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: 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/default.cfm?layer=EmergencyE911_RDS>
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:
Time_of_Day: unknown
Metadata_Reference_Information:
Metadata_Date: 20081002
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Database Administrator
Contact_Organization: Enhanced 9-1-1 Board
Contact_Position: Manager
Contact_Address:
Address_Type: Mailing and Physical Address
Address: 94 State Street - Drawer 20
City: Montpelier
State_or_Province: VT
Postal_Code: 05620-6501
Country: USA
Contact_Voice_Telephone: 800-342-4911
Contact_TDD/TTY_Telephone: None
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
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.7.24 on Thu Oct 02 13:16:40 2008