To edit the Wiki, please login with the same username and password as WME and the forum. Visit the forum for editing guidelines and discussions.

Utah

From waze
Jump to: navigation, search


USA Utah.png

This page serves as the primary resource for editors of Utah. Review all the sections to better understand how the guidelines for this state might deviate from the overall USA or worldwide guidelines. If you have any comments or questions about this page or state refer to the community links below.

If you edit in Utah, please make sure you add yourself to the table below.

Functional Classification updates are Complete, as of Jan 10, 2015!


Introduction

Utah is a part of the Southwest region, which includes the states and/or territories of:

Arizona / California / Colorado / Hawaii / Nevada / New Mexico / Utah.

Thank you for your interest in editing the Waze maps for the State of Utah. Please note Utah follows the US national guidance with a few exceptions. Be sure to click on and read every link from this page for in-depth tips, guidance and advice.

All editors should have a real username, not a usa_username and are required to have their private messaging turned on.

Refer to the Glossary for common Waze related terms.


Mapping resources

Media-book-and-disc.png

Before editing the maps in Utah, be sure to fully review and understand the editing manual.

The Waze user community follows the Waze etiquette guidelines discussed in the Wiki. Be sure to familiarize yourself with these guiding principals while editing the maps and this Wiki, as well as when communicating with other Waze users.

Functional Classification

Utah counties map.png

Utah follows the Functional Classification (FC) system for both state and non-state roads. This change from the previous road-typing guidance was changed in September 2014. As of January, 2016, all counties in Utah have been updated to the new standard.


Statewide

County GIS Data

This is a collection of County maps, along with state maps focused on counties that do not maintain separate mapsets.


Alternate Source for GIS information: Check the State Parcel map and zoom into the county/town in question.

WME Scripts

Useful scripts to help you start your WME carrier. Please read the General installation instructions before installing scripts.



Community

People-in-forum.png

The Waze forum is a great place to find answers to previously asked questions and also a place to ask new ones. Below are links to the forums specific to Utah.

Area Managers for Utah can be found in the table below.

New editors should consider checking into the formal mentoring program available at no charge.


Cities and towns

House.png

One of the most common errors when editing the maps is when an editor creates a road and does not confirm the road by setting the city and road name (or stating it has none).

Duplicate cities can be caused by incorrectly named segments and should be corrected following the guidelines in the duplicate cities article.


Some states and territories manage a separate page on cities and towns to identify the specific city names that should be entered, and no others. For states that do not have a separate page to track the names, see this Wikipedia link and find the state or territory in question.


Major roads

4lane road icon.png

Utah follows the general road naming and road type guidelines of the USA.

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.

A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current US road type standards.

Utah locking standard
Segment Type Urban  Rural
 Freeway  5
 Ramp  4
 Major Highway  4 3
 Minor Highway  3 2
 Primary Street  2
 Street  1
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5
UTUL.png
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).

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.


Functional Classification

Functional Classification Implementation is complete in Utah.

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

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   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.

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 County Link Reason Approved
SR-59 Washington Link Corrects routing from US-89 to I-15 RC


Special roads

Drivable roads

Utah follows the standard USA guidelines for all of the following special road types.

Non-drivable roads

Review the Wiki guidelines for non-drivable roads to ensure compliance with the general guidelines.

Railroads

When mapping Railroad/Light Rail tracks, please keep the following information in mind (from the Railroad wiki page):

Use the following guidelines when mapping railroad segments:

  • If you do not know the owner of the railroad tracks, enter "Railroad" for the street name of every railroad segment.
  • Always select "None" for the city name. This avoids city smudging.
  • Lock the segment at L2.
  • Do not map railroads below ground, as they do not serve any of the three purposes outlined above. This is especially true in urban areas where underground rail lines are common, and their appearance on the map would be confusing to drivers.
  • Set the elevation just as you would a drivable segment. When tracks junction a road on the ground, the Elevation should be set to Ground.
  • Create junctions between drivable roads and railroads.[rr]
  • Set railroad to 2-way directionality
  • Restrict turns to and from the railroad segments.
  • When mapping railroad tracks, focus on those near drivable roads.
  • Map rail yards simply, with one railroad segment along either edge of the yard's tracks.
  • Map industrial spurs only if they cross drivable roads.
  • Do not map every piece of parallel track, such as in sidings or yards, or industrial spurs that don't cross any roads. Your work may otherwise be seen as clutter, much like mapping every parking lot row.
  • Multiple parallel lines at crossings:
    • At most crossings, there should be only one railroad segment mapped and no more than two parallel railroads mapped at any crossing.
    • Parallel lines are to be at least 5m apart
    • In general, there is no reason to have multiple lines mapped. When not at a crossing, even four parallel lines can be easily mapped as a single railroad segment in Waze.
  • Keep segment lengths under 10,000 meters – the longer the segment length, the more sluggish the editor is to respond to changes.
  • Do not map railroads using a drivable road type (streets, primary streets, etc.); it could be a hazard to human life if drivers were routed to them.

^rr Note: The routing server will properly account for delays at railroad crossings through a segment without a junction. However, with a junction, the historical data for the rail crossing will be more accurate.

Walking Trails

They should only be used in rare cases. Walking Trails may have strange side effects on nearby routing. Never use the Walking Trail road type for ordinary hiking paths or bike paths. Most hiking and bicycling paths should not be on the map at all.

The WME lists the Walking Trail road type as non-drivable. Historically, editors have disconnected Walking Trails to make sure Waze doesn't route drivers over them. This doesn't always work as desired. If a disconnected Walking Trail comes closer to a destination than any other road, Waze may route drivers to a location nearer to the Walking Trail than to the destination. This problem can be severe for Walking Trails passing close to many destinations in a dense neighborhood. Connected or not, the Walking Trail type should never be used where effects on local routing are not desired.


Dirt Roads 4x4

Utah follows the following functional classification for Gravel and Dirt Road /4x4 trails.

 Gravel Roads 
Functional Classification
Minor Arterial  Minor Highway 
Minor Collector  Primary Street 
Local/Not Mapped  Street 
USFS-level3a.jpg


 Dirt Road / 4X4 Trail 
Functional Classification
Minor Arterial  Dirt Road / 4X4 Trail 
Minor Collector  Dirt Road / 4X4 Trail 
Local/Not Mapped  Dirt Road / 4X4 Trail 
USFS-level2b.jpg

Images demonstrated above can not cover all scenarios for mapping maintenance level to Waze road type. These types of roads may undergo variation in quality over seasons additionally depending on the climate (rain/snow). Particularly, some gravel roads may have qualities that are closer to Dirt Road / 4x4 Trail than street. Editors with local experience or potential Street View images may help in this determination.


Driveways / Private Roads

Please follow the following guidelines for Private Driveways. Wiki standard can be found here. Driveways


Mapping rural diveways

  • If an address/location cannot be reasonably guided to without a private drive, it can be added.
  • Single house at the end of a 1mi (1609m) private drive, and that's the only house, it probably isn't needed.
  • If it's 5 houses at the end of a single shared 1/4mi (402m) long private drive, it probably is needed.
  • If it's a house at the end of a 500m (1640 ft) long private drive which is right up against another street from which you cannot access the address (stop point will be on the segment closest), then a private drive is probably needed.




Closures

When managing a section of roadway under construction or being closed for a major event, follow the Wiki guidelines on construction zones and Real time closures.

Road Closures

You can follow UDOT Traffic on Twitter to stay up to date on the latest traffic conditions and road closures.


This section contains details about road closures, mainly state highways, but can contain City, Urban and Rural streets in the state of Utah. If you perform a road closure at any time please use the Waze Closures form and report all closures here.

UDOT maintains a Traffic Information center with all known closure/incident information included.


Places

Utah follows the USA standard for Places. Do not deviate from the guidelines without first obtaining consensus to do so via the state forum linked on this page.

Minimum Acceptable Information

All Places added to the map must contain the following entries:

  • Proper Category
  • Place Name
  • Address (including address numbers)
  • Placed in the correct location on the map

This is the minimum acceptable amount of information for inclusion on the map.


Locking Standard

Utah Place Lock Level Standards
PLACE TYPE LOCK LEVEL
Military Installation / Airport 4
Hospitals / Urgent Care / Police & Fire Dept 4
National & State Parks and Monuments 4
Gas Stations / Charging Stations 3
Schools / Universities / Colleges 3
Government Buildings / Consulates 3


All Places that have complete information (to include, at a minimum, address/city, hours of operation, phone number) are to be locked at Level 2. This is to prevent loss of data due to automatic acceptance of Place Update submissions from Trusted Users, or Place Update Request approvals from other editors without careful examination.
If you do not have a high enough enough rank to lock the place as indicated, please lock it as high as you can, and notify a higher rank AM, SM, CM, or Champ to lock it higher.


Area Editing

Area Mapping
When creating an Area, map it to the "fence line" of the area.

For instance, if you are mapping a shopping center, this means that you map the area to cover the shopping center buildings, and the parking lots out to the outer ring road (if applicable). If there is no ring road, or for smaller shopping centers, map to the curb line.

If you are mapping a school, you would map out to the fence line (if visible) or to a reasonable distance from the school. Contact a AM, SM, CM, or Champ for assistance.

Hospitals / Urgent Care
Hospitals with Parking, ER, and Ambulance Entrance mapped.
A special Category of Hospital / Medical Center is used for Hospitals, Medical Centers and Urgent Care facilities. ONLY Hospitals, Emergency Rooms, and places offering Urgent Medical Care should use this category. Clinics, and Medical offices which do not offer urgent medical care for Walk-Ins should use the Office, and any other appropriate category, instead.

When you map a hospital, or medical center, you need to map the following additional areas/points, as appropriate for your facility.

  • The Hospital itself (map it to the fenceline, or to an extent that you feel is appropriate)
    • Make sure you set the Navigation Stop point over the main entrance.
  • The Emergency Room Entrance (Set a Point Place)
  • Emergency Room Ambulance Entrance (if this is separate from the public entrance)
  • Hospital Parking (This may also include a separate Emergency Dept parking lot, if necessary)
What do I name It?

When you map a hospital/medical center, you need to name it with the official name ("Primary Children's Hospital" for example). However, you can add alternate names as well. The official website for the facility will have the actual name.

When you name the Emergency Room entrance, as well as any other points on the complex, please use the following formula of "specific name - hospital name":

  • Hospital Name (on main Area Place)
  • ER - Hospital Name
  • ER Ambulance Entrance - Hospital Name
  • Labor & Delivery - Hospital Name
  • Outpatient Entrance - Hospital Name

...and so on.

Layered Areas

Places which are part of a larger encompassing place (i.e. place points for lot in a university area, Separate ER entrances in a hospital area, stores in a shopping mall, etc.) should be named with their unique name followed by a hyphen and the name of the larger area they belong to. For example, "ER - Generic Medical Center"

Parking Lots

The Parking Lot Place marks a well-defined area constructed for off-street public parking, including parking structures and garages as well as at-grade lots. There are many elements that must be considered before deciding to map a parking lot. Currently, the details are covered in Places/Parking lot.

Unless you have permission from the State Manager, please only map the following types of parking lots:

  • Public parking lots (Indicate that they are public lots in the description)
  • Named lots around an arena/theater/venue (advise SM when you do these)
  • Park and Ride lots/structures

Mass Transit parking structures should be mapped as Parking Lots, with the additional categories of "Train Station" and "Transportation" added. Additional, the Area should cover the actual station and platform, not just the parking lot/garage.



Cameras

Not every camera-looking device at an intersection is a speed or red light camera. Generally speaking:

  • Camera2true.png
    Rlc truvelo speed cam.jpeg
    a speed camera takes a photograph of a vehicle when it passes by the camera at too high a speed.
  • Camera4true.png
    Rlc white.jpeg
    a red light camera takes a photograph of a vehicle that enters an intersection after the light is red. In some areas, it takes the photograph when a vehicle is not clear of the intersection some period after the light turns red.

Be sure to know your cameras before accepting new camera reports.

Currently only the Waze client app can add cameras to the map. When adding a camera from the app, be sure to review the camera placement recommendations.

Laws regarding speed and red light cameras vary between the states and territories, so be sure to understand the details of camera legality in Utah.



Based on information researched at the time this page was created, red light and speed cameras are illegal statewide in Utah.

No other camera types should be mapped in Waze.

Speed Cameras and Red light Cameras are NOT CURRENTLY USED in the State of Utah. Or more specifically the restrictions on use are strict enough that no entity is using Speed Cameras. The reason is that unlike most states that allow such devices, Utah's law requires that a certified Law Enforcement Officer must personally approve each ticket at the time of the infraction.


To do list

To do list.png

Many states and territories keep an active list of pending or closed actions that need to be done in the state by the editors. All editors are welcome to contribute to the list of activities.


This state does not currently have an active "to do" list at this time. Check in the Utah section of the Waze forums to discuss creating one.


Other


Working with URs

Utah has adopted a 36hr/4/7 day standard when dealing with User Requests.

Request pin open-low.png
Our goal is to respond to new URs within 36 hours. Fix the issue and solve the UR (if within our control, and identifiable), or solicit additional needed information from the reporter.
Request pin open-med.png
If there is no response from the reporter within 4 days, "bump" the request with a reminder message.
Request pin open-med.png
If there is a response from the reporter, and a conversation starts about the error and how to resolve it, the 7 day clock starts over.
Request pin open-high.png
Resolve URs that have no response to comment in 7 days, or are completed. NEVER close a UR without leaving a closing comment, even if it's something as simple as "No info received, closing."


When responding to URs, please remember the wise words of the scholar, brevity is the soul of wit.

More than likely, the user is going to be reading your response in the Waze App, so try and keep it as short as possible, while still conveying the information, or request desired.

Before working with URs, you should review the Wiki documentation on URs and especially the section on etiquette.


Don't be this guy.

Live Users

If you're editing in Utah, we ask that you turn on the LIVE USERS layer in the editor. If you see another editor show up where you are editing, and move around you, please check WME Chat. Also, check and see if you have a Private Message (PM) in the Forum.

There may be an issue with the area you're editing in, or what you are doing.

Never Be Unreachable!


Area Managers

The table below identifies the editors also designated as Area Managers or higher who are editing in Utah. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers Utah, or a USA Country Manager that does a lot of work in Utah, please add yourself to this list (alphabetical by username) in the correct rank section.

The editor who also serves as the Regional Coordinator for Utah is automatically listed at the top of the table. That editor may not be highly active in this state and therefore may not be listed separately in the table.

Utah — Area, State and Country Managers
Regional Coordinator(s): jemay (PM)
Username
"
  GHO Name
Area Managed Comments
Country Managers (Southwest region)
(Add to or edit Country and State sections of table)
daknife(6) [PM] Profile L6.png Statewide If there is a Problem, Yo I'll Solve it!
Dmcrandall(5) [PM] Profile L5.png
Avatar Dmcrandall.jpg
  David
Country Wide Badge Mentor.pngBadge CountryManager.pngBadge MapRaider.png
US Country Manager
State Managers (Southwest region)
Area Managers
(Add to or edit this section)
mwburn(5) [PM] Profile L5.png Logan Area I edit statewide
Josephaw(3) [PM] Profile L3.png Salt Lake to Sevier County
Thewebdiggity(3) [PM] Profile L3.png Salt Lake Metro Area Roy to Point of the Mtn
DustinHetzel(2) [PM] Profile L2.png Statewide


The following editors are also editing in the state and may be working towards an Area Manager position. Feel free to contact them for assistance in their respective areas.

Other Area Editors (Add to or edit this section)
Username General Editing Area Comments
Chasing_Blue_Sky(4) [PM] Profile L4.png SLC Metro Area
jellicle0(2) [PM] Profile L2.png SLC Metro Area
Marnoot(2) [PM] Profile L2.png SLC Metro Area
Ohbewise(2) [PM] Profile L2.png SLC Metro Area
SkyviewGuru(4) [PM] Profile L4.png Near I-15 between ID and SLC Badge StateManager.png
Idaho State Manager


Other states and territories

USA CommonState.png
The other states and territories of the USA can be found in the navigation box below. Press the "show" button to open the box.


About this page