SGID Street Centerline Update 5/19/2009 PDF Print E-mail

Written by Kelly Green,

The following update has been made to GIS data residing on the State Geographic Information Database’s ArcSDE server, gdb93.agrc.utah.gov (v9.3):

The SGID SGID93.TRANSPORTATION.Roads (known as U024.Transportation.StatewideStreets in the SGID 9.2 Database) feature class has been updated on the SGID ArcSDE Database Server. Shapefiles and File-Based Geodatabase files for Roads are available for download on the SGID FTP site. Geocoding services, ArcIMS Applications, and ArcGIS Server Applications & Web Services are now using this new data.

County Updates: 

  • San Juan: Received centerline update 3/30/09: updated entire dataset; geocoding improvements
  • Sevier: Received centerline update 2/4/09: new roads added; geocoding improvements
  • Tooele: Received centerline update 12/17/08: new roads added; geocoding improvements
  • Washington: Received centerline update 3/2/09: new roads added; geocoding improvements
  • Utah: Received centerline update 1/21/09: new roads added; geocoding improvements
  • Weber: Received centerline update 5/5/09: new roads added; geocoding improvements

UDOT Route System:

Significant updates have been made to the attributes that describe the UDOT state and federal routes: 

New fields were added and populated to enable UDOT to begin to store its state route attributes within the UTDM. The fields added for this purpose are: DOT_RTID (internal UDOT LRS route unique identifier), DOT_RTNAME (5 digit UDOT LRS route name, example: I-15 NB is stored as 0015P where P is the positive direction), DOT_RTPART (for concurrent or broken routes, example: US 191 is composed of 3 parts where it is the primary route).
 
New fields were added and populated to enable Route and Milepost location lookup. Together with DOT_RTNAME (described above), DOT_F_MP, DOT_T_MP were added to store the from and to milepost range for each feature that is part of a state or federal route. With a route and milepost location (0015P, mile 312.456), a locational coordinate can now be derived through a simple query and interpolation (geocoding). At present, milepost values have been derived using the route beginning and end points as milepost locations were not available statewide at a high enough level of precision. A polylineM-based route feature class "SGID.Transportation.UDOTRoutes_CalibratedEP" is also available for those wanting to use linear referencing tools to locate events along the route network.
 
Notes on UDOT Route Attributes: ALT_NAME is still the best attribute to pull the state highway system for cartographic purposes as it includes the ramp and collector systems which have not been coded in the new DOT attribute fields at this time. The ALT_NAME field was corrected to agree with the DOT_RTNAME field for all features that were not ramps or collectors. In addition, UDOT routes 0282P-0312P and 0314P-0320P are institutional and state park roads and did not receive an ALT_NAME value as they are not major thoroughfares like the rest of the UDOT routes. AGRC plans to continue to work with UDOT in the coming months to incorporate additional system features including ramps, collectors, and B and C roads into the new attribution scheme.


Blue Stakes of Utah Feedback:

  • Wasatch: geocoding improvements
  • Duchesne: geocoding improvements
  • Uintah: geocoding improvements

Users' Comments  
 

No comment posted

Add your comment

01, Jun. 2009
Last Updated ( 08, Jul. 2009 )
 
< Prev   Next >

AGRC Contacts | UGIC Contacts

feed image feed image

Utah GIS Portal © 2010 AGRC

Optimized for