| The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.
Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.
Information and resources regarding editing Waze maps in Michigan. Resources for other states and the entire country can be found on the mapping resources page.
- 1 Statewide
- 2 Major Cities
- 3 Counties
- 4 Road Categorization
- 5 Road Construction
- 6 Places (fka Landmarks)
- 7 Speed / Red Light Cameras
- 8 Michigan Exceptions to the Community Wiki
- 9 Forum
- 10 To-do Lists
- 11 Area/Country Managers
- 12 About this page
- MDOT NFC Maps - MDOT National Functional Classification (NFC) maps by county and urban area. An effort was started in late 2013 to convert metro Detroit and other major cities to their corresponding NFC road classifications.
- Boundary and Annexation Survey Maps from US Census Bureau
- TIGERweb from US Census Bureau
- MDOT Physical Road (PR) Finder (also see the PR Finder Home page)
- MDOT MiDrive (Traffic, Construction, etc.)
- Create a bookmarklet with the following code to link from your position in WME to same position in Map Michigan.
Here are instructions on Adding a Bookmarklet.
Please list cities smaller than 100,000 under their county in the category below this one.
- Links are GIS resources unless otherwise indicated.
- Sites marked with a $ have fee based access.
- Barry GIS | Barry Map
- Berrien $
- Grand Traverse (use Internet Explorer)
- Kent (same link as Grand Rapids above)
- Monroe $
- Montmorency 1 | Montmorency 2
- Presque Isle
- St. Clair
- St. Joseph
- Van Buren
General wiki resources are available here:
In addition to the standard wiki resources, considerations specific to Michigan include:
County Highways versus County Roads
- Michigan has an "intercounty" highway system in addition to locally maintained county roads. In both cases, naming conventions should follow highway naming by state.
- Numbered county highways are prefixed with A through H based on geography. Naming convention should be "CR-[Letter Prefix][#]" (i.e. "CR-D19"). In all cases, local signage should be used to designate a primary name, while the county highway designation could be an alternate name if appropriate. While these roads could conceivably be classified higher, the lowest road type used should be Minor Highway regardless of appearance or functional classification.
- A small number of counties maintain numbered county roads that are not part of the statewide A-H highway system. These roads should be named CR-[#] (i.e. "CR-388") and would typically appear as Primary Street, Street, or even Dirt Road.
Use of Functional Classification for Road Types
- As noted on the Road types/USA page, public road types in the United States are determined by the FHWA functional classification and, if applicable, by the highway system to which a road may belong. This methodology was adopted in April 2014, superseding previous road type guidance. In order to assist editors in determining proper road types, functional classification maps published by each state's department of transportation are available on the National resources/USA/Functional classification page.
- Prior to reclassifying any road segment to its functional classification, however, the following levels of precedence should be observed:
- Private roads should be classified as Private Road (even if dirt or otherwise unpaved).
- Public dirt or unpaved roads should be classified as Dirt road / 4X4 Trail.
- Any road classified higher than the current functional classification type due to a separate consideration for highway system, statewide standard, or local editor judgment should remain as is. Segments should be upgraded but should not be downgraded to match functional classification. For example, a county highway with the Michigan A-H designation that may functionally be a major collector would be classified as a "Minor Highway" due to other accepted guidelines.
- If none of the above conditions apply, the road segment can be edited to match the corresponding functional road type.
As a general rule in Michigan, only residential alleys should be mapped, and only if they are the locally accepted destination for parking at or near a residence. Alleys should only function as a starting point or final destination, not as a thoroughfare. If alleys are mapped, the road type should be set to "Parking Lot Road" and given the name "Alley". Other attributes (city, direction, turn restrictions) should be set as if the alley were any other drivable road.
When adding or editing an alley, an important consideration is to verify that house numbers are properly situated for the surrounding street segments. Waze will route to the closest segment for a set of destination coordinates. This may result in the destination being in the alley, which may or may not be the desired result. Refer to the FAQ for additional information. If you need guidance or are uncertain whether a certain alley would meet the criteria to be mapped, please post a permalink in this existing Michigan forum thread.
Examples of Michigan Roads by Type
- Detail for each road type and links to examples are available at Michigan/Roads by type.
- Directory of county road commissions, many of which maintain a list of planned improvements or current projects
Places (fka Landmarks)
As of March 2014, national guidelines were created for Places that all editors should now follow.
Since changes are still in progress with these guidelines, editors should be conservative about adding Places until these guidelines are solidified.
For more information regarding this ongoing process, please see the forum link at the top of the Places page.
Speed / Red Light Cameras
While traffic monitoring devices are employed in the state, no cameras are used for enforcement or issuing citations according to the Michigan State Police.
Michigan Exceptions to the Community Wiki
(DRAFT) Median U-Turn Intersection (MUTI)
- NOTE: Although these guidelines have not officially been adopted as a Waze standard, the discussion is occurring at this forum thread. This section is in place as a guide for editors experimenting with this type of intersection while a consensus is being reached statewide or country-wide.
A Median U-Turn Intersection (MUTI) is a procedure involving an indirect left turn onto or from a split roadway onto another road where the direct left turn is prohibited at the intersection itself. A MUTI can only occur at the intersection with a cross street. Other median u-turns may be available at crossovers along a split road, however these would not be classified as MUTI since they simply facilitate going the opposite direction along the same split road. A reference figure showing both types of u-turns together appears below.
To execute the turn, the driver proceeds through the intersection to turn left at the next median u-turn, then turns left onto the same road (in the opposite direction), and finally turns right at the main intersection. Alternatively, if the intersection involves turning onto a split cross road, the driver could also turn right onto the intersecting split road, then turn left at the median u-turn, finally turning left onto the road and proceeding through the main intersection.
This procedure has proliferated in Michigan since the late 1960's, and is locally referred to as a “Michigan Left Turn (MLT)” or just “Michigan Left“, even in locations other than Michigan. The MUTI and its variants are now used or being considered in several states and other countries.
Other terms for this procedure in transportation literature from the Federal Highway Administration and individual states include:
- “Arizona Parkway”
- “Boulevard Turnaround”
- “Median U-Turn Crossover”
- “Median U-Turn Intersection Treatment (MUTIT)”
- “ThrU-Turn Intersection (TTI)”
In addition, there are a number of related procedures directed toward the same or a similar result as the MUTI. Consequently, some of these procedures may need treatment similar to the MUTI in Waze:
- "Continuous Flow Intersection (CFI)"
- “Reduced Conflict Intersection (RCI)”
- “Restricted Crossing U-Turn Intersection (RCUT)”
- “Super-Street Median Crossover”
In order to be considered a MUTI (or variant), proper signage should be in place. Depending on what entity maintains the road, however, the quality of signage will vary.
- Naming Convention: to [street name] [opposing direction] / to [cross street name] [direction]
- Similar to highway way-finder segments, the “street name” is instructional rather than official
- Example intersection of Mound Rd and Metro Parkway in Macomb County
- Driving north on Mound Rd: "to Mound Rd S / to Metro Pkwy W"
- Driving south on Mound Rd: "to Mound Rd N / to Metro Pkwy E"
- Driving west on Metro Pkwy: "to Metro Pkwy E / to Mound Rd S"
- Driving east on Metro Pkwy: "to Metro Pkwy W / to Mound Rd N"
- Road Type: RAMP
- Although this departs from traditional rules for At-grade connectors and for use of the ramp road type, it hides the instructional street name in the client. It is close to the exception stated on the at-grade connector page, however, in that a MUTI is a signed--though unnumbered--exit from the current direction of travel on a roadway.
- Junction Angles: Between 45 and 90 degrees
- The angles for the median u-turn should generate two "turn left" instructions. The first “turn left” should occur prior to entering and the second should occur while exiting the median crossover.
- Junction Position:
- The initial junction ideally should be as close to the start of the solid white line as possible (if present). This prevents a turn instruction from occurring too early or too late. In many cases, this will require adding a geometry node at the start of the segment at the most detailed zoom level to generate the correct turn angle.
Sample MUTI as it appears in Waze Map Editor:
Distinction between MUTI and standard crossovers:
Keep track of work that needs to be done and coordinate efforts with other AMs.
- Functional Classification Inventory
- Freeway Consistency
- State and County Highway Consistency
- Ferry list (add docks as Point Places)
For spreadsheets above, comments can be inserted, but edits are locked. Send a PM to davielde for editing access.
If you are an Area Manager who covers the State of Michigan, or a USA Country Manager active in Michigan, please add yourself by rank and then alphabetically to this list.
You are also encouraged to create your own User Profile here in the Wiki. The profile can then also be linked to from your Forum Signature.
|Michigan — Area, State and Country Managers|
Regional Coordinator(s): [RC] GizmoGuy411 ( ) and [ARC] TerryPurdue ( )
| Country Managers (Great Lakes region)|
|GizmoGuy411(6) [ ]||Home AM area: NE Ohio, SE Michigan, NW Indiana|| |
US Country Manager, Global & US Waze Champ, Great Lakes Regional Coordinator
|sketch(6) [ ]||Louisiana, Metro Detroit|| |
US Country Manager, Global & US Waze Champ
|davielde(5) [ ]||Ann Arbor|| |
US Country Manager
|State Managers (Great Lakes region)|
|SkiDooGuy(5) [ ]||Detroit|| |
MI State Manager
|jdeyoung(6) [ ]||West Michigan|
|lelehman(5) [ ]||Lower Peninsula||Based in Mid-Michigan|
|captnkeegs(4) [ ]||West Michigan||Mostly Working Kent, Barry, Allegan, Ottawa, Muskegon Counties and other areas between Cadillac and South Haven|
|hitfactor(4) [ ]||SW Lower MI||Berrien and Cass Counties|
|SuperMari0O(4) [ ]||Upper Peninsula||Alger, Baraga, Chippewa, Delta, Dickinson, Gogebic, Houghton, Iron, Keweenaw, Luce, Mackinac, Marquette, Menominee, Ontonagon, and Schoolcraft counties|
|miked_64(3) [ ]||SW Lower MI||GR, Kzoo and surrounding areas|
About this page
Please report broken links to: davielde (other volunteers needed).
If you are a Michigan AM, please help develop this page and add a link to your profile and/or PM below to show you are a contributor to this page.