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
- 7.1 Other drivable roads
- 7.2 Non-drivable 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.
You will hear the phrase Functional Class or FC a lot when it comes to the standard for road types. According to the US Federal Highway Administration, The concept of functional classification defines the role that a particular roadway segment plays in serving the flow of traffic through the network. Waze has its own interpretation of this system, but it utilizes the state's functional class map to help determine the road type to use.
Check out our Mapping Resources for knowledge on how to use the state's map system to find Functional Classifications Standards in Minnesota. From that knowledge, use this chart to determine how the road should be classified using the Waze Standard. Minnesota follows this chart completely aside from dirt or gravel roads in rural areas. This exception will be changed as soon as an unpaved road option exists in Waze.
If you have any questions about Functional Class, please use our Community Resourses to reach out to gain further information.Interstate Roads Will be freeways aside from Business Loops and Spurs (Which instead will be a Major Highway). Also, watch for some roads that are Principal Arterial - Other or Other Freeways (colored red or orange) as they could fit the profile of a Freeway. All roads that have to be entered or exited using a ramp, where 3 or more consecutive exits occur, needs to be set as a freeway. A Freeway will end at first direct connection of a road to the highway.
- Freeways will usually only be named the Highway number of the most prominent highway of the section. For instance, If a highway is a State Highway connected with a US highway, then it will be named the US highway.
- If two of the same type connect such as a US highway and another US highway, then the road that stayed on course will be the named highway.
- All highway numbering will be as follows: Interstate: I-XXX, US Highway: US-XXX, Minnesota State Highway: MN-XXX, County Highway: CH-XXX. Notice that there are no spaces between the dashes. The only exception to using the Highway Number would be if there is clear signage that the freeway is known by another name.
A will connect two roads together; however, it will not be used for a simple At-grade connector or in other words a road that doesn't have a different elevation level. There are some exceptions to this rule to understand.
Even veteran editors need to pay attention here! Naming of an entrance and exit ramp correctly is crucial to the users of this app when being navigated around. If the name of the entrance ramp is incorrect it will confuse the experience and may confuse the driver to take the exit absurdly or miss it all together. Please follow these rules:
- Only time to ever type in the word "Exit" in the ramp is when the exit is a numbered exit. The only roads that have numbered exits are exits off an Interstate with the exception of US-52.
- For all Numbered exits, it will start with "Exit XX:" For example, if the Exit is number 114A then you will start the exit name as "Exit 114A:" and there will always be a colon after the exit number
- For non-numbered exits, just start the exit as such, "to" For example, if the exit was to US Highway 169 Northbound, then the exit would be "to US-169 N"
- All numbered highways need to be typed as such: Interstate: I-XXX, US Highway: US-XXX, Minnesota State Highway: MN-XXX, County Highway: CH-XXX, County Road: CR-XX all with no spaces between the Highway type and the number.
- Include as much information in the sign as possible. For example, If the actual sign shows it will take you to County Highway 1 Eastbound and it also takes you to Riverview Rd and Old Shakopee Rd, then the ramp needs to be labeled: "to CH-1 E / Riverview Rd / Old Shakopee Rd" using the slash "/" to separate the different roads to take. Try to match the sign as close as possible.
- If a road splits showing arrow marking under lanes to of which to stay on to continue your course, use ramps for each side. For example: in Burnsville, a person taking I-35 N will have the decision to take I-35W N or I-35E N. The I-35W side is a numbered exit, the other side is just a guided direction to head towards I-35E N. The one side is labeled: "Exit 88A: I-35W / Minneapolis" and the other side is just labeled: "to I-35E / St. Paul". Using ramps here will guide the driver to the right side of the highway.
- For road splits that have 3 or more splits, usually paying attention to the one that splits first will guide you to how to set it up correctly, but it is often best to reach out for support to find the best solution based on the more complexity of an issue.
Any road with the Functional Class (FC) as Principal Arterial - Other (Freeways), colored red or orange on the FC map, will be a Major Highway (MH) if these roads do not fit the standard definition of a Freeway. All US Highways (Such as US-169) will be labeled as a Major Highway regardless of what the FC map shows unless it can be labeled as a freeway.
- Naming of a major highway typically will be in the road number standard: US Highway: US-XXX, Minnesota State Highway: MN-XXX, County Highway: CH-XXX, County Road: CR-XXX; however, pay close attention to the way the signage really is in these areas.
- In town, these highways need to be named as the street names used for house numbering.
- Out of town, should be labeled the same as the street name for house numbering if looking at a 2 lane highway
- and the Highway number for split direction Major highways unless signage clearly indicates it is known by another name
Any road with the Functional Class (FC) as Minor Arterial, colored as green on the FC map. will be a Minor Highway (mH). Also, all State Highways (such as MN-13) will be set at a minimum of a minor highway regardless of the current FC classification from the State of Minnesota unless it is a higher classification or could be considered a freeway.
- Naming of a minor highway typically will be in the road number standard: Minnesota State Highway: MN-XXX, County Highway: CH-XXX, County Road: CR-XXX; however, pay close attention to the way the signage really is in these areas.
- In a town or city, the naming will typically be the street name unless the name of the street is Co Hwy XX where we would change it to CH-XX
- Pay close attention to the name assigned for house numbering. If house numbering suggests using the wording, "State Highway XXX", we need to set the name of the road as such.
Primary streets should only be named the actual name of the street (same name as house numbering indicates). The only exceptions to this rule would be tricky intersections where a county road sign is the only prevalent name of the street.
A will be for any road in a town or city that doesn't fit in the categories above. In rural areas, this will be lightly used for paved roads that cannot be considered a County Road (a rarity in the rural areas). This will be named the same name used for house numbering.
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 is 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.
Other drivable roads
|Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!|
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. Keep in mind that because of the way Waze handles dirt roads, we will not use the dirt road class in the city limits of any town. Any in-town gravel roads will be streets.
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.
Parking lots roads are essential to navigating users to the proper destinations. It also helps to properly exit a parking lot. Follow these examples to creating parking lots correctly. Click the image to the right to see a well-designed parking lot section.
- Simple is best. Do not map every lane
- Map the main entrances from the roads outside the parking lot
- Map lanes that run along storefronts
- Map lanes that run along main roads outside the parking area
- Map primary lanes that serve to get people from one area of the lot to another
For for information about mapping parking lots, follow this article
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.
If you are adding a private road for a private housing section, make sure 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 as long as it has a proper address to navigate to. Pay attention to this article for more information.
In the case of very long driveways, it may helpful to a driver to see the driveway mapped on the client app or even necessary for Waze to determine how to reach the destination. In those cases it may be prudent to add a road. See the article on Driveways for more information.
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. Most alleyways that would be mapped will use the Parking Lot class.
This is a good example of where alleyways will be mapped. This is in South Minneapolis at the corner of Xerxes Ave S and W 56th St. It is also the location of Pizzeria Lola. The parking at this location is on the side of the Cavé Vin building. It is a one-directional section and the only way to leave is through an alleyway. In this case, you would create the section as a parking lot road and you only map out what is needed to enter the parking lot and exit; however, you would not need to map any other section of that alleyway.
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.
HOT & Hov Roads/Lanes
High Occupancy Toll or High-occupancy Vehicle roads are not yet handled 100% by Waze as of yet, but we will still map these out to prepare for that time.
These roadways have the following features:
- These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.
- There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.
- Entrances and exits to the HOT lanes are limited to help maintain high speeds.
- There are no entrance/exit combinations where the toll fare rules don't apply.
- Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.
To avoid traffic from entering this section, all entrance ramps will be will be restricted as in this article. From there, nothing will be restricted so if a user decides to take this route, he or she will be directed correctly.
This will all be changing shortly as we find a better way to develop these roads.
When a road or lane is designated for bus or cab use only, mark that road segment(s) as a Private Road to prevent the Waze router from using that segment(s) for general traffic, since the majority of the users will not be able to use that lane. It is also advisable to set the turn restrictions to prevent turns into that segment(s), but permit turns exiting the segment.
If a road is one-way but allows bus or cab traffic to flow the other direction, leave the road as one-way with the normal flow of traffic. There is no need to create a second road traveling the opposite direction for the bus and cab-only traffic.
Railroads are not yet added to the map, but these can be added to prepare the maps for when it is. Mapping the tracks allows Waze to recognize spurious speed data from people Wazing on the train and prevent it from corrupting speed data for the adjacent road.
|Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!|
- Elevation will be set to the same elevation standards as a drivable road. When tracks junction a road on the ground, the Elevation should be set to Ground.
- If the railroad crosses a segment of road, it should be connected to the road to so the historical data for the rail crossing will be more accurate.
- Always select "None" for the city name. This avoids city smudging.
- Set railroad to 2-way directionality and Restrict turns to and from the railroad segments.
- Follow the Federal DOT Railroad GIS to verify the owner of the rail line to help on naming of the segment. Use the acronyms under RROWNER1 to help on naming.
- Name each segment using the rail owner name acronyms or abbreviations railroad. For example, Twin Cities & Western Railroad uses TCWR. We would name this section TCW Railroad. We leave off the R in the acronym because it would be redundant to say, Twin Cities & Western Railroad Railroad.
- Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad
- 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.
- Lock all railroads to a Level 2
- Keep segment lengths under 10,000 meters (32,808 Ft) – the longer the segment length, the more sluggish the editor is to respond to changes.
- Read this section for more information about railroads.
We will map all airports runways such:
- These roads will not connect to any drivable sections
- The runways will not be connected to each other
- Always select "None" for the city name. This avoids city smudging.
- Using this article we will find the airport code. We will use the IATA code unless the airport does not have one, then we will revert to the ICAO code.
- After finding the code, we will use this to find the runway numbers for the airport.
- Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views.
- Name each runway as such: [Airport Code] Runway [x-x] ... for example, in the image to the right, you will see the runways for Albert Lea Municipal Airport. The IATA code for this airport is AEL and it has two runways including Runway 5/23 & Runway 17/35 so one will be named "AEL Runway 5-23" and the other AEL Runway 17-35".
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.
|The Ferry Road type is not to be used at this time. Do not use the Ferry Road type for any purpose. See ferries page for more information on how to map ferries.|
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails
- Do not map trails that run parallel to a road unless it is more than 100 Ft from the road
- Do not connect this road type to any drivable section of road
- If the trail has a name, name it [Trail Name] Trail
- Always select "None" for the city name. This avoids city smudging.
- Keep segment lengths under 10,000 meters (32,808 Ft) – the longer the segment length, the more sluggish the editor is to respond to changes.
- Use elevation standards as a standard road.
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate.
- Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.
- The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads
- Do not connect this to any drivable road
- Always select "None" for the city name. This avoids city smudging.
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.
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?
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.
The first thing to do is to look at the UR and try to figure out the issue that happened. It is imperative to look at everything before ultimately deciding that you don't get it. If you click on More Information you can look at the Waze provided route and what the user took to determine this issues. Check the area roads for any restrictions, incorrect elevation, incorrect street names, bad geometry, etc.
If you can figure out the issue, Fix it or submit an unlock request!
""Thank you for reporting the [general error] through the Waze app. The issue has been corrected in the system and will be updated on the map within the next few days. If you are still having issues, 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.""
""Thank you for reporting the [general error] through the Waze app. A request has been made to fix the issues. This should be resolved within the next week or two. If you still are having issues after 2 weeks, 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.""6 and 15-day example from there.
""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?""
"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."
"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.
Do Not Lock a place if the following is not true:
Places should be completed as fully as possible any time they are created or updated. At a minimum, editors should:
- Verify correct spelling of the name, using the guidelines below
- Complete the address, to help when choosing among search results in the app, and
- Ensure the correct location of the Point or Stop Point, to guide drivers to the correct location. Note that this may not always be on the street side of the location.
Phone numbers and opening hours are also particularly helpful to Wazers. Complete them whenever possible, using an online search, if necessary. Photos should help Wazers recognize the destination when they arrive.
|PLACE TYPE||LOCK LEVEL|
|Commercial Service – Primary Airports||5|
|General Aviation Airports||3|
|Other Public-Use Airports||3|
|Hospitals / Urgent Care / Police & Fire Dept||4|
|National & State Parks and Monuments||4|
|Major Shopping Centers||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.
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|
MN Highway Cleanup
Check Minnesota highways for; current naming standard, proper alt names, minor highway or higher road type, and lock per MN standards See MN Highway List
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|
|MyBigRed2(4) [PM]||NE Metro Area|
|Karrows(5) [PM]||North Metro||Usually edit around 694 to Hinckley|
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