User:Voludu2/sandbox View history

(imagemap)
(inline length)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Locking Standard Latam
[[File:FreewayS-inS-out.png|200px|right]]
|lede=In our country we have a minimum locking standard for segments according to road type. Any road should be locked to at least the locking level in the table below. Roads that need more protection because of special situations (construction, inaccurate images, complicated design, frequent editing errors) may be locked higher. Do not leave roads locked lower than the minimum values below.
In these cases, we need to use a wayfinder configuration. Each wayfinder configuration will have one "IN" segment and two "OUT" segments.
|caption=Minimum Lock Level
==== Configuration ====
|title=Lock Level}}


<imagemap>Image:Venezuela_map.png
These configurations have been designed based on a very in-depth understanding of [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|Waze's standard rules for generating instructions]]. Please don't deviate from these precise configurations.
poly 217 16 147 40 123 84 63 128 22 270 57 291 111 343 124 313 148 317 166 295 182 302 227 275 188 197 189 133 206 67 [https://www.waze.com/editor/?env=row&lon=-71.92227&lat=10.57971&layers=517&zoom=0 group 1 - Maracaibo]
 
poly 205 413 221 390 262 354 294 301 266 275 233 259 180 314 169 350 209 377 [https://www.waze.com/editor/?env=row&lon=-71.14190&lat=8.58544&layers=5&zoom=0 group 4 - Merida]
* Each "stub" segment should be {{User:Voludu2/ttt}} long. This is long enough so it will not cause routing problems, but it is short enough to suppress display of the names (on Freeway stubs) and keep freeways looking contiguous (on Ramp stubs).
poly 262 153 262 183 279 211 254 230 230 226 211 178 194 120 200 93 239 101 [https://www.waze.com/editor/?env=row&lon=-71.32077&lat=10.39192&layers=517&zoom=0 group 3 - Cabimas]
poly 144 441 96 411 124 322 169 314 160 354 192 392 201 436 [https://www.waze.com/editor/?env=row&lon=-72.24877&lat=7.74774&layers=517&zoom=0 group 2 - Tachiba]
poly 347 216 281 169 269 184 285 215 264 235 232 238 237 255 271 265 274 273 303 278 326 273 [https://www.waze.com/editor/?env=row&lon=-70.44023&lat=9.35643&zoom=0 group 5 - Trujillo]
poly 556 380 515 310 435 349 328 275 294 287 278 346 213 406 206 431 284 440 393 381 [https://www.waze.com/editor/?env=row&lon=-70.19673&lat=8.62176&layers=5&zoom=0 group 6 - Barinas]
#<!-- Created by Online Image Map Editor (http://www.maschek.hu/imagemap/index) -->
</imagemap>

Latest revision as of 18:33, 5 April 2016

In these cases, we need to use a wayfinder configuration. Each wayfinder configuration will have one "IN" segment and two "OUT" segments.

Configuration

These configurations have been designed based on a very in-depth understanding of Waze's standard rules for generating instructions. Please don't deviate from these precise configurations.

  • Each "stub" segment should be

5 m (16 feet) long. This is long enough so it will not cause routing problems, but it is short enough to suppress display of the names (on Freeway stubs) and keep freeways looking contiguous (on Ramp stubs).