User:Moweez/SouthAsiaSupport/Editing/Improve your skills
Improve your skills
|This page 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 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 general needs in South Asia. 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].
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. Exceptions to guidelines are always possible and not a problem, provided you have good arguments.
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 the South Asia Support Slack community on Slack platform].
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 divided; walking trails are added; perfect rounded corners and area places are exactly drawn. The actual goal of Waze is to get the best routing instructions with the least possible data and clear instructions on a small screen. The lesser 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 few as possible is speed. The lesser details, the lesser bandwidth the downloading of the map requires. Also the lesser 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, especially on longer routes.
To help you Waze has created a number guidelines. That is what this page is about.
- 1 Improve your skills
- 1.1 Waze is not a map, but a navigation system
- 1.2 Common functional problems
- 1.3 Local agreements (that are not logical at first glance)
- 1.4 Starting editors: what you can do best
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 enthusiast 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.
Errors are often the result of a misunderstood or unknown guideline, or a lack of technical knowledge, and cannot be really viewed as a fault. 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.
For South Asia, there is special communication platform at South Asia Support Slack, free entrance.
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 motorcycles, 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:
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.
- 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.
- 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.
- Another reason to be cautious with deleting segments is that another editor had a reason to add it. It can be very demotivating when someone just deletes work without any consultation. Everybody can make a mistake, or guidelines can be changed over time. Preferably consult the editor who added the segment, rather than change the segment yourself.
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. This 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.
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
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.
Junction Arrows (JA)
Junction Arrows are the red, green en orange arrows when you select a segment. They control which turns are allowed. Green is allowed, red is not allowed and orange is |partially restricted. Restrictions can be set in time, vehicle type or passes if applicable.
When you change the driving direction of a segment always remember to check the junction arrows. The WME does not adjust them automatically based on the driving direction. The quickest way to correct hem is to select the junction and press q and w or click on the button 'Allow all turns'. When creating a new road by default all JA's are red. In the advanced settings of the editor check the option 'Draw new roads with all turns allowed'. If you select this option, it is advised to also check the option 'Draw new roads as two-way'.
An easy way to check incorrect red junction arrows is Shift-Z. This will show all the red arrows in the area on your screen, also for the not selected segments. Of course these are not all incorrect, but you can check them. It is advised to before you do the correction, you press Shift-Z again and select the segment with the red arrow. Otherwise you can not see which segment has the red arrow.
Turn instructions Overrides
If the default turn instructions are not clear, you can use a Turn Instruction Override (TIO). A TIO allows editors to manually set a turn arrow to give a non-default text and verbal instruction to the driver making that turn through a junction.
- Hoover over the arrow, and change the voice prompt in the popup box.
However, use it it sparsely and only if needed. Otherwise it is just adding extra load to the engine and it clutters WME as well. Advanced info on how Waze determines instructions can be found in the global page on turns, keeps and exits.
Even when segments appear to be connected on your screen, it does not necessarily mean they actually are properly connected. The fastest way to check this is to select one of the segments. When you don't see the Junction Arrow(s) light up, it is not connected.
When a road should be connected, please check the Junction Arrows. If it is not connected, move the end node away from where it should connect, and drop it somewhere else. Than pick it up again and drag it to where you want the junction to be. WME now automatically creates a junction. Again, check the Junction Arrows.
If you cannot connect a segment using the above described method, one of the segments could have a lock level higher than your editing level. In that case you cannot solve this functional mistake yourself and you might want to ask for an unlock. If the segment is a pedestrian boardwalk, check whether this segment should be connected anyway. If you are unable to connect the segment and cannot get a hold of a more senior editor that can make the connection, leave a gap between the 2 segments. That way it is clear to other editors that this segment still needs to be connected. If you place it onto the other segment it will look ok at first glance but routing instructions will not function properly.
To protect the map from unwanted errors, some segments are secured with a lock. Important main roads will show higher locks than small side streets. Locked roads can only be changed by editors with a rank the same or higher than the lock level. Even if you succeed to edit such a segment, you won't be able to save your changes. Also, you will not be able to connect other roads to locked roads. If you try to do that, it will result in disconnected segments, like described in the previous paragraph.
When you want to change a segment with a higher lock level than your own rank, propose your changes to a higher rank editor, or ask a temporary decrease in lock level. You always need to make a permalink, and specify the region or city, and the needed rank.
Use one of the following methods:
- Use the South Asia Support Slack channel of your country.
- Use a private message (DM or PM, in Slack or forum) to ask the last editor, who is visible at the bottom left of your screen when selecting the segment.
Incorrect use of roundabouts
Roundabouts, rotaries, or traffic circles, are unique segments in the Waze routing engine. When a driver approaches a roundabout segment, a specific icon is displayed in the turn direction area of the display with a number corresponding to the exit count. A roundabout gives you instructions like: "On the roundabout, take the 3rd exit" or, "On the roundabout, go left" depending on the way of drawing.
Some issues often found with roundabouts:
- A roundabout should be assigned the same road type as the highest type connected.
- Roundabout segments have no street name in the primary field (check the None box)
- Each connected road segment use 1 specific node. Connecting 2 segments to 1 roundabout node will corrupt the instructions
- A dead-end street or cul-de-sac should not have a roundabout at the end.
However, the use of roundabouts might be confusing. For very large roundabouts, where people might loose track of the count, working with a normal road using Keeps left/right, might be more helpful.
Other examples can be rounds at divided roads, where the ongoing roads are in fact not using the roundabout. Always ask yourself, what kind of instruction will you hear or see in the app? Do that for every road into every direction.
In the picture, if you want to travel from segment 1 to segment 3, you will now get "On the roundabout, take the 2nd exit". That is not conform the actual situation for the driver, who just drives straight. In this case, a roundabout might thus yield confusing instructions.
Some alternative solutions for such junctions are the following:
Intersections that could cause confusion like described above, should be locked to at least level 3. If you have any doubt, please ask a senior editor or local champ for advise.
How to create a roundabout is described in the Quick Start Guide.
Private access roads that distort routing
Waze finds your destination based on GPS coordinates, in a lot of cases from Google. Based on those coordinates it pins your destination. Then it looks for the closest drivable road, without looking at the name of that road. So that means if the driveway of the rear neighbors is closer to the pin of your destination then you will be lead to the wrong road. And when this is a long road, it can be far of from your actual destination.
Local agreements (that are not logical at first glance)
to be added
The relation between the satellite view and map
The satellite view may be outdated or doesn´t show everything. For example, a road in a forest is probably not visible on the satellite view. Thus, use the satellite view as a source, not as a goal to copy. In case the road is mapped differently, please consult the previous editor or the area manager. It is recommended to add a Map Comment (MC) in such situations.
Too many geometry nodes
Too many geometry points can slow down the build of your screen. Also, it is harder to maintain the map. Therefore, we use as few nodes as possible, even if that means that a road in Waze does not exactly follow the road in the Satellite View. If a segment has too many nodes, please remove them by hovering your mouse over the nodes, and press d.
For more information see the Changing elements on the map paragraph in the Quick Start Guide.
Splitting up roads
We always try to keep the map simple and effective. Hence, roads having 2 or more lanes general don't need to be split into 2 lanes. There are a lot of consequences to splitting as well as to unsplitting. The best guidance we can give in early stages of the map is to leave it as you find it as long as there are no problems (e.g., local reports).
Reasons NOT to divide:
- Flyovers, bypasses and Highways with Service Lanes need not be split. They rarely have turns in between them. Also, not splitting, will give a better chance to a correct GPS fix between ground roads and the flyover, or service roads and the bypass or main highway. Only split them when the lanes are really too far apart for GPS to fix properly (depending on GPS accuracy guideline is about 20m)
- Zoom Level: When GPS Tracks are not clearly definable at the 100m/500ft zoom, i.e. zoom level 4. _This criteria matches with criteria mentioned in the global wiki_
- Road Branches: When there are not many branches from road segments on either side of divider/median in a short distance.
- Matching objective: When the objective is solely to match the visual appearance or match other sources.
- For lane guidance: Waze will install Lane Guidance in a different way
If you still think a a road needs to be divided into multiple lanes, please watch this video how to split roads while keeping traffic data. There is a video on how to unsplit (merge) lanes as well.
Other means of splitting/combining can be found in the [Start Guide].
Update request (UR)
While driving, a driver can report a problem by submitting an Update Request (UR). Often there is not enough time to fully describe the issue. Therefore, Waze developed the possibility to start a conversation in the UR. Whenever you respond to an UR, you should do this with care and attention. The user does not report if he or she doesn't encounter a problem! It is your task to solve the problem as best as you can, or find the help needed to solve it. By solving the user's problem, we can improve Waze to serve the needs of all Wazers. Never just close a UR, even if you think it is bogus. See the guidelines for handling URs in India.
Starting editors: what you can do best
Everywhere you have driven with Waze on, you can edit. As the map of India needs a lot of work, there is a lot to do. Keep in mind that when you start, you are probably not aware of all the background processes. We tried to explain that in the Indian Wiki, but you cannot learn everything at once. So, start at the section Editing#How_to_start>how to start and get in touch with your community. And then, just start! It is the most efficient way to learn how to use the map editor and get to a higher level.
To give some extra support, we have made two lists: one with actions you better postpone or be extremely cautious with, and the other one you can do easily as a starting editor.
Risky actions for starting editors
Unless you work together with a mentor, we suggest the following don'ts when you start:
- Don't deleting road-segments. This also deletes the historic traffic information, e.g. the historic average speed.
- Do not change or delete segments that are connected to locked segments.
- Do not split (undivide) roads, even when there lanes are physically split.
- Do not add non-drivable roads, like pedestrian boardwalks, cycle paths, railways, runways and bus lanes. This seems harmless, but they can result in wrong navigation. It will also clutter the map and increase the amount of bandwidth used.
- Do not change the road type, this has a big influence on the navigation.
- Do not close update requests or make changes based on them. If you want to help, because you have local knowledge, please make a comment that can help a more experienced editor.
If you think the map needs one of the above mentioned actions, please get in touch with the community to get assistance.
Things a starting Waze-editor can do
- Read the Quick Start Guide.
- Check if streetnames are filled in and spelled correctly.
- Check if the city names in your area are correct.
- Check the driving direction of streets. You can base this on Streetview within Waze, the GPS tracks and your own local knowledge.
- Check if Junction Arrows (link) are set correctly. With Shift-Z you will see all the red arrows. When you suspect a red junction arrow to be incorrect, first do Shift-Z again and select the segments connected to the junction one by one. That way you can see which segment has the red junction arrow.
- Check the category, name and address of Places (link). The name should be the official name of the place. If you know this place is referred to with other names then the official one, please add that name as a alternative name. That way the search will improve. Also check if this place is visible on the live map, if not, please convert it to a point place, when applicable.
- Inform the area manager of possible issues. If your area does not have an area manager yet, contact a champ. See the community page (link) on how to do that.
- Monitor road-closures in your neighborhood, see this [ forum topic] how to report them.
- Help with keeping the Wiki up-to-date and make it better (link to wiki forum).