(→Too long: draft proposal) |
(return the warning against unecessary junctions) |
||
| Line 1: | Line 1: | ||
===Too long=== | ===Too long=== | ||
Waze bots will add junctions to reduce the length of any segment longer than 100km. In addition, there are several good reasons to keep segments shorter than 10km: | Waze bots will add junctions to reduce the length of any segment longer than 100km. In addition, there are several good reasons to keep segments shorter than 10km (though they should still not have [[unnecessary junctions]]): | ||
* Long roadways or railroads with the city name present will cause a [[smudged city]] issue on the [[Map_Editor_Interface_and_Controls#Cities|city layer]]. | * Long roadways or railroads with the city name present will cause a [[smudged city]] issue on the [[Map_Editor_Interface_and_Controls#Cities|city layer]]. | ||
* Editors cannot change the name or properties of segments that extend outside of an editor's [[Waze_Map_Editor#Editable_Area|editable area]] | * Editors cannot change the name or properties of segments that extend outside of an editor's [[Waze_Map_Editor#Editable_Area|editable area]] | ||
* Long segments require more resources in the client and WME when rendering them on screen. | * Long segments require more resources in the client and WME when rendering them on screen. | ||
Revision as of 20:41, 23 March 2016
Too long
Waze bots will add junctions to reduce the length of any segment longer than 100km. In addition, there are several good reasons to keep segments shorter than 10km (though they should still not have unnecessary junctions):
- Long roadways or railroads with the city name present will cause a smudged city issue on the city layer.
- Editors cannot change the name or properties of segments that extend outside of an editor's editable area
- Long segments require more resources in the client and WME when rendering them on screen.