Difference between revisions of "Ohio/Special roads/Main"

From Wazeopedia

< Ohio

Line 8: Line 8:
* "Sensitive" Areas: '''L6'''
* "Sensitive" Areas: '''L6'''
* {{Freeway}}: '''L5'''
* {{Freeway}}: '''L5'''
* {{Runway}}: '''L5'''
* {{Ramp}}: '''Highest Connected Segment''' (HCS)
* {{Ramp}}: '''Highest Connected Segment''' (HCS)
* Advanced intersections (e.g., [[At-grade_connectors#Exceptions | MUTI, RCUT, DLT]]): '''L4'''
* Advanced intersections (e.g., [[At-grade_connectors#Exceptions | MUTI, RCUT, DLT]]): '''L4'''

Revision as of 16:14, 7 December 2015

Lock Levels

Ohio implements a version of the (still-solidifying) Great Lakes Region minimum lock levels for Waze road types:

  • "Sensitive" Areas: L6
  •  Freeway : L5
  •  ⁃     ⁃        ⁃        ⁃        ⁃ Runway ⁃        ⁃        ⁃        ⁃        ⁃ : L5
  •  Ramp : Highest Connected Segment (HCS)
  • Advanced intersections (e.g., 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
  •  |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-| : L2
  •  Street 
    • One-way: L2
    • Two-way: L1
  • All Others: L1

"Sensitive" Areas

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.


 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.


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.

Update Requests

Ohio is using the Great Lakes region Update Requests Response System:


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


  • 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

GLR - UR Process 20150606.png