Hawkeygoal (talk | contribs) (Introduced initial overview text) |
Hawkeygoal (talk | contribs) |
||
| (11 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
This will be a set of minimums. If a state feels they need a higher level for a particular segment type, they can adjust as needed, just not below the minimums. Also, this will focus solely on segments. | ''This will be a set of minimums. If a state feels they need a higher level for a particular segment type, they can adjust as needed, just not below the minimums. Also, this will focus solely on segments.'' | ||
== | Places, segments within places, etc. will not be included in this particular discussion. | ||
== Road Lock Standard == | |||
The following defines a set of ''minimum'' locking standards proposed for all '''roads''' within the Great Lakes Region. | |||
Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower. | |||
It is understood that more rural or inactive areas may not yet meet this standard: editors are encouraged to recruit and mentor additional editors to build state-wide coverage. | |||
A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current [https://wiki.waze.com/wiki/Road_types/USA#Quick_reference_chart US Road Type Standards]. | |||
=== Road Lock Standard (chart) === | |||
{| class="wikitable" style="text-align:center" | {| class="wikitable" style="text-align:center" | ||
!colspan="3" style="background-color:#6699cc"| | !colspan="3" style="background-color:#6699cc"|GLR Road Lock Standard | ||
|- | |- | ||
|style="font-weight:bold; background-color:#ccffcc"|Segment Type | |style="font-weight:bold; background-color:#ccffcc"|Segment Type | ||
|style="font-weight:bold; background-color:#ccffcc"| | |style="font-weight:bold; background-color:#ccffcc"|Direction | ||
|style="font-weight:bold; background-color:#ccffcc"|Level | |style="font-weight:bold; background-color:#ccffcc"|Level | ||
|- | |- | ||
| Line 16: | Line 24: | ||
|- | |- | ||
|{{Ramp|Ramp}} | |{{Ramp|Ramp}} | ||
| | | | ||
|HCS | |HCS* | ||
|- | |- | ||
|{{Major Highway|Major Highway}} | |{{Major Highway|Major Highway}} | ||
| Line 28: | Line 36: | ||
|- | |- | ||
|rowspan="2"|{{Primary Street|Primary Street}} | |rowspan="2"|{{Primary Street|Primary Street}} | ||
|One | |One-way | ||
|3 | |3 | ||
|- | |- | ||
|Two | |Two-way | ||
|2 | |2 | ||
|- | |- | ||
|rowspan="2"|{{Street|Street}}<br>{{Private Road|Private Road}} | |rowspan="2"|{{Street|Street}}<br>{{Private Road|Private Road}} | ||
|One | |One-way | ||
|2 | |2 | ||
|- | |- | ||
|Two | |Two-way | ||
|1 | |1 | ||
|- | |- | ||
| Line 60: | Line 68: | ||
|style="font-weight:bold; background-color:#ffffcc"| | |style="font-weight:bold; background-color:#ffffcc"| | ||
|style="font-weight:bold; background-color:#ffffcc"|Level | |style="font-weight:bold; background-color:#ffffcc"|Level | ||
|- | |- | ||
|Construction Areas<br><small>''(changes without aerial images)''</small> | |Construction Areas<br><small>''(changes without aerial images)''</small> | ||
| Line 72: | Line 76: | ||
* HCS - Highest Connecting Segment | * HCS - Highest Connecting Segment | ||
=== Additional Info === | |||
==== Expectations ==== | |||
We understand that higher locks mean there is less available to lower rank and beginning editors. We would like to emphasize that Waze Map Editing is a community activity and, within the US, it is not possible to increase to rank 3 or above without community involvement. It is the responsibility of all members of the editing community to actively reach out, recruit, and mentor new editors. | |||
It is OK to '''temporarily lock segments below standards''' for more junior editors. Area Managers are encouraged to monitor their areas for non-standard locks and follow up with other editors on any discrepancies. As a courtesy, any down-locks made outside your area should be brought to the attention of the local area manager. | |||
==== One-Way Streets ==== | |||
The +1 locks on one-way segments originated as guidance from GLR RC GizmoGuy411 based on trends found while performing Area Manager Reviews: | |||
He would encourage editors to +1-lock one-way street/PS in order to explicitly signal, "Yes, the legwork has been done in order to confirm this segment really is one-way, and it's not a soft-directional issue." | |||
== Discussion == | == Forum Discussion == | ||
This proposal is under discussion on the fourms, at the following link: https://www.waze.com/forum/viewtopic.php?f=943&t=174545 | |||
<!-- https://www.waze.com/forum/viewtopic.php?f=943&t=118338 --> | |||
Latest revision as of 15:47, 17 January 2016
Overview
This will be a set of minimums. If a state feels they need a higher level for a particular segment type, they can adjust as needed, just not below the minimums. Also, this will focus solely on segments.
Places, segments within places, etc. will not be included in this particular discussion.
Road Lock Standard
The following defines a set of minimum locking standards proposed for all roads within the Great Lakes Region. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
It is understood that more rural or inactive areas may not yet meet this standard: editors are encouraged to recruit and mentor additional editors to build state-wide coverage.
A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current US Road Type Standards.
Road Lock Standard (chart)
| GLR Road Lock Standard | ||
|---|---|---|
| Segment Type | Direction | Level |
| Freeway | 5 | |
| Ramp | HCS* | |
| Major Highway | 3 | |
| Minor Highway | 3 | |
| Primary Street | One-way | 3 |
| Two-way | 2 | |
| Street Private Road |
One-way | 2 |
| Two-way | 1 | |
| |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-| | 2 | |
| • • • • Ferry • • • • | 2 | |
| ⁃ ⁃ ⁃ ⁃ ⁃ Runway ⁃ ⁃ ⁃ ⁃ ⁃ | 5 | |
| Other Named Types | 1 | |
| Segment Group | Level | |
| Construction Areas (changes without aerial images) |
3 | |
Terms
- HCS - Highest Connecting Segment
Additional Info
Expectations
We understand that higher locks mean there is less available to lower rank and beginning editors. We would like to emphasize that Waze Map Editing is a community activity and, within the US, it is not possible to increase to rank 3 or above without community involvement. It is the responsibility of all members of the editing community to actively reach out, recruit, and mentor new editors.
It is OK to temporarily lock segments below standards for more junior editors. Area Managers are encouraged to monitor their areas for non-standard locks and follow up with other editors on any discrepancies. As a courtesy, any down-locks made outside your area should be brought to the attention of the local area manager.
One-Way Streets
The +1 locks on one-way segments originated as guidance from GLR RC GizmoGuy411 based on trends found while performing Area Manager Reviews: He would encourage editors to +1-lock one-way street/PS in order to explicitly signal, "Yes, the legwork has been done in order to confirm this segment really is one-way, and it's not a soft-directional issue."
Forum Discussion
This proposal is under discussion on the fourms, at the following link: https://www.waze.com/forum/viewtopic.php?f=943&t=174545