No edit summary |
mNo edit summary |
||
| Line 11: | Line 11: | ||
}} | }} | ||
<br /> | <br /> | ||
==Alleys== | |||
Generally alleys are not mapped in Wisconsin. Alleys are drivable roads passing between or behind buildings and are not intended for thru-traffic. They can be an important component in routing when primary access is not on a local street or drivers start or end a route on an alley. However, their existence also presents many routing problems. Please avoid mapping alleys unless they meet the criteria set below: | Generally alleys are not mapped in Wisconsin. Alleys are drivable roads passing between or behind buildings and are not intended for thru-traffic. They can be an important component in routing when primary access is not on a local street or drivers start or end a route on an alley. However, their existence also presents many routing problems. Please avoid mapping alleys unless they meet the criteria set below: | ||
| Line 25: | Line 25: | ||
Please consult with an LAM or SM before adding or removing alleys to verify whether a certain alley would meet the criteria to be mapped. | Please consult with an LAM or SM before adding or removing alleys to verify whether a certain alley would meet the criteria to be mapped. | ||
==Left-turn lane(LTL)== | |||
=== Should the left turn lane be mapped? === | |||
Left-turn lanes should only be mapped in very limited circumstances- | |||
* When there is a raised curb or median between the left turn lane and the through lanes for a long distance before the intersection that the driver might overshoot while waiting for a delayed "turn" audible. Wisconsin DOT calls these slotted left-turn lanes [http://wisconsindot.gov/rdwy/fdm/fd-11-25.pdf] [http://wisconsindot.gov/rdwy/fdm/fd-11-25-att.pdf#fd11-25a5.3]. The main reason to map these in Wisconsin is the DOT has built many slotted left-turn lanes. | |||
-or- | |||
* When the turn lane physically separates from the main road well in advance of the intersection | |||
* When there are user complaints (Update Requests) that the audible was too late, or that the map should have shown a left-turn lane | |||
The routing server does not play nice with LTLs and will often create unnecessary right-turn/ U-turn or U-turn/ right-turn to route a left through these intersections. Often a junction box is required to help with routing when LTLs are created. | |||
When in doubt, leave it out. Each left-turn lane complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. | |||
=== {{anchor|How to label the connector type}} Road type === | |||
[[Image:Left_turn_Lane_1.PNG|right|border]]Essentially these left-turn lanes are the same road as the through road, we are just adding a segment for better turn instruction timing, so they should be mapped using the same road type as the through road. | |||
*Ex: Street to Minor Highway should be Street type. | |||
*Ex: Minor Highway to Primary Street should be Minor Highway type. | |||
*Ex: Primary Street to Primary Street should be Primary Street type.{{clear}} | |||
=== {{anchor|How to name the connector}} Road name === | |||
In most cases, checking None for the Street name will be sufficient. Navigation instructions will simply use the name of the next segment to which the left-turn lane segment connects. | |||
If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the left-turn lane. | |||
=== {{anchor|Turn restrictions necessary for proper connector routing}} Geometry and Turn restrictions === | |||
In general using geometry is sufficient for the desired turn instructions- keep left instruction entering the turn lane and turn left instruction at the turn. When geometry won't work use TIOs for these instructions. | |||
==== Divided road ==== | |||
[[Image:Left_turn_lane2.PNG|right|border]]Add turn restrictions to the left turn lane segment to prevent U-turn(if applicable) and right turns.{{clear}}[[Image:Left_turn_lane3.PNG|left|border]]Add turn restrictions to the adjacent through lane segment left turn(to force use of the left turn lane).{{clear}}{{clear}} | |||
==== Non-divided road ==== | |||
[[Image:Left_turn_lane4.PNG|right|border]]Add turn restrictions to the left turn lane segment to prevent right turns.{{clear}} | |||
[[Image:Left_turn_lane5.PNG|left|border]]Add turn restrictions to the adjacent through lane segment left turn(to force use of the left turn lane) and prohibit U-turns.{{clear}}{{clear}} | |||
=== Speed Limit === | |||
Left-turn lanes should be mapped using the speed limit of the segment feeding into the left-turn lane(unless signed otherwise). | |||
== Speed Limits == | == Speed Limits == | ||
Revision as of 13:54, 29 October 2018
 |
As of April 23, 2018[update], the new road type Passageway is available in the WME. The routing, display, and restriction details of Passageway are not finalized, and it is not functional on the routing servers (it acts like a Local Street ). At this time, DO NOT use the Passageway road type in the USA without explicit champ approval for each instance. |  |
Alleys
Generally alleys are not mapped in Wisconsin. Alleys are drivable roads passing between or behind buildings and are not intended for thru-traffic. They can be an important component in routing when primary access is not on a local street or drivers start or end a route on an alley. However, their existence also presents many routing problems. Please avoid mapping alleys unless they meet the criteria set below:
Alleys should only be considered for mapping when one of the following criteria is met:
- a) the main access to a business entrance is on an alley,
- b) a parking lot entrance is in an alley,
- c) current GPS tracks support a residential alley that is frequently used and would benefit from being added to the map, or
- d) a UR indicates an alley should be added.
Please do not add every alley in a residential neighborhood.
All alleys should have their road type set to Parking Lot Road , should be named "Alley", and speed limit should be set to 15mph unless otherwise posted.
Please consult with an LAM or SM before adding or removing alleys to verify whether a certain alley would meet the criteria to be mapped.
Left-turn lane(LTL)
Should the left turn lane be mapped?
Left-turn lanes should only be mapped in very limited circumstances-
- When there is a raised curb or median between the left turn lane and the through lanes for a long distance before the intersection that the driver might overshoot while waiting for a delayed "turn" audible. Wisconsin DOT calls these slotted left-turn lanes [1] [2]. The main reason to map these in Wisconsin is the DOT has built many slotted left-turn lanes.
-or-
- When the turn lane physically separates from the main road well in advance of the intersection
- When there are user complaints (Update Requests) that the audible was too late, or that the map should have shown a left-turn lane
The routing server does not play nice with LTLs and will often create unnecessary right-turn/ U-turn or U-turn/ right-turn to route a left through these intersections. Often a junction box is required to help with routing when LTLs are created.
When in doubt, leave it out. Each left-turn lane complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc.
Road type
Essentially these left-turn lanes are the same road as the through road, we are just adding a segment for better turn instruction timing, so they should be mapped using the same road type as the through road.
- Ex: Street to Minor Highway should be Street type.
- Ex: Minor Highway to Primary Street should be Minor Highway type.
- Ex: Primary Street to Primary Street should be Primary Street type.
Road name
In most cases, checking None for the Street name will be sufficient. Navigation instructions will simply use the name of the next segment to which the left-turn lane segment connects.
If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the left-turn lane.
Geometry and Turn restrictions
In general using geometry is sufficient for the desired turn instructions- keep left instruction entering the turn lane and turn left instruction at the turn. When geometry won't work use TIOs for these instructions.
Divided road
Add turn restrictions to the left turn lane segment to prevent U-turn(if applicable) and right turns.
Add turn restrictions to the adjacent through lane segment left turn(to force use of the left turn lane).
Non-divided road
Add turn restrictions to the left turn lane segment to prevent right turns.
Add turn restrictions to the adjacent through lane segment left turn(to force use of the left turn lane) and prohibit U-turns.
Speed Limit
Left-turn lanes should be mapped using the speed limit of the segment feeding into the left-turn lane(unless signed otherwise).
Speed Limits
Wisconsin has no variances from the USA Speed Limits wiki: USA Speed Limits Wiki
Speed Limit Effective-Location for Wisconsin
Speed Limits in Wisconsin change at the sign. This is important when determining where speed limit changes should be marked on the Waze map. USA guidance for states that "change at the sign" is given here.
Where speed limits change is an important decision for clear guidance to drivers. There are many considerations for appropriately marking speed limit changes on the map. Editors, especially new editors, should be familiar with the USA Speed Limits wiki, a link to which is shown above.
For example, if there is an intersection within 200 feet of the speed limit sign, then the speed-change location should be made at that intersection. If the speed-change location is within 200 feet of an existing junction node, not an intersection, then we don't add a new junction node.
Alleys in Wisconsin - max speed is 15 mph unless posted otherwise.
Always refer to the USA Speed Limits wiki for guidance, and check with your Area or State Managers for clarification if needed.
Update Requests
Wisconsin is using the Great Lakes region Update Requests Response System:
Overview
NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter.
Response Timeline
- Day 0: the first editor who is able to respond to UR should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it closed. If more information from the reporter is required to make progress towards closure, a response should be sent to the reporter containing the information needed for resolution
- Day 4+: polite reminders should be sent to reporters who have not responded to the initial request for information at any time, provided at least four full days have elapsed since the initial response was sent.
- Day 8+: URs may be noted as closed due to lack of reporter response at any time, provided at least four full days have elapsed since the followup message was sent
Shared Ownership:
- All editors are considered to have equal ownership of and responsibility for all URs in the Great Lakes Region.
- All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere to the minimum time spacing guidance between responses.
- All editors are explicitly encouraged to attempt resolving URs at any point during their lifecycle, even if others happen to be actively working it at the same time
Notes:
- The ideal timeline for UR response is when responses are sent as early as the minimum required time spacing between messages permits; experience has reliably shown that UR response rates are much higher when editors are able to send responses promptly
- While strongly recommended, it is not required to send the followup message.
Process Chart
