User:Ojlaw View history

(LTL)
No edit summary
Line 14: Line 14:
When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc.
When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc.


Left turn lanes should be mapped using the same road type as the thru lanes, with no name, and the speed limit should be set to SL of the segment feeding into the left turn lane. Essentially these lanes are the same road as the thru road so they should be mapped using the road type and speed limit of the through road.
Left turn lanes should be mapped as one-way, using the same road type as the thru lanes, with no name, and the speed limit should be set to SL of the segment feeding into the left turn lane(unless signed otherwise). Essentially these lanes are the same road as the thru road so they should be mapped using the road type and speed limit of the through road.


Use TIOs as necessary to give keep left instruction entering the turn lane and turn left instruction at the turn
In general using geometry is sufficient for the desired turn instructions for keep left instruction entering the turn lane and turn left instruction at the turn. When geometry won't work use TIOs for these instructions.
 
Add turn restrictions to prevent U-turn(if applicable) and to the thru-lane left turn(to force use of the left turn lane).

Revision as of 20:03, 14 March 2018

Function Classification Continuity

There are instances when the Waze road typ may need to be upgraded to preserve functional classification continuity. This happens

You're doing the routing engine a favor by interpreting what the intended flow of traffic is, as in "this PS is clearly designed to be the primary route between the limited access road and the mH/MH," this meaning you can justify the upgrade the PS to match the mH/MH

Left Turn Lane(LTL)

Left turn lanes should only be mapped in very limited circumstances-

  • When the turn lane physically separates from the main road well in advance of the intersection
  • When there is a raised curb between the left turn lane and the thru lanes for a long distance before the intersection that the driver might overshoot while waiting for a delayed "turn" audible.
  • When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a left turn lane lets you notify the driver a little earlier
  • When there are user complaints (Update Requests) that the audible was too late, or that the map should have shown a left turn lane

When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc.

Left turn lanes should be mapped as one-way, using the same road type as the thru lanes, with no name, and the speed limit should be set to SL of the segment feeding into the left turn lane(unless signed otherwise). Essentially these lanes are the same road as the thru road so they should be mapped using the road type and speed limit of the through road.

In general using geometry is sufficient for the desired turn instructions for keep left instruction entering the turn lane and turn left instruction at the turn. When geometry won't work use TIOs for these instructions.

Add turn restrictions to prevent U-turn(if applicable) and to the thru-lane left turn(to force use of the left turn lane).