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.

Clock over a larger globe

Difference between revisions of "India/MMR India"

From waze
Jump to: navigation, search
(slightly simpler English, with bullet points, and numbers as digits)
Line 116: Line 116:
  
 
====Solve URs and MPs====
 
====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.  
+
URs (update requests; map problems reported by waze users) and MPs (automatically generated map problems) show where the map needs work. We must solve them to fix the map. URs also give us a way to contact our fellow wazers, who may become interested in editing.
  
You can handle the URs using the responses in this doc file (link to be added) according to the following guideline:
+
* Respond to URs in English.
 +
* Follow the guidelines below (they are based on [[Update_Requests_in_Waze_Map_Editor|guidelines for URs]])
 +
* You may use this list of [responses to common UR problems] to help you.
 +
* UR reporters are our partners in fixing the map.  Always use friendly comments that show this. Always ask for information in a friendly way, thank them for working with you, and always leave a comment before closing.
 +
* If another editor is already working on a UR, communicate with them using Slack. You may find a solution together.
 +
* If one of the mapraid hosts has asked for more information before the mapraid began, you may begin to work that UR -- you do not need to ask for permission.
 +
* Some problems are easy. Some problems are difficult. Sometimes the reporter gives incorrect information. You can ask a more experienced editor for help solving a UR.
 +
* If you did not solve a map problem, do not mark the UR solved.  If the problem is with the app, give the reporter a link to the waze support pages.
  
'''For recent URs (<1 month):'''
+
=====Recent URs (< 1 month)=====
Most of the URs that need further explanation received an initial response already from the map raid hosts before the raid.
+
* If the report has enough information, please fix the problem. Tell them what you did. Say "thank you". Maybe they will send more helpful reports after this. After it is fixed, close the UR as '''solved''. Remember to '''send''' your closing comment.
* 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 you need more information, ask. Be friendly, say thank you, and '''send'''.
* If there is no response to the initial reaction, send a reminder message. It often happens that reporters do respond only after a reminder
+
* If the reporter did not answer after 4 days, send 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 (link to be added)
+
* If the reporter did not respond to the reminder after 7 days from the reminder, check again. Try to solve the problem. Check other URs for more information.  If it cannot be solved, close the UR '''Not identified'''.  Use a closing comment such as "I'm sorry we were unable to identify the problem. If it continues, please start a new report.  Thank you for your help with the map" (link to responses).  Remember to '''send'''.
  
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 '''always check before closing'''. Additionally, do not forget to leave a closing comment.
+
=====Older Reports=====
 +
* Say we are working on the map and they can help fix the map if they want to.
 +
* After your first response to the UR, allow at least 10 days before closing it.
 +
* Try to figure out the problem. '''Always look for other problems in the area'''.
 +
* Always leave a closing comment. (link to be added). Remember to '''send'''.
  
'''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 (link to be added).
+
To learn more, please read about [[Update_Requests_in_Waze_Map_Editor|Update Requests]]. Follow the mapraid guidelines above. <div style="text-align: right; direction: ltr; margin-left: 1em;">[[#TOC|<small>''
 
+
If you like to learn more, there is elaborate information on URs in the general Wiki page on [[Update_Requests_in_Waze_Map_Editor|Update Requests]]. Be aware, that if guidelines differ from what is written above, the raid guidelines precede.
+
<div style="text-align: right; direction: ltr; margin-left: 1em;">[[#TOC|<small>''
+
 
go back to the table of content''</small>]]</div>
 
go back to the table of content''</small>]]</div>
  

Revision as of 11:45, 4 May 2016

This wiki page is under construction, please check back later to read updates.

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.

India.png

MapRaid! India

  • Start: May 15 meet and greet, webinars, classes and mentoring; May 21, raid area opens
  • End: June 5

Date and Times are approximate.

If you would like to participate, please fill out this registration form. Registration is open until May 8 2016, 22 UTC, or until 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.

Goals

In order of importance:

  1. To welcome and help new editors in Bangalore
  2. Solve URs and MPs
  3. Check and improve major connectivity
  4. Improve Wiki page
  5. Add Gas Stations

Hosts

editor Rank Role Group
moweez (PM) 6 GC/MapRaid Coordinator
cherianchris (PM) 6 Regional Coordinator
lunarplexus (PM) 5 Country manager/Local Champ
DidierLmn (PM) 3 assistent host

The raid will be supported by a team of Global Mentors:

Mentor Rank Country Group
moweez (PM) 6 Turkey
Marcin_S (PM) 5 Poland
Voludu2 (PM) 5 USA
Machete808 (PM) 5 Hawaii
ci2212 (PM) 6 Indonesia
steveningelbrecht (PM) 6 Belgium
carloslaso (PM) 5 Mexico
and many others assisting

Communication

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. Local time is UTC + 5.30h.

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

India is on the World server. If you are on a different server (US, Canadian and Israeli visitors), and you enter an area at a different server, WME will warn you with an orange bar at the bottom to change. In the upper right hand corner of WME, where it says US & Canada, you can click it for a dropdown menu. To edit in India, change to the World server, commonly known as the ROW (Rest of the World) server.

People drive at the left side of the road. Distances are measured with the metric system. Make sure to have the right settings in WME. Also, in India, u-turns are allowed/used on almost every corner of the street. Please keep them allowed.

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

You can find a lot of information in the Indian wiki pages. Where applicable, we will refer to the info on these pages if they are needed or useful for the mapraid goal. If there is something you don't understand, please just ask. We all want to have constructive edits and a good map in the end.

Welcome new editors of India

We are happy to invite you to the amazing world of Waze Map Editing. We all once started and in the last years, we developed and shared the info that is needed to make it into a nice experience. The first time might be confusing, for there is a lot of information available. Our best advice is to take your time and ask everything that is confusing. Many people learn from your questions.

Especially for this mapraid, we have teachers and mentors that will help you get around. During the first week, there will be a series of webinars and classes that will provide you with the necessary steps. Everything will be comunicated in Slack.

You might want to start with the very general and simple Quick-Start guide (link to updated Indian Quick Start needs to be added).

Solve URs and MPs

URs (update requests; map problems reported by waze users) and MPs (automatically generated map problems) show where the map needs work. We must solve them to fix the map. URs also give us a way to contact our fellow wazers, who may become interested in editing.

  • Respond to URs in English.
  • Follow the guidelines below (they are based on guidelines for URs)
  • You may use this list of [responses to common UR problems] to help you.
  • UR reporters are our partners in fixing the map. Always use friendly comments that show this. Always ask for information in a friendly way, thank them for working with you, and always leave a comment before closing.
  • If another editor is already working on a UR, communicate with them using Slack. You may find a solution together.
  • If one of the mapraid hosts has asked for more information before the mapraid began, you may begin to work that UR -- you do not need to ask for permission.
  • Some problems are easy. Some problems are difficult. Sometimes the reporter gives incorrect information. You can ask a more experienced editor for help solving a UR.
  • If you did not solve a map problem, do not mark the UR solved. If the problem is with the app, give the reporter a link to the waze support pages.
Recent URs (< 1 month)
  • If the report has enough information, please fix the problem. Tell them what you did. Say "thank you". Maybe they will send more helpful reports after this. After it is fixed, close the UR as solved. Remember to send' your closing comment.
  • If you need more information, ask. Be friendly, say thank you, and send.
  • If the reporter did not answer after 4 days, send a reminder.
  • If the reporter did not respond to the reminder after 7 days from the reminder, check again. Try to solve the problem. Check other URs for more information. If it cannot be solved, close the UR Not identified. Use a closing comment such as "I'm sorry we were unable to identify the problem. If it continues, please start a new report. Thank you for your help with the map" (link to responses). Remember to send.
Older Reports
  • Say we are working on the map and they can help fix the map if they want to.
  • After your first response to the UR, allow at least 10 days before closing it.
  • Try to figure out the problem. Always look for other problems in the area.
  • Always leave a closing comment. (link to be added). Remember to send.
To learn more, please read about Update Requests. Follow the mapraid guidelines above.

Connectivity

There are many aspects when we deal with connectivity. In the end, we all want drive to our destination in the fastest way. Therefore, we need roads. No roads, no navigation. These roads need to be connected, so there is a route possible from one to the other. The more experienced you get, the more you can do to improve connectivity, like using road types, naming, and corners, to improve routing and navigation instructions.

  1. The first sub goal of connectivity is adding drivable roads.
    Roads are build up from segments.
    How to add roads is explained in (link to be added-include settings).
    In India there are many narrow streets that are not drivable. See the extended explanation on Extremely narrow streets
  2. These segments need to be connected in a good way
    • always check if a junction is working correctly
    • and don't forget that u-turns are allowed in India. Read more at (link to be added)
  3. Make sure to use the appropriate road type.
  4. Check the corners and other aspects that are needed for good instructions (see detailed info)

We advice starting editors to stick with the first 2 goals for the time being. If you want to learn more, ask a mentor to help you.

A rough guideline to using 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 ar least be MH (major Highway)

Please read the Indian wiki page on road types before changing the type.

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 or higher 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 hosts/mentors if anything is unclear.

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.

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

Add Gas Stations

description

Mass edits and quality

We all want to drive with a good map! So, make sure you make quality edits that help all Wazers.

Your edits should always be constructive to the map. Be aware that we will monitor edits, so avoid unnecessary edits and hunting for points. Sanctions are strict, being banned from this and future mapraids. In addition, Waze throttles your edits and points when scripts are used excessively, meaning that you don't earn points for mass editing.

In short, if you make unneccesary edits:

  • You will not get credited for your edits.
  • You will not get any points for your edits.
  • You will be REMOVED from the MapRaid immediately.
  • Possibly banned from editing altogether.

Quality counts, not quantity!

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 the first time, 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.

Highly Recommended Tools

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

URComments

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

Validator

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



!!PLEASE REMEMBER THAT YOU ARE RESPONSIBLE FOR THE USE OF ALL SCRIPTS!!

You need to understand the basics of editing before using scripts. If you start using scripts, always make yourself acquainted with the script before using it! There is a wiki page and a forum with more information about scripts.