m (→Description) |
(moved chart to within the description section) |
||
| Line 3: | Line 3: | ||
Places, segments within places, etc. will not be included in this particular discussion. | Places, segments within places, etc. will not be included in this particular discussion. | ||
== Description == | |||
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. | |||
{| class="wikitable" style="text-align:center" | {| class="wikitable" style="text-align:center" | ||
| Line 69: | Line 75: | ||
''Terms'' | ''Terms'' | ||
* HCS - Highest Connecting Segment | * HCS - Highest Connecting Segment | ||
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. | 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. | 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. | ||
=== Forum Discussion === | |||
This proposal is under discussion on the fourms, at the following link: https://www.waze.com/forum/viewtopic.php?f=943&t=118338 | |||
Revision as of 17:53, 10 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.
Description
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.
| Minimum Lock Settings | ||
|---|---|---|
| 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
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.
Forum Discussion
This proposal is under discussion on the fourms, at the following link: https://www.waze.com/forum/viewtopic.php?f=943&t=118338