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:
Daggett: Received centerline update 9/17/09: new roads added; geocoding improvements
Millard: Received centerline update of addressed roads 8/27/09: new roads added; geocoding improvements
Salt Lake: Received centerline update of Emigration Canyon 9/8/08: updated entire dataset; geocoding improvements
Utah: Received centerline update 8/19/09: new roads added; geocoding improvements
UDOT Route System:
Statewide: Improvements were made to the geometry and attributes that describe the UDOT state and federal routes (DOT_RTNAME, DOT_F_MP, DOT_T_M). Also, the DOT_RTID field that stores the unique route identifiers was updated.
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:
Carbon: Received centerline update 4/7/09: new roads added; geocoding improvements
Davis: Received centerline update 4/21/09: new roads added; geocoding improvements
Garfield: Received centerline update 8/17/08: updated entire dataset; geocoding improvements
Kane: Received centerline update 5/20/09: new roads added; geocoding improvements
Morgan: Received centerline update 6/11/09: new roads added; geocoding improvements
Salt Lake: Received centerline update 7/1/09: new roads added; geocoding improvements
San Juan: Received centerline update from Blanding City 6/23/09: updated entire dataset; geocoding improvements
Summit: Received centerline update 5/13/09: new roads added; geocoding improvements
UDOT Route System:
Statewide: Improvements were made to the geometry and attributes that describe the UDOT state and federal routes (DOT_RTNAME, DOT_F_MP, DOT_T_M). Also, polylineM route geometry has been updated in the SGID93.Transportation.UDOTRoutes_CalibratedEPfeature class.
Update 8/13/2009: The link below pointed to the wrong file on our FTP site. If you've downloaded this from the link before today, you'll want to download again and replace your existing .loc file.
A new ArcGIS 9.3 compatible composite address locator is now available from the agrc ftp site.To download, right click on the link below and select Save Target As:
After saving this file, make sure the file extension is .loc NOT .loc.txt This a file-based locator file with a .loc extension. This small file references 4 address locators on the SGID ArcSDE database server and can be used from ArcCatalog or ArcMap. The composite locator references the SGID93.Transportation.StatewideRoads feature class and its S_NAME, ALIAS_1, ALIAS_2, and ACS_NAME fields.
It should not need to be rebuilt as changes are made to the SGID93.Transportation.StatewideRoads feature class . A high speed internet connection is necessary for this locator to perform adequately.
The SGID93.Transportation.StatewideRoads feature class contains several attributes to hold alias street names and address coordinate system (ACS) aliases. Examples.
Broadway is a street name alias for 300 S in Salt Lake City
Highway 68 is a street name alias for Redwood Road in SL County
1700 W is an ACS alias for Redwood Road in SL County
When setting up a standard address locator in ArcGIS, these fields are not taken into consideration in finding candidate locations for an address to be geocoded. A composite address locator allows for the alias and ACS alias data to be used to make a match when a match is not found when just considering the street name field (S_NAME).
Why is this being distributed as a file? Composite address locators do not currently work when stored within ArcSDE.
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.
