(Updating to match new version of source page) |
(Bijgewerkt vanwege een nieuwe basisversie van de bronpagina) |
||
(13 tussenliggende versies door 2 gebruikers niet weergegeven) | |||
Regel 1: | Regel 1: | ||
{{TopLine}} | {{TopLine}} | ||
[[Category:Editing]] | |||
[[Category:How To]] | |||
<languages /> | <languages /> | ||
==KISS As simple as possible, as complex as necessary== | ==KISS As simple as possible, as complex as necessary== | ||
Regel 13: | Regel 15: | ||
:Segments doesn't have to have the exact metres of paved road. | :Segments doesn't have to have the exact metres of paved road. | ||
<div class="mw-translate-fuzzy"> | |||
===Why ?=== | ===Why ?=== | ||
Why do we apply <i>KISS</i>? There are several reasonsː | Why do we apply <i>KISS</i>? There are several reasonsː | ||
:The available resources are limited, we have to use them in a optimal way. Each segment, each node, is data, consumes space and takes time to process, transmit | :The available resources are limited, we have to use them in a optimal way. Each segment, each node, is data, consumes space and takes time to process, transmit. | ||
</div> | |||
:How greater the number of segments, how less clear the map will be. In the [[Waze Map Editor|WME]] it is possible to zoom-in and zoom-out, in the [[Waze app|app]] this is difficult. We choose for a <i>clear and simple map</i>. | :How greater the number of segments, how less clear the map will be. In the [[Waze Map Editor|WME]] it is possible to zoom-in and zoom-out, in the [[Waze app|app]] this is difficult. We choose for a <i>clear and simple map</i>. | ||
: | :Andere redenen zoals de hoeveelheid te versturen data of problemen met het plaatsen van de Wazer op de juiste rijbaan ([[GPS]] locatie) speelt nu minder dan vroeger. | ||
===When ?=== | ===When ?=== | ||
Regel 35: | Regel 37: | ||
: Merge segments into one segment when there is no real added value to have more segments in terms of navigating and routing. | : Merge segments into one segment when there is no real added value to have more segments in terms of navigating and routing. | ||
<div class="mw-translate-fuzzy"> | |||
===Examples=== | ===Examples=== | ||
'''1-Reduce the number of nodesː'''<br /> | '''1-Reduce the number of nodesː'''<br /> | ||
Regel 65: | Regel 68: | ||
{{Clear}} | {{Clear}} | ||
'''8-A quite complex Major Highwayː'''<br /> | '''8-A quite complex Major Highwayː'''<br /> | ||
No need for splitting this highway, remove unnessary [[Pedestrian Boardwalk|pedestrain boardwalks]] and just use [[Street|streets]] instead of [[Ramp|ramps]]. | No need for [[Road_Aspects#Twee-richting_verkeer_segmenten_splitsen|splitting]] this highway, remove unnessary [[Pedestrian Boardwalk|pedestrain boardwalks]] and just use [[Street|streets]] instead of [[Ramp|ramps]]. | ||
<table><tr><td>[[File:KISS-12a.png|750px|before]]</td></tr> | <table><tr><td>[[File:KISS-12a.png|750px|before]]</td></tr> | ||
<tr><td>[[File:Kiss-12b.png|750px|after]]</td></tr></table> | <tr><td>[[File:Kiss-12b.png|750px|after]]</td></tr></table> | ||
<br /> | <br /> | ||
</div> | |||
__NOTOC__ | __NOTOC__ | ||
{{Bottomline}} | {{Bottomline}} |
Huidige versie van 28 mrt 2024 om 23:15
KISS As simple as possible, as complex as necessary
KISS is keeping the road geometry as simple as possible, without losing the essential driving instructions.
There is one important thing to always keep in mind when you edit the map: Waze is not a topographic map, but a navigation system! Over the years, the community discovered ways to edit the map in a way that maximizes navigation. Waze relies on a map’s display suitable for a small smart-phone screen. It needs a map that accurately instructs where cars can drive, is simple and clear, and uses real time traffic data bound to the parts on the map. Therefore, we follow the three basic principles "Usability, Simplicity, & Retention"; Make it useful, keep it as simple as possible. See also the global page on Best map editing practise
What ?
What is this KISS all about? Summarized: "As simple as possible, as complex as necessary". In short statementsː
- Simplify the map and segments as far as possible
- Make situations only as complex as needed
- Use segments only for routing, not for something like lane assistance.
- Segments doesn't have to have the exact metres of paved road.
Why ?
Why do we apply KISS? There are several reasonsː
- The available resources are limited, we have to use them in a optimal way. Each segment, each node, is data, consumes space and takes time to process, transmit.
- How greater the number of segments, how less clear the map will be. In the WME it is possible to zoom-in and zoom-out, in the app this is difficult. We choose for a clear and simple map.
- Andere redenen zoals de hoeveelheid te versturen data of problemen met het plaatsen van de Wazer op de juiste rijbaan (GPS locatie) speelt nu minder dan vroeger.
When ?
KISS is a principle. It is not about when , but we always apply the principle.
The following situations can but doesn't have to lead to road separationː
- There is a concrete road separation.
- There is a green zone between the two driving directions, the two driving directions are separated.
It is not easy to formulate simple and clear rules to describe which situations can be simplified for how far. We try to give some guidelinesː
- If you're looking in the WME at the GPS-tracks of the two driving directions on zoom level 5 (100 m / 200 ft) and you don't see a clear separation than the road should by simplified to one two directions road instead of two separated one directions roads.
- Merge segments into one segment when there is no real added value to have more segments in terms of navigating and routing.
Examples
8-A quite complex Major Highwayː
No need for splitting this highway, remove unnessary pedestrain boardwalks and just use streets instead of ramps.