|Please be sure to login to see the latest content.|
This page serves as the primary resource for editors of Ohio. Review all the sections to better understand how the guidelines for this state might deviate from the overall USA or worldwide guidelines. If you have any comments or questions about this page or state refer to the community links below.
- 1 Introduction
- 2 Mapping resources
- 3 Community
- 4 Cities and towns
- 5 Major roads
- 6 Special roads
- 7 Lock Levels
- 8 Update Requests
- 9 Closures
- 10 Places
- 11 Cameras
- 12 To do list
- 13 Area Managers
- 14 Other states and territories
- 15 About this page
Ohio is a part of the Great Lakes region, which includes the states and/or territories of:
Before editing the maps in Ohio, be sure to fully review and understand the editing manual.
The Waze user community follows the Waze etiquette guidelines discussed in the Wiki. Be sure to familiarize yourself with these guiding principals while editing the maps and this Wiki, as well as when communicating with other Waze users.
The Waze forum is a great place to find answers to previously asked questions and also a place to ask new ones. Below are links to the forums specific to Ohio.
- Ohio section of Waze forum
- The Great Lakes region forum
- The USA section of Waze Forum
- The USA segment unlock requests
New editors should consider checking into the formal mentoring program available at no charge.
Cities and towns
One of the most common errors when editing the maps is when an editor creates a road and does not confirm the road by setting the city and road name (or stating it has none).
Some states and territories manage a separate page on cities and towns to identify the specific city names that should be entered, and no others. For states that do not have a separate page to track the names, see this Wikipedia link and find the state or territory in question.
Some states have a separate page to track and identify the major roads in the state, but at this time, this one does not have such a page.
Ohio follows the standard USA guidelines for all of the following special road types.
- Divided highways and roadways
- Carpool, HOV, Transit lanes
- Roundabouts and traffic circles
- Dirt roads
- Toll roads
- Partial and scheduled restrictions
- Private installations and military bases
Review the Wiki guidelines for non-drivable roads to ensure compliance with the general guidelines.
Ohio implements a version of the (still-solidifying) Great Lakes Region minimum lock levels for Waze road types:
- "Sensitive" Areas: L6
- : L5
- : Highest Connected Segment (HCS)
- Advanced intersections (e.g., MUTI, RCUT, DLT): L4
- (MH): L3
- (mH): L3
- Areas where aerial imagery does not match reality due to construction: L3
- One-way: L3
- Two-way: L2
- One-way: L2
- One-way: L1
- All Others: L1
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.
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 and L2 will be minimum of L3.
One wayand 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.
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.
- 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
- 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.
The Federal Highway Administration keeps a website indexing all states that can provide highway and construction project information. Go to the page, find your state, and check the links for the desired information.
Not every camera-looking device at an intersection is a speed or red light camera. Generally speaking:
Be sure to know your cameras before accepting new camera reports.
Currently only the Waze client app can add cameras to the map. When adding a camera from the app, be sure to review the camera placement recommendations.
Laws regarding speed and red light cameras vary between the states and territories, so be sure to understand the details of camera legality in Ohio.
No other camera types should be mapped in Waze.
Based on information researched at the time this page was created, Waze editors have not determined the legality of red light or speed cameras in Ohio.
To do list
Many states and territories keep an active list of pending or closed actions that need to be done in the state by the editors. All editors are welcome to contribute to the list of activities.
This state does not currently have an active "to do" list at this time. Check in the Ohio section of the Waze forums to discuss creating one.
The table below identifies the editors also designated as Area Managers or higher who are editing in Ohio. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers Ohio, or a USA Country Manager that does a lot of work in Ohio, please add yourself to this list (alphabetical by username) in the correct rank section.
The editor who also serves as the Regional Coordinator for Ohio is automatically listed at the top of the table. That editor may not be highly active in this state and therefore may not be listed separately in the table.
|Ohio — Area, State and Country Managers|
Regional Coordinator(s): GizmoGuy411 ( ) and SkiDooGuy ( )
| Country Managers (Great Lakes region)|
|SkiDooGuy(6) [ ]||RC (acting)|| |
|GizmoGuy411(6) [ ]||RC (on hiatus)|| |
|TerryPurdue(5) [ ]||Country Mgr, USA|| |
|State Managers (Great Lakes region)|
|Helgramite(5) [ ]||State Mgr, Ohio|| |
|ohiostmusicman(5) [ ]||State Mgr, Ohio|| |
|TerryPurdue(5) [ ]||State Mgr, Ohio|| |
| Area Managers |
Other states and territories
About this page