The new Waze Wiki, aka Wazeopedia, is now live at! 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.

Clock over a larger globe

India/MMR India

From waze
< India
Revision as of 16:09, 29 March 2016 by Cherianchris (Talk | contribs)

Jump to: navigation, search

A MegaMapRaid (MMR) is a MapRaid in which a group of international map editors join together and update a large area. Besides the benefits of a normal MapRaid, it opens up different ways of dealing with editing and navigation situations, because every country has it´s own specifics. It is always fun and a great learning experience to people from several backgrounds. Besides, the raiders together quickly improve the overall condition of the Waze map.

MapRaid! India

  • Start: to be defined
  • End: to be defined

Date and Times are approximate.

If you would like to participate, please fill out this [ registration form]. Registration is open until XX UTC, or untill the maximum amount of participants is exceeded.

Please do not make any edits in the raid area until after the raid begins. This will allow us to get good mapraid statistics.


In order of importance:

  1. Solve URs and MPs
  2. Check and improve major connectivity


  1. Correct road naming
  2. Correct base map positioning
  3. Check and correct city boundaries
  4. Improve Wiki page


editor Rank Role Group
moweez (PM) 6 GC/MapRaid Coordinator
cherianchris 6 Regional Coordinator 1
lunarplexus 5 Country manager/Local Champ 2
yourname level Country manager/Local Champ 3


Because of the international character of this MapRaid, the main language is English. There is help for translations. As we have raiders from many different time zones, we will use time in UTC.

Participants will be divided into several groups, one for each section of the map. Each group will have both local and senior editors, and a Group leader. Please direct all questions to your group leader. The raid hosts will be available across all areas for added support.

When working in the raid area, please set yourself to set yourself visible in WME chat. Also, turn on the Live Users layer. This will serve to collaborate smoothly and get quick help at your location if needed.

We will use Slack as the main communication service. There is a special Country MapRaid channel for this raid. Also, every group will have their own channel. If you are not already part of the MapRaid Slack team, you will be invited shortly before the Raid starts.

Raid Areas

This MapRaid has X groups according to the following map (to be added). Use the overlay to show the borders of your group area in WME. Keep in mind that editing access may slightly differ from the overlay. If areas neighbour another country, please do not edit in other countries, even though you have access. If something needs to be updated, inform one of the hosts who will contact the neighbouring country.

Mapraid guidelines

First of all, you can find a lot of information on the Indian wiki pages. Keep in mind that if you are working in an area which has been edited recently, the Satellite Imagery may be out of date or something else is going on. Please be careful before changing others' work. You can always discuss it with your group leader.

Solve URs and MPs

There are many URs in Bangalore. They signal where the map needs work. Also, it provides a possibility to get into contact with our users. The script URComments is a very handy tool to use. Download the International List (or if we make one: Indian List) to work with the URs.

few basic responses in a doc file or make a separate Indian List
unclear URs received a first response already (done by the hosts a couple of days before the raid start. Raiders then can start the next step as soon as the raid starts:

For recent URs (<1 month): (taken the first option that unclear URs received a first response before the raid)

  • If the report is clear and you can solve the issue directly, please do so. Explain to the reporter what you have done to resolve it. The reporter receives a message of your comment, and will feel valued for his/her addition. In addition, other editors can learn from your solution and it can help solving other issues in the neighborhood. You can close the UR as solved.
  • If there is no response to the initial reaction, send a reminder message. It often happens the reporters do respond only after a reminder
  • When the reporter also does not respond to your reminder within another week, you can close the UR as "Not identified", with a comment in the conversation why you closed it (there is a default response available in the doc/URComments script).

Before closing an UR "Not Identified", make sure it really cannot be solved. The information in the UR and on the map may be sufficient to resolve it, so do not close before checking. Additionally, do not forget to leave a closing comment.

For older reports, our main focus is to inform the reporter that we are working on the map and they can help if they want. Allow at least 10 days before closing. In addition, before you close the report, try to figure out what the problem was. Always improve the area before you close the UR. Use the "Closing an UR after no feedback" comment (option: from the script URComments).

Elaborate information on URs can be read in the general Wiki page on Update Requests. Be aware, that if guidelines differ from what is written above, the raid guidelines precede.


Always make sure a road is at least connected to a same level of road type or higher. Thus, Waze should be able to route from primary to primary (or higher), from minor to minor (or higher), from major to major (or higher), and from Freeway to Freeway. Another way of explaining this, is that you should be able to continuously drive on the same type of segments for the routing engine to use that road type in the calculations.

This means we need to sometimes make small roads mH, for the possibility of calculating long distance routing. Please discuss with the local champs if anything is unclear.

Road types?

  • The main roads in a district or town should at least be set to primary.
  • If segments will be used for through-going traffic or for longer distances connecting districts or towns, they should at least be mH (minor Highway)
  • Main interconnecting roads with fast traffic should be MH (major Highway)
Extremely Narrow Streets

The city of Bangalore, like in many locations in Indian. is extremely densely populated. Perhaps this is because they used to be villages that have been absorbed into one large city. Villages often have the same layout and structure. Many of the streets in these areas are too narrow to drive through, and shouldn’t be allowed for routing. You can turn off the Roads layer to have a proper view on the Satellite Imagery.

Extremely Narrow Streets
Extremely Narrow Streets with Segments

As the pictures show, the primary street on the left side of the frame is a proper drivable road. On the right side, the buildings are densely packed and the streets are too narrow to drive through with a car.

If you see streets drawn over these areas, please turn the Roads layer off and verify if the roads are drivable or not based on the Satellite View. Also verify if there are NO GPS tracks by by turning on the GPS Points layer.

If both verifications confirm these streets are not drivable, delete them.

Always use extreme caution before deleting segments. If you have any doubt, please discuss it with your group leader, or contact one of the local map raid hosts.

Improve Wiki page

As we are currently updating our wiki pages, we can use your help. Tell us where it is unclear, needs examples, or when pictures are outdated. We are grateful for your feedback. You can use this form India to do list to report your findings.

Base map


Road naming


Mass edits

In Base Map areas, mass edits are allowed. Be aware that we will monitor edits, so avoid unnecessary edits and hunting for points. Sanctions are strict, being banned for this and future MR and MMR. In addition, Waze throttles your edits and points when scripts are used excessively.

If you are using a tool or script, you are fully responsible for its use and its consequences. Please make sure that you understand the features of the script you are using. You will be held accountable for any side effects.

  1. If you are unsure about something, please ask.
  2. Check and triple check.
  3. We have great leaders here who can help you.
  4. Let's make sure we do it right, and set a great example for the rest of the world.

Editing Resources

Only use sources that are allowed by Waze.

Allowed sources:

  • Satellite Imagery and Street-view from within WME.
  • Websites from businesses.

NOT allowed sources:

  • Info from other Maps.
  • Google Maps
  • Google Street-view.

Warning: If you copy information from unauthorized sources, you may be removed from this mapraid. Also, every segment you edited may be removed from the map. Copying information from copyrighted sources is illegal!

Basic reference links

a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.

Specific tools for this MapRaid

  • There is an [link to overlay for WME|Overlay] to view the boundaries of the group areas via an extra layer. To use it, you need to have TamperMonkey (Chrome) or Greasemonkey (Firefox) installed. The areas are kept simple for smooth working in WME. Please note that they may slightly differ from the actual areas you can edit during the raid.
  • There is a Places Browser for this MapRaid to update Places according to the rules of the location. >

Highly Recommended Tools

Many tools are essential for good editing, and others make the editing process much easier. Highly recommended are:


  • a time and labor saving tool for responding to URs. For this raid, you can use the International List.
  • Read the documentation.
  • To use it, you need to have TamperMonkey (Chrome) or Greasemonkey (Firefox) installed.


  • This is a script that validates a map area in the Waze Map Editor, highlights issues and generates a very detailed report with U.S. wiki references and possible solutions. Keep in mind that the guidelines of of the country where you edit (if available on the subject) precede over the guidelines of the U.S..

WME Toolbox

  • This is a script that facilitate the process of editing maps in the WME. It has a toolbar that facilitates the process of removing unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.

WME Aerial Shifter

  • Please note, that Google satelite imagery may be shifted for some areas. If you notice that entire city is shifted, please do not adjust all streets to fit the background. You may use this script instead to shift imagery

WME Speedhelper

  • WME Speedhelper has made inputting speed data easy, with the use of handy speedsign images. You just need to select one or more segments and click the speed you want. If a segment isn't yet verified, don't worry, these checkboxes will be automatically checked.
  • To use it, you need to have TamperMonkey (Chrome) or Greasemonkey (Firefox) installed.


Always make yourself acquainted with the script you want to use before using it! There is a wiki page and a forum with more information about scripts.