Utah/Major roads/Main: Difference between revisions View history

(→‎Major_roads/Main: Added Urban Lock Area description.)
m (→‎Major_roads/Main: Correcting usage of "split")
 
(10 intermediate revisions by 5 users not shown)
Line 2: Line 2:
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  


==== State Highway Naming ====
=== State Highway Naming ===


The approved format for State Highway naming in {{RootPage2}} is:  '''SR-##'''
The approved format for State Highway naming in {{RootPage2}} is:  '''SR-##'''


==== Locking Standard ====
=== Locking Standard ===
{{Lock Standard State|UT}}
{{Lock Standard State|UT}}


[[File:UTUL.png|200px|thumb|right]]Please reference the map to the right for areas included in the Urban Lock level. The Urban Lock Level area includes all of the follow counties:  Salt Lake County, Davis County, Weber County, Morgan County, Cache County, and portions of Utah County (Everything W of Thistle Junction (US-6/US-89 Jct), Tooele County (including the city of Tooele), Box Elder County, and the northern tips of Juab County (to include Mona and Eureka/Mammoth areas).
=== Functional Classification ===


All metro areas west of the Wasatch Front, out to the western edge of the Great Salt Lake are included in the Urban Lock area.
Please refer to this forum topic for more information on FC - [http://www.waze.com/forum/viewtopic.php?f=276&t=85397 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.


==== Functional Classification ====
==== UT to Waze FC conversion ====
See [[{{BasePage2}}/Major roads]] for {{RootPage2}} Functional Classification guidelines.
 
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.
 
===== Resource Links =====
 
* UDOT [http://www.arcgis.com/home/webmap/viewer.html?webmap=494d57208ea4464bb664ac2da38f9c91 Interactive Functional Classification Map] - ArcGIS
* UDOT [http://www.udot.utah.gov/main/f?p=100:pg:0::::V,T:,1226 Functional Classification Maps] by County (PDF Format) (May be out of Date)
 
===== UDOT GIS class and color description =====
[[File:UTFC.png|left|GIS Legend]]
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.
{{clear}}
 
==== UDOT to Waze conversion table ====
 
 
<div style="font-size:smaller">
{| border="1" style="border-collapse:collapse; text-align:center"
! scope="row" rowspan="2" colspan="2"|
! colspan="7"| <big>Highway Systems</big>
|-
! Interstate
! Interstate Business Loop/Spur
! US Hwy (incl. some [[wikipedia:special routes|special routes]])
! State Hwy (incl. some special routes)
! State Hwy BUS, SPUR, LOOP<ref>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.</ref>
! Locally-maintained
|-
|
| ''example>>>>>''
| I-15 N
| I-15 BUS
| US-89
| SR-28
| SR-24 Spur
| Fremont St
|-
! scope="row" rowspan="7" style="width:28px"| <big>F<br>u<br>n<br>c<br>t<br>i<br>o<br>n<br>a<br>l<br> <br>C<br>l<br>a<br>s<br>s</big><!-- Temp placeholder -->
| {{Road | style = color: black; background-color: #ffffff; border-color: #5ed6ff | Interstate (1) }}||{{Freeway|Fw}}||n/a||n/a||n/a||n/a||n/a
|-
| {{Road | style = color: black; background-color: #e2c54c; | Other Freeway/Expy (2)}}||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}
|-
| {{Road | style = color: white; background-color: #ff0000; | Other Principal Arterial (3)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}
|-
| {{Road | style = color: black; background-color: #7cd0b2; | Minor Arterial (4)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}
|-
| {{Road | style = color: white; background-color: #d14cff; | Major Collector (5)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}
|-
| {{Road | style = color: black; background-color: #ffff00; | Minor Collector (6)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}
|-
| {{Street|Local (7)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}<ref>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.</ref>||{{Primary Street|PS}}||{{Street|Street}}
|}
 
 
References: {{reflist}}
</div>
 
If you encounter a specific type of road (Interstate/US Hwy Business route, etc) that is not shown, reference the main [[Road types#Quick_reference_chart | FC Quick Reference chart]]
 
==== Functional Classification Exceptions ====
 
These roads have changed from the recommended Functional Classification for the reason noted.
 
{| class="wikitable"
|-
! Road Name !! New Type !! Area !! Link !! Reason !! Approved
|-
| SR-59 || Major Highway || Washington|| [https://www.waze.com/editor/?env=usa&lon=-113.05354&lat=37.08720&zoom=0 Link] || Corrects routing from US-89 to I-15 || [[User:Jemay|RC]]
|-
| SR-291 || Parking Lot Road || Ogden || [https://www.waze.com/editor/?env=usa&lon=-111.94511&lat=41.25086&zoom=6&mode=0 Link] || State facility parking lot roads || [[User:herrchin|SM]]
|-
| SR-296 || Street || American Fork || [https://www.waze.com/editor/?env=usa&lon=-111.77559&lat=40.39731&zoom=5&mode=0 Link] || State facility campus roads || [[User:herrchin|SM]]
|-
| SR-298 || Parking Lot Road || South Ogden || [https://www.waze.com/editor/?env=usa&lon=-111.96534&lat=41.16787&zoom=7&mode=0 Link] || State facility parking lot roads || [[User:herrchin|SM]]
|}
 
=== U-turns ===
 
U-turns are permitted in Utah where they are safe {{ref label|1|1}}, except where prohibited by signage or restricted by local municipal law. Legal U-turns includes those made from a two-way (i.e. shared) turn lane. {{ref label|2|2}}
 
U-turns on Primary Street through Major Highway type roads may be enabled in either of the following two circumstances (Do not enable U-turns on Street type roads):
 
#) The U-turn is ''explicitly'' allowed by signage; or
#) The U-turn is otherwise legal and safe, and there is ''at least'' 10.1 m (33 feet) from the left edge of the departure lane to the "destination" curb. This can include any median that may exist to the left of the departure lane. (The measurement is intended to accommodate the turning radius of most passenger vehicles.)
 
Do ''not'' make a point of enabling all U-turns valid under this guidance, only as you encounter them and they are necessary. For Waze routing, U-turns should only be enabled where they provide for improved routing, which includes recovering from missed turns. A common example is a median-divided primary street that has homes/businesses with their driveways/entrances directly on it, where reaching them would otherwise require lengthy, multi-turn deviations through side roads in order to end up on the correct side of the median.
 
Note that when editing, a functional U-turn can arise from more than just the u-turn flag on a road segment, such as with these common scenarios:
 
# Divided roads with box and partial-box intersections where the median segment is 15 m (49 feet) or longer.
# Divided roads with explicitly-mapped inside turn lanes unless the turn arrow in the u-turn direction is disabled.
 
{{note|1|1}} [http://le.utah.gov/xcode/Title41/Chapter6a/41-6a-S802.html | Utah Code 41-6a-802 (2)]
 
{{note|2|2}} [http://le.utah.gov/xcode/Title41/Chapter6a/41-6a-S801.html | Utah Code 41-6a-801 (3)(b)]
 
=== Speed Limits ===
 
Utah follows the Waze [[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 [https://le.utah.gov/xcode/Title41/Chapter6A/41-6a-S601.html 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 ====
* [http://utahvalley360.com/wp-content/uploads/2013/09/80-mph-Speed-Limit-Map1.jpg Year 2013 Fwy 80mph changes]
* [http://img.deseretnews.com/images/article/graphic/1440798/1440798.jpg Late 2014 Fwy speed changes]. [http://www.deseretnews.com/article/865615529/Wasatch-Front-freeway-speed-to-be-70-mph-but-UHP-not-in-favor.html?pg=all An article]. [http://www.sltrib.com/news/1821647-155/speed-limit-mph-udot-davis-increase Another article].
 
==== Useful Scripts For Editing Speed Limits ====
* [https://www.waze.com/forum/viewtopic.php?f=819&t=167387 WME Color Speeds]
* [https://www.waze.com/forum/viewtopic.php?f=819&t=178371 WME Context Menu]
* [https://www.waze.com/forum/viewtopic.php?f=819&t=166746 WME Speedhelper]
* [https://www.waze.com/forum/viewtopic.php?f=819&t=166497 WME Speeds]
 
=== Road Elevations ===
Utah practices "True Elevation" where almost all segments are set with elevation ''Ground'' unless they are passing over/beneath another segment, major waterway, or natural feature.
* 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.
* Only elevate/lower the actual bridge/tunnel section of the road.
* Bridges should be cut with a junction node at the start/end of the bridge where the land falls away. You can typically see guardrail at the start/end of the bridge section, an expansion gap in the pavement where the bridge starts/ends, and/or a pavement change (asphalt to concrete, for example).
* Don't create elevated bridges for water unless the waterway is of significance (i.e. don't bridge every 5 foot rural box culvert).
* Tunnels should be cut with a junction node at least 15m / 50ft before and after the tunnel, to allow time for the GPS to regain signal. Set the "Tunnel" checkbox as well.
* Do not cut 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." Also be aware of cutting segments "too close" (which is always relative) to an intersection.
* '''The use of common sense is paramount in using True Elevation.'''


<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----

Latest revision as of 23:28, 22 May 2021


State Highway Naming

The approved format for State Highway naming in Utah is: SR-##

Locking Standard

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.

Utah locking standard
Segment Type Statewide
 Freeway  4
 Ramp  Highest rank of connected segments
 Major Highway  3
 Minor Highway  2
 Primary Street  2
 Street  1
 • • • • Ferry • • • •   5
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2

Functional Classification

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.

Resource Links
UDOT GIS class and color description
GIS Legend
GIS Legend

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

Highway Systems
Interstate Interstate Business Loop/Spur US Hwy (incl. some special routes) State Hwy (incl. some special routes) State Hwy BUS, SPUR, LOOP[1] Locally-maintained
example>>>>> I-15 N I-15 BUS US-89 SR-28 SR-24 Spur Fremont St
F
u
n
c
t
i
o
n
a
l

C
l
a
s
s
  Interstate (1)    Fw  n/a n/a n/a n/a n/a
  Other Freeway/Expy (2)  n/a  Fw   Fw   Fw   Fw   Fw 
  Other Principal Arterial (3)  n/a  Major   Major   Major   Major   Major 
  Minor Arterial (4)  n/a  Major   Major   Minor   Minor   Minor 
  Major Collector (5)  n/a  Major   Major   Minor   PS   PS 
  Minor Collector (6)  n/a  Major   Major   Minor   PS   PS 
 Local (7)  n/a  Major   Major   Minor [2]  PS   Street 


References:
  1. 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.
  2. 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

U-turns

U-turns are permitted in Utah where they are safe [1], except where prohibited by signage or restricted by local municipal law. Legal U-turns includes those made from a two-way (i.e. shared) turn lane. [2]

U-turns on Primary Street through Major Highway type roads may be enabled in either of the following two circumstances (Do not enable U-turns on Street type roads):

  1. ) The U-turn is explicitly allowed by signage; or
  2. ) The U-turn is otherwise legal and safe, and there is at least 10.1 m (33 feet) from the left edge of the departure lane to the "destination" curb. This can include any median that may exist to the left of the departure lane. (The measurement is intended to accommodate the turning radius of most passenger vehicles.)

Do not make a point of enabling all U-turns valid under this guidance, only as you encounter them and they are necessary. For Waze routing, U-turns should only be enabled where they provide for improved routing, which includes recovering from missed turns. A common example is a median-divided primary street that has homes/businesses with their driveways/entrances directly on it, where reaching them would otherwise require lengthy, multi-turn deviations through side roads in order to end up on the correct side of the median.

Note that when editing, a functional U-turn can arise from more than just the u-turn flag on a road segment, such as with these common scenarios:

  1. Divided roads with box and partial-box intersections where the median segment is 15 m (49 feet) or longer.
  2. Divided roads with explicitly-mapped inside turn lanes unless the turn arrow in the u-turn direction is disabled.

^1 | Utah Code 41-6a-802 (2)

^2 | Utah Code 41-6a-801 (3)(b)

Speed Limits

Utah follows the Waze 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

Road Elevations

Utah practices "True Elevation" where almost all segments are set with elevation Ground unless they are passing over/beneath another segment, major waterway, or natural feature.

  • 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.
  • Only elevate/lower the actual bridge/tunnel section of the road.
  • Bridges should be cut with a junction node at the start/end of the bridge where the land falls away. You can typically see guardrail at the start/end of the bridge section, an expansion gap in the pavement where the bridge starts/ends, and/or a pavement change (asphalt to concrete, for example).
  • Don't create elevated bridges for water unless the waterway is of significance (i.e. don't bridge every 5 foot rural box culvert).
  • Tunnels should be cut with a junction node at least 15m / 50ft before and after the tunnel, to allow time for the GPS to regain signal. Set the "Tunnel" checkbox as well.
  • Do not cut 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." Also be aware of cutting segments "too close" (which is always relative) to an intersection.
  • The use of common sense is paramount in using True Elevation.