This page serves as the primary resource for editors of Minnesota. 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.
- 1 Introduction
- 2 Mapping resources
- 3 Statewide Minnesota
- 4 Community
- 5 Cities and towns
- 6 Major roads
- 7 Special roads
- 8 Closures
- 9 Update Requests
- 10 Unlock Requests
- 11 Places
- 12 Cameras
- 13 To do list
- 14 Area Managers
- 15 Other states and territories
- 16 About this page
Minnesota is a part of the Plains region, which includes the states and/or territories of:
Before editing the maps in Minnesota, 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.
|Replace this template message with specific information unique to the state. If the information is more than a screen full, consider moving it to a full subpage. Minimally the following link is required to reach the full subpage from the main page. Exclude this link if all the relevant information is already displayed in this section.|
See Minnesota/Resources for guidance in Minnesota that may not be universal to all other states and territories.
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 Minnesota.
- Minnesota section of Waze forum
- The Plains region forum
- The USA section of Waze Forum
- The USA segment unlock requests
New editors should consider checking into the formal mentoring program available at no charge.
Minnesota also has a Hangout Group for the state. Originally, this was only opened for Minnesota Area Managers; however, after serious consideration, it is now opened to any person doing editing in the state of Minnesota. This will give quick editing guidance and will allow to easily collaborate information between other users in the state. If you wish to be included in this Hangout, Please PM DallasGrant with your Google (Gmail) email address so he can add you to the group.
Hangouts is a free app available on Android and iOS devices. You also can use an extension in the Chrome Web Browser to access this chat. Go to: google.com/+/learnmore/hangouts for more information.
Cities and towns
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).
Minnesota bases cities and towns on standard city line boundaries and not USPS standards. Where the city limits end, another city or township will begin.
Minnesota does show townships throughout the state. Keep in mind that many of these are named incorrectly. All township names should be [Township] Twp. It should not end in the full word Township or be called Greater [Township] Area.
If we see an error with a city, town, or township name, DO NOT correct the issue in the map itself. Correcting it in the map either will give you errors when you attempt or it will smudge cities. Even if you update every street in the township, the incorrect city name will still exist and will show both names on the live map.
If you see an issue, post it Here and we will submit a report to fix the city name. Keep in mind that this is a very time-consuming process and averagely takes 2-3 months to show correctly on the editing map and another 1-2 months after that before the live map will see it.
We currently are running an experiment with adding residential addressing as a place point using the USPS city as opposed to the township or city it is actually located. We are verifying the negative implications of this and seeing if the positives outweigh the negatives. If you see this on the map, please do not delete it or follow suit as this is an isolated test.
In Minnesota we have a set minimum standard for locking roads based on the segment type. Any road of a certain segment type must be locked to at least 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|
Note: Before locking these roads to these standards, you must verify that the name of the road, direction of the road, and turn functionality is correct. If this information is not correct, it should not be locked unless we are having issues with editors in the area. The only exception here are Freeways due to the routing priority. Refer to Unlock Requests if you need a section of road altered or unlocked to correct an issue.Additional:
Minnesota follows the standard USA guidelines for all of the following special road types.
- Divided highways and roadways
- Carpool, HOV, Transit lanes
- Roundabouts and traffic circles
- Dirt roads
- Toll roads
- Partial and scheduled restrictions
- Private installations and military bases
Review the Wiki guidelines for non-drivable roads to ensure compliance with the general guidelines.
In the state of Minnesota, most unpaved roads are considered dirt roads. Knowing this will help you create the correct road levels. Undrivable roads should not be mapped, should be restricted, or should be listed as a trail instead and not be connected to any functional roads. Even though 4x4 is in the title, we will only use dirt roads for standard gravel or dirt roads that most vehicles can drive on.
Because most likely people in Minnesota feel a gravel road is a dirt road, we will use Dirt Road for both examples. Please be aware of any of these dirt roads that are minimum maintenance roads as these roads should have restrictions in place for winter months.
The reason the dirt roads classification is important is because a user can decide to not be sent on dirt roads or to only be sent on dirt roads for short distances in the settings of the Waze App.
Keep in mind that if the person does allow for dirt roads, Waze will treat the road as a Primary Street so do not try to make an exception to well maintained dirt roads as a street or you will cause the driver to be directed on undesirable roads. Yes, that's right, a dirt road can be seen as a higher priority than a street! This is very important in rural areas where the Street Category should only be used on very short road segments that are paved. In towns, the Dirt Road Category should be rarely used and an unpaved road should be considered a street or a private road.
Keep in mind that on the Waze App, a private road will look like a street. Nothing looks more off than a bunch of streets connected to a dirt road. Also, if house numbering is correct or there is a place point or area within a private road section, this area will still be able to be navigated to the correct destination.
Please follow this Wiki article on Runways for information about how to set runways correctly. These roads should be locked to the same standard as Airport Area itself.
Avoid drawing alleyways unless it is considered a street by the general public. Most alleyways should not be used to direct traffic and will cause unneeded nodes in the road that can cause roads connected to the alleyways to be less desirable.
Minnesota has been adding roundabouts in many locations throughout the state. It is important to note that most roundabouts should only have three to four connections or it will sound confusing to a driver. Following this Example will give proper turn information and roundabout icons on the screen. If you would use multiple-point access, it instead will say the exit number such as, "At the Roundabout, take the 3rd exit".
This is an indication of what a user of Waze should see on an upcoming Roundabout. It is clear at showing the direction of the turn. It also will verbally say what is referenced on the signage such as "At the Roundabout, Continue Straight" or "turn left". This is the Minnesota Standard for creating and editing Roundabouts.
This is how it looks when more than four exit points occur. It does not give clear guidance to the driver on what way to go aside from the highlighted road ahead. This should be avoided, Only add multiple connections per side if the signs clearly mark Exit numbers (Commonly seen on signs showing 5 or more exit points).
Roundabouts will use the same functional class of the main route traveling through the roundabout. Follow This Article for more information.
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.
When an event occurs that causes a road to be closed, it is important to know that we have a closure system in place to properly close the road and return the road to normal when the closure is over. There is no need to take the closure into your own hands using restrictions.
Closure or Restictions?
I'm glad you asked. There will be times we will use restrictions to a road being set for closure. If the road has a Scheduled Restriction that occurs like clockwork restricting access during certain times of the day or months of the year, it would be a restriction. You can also set Turn Restrictions for turns that need to be restricted certain times of the day. These are all restrictions because they are standard road limitations that occur on a regular basis.
On the flip side, if the road is being closed due to an event such as construction, a parade, or a natural disaster, we need to create a Closure. Keep reading to see if what you have needs to have a closure in place.
When is a closure required?
This is really dependant on a few simple requirements. First of all, does it require a direction of traffic to be impacted at all? This is important because an actual lane of traffic closed does not necessarily mean a closure is needed if traffic still goes the direction(s) it would normally travel; however, this still could be important if access from the side of the road that is closed is restricted (such as exit ramps and connecting streets). One thing to consider is that a divided highway, in most cases, needs no closures if it affects one of the sides of the highway and all traffic is moved to the other lane unless there is a significant split in the road. In a lot of cases, nothing will need to be altered to make this work.
Bottom line: if the closure will restrict access to a certain direction of the road, restrict access to the road completely, or has a limited connection to a closed road it will require a closure.
In Minnesota, there is not a single location to find all road closing; however, we have included a series of links to multiple city, county, and state resources. These Tools will help find any upcoming closures throughout Minnesota. Also, check our Current Closures to see if an anticipated closure is already being recognized.
Report a Closure
If you know of an upcoming closure that is not listed, or Waze is trying to drive you through roads that should be closed (and we are not too late) Let us know so we can add it to the system. Click Here To access our forum for Road Closure Reports.
An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See update requests for more information.
In Minnesota, we have adopted a 1/6/15 system for response to Update Requests. We use this system based on the colors the UR icon would be based on the Interface Elements.
This is the first day the editor responds. We typically want to answer a report within 24 hours, but this should be at least attempted within the first 3 days. This will show a yellow UR on the map.
""Thank you for reporting a [general error] through the Waze app. The report was not clear on what exactly happened at [this location]. Could you please explain the issue that occurred further?""
If the reporter has not commented after 6 (to 10) days of this initial comment a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue. This will show an orange UR on the map.
"We apologize that we have not heard back from you to explain the issue further. We will need a response to fix the issue further. This ticket will be closed in 9 days if no response occurs."
If the reporter still has not commented after 9 more days (15 days since the initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified. This will show a red UR on the map.
"We apologize that we still have not heard back from you about the issue. We have not found the issue and it could be that your map is giving you incorrect information. Please go to the Waze App, then go to Settings / Advanced Settings / Data Transfer and then Refresh Area of My Map to see if that improves anything. Due to no response, we are closing this ticket. You can submit another report if the issue is still present"
While we would like to have every inch of Minnesota covered with a network of editors, we are not currently at that level of community involvement. The 1/6/15 rule has been set as the standard for areas with Area Managers and active editors; However, in many areas, there is very little editor coverage. That being said, use good judgment in these areas as there may be Update Requests that are greater than 30 or even 60 days old. There is no penalty or negative perception to answering these, quite the opposite. Please, still take the time to send the reporter a message to see if they can remember the issue and allow them additional time to provide more information. In these areas, we will follow a 1/15/30 rule. Day 1 is the first day an editor responds. Day 15 is the warning message stating the issue will be closing in 15 days. Day 30 to close out the ticket.
"Thank you for your report! I apologize for the late response, we are volunteer editors and in some areas there are not many of us. You reported a General Error near [this location] in [City], Minnesota way back on 9 Dec 14. Do you remember what issue you encountered?"
Sometimes, you will come to an issue with a road, but you do not have a sufficient lock level to fix the situation. Click here if you need to setup an unlock request. Please pay attention to the top of this forum where it will give clear instructions on how to create an unlock request.
If you want to check to see if there are any Unlock Requests that you can handle, Click Here to check all open reports for Minnesota. Anything showing the green check mark means it has been completed.
Not every camera-looking device at an intersection is a speed or red light camera. Generally speaking:
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 Minnesota.
|As of February 2013, Minnesota legislature has not approved the use of red-light or speed cameras anywhere in the state. These camera types should not be mapped in Waze. Please delete any of these cameras that get posted to the map!|
To do list
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.
Current/upcoming editing tasks and projects for Minnesota
|Priority||Task Name||Assigned To||Latest Update|
|1 High||Update all roads to appropriate Functional Classifications||DallasGrant and all AMs||DallasGrant has been editing around the state fixing this|
|1 High||Ensure all Roads are named correctly||DallasGrant and all AMs||DallasGrant has completed this in Nicollet, Blue Earth, & Le Sueur Counties|
|1 Medium||Ensure all House numbering is correct||DallasGrant and all AMs||DallasGrant has finished approximately 75% of Blue Earth county|
|1 High||Ensure all interstate highways are routing correctly and locked||DallasGrant and all Level5||N/A|
|1 High||Use Validator to verify no issues with roads||DallasGrant and all AMs||N/A|
|2 Medium||Establish Area Managers for the 17 cities with a population of 50,000 or more||DallasGrant||DallasGrant has AMs covering all these cities, but he still needs AMs for Owatonna, Albert Lea, Saint Cloud, the Iron Range, Brainerd, and Morehead|
The table below identifies the editors also designated as Area Managers or higher who are editing in Minnesota. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers Minnesota, or a USA Country Manager that does a lot of work in Minnesota, please add yourself to this list (alphabetical by username) in the correct rank section.
The editor who also serves as the Regional Coordinator for Minnesota 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.
|Minnesota — Area, State and Country Managers|
Regional Coordinator(s): the1who (PM)
| Country Managers (Plains region)|
|OscarC(6) [PM]||Statewide (also AM for Red Wing and Duluth)|| |
|State Managers (Plains region)|
| Area Managers |
|OscarC(6) [PM]||Twin Cities metro, Red Wing and Duluth|| |
|Sdtahoe(5) [PM]||SW Minnesota||Also covers parts of South Dakota|
|AVdriver(5) [PM]||Winona, Alexandria, Brainerd, Winnebago City vicinity, Helen, Young America, SXSW Twin Cities metro|
|DallasGrant(4) [PM]||Mankato||Also State Manager|
|bbrakke(2) [PM]||Greater Duluth area|
|GiannaRama(2) [PM]||Rochester area|
|psubrian(2) [PM]||NW Metro Area|
|YukonXL00(2) [PM]||SE Metro Area|
The following editors are also editing in the state and working towards an Area Manager position.
| Other Area Editors |
|Username||General Editing Area||Comments|
Other states and territories
About this page