Ohio/Special roads/Main: Difference between revisions Discussion View history

Latest revision as of 18:28, 24 December 2018

Press here to return to the Special roads section to see your changes

Speed Limits

Ohio has no variances from the USA Speed Limits Wiki

Speed Limit Effective-Location for Ohio

Speed Limits in Ohio 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 Ohio - max speed is 15 mph.

Always refer to the USA Speed Limits wiki for guidance, and check with your Area or State Managers for clarification if needed.

Update Requests

Ohio 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 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 describe above, provided they adhere 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.

@@ Line 2: / Line 2: @@
 ------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
-== Lock Levels ==
+== Speed Limits ==
-Ohio implements a version of the (still-solidifying) Great Lakes Region minimum lock levels for Waze road types:
+Ohio has no variances from the [[Speed_limits/USA | USA Speed Limits Wiki]]
-* "Sensitive" Areas: '''L5''' (determined on case-by-case basis by SMs with RC approval, but intended for rare cases such as major freeway interchanges where aerial imagery does not match reality due to construction, high-security private installations, etc.)
+=== Speed Limit Effective-Location for Ohio ===
-* {{Freeway}}: '''L5'''
-* {{Ramp}}: '''Highest Connected Segment''' (HCS)
-* Advanced intersections (e.g., [[At-grade_connectors#Exceptions | MUTI, RCUT, DLT]]): '''L4'''
-* {{Major Highway}} (MH): '''L3'''
-* {{Minor Highway}} (mH): '''L3'''
-* Areas where aerial imagery does not match reality due to construction: '''L3'''
-* {{Primary Street}} (PS)
-** ''One-way'': '''L3'''
-** ''Two-way'': '''L2'''
-* {{Street}}
-** ''One-way'': '''L2'''
-** ''One-way'': '''L1'''
-* All Others: '''L1'''
-{{Ramp}} segments are locked to the highest level of all segments that they share a junction with.  '''I.e.''' any ramp connected (directly or indirectly through other ramps) to a Freeway will have a minimum lock of  '''L5'''; a ramp connecting an L3 {{Major Highway}} and L2 {{Primary Street}} will be minimum of '''L3'''.
+Speed Limits in Ohio 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 [[Speed_limits/USA#State_law_speed_limit_changes_at_the_sign | here]].
-One way {{Primary Street}} and {{Street}} sections have their minimum lock level set one lock level higher than their two-way equivalents to clearly demonstrate to other editors that the necessary research has been performed to confirm they are, in fact, one-way in real life.
+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 Ohio - max speed is <b>15 mph</b>.
+Always refer to the USA Speed Limits wiki for guidance, and check with your Area or State Managers for clarification if needed.
+== Update Requests ==
+Ohio is using the [[USA/Great Lakes/Test#Update Requests | 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 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 describe above, provided they adhere 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 ===
+[[File:GLR_-_UR_Process_20150606.png|700px]]
 <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
 -------------------------------------------------------------------------------------

Search