ArcGIS REST Services Directory
JSON

Layer: FS_VCGI_OPENDATA_Emergency_RDS_line_SP_v1 (ID:0)

View In:   Map Viewer

Name: FS_VCGI_OPENDATA_Emergency_RDS_line_SP_v1

Display Field: PRIMARYNAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: 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. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. http://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfm

Copyright Text: E911

Min. Scale: 0

Max. Scale: 0

Default Visibility: false

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: true

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field: GlobalID

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 8/14/2025 9:45:37 AM

Schema Last Edit Date: 8/14/2025 9:45:37 AM

Data Last Edit Date: 8/14/2025 9:45:37 AM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat