Improve your skills

This part of the Indian wiki is under construction.

This Wiki page is not supposed to be a full manual of how to edit the Waze Map. It is an overview of subjects that are often confusing for starting editors, because they do not know the guidelines yet and their own logic tells them differently. This is not surprising because many of the guidelines have changed over the years and if you don't know the history, you don't always see the logic. All (starting) editors had this issue. And because guidelines are still changing and will keep changing, this will also happen to more experienced editors. In addition, the technical working of Waze changes often.

On this Wiki page, we have tried to combine technical knowledge of Waze with the users guidelines in India. It is a helpful tool for senior editors to refer to when explaining the concepts to starting editors. To keep duplicate texts to a minimum, we also refer to other Wiki pages [disclaimer].

The best advice we can give to starting editors is to just start. Pick a topic that is of interest to you and practice the guidelines. If anything is unclear, just ask your community.

Other editors are very willing to help. While reading the information in the Wiki or getting it from other editors, please keep in mind that, like in real life, also in Waze things are not always black and white. That is why we say we don't have rules or regulations, but guidelines. You may receive several opinions from two experienced editors and both can be correct, although a different interpretation. In addition, exceptions to guidelines are always possible and not a problem, provided you have good arguments.

Waze is not a map, but a navigation system

Most mistakes are because of a misunderstanding of the overall principle: 'Waze is not a topographic map, but a navigation tool'. Many starting editors try to make the map in Waze an exact copy of the actual situation. Roads are split; pedestrian boarding walks and cycle paths are added; perfect rounded corners and area places are exactly drawn. The actual goal of Waze is to get the best routing instructions. The less detail on the map, the easier and faster a map can be interpreted during driving, especially on small smartphone screens.

Another reason to keep the detail as low as possible is speed. The less details the less bandwidth the downloading of the map requires. Also the less junctions there are, the faster the route calculation is. The number of junctions that Waze can handle in one route is limited. So keeping the number of junctions as low as possible allows for a longer route.

To help you Waze has created a number guidelines. That is what this page is about.

Editing errors are inevitable

Everybody, without the need of any prior knowledge or practice, can start editing the Waze map. Therefore, Waze accepts the risk that users make edits that seems logical to them, but lead to undesired results. The Waze community is enthousiastic and active, so the mistake will often quickly be noticed. A more experienced editor will contact you to correct the mistake or do the correction himself. It is not meant as criticism, but an encouragement to learn more about editing.

Mistakes are often the result of a misunderstood or unknown guideline, or a lack of technical knowledge. In fact, there is only one true "mistake" you can make, which is withholding from communication with other editors.

Make sure that other editors can contact you

The only true mistake you can make as an editor, is being unreachable to other editors. If editors spot your edits with an undesired result, or if they don't understand the reason why you made this edit, they will try to contact you. They want to increase the quality of the map and at the same time help you to become a better editor. If other editors cannot reach you, they cannot help you! Moreover, they will probably change your edits according to their own interpretation of the situation.

Therefore, make sure that you can receive e-mails from Waze by providing a valid mail address. Check your mailbox regularly. Also check whether e-mails from Waze are not delivered to your spam- or junkfolder. You might want to make a filter to move the e-mails from Waze to a specific folder, or even create a separate mailbox for Waze. If needed, adjust your Waze settings. See the extended info about communication tools.

You might also want to get in touch with your community and get to know the Area Managers in your neighbourhood (link) who have shown good editing skills and have been allocated a specific area to look after.

go back to the table of content or back to the top

Basic principles of Waze

Because Waze is a navigation tool and not a topographic map, some things may be drawn differently than expected. Waze is developed for drivers of cars and should not be used for other means of transportation like pedestrians, pedal cyclists, public transport, or commercial transport. Also, Waze is not meant to include your personal favorite places, historic railways and illegal shortcuts. While editing, keep in mind the following 3 principles:

Usability

When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed.

Simplicity

It is not a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance.
Do NOT map every road you see. Waze is meant for car drivers. If a road is not accessible to cars, it often is not useful to draw this in Waze. Pedestrian area's are usually only drawn if they are useful for navigational purposes. When in doubt, contact a more experienced editor.

Retention

As a result of people driving with Waze on, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is deleted too. Given a choice between deleting a tangle of segments and creating new ones, or untangling them and reusing them, it is often better to "recycle".
Does the area look different on the satellite view than the roads show? Check if the roads have been recently updated before changing it - satellite imagery might not be up te date.
Are you working in an area which has been edited recently? Remember that this has been done by other editors who have invested their time trying to make the roads and cities as accurate as possible, so please be careful before changing others' work. Rather contact the editor first and discuss the changes.

go back to the table of content or back to the top

Common functional problems

Incorrect or incomplete data can have a negative effect on the navigation or even make it impossible to navigate to a specific location. We call these functional mistakes and they should be corrected as soon as possible. Functional mistakes are, if noticed by an other editor, often directly corrected because of the great impact to the functionality of the App.

Unnamed roads

When a road does not have a city- or street name, it will get a red outline in WME and it won't be used for navigation. These roads can originate from

Paving roads, that are not confirmed in WME
an editor added a road, but forgot to give it a name

Fill in the city and street name by selecting the segment, than click in the top left of the menu. If you don't know the name of the street or the city, check None.

Before you delete a segment, first consult the editor who added it. If you think the segment is an improvement to the map, fill in the missing data. Also check the junction arrows; when an editor has forgotten to fill in the name, probably the junction arrows are not set either.

Read more information about how to create a road.

go back to the table of content or back to the top