| The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.
Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.
- 1 State Highway Naming
- 2 Locking Standard
- 3 Functional Classification
- 4 Speed Limits
- 5 Road Elevations
State Highway Naming
The approved format for State Highway naming in Utah is: SR-##
In Utah we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
|Highest rank of connected segments|
Please refer to this forum topic for more information on FC - Road Types (USA) – comprehensive overhaul of drivable roads
The Utah Functional Classification system is on par with the Nationwide standard, and consists of 7 Road Types.
UT to Waze FC conversion
Utah's Dept of Transportation has made Functional Classification maps available online, in PDF format, for each county. They also provide an interactive statewide map.
- UDOT Interactive Functional Classification Map - ArcGIS
- UDOT Functional Classification Maps by County (PDF Format) (May be out of Date)
UDOT GIS class and color description
The Utah Classification and Color scheme come from the official Utah D.O.T (UDOT) Functional Classification (FC) map that is published by UDOT. The legend shows what classifications UDOT uses and what color is assigned to each class.
UDOT to Waze conversion table
|Interstate||Interstate Business Loop/Spur||US Hwy (incl. some special routes)||State Hwy (incl. some special routes)||State Hwy BUS, SPUR, LOOP||Locally-maintained|
|example>>>>>||I-15 N||I-15 BUS||US-89||SR-28||SR-24 Spur||Fremont St|
- When a state highway "SPUR" route is used to connect a state highway with another state highway, a US highway, or an Interstate (i.e., when it is used as a connector/CONN route), use the first state highway column.
- All FC "Local" roads with a State Route designation (SR-XXX) discovered so far have been local roads serving a state facility campus, and are more appropriately typed as Primary Street, Street, or even Parking Lot Road. Check with a state manager for any of these.
If you encounter a specific type of road (Interstate/US Hwy Business route, etc) that is not shown, reference the main FC Quick Reference chart
Functional Classification Exceptions
These roads have changed from the recommended Functional Classification for the reason noted.
|Road Name||New Type||Area||Link||Reason||Approved|
|SR-59||Major Highway||Washington||Link||Corrects routing from US-89 to I-15||RC|
|SR-291||Parking Lot Road||Ogden||Link||State facility parking lot roads||SM|
|SR-296||Street||American Fork||Link||State facility campus roads||SM|
|SR-298||Parking Lot Road||South Ogden||Link||State facility parking lot roads||SM|
Utah follows the Waze USA speed limits guidance. Please read that page carefully before editing any Speed Limits (SLs).
Utah does not alter speed limits for temporary reductions such as school zones or work zones, unless the work zone duration will exceed 3 months and the signs present are fixed-speed and on permanent style mountings (no digital variable speed limit signs, no portable signs).
Speed Limit standards
The following are the speed limits laws of Utah, except where posted signs indicate differently (higher or lower speed limits).
- Urban district: 25 mph.
- All other locations: 55 mph.
Speed Limit Resources
Useful Scripts For Editing Speed Limits
Utah practices "True Elevations" where almost all segments are set with elevation "Ground", unless they are passing over/beneath another segment or major waterway.
- Drivable and non-drivable (Railroad, etc.) segments are handled by the same rules.
- Only segments that "cannot see the sky" should have negative elevation (e.g. tunnels, underground parking garages)
- Only set elevation as high as necessary, with the relative elevations representing the true physical relationships. Example: Nothing should be +2 unless it is crossing over a +1 segment, which is crossing over a Ground level segment.
- If you use the Bridge tool to join segments, be aware that it raises the elevation of the newly-joined segment. Lower the joined segment as appropriate.
- The "Seagull" guidelines apply to elevations in Utah, though the nomenclature "True Elevation" is preferred.
- Only elevate/lower the actual bridge/tunnel section of the road.
- Bridge segments should be split with a junction node at both the start and end of the bridge. Don't create elevated bridges for water unless the waterway is of significance (i.e. don't bridge every 5 foot rural creek).
- Tunnels should be split with a junction node at least 15m before and after the tunnel, to allow time for the GPS to regain signal. Set the "Tunnel" checkbox as well.
- Do not split segments for elevation purposes if the bridge/tunnel starts/stops within 60m/200ft of an existing junction. Re-use that junction that is "close enough."