LostInMyMaps (talk | contribs) No edit summary |
LostInMyMaps (talk | contribs) |
||
| Line 2: | Line 2: | ||
In line with our Revised Waze Editing Philosophy, our mapping standards have changed in 2020. For more information, see [[new technology, new mapping standards]]. | In line with our Revised Waze Editing Philosophy, our mapping standards have changed in 2020. For more information, see [[new technology, new mapping standards]]. | ||
== Doglegs and micro-doglegs == | ==Doglegs and micro-doglegs== | ||
For years, doglegs and micro-doglegs map hacks have been used by map editors to: | For years, doglegs and micro-doglegs map hacks have been used by map editors to: | ||
* Force turn instructions before turn instruction overrides were introduced | *Force turn instructions before turn instruction overrides were introduced | ||
* Force lane arrows before lane arrow overrides were introduced | *Force lane arrows before lane arrow overrides were introduced | ||
* Make junction locations stand out on the map before the on-route turn arrow overlay was introduced, and more. | *Bypass the automated u-turn prevention mechanism | ||
*Make junction locations stand out on the map before the on-route turn arrow overlay was introduced, and more. | |||
They are no longer valid, as the Waze Map Editor and app limitations that necessitated them have been addressed with native features, and they can cause problems with snapper which is sensitive to the angle of the driver’s movements. The map needs to be as accurate as possible and representative of reality: the position of the segment on the road, and the direction and angle of intersecting segments are important to snapper. | They are no longer valid, as the Waze Map Editor and app limitations that necessitated them have been addressed with native features, and they can cause problems with snapper which is sensitive to the angle of the driver’s movements. The map needs to be as accurate as possible and representative of reality: the position of the segment on the road, and the direction and angle of intersecting segments are important to snapper. | ||
| Line 21: | Line 22: | ||
[[File:DoglegNo3.png|300x300px]][[File:DoglegYes3.png|300x300px]] | [[File:DoglegNo3.png|300x300px]][[File:DoglegYes3.png|300x300px]] | ||
== Segment stubs == | ==Segment stubs== | ||
Fictional segments added to an intersection to manipulate lane guidance. Not allowed, please remove if you find it. | Fictional segments added to an intersection to manipulate lane guidance. Not allowed, please remove if you find it. | ||
<nowiki>https://wazeopedia.waze.com/wiki/Commons/File:Map-hack-stubs.png</nowiki> | <nowiki>https://wazeopedia.waze.com/wiki/Commons/File:Map-hack-stubs.png</nowiki> | ||
== Roundabout hack == | ==Roundabout hack== | ||
Physically impossible turns on a roundabout to manipulate instructions. Not allowed, please remove if you find it. Failure to do so will make Gil cry. | Physically impossible turns on a roundabout to manipulate instructions. Not allowed, please remove if you find it. Failure to do so will make Gil cry. | ||
<nowiki>https://wazeopedia.waze.com/wiki/Commons/File:Roundabout-map-hacks.png</nowiki> | <nowiki>https://wazeopedia.waze.com/wiki/Commons/File:Roundabout-map-hacks.png</nowiki> | ||
== Segment map hack == | ==Segment map hack== | ||
Poor practice to manipulate routing based on times. Remove where possible to replace. | Poor practice to manipulate routing based on times. Remove where possible to replace. | ||
<nowiki>https://wazeopedia.waze.com/wiki/Commons/File:Map-hacks.png</nowiki> | <nowiki>https://wazeopedia.waze.com/wiki/Commons/File:Map-hacks.png</nowiki> | ||
Revision as of 04:45, 29 August 2021
 |
This page is now a final draft and has entered a review period for feedback. This page will go live on 13 September 2021. Please discuss this page with your peers and leaders, and share your feedback with the community. If you spot any typos or errors, please feed them back to LostInMyMaps. |
In line with our Revised Waze Editing Philosophy, our mapping standards have changed in 2020. For more information, see new technology, new mapping standards.
Doglegs and micro-doglegs
For years, doglegs and micro-doglegs map hacks have been used by map editors to:
- Force turn instructions before turn instruction overrides were introduced
- Force lane arrows before lane arrow overrides were introduced
- Bypass the automated u-turn prevention mechanism
- Make junction locations stand out on the map before the on-route turn arrow overlay was introduced, and more.
They are no longer valid, as the Waze Map Editor and app limitations that necessitated them have been addressed with native features, and they can cause problems with snapper which is sensitive to the angle of the driver’s movements. The map needs to be as accurate as possible and representative of reality: the position of the segment on the road, and the direction and angle of intersecting segments are important to snapper.
Where found, micro-doglegs should be removed, and the segments mapped with the above guiding principles. Add Voice Prompts (previously known as turn instruction overrides) and Lane Angle Overrides (LAOs) where necessary to provide the best driver experience.
Below are some examples of what to look out for and remove:
Segment stubs
Fictional segments added to an intersection to manipulate lane guidance. Not allowed, please remove if you find it.
https://wazeopedia.waze.com/wiki/Commons/File:Map-hack-stubs.png
Roundabout hack
Physically impossible turns on a roundabout to manipulate instructions. Not allowed, please remove if you find it. Failure to do so will make Gil cry.
https://wazeopedia.waze.com/wiki/Commons/File:Roundabout-map-hacks.png
Segment map hack
Poor practice to manipulate routing based on times. Remove where possible to replace.
https://wazeopedia.waze.com/wiki/Commons/File:Map-hacks.png