The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "Template:Lock Standard State"

From waze
Jump to: navigation, search
(Updating WI locking note, as discussed on GHO)
m
 
(21 intermediate revisions by 10 users not shown)
Line 9: Line 9:
 
| CT
 
| CT
 
| ME
 
| ME
| NEW ENGLAND = {{Locking Standard
+
| NEW ENGLAND<!-- per Regional SM HO discussion with OrbitC on 2/11/16 https://www.waze.com/forum/viewtopic.php?f=945&t=177664&p=1328584#p1328582 -->
  <!-- per HO discussion with OrbitC same as NORTHEAST with special guidance -->
+
  |title=Statewide
+
  |Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=2
+
  |note=Exception: At the request of an AM (or other trusted local editor) a [[State Manager/USA | State Manager]] (SM) may optionally lower an entire area to facilitate local editing. Requests must be formally recorded in the [https://www.waze.com/forum/viewforum.php?f=622 US Unlock Forum], but can be discussed and pre-approved by an SM beforehand. The AM should request the locks be raised again to standard when the area has stabilized; the request should be made in the same thread where the unlock was originally requested. SMs should use caution when uplocking an area to standard: If the area is consistently locked below standard, it might have been granted such an exception, and should not be uplocked without verification.}}
+
 
| NJ
 
| NJ
 
| DE
 
| DE
| NORTHEAST = {{Locking Standard
+
| PA
  <!-- per forum discussion with OrbitC and old template -->
+
| NORTHEAST = {{Locking Standard<!-- per Regional SM Hangout discussion with OrbitC https://www.waze.com/forum/viewtopic.php?f=569&t=177663 -->
  |title=Statewide
+
    |title=Statewide
  |Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=2}}
+
    |Fwy=5
 +
    |Ramp=Highest rank of connected segments
 +
    |MH=3
 +
    |mH=3
 +
    |PS=1 (Auto)
 +
    |Street=1 (Auto)
 +
    |Private=1 (Auto)
 +
    |note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.
  
| NY = {{Locking Standard
+
Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of [[Detour Prevention Mechanisms/USA|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}
 +
| NY = {{Locking Standard <!-- https://www.waze.com/forum/viewtopic.php?f=569&t=177663 -->
 
     |title=NYC Only
 
     |title=NYC Only
     |Fwy=5|Ramp=Highest rank of connected segment|MH=5|mH=4|PS=3|Street=1
+
     |Fwy=5|Ramp=Highest rank of connected segment|MH=5|mH=4|PS=3|Street=1 (Auto)
 
     |title2=Everywhere Else
 
     |title2=Everywhere Else
     |MH2=4|mH2=3|PS2=2}}<!--A/p wiki-->
+
     |MH2=3|mH2=3|PS2=1 (Auto)|Street=1 (Auto)|Private=1 (Auto)
| PA = {{Locking Standard
+
    |note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.
<!--per HO discussion with OrbitC and PA state managers-->
+
 
|title=Statewide|Fwy=5|Ramp=Highest rank of connected segment|MH=3|mH=3|PS=2|Street=1|PLR=2{{ref|PLR}}|append={{note|PLR|1}}This rule should primarily apply to LARGE parking lots such as shopping malls/centers/plazas, tourist attractions/sports/music venues, large office buildings and schools/colleges.}}<!--A/p wiki-->
+
Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of [[Detour Prevention Mechanisms/USA|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}<!--A/p wiki-->
 
| TX = {{Locking Standard
 
| TX = {{Locking Standard
 
   |lede=In Texas we have a set minimum standard for locking roads based on segment type. 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. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.
 
   |lede=In Texas we have a set minimum standard for locking roads based on segment type. 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. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.
 
   |title=Lock Level
 
   |title=Lock Level
 
   |Fwy=5
 
   |Fwy=5
   |Ramp=Highest Rank of Connected Segment
+
   |Ramp=4
   |MH=5
+
   |MH=4
   |mH=4
+
   |mH=3
   |PS=3
+
   |PS=2
   |Street=Automatic (1)
+
  |Private=2
  |Private=Inquire with RC or SM}}
+
   |Street=Automatic (1)}}
  
 
| CA = {{Locking Standard
 
| CA = {{Locking Standard
Line 50: Line 54:
 
   |PS=2
 
   |PS=2
 
   |Street=1}}
 
   |Street=1}}
| UT = {{Locking Standard <!-- Per Jemay, 2015-11-19 -->
+
| UT = {{Locking Standard <!-- Per Jemay, 2015-11-19. Temporary lowering from 54-4/3-3/2-2 to 4H322 per herrchin/AoTB/Bretmcvey 2016-06-01-->
 
   |caption=Utah locking standard
 
   |caption=Utah locking standard
   |title=Urban
+
   |title=Statewide
  |title2=Rural
+
   |Fwy=4
   |Fwy=5
+
   |Ramp=Highest rank of connected segments
   |Ramp=4
+
   |MH=3
   |MH=4|MH2=3
+
   |mH=2
   |mH=3|mH2=2
+
 
   |PS=2
 
   |PS=2
 
   |Street=1
 
   |Street=1
 +
  |lede=In {{RootPage2}} we have a set minimum standard for locking roads based on segment type. 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.
 
   }}
 
   }}
 
| NV = {{Locking Standard <!-- As per State Forum discussions, SuperDave1426, 2015-01-28 -->
 
| NV = {{Locking Standard <!-- As per State Forum discussions, SuperDave1426, 2015-01-28 -->
Line 75: Line 79:
 
| CO = {{Locking Standard <!-- per Random sample from the map - 2015-11-25 -->
 
| CO = {{Locking Standard <!-- per Random sample from the map - 2015-11-25 -->
 
   |Fwy=5|Ramp=Highest Rank of Connected Segment|MH=3|mH=2|PS=2|Street=1}}
 
   |Fwy=5|Ramp=Highest Rank of Connected Segment|MH=3|mH=2|PS=2|Street=1}}
| AZ
 
 
| NM  
 
| NM  
 
| SOUTHWEST = {{Locking Standard <!-- per Jemay - 2015-11-25 -->
 
| SOUTHWEST = {{Locking Standard <!-- per Jemay - 2015-11-25 -->
Line 81: Line 84:
 
   |lede=Actual locks used may be more or less than values in the table, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance.
 
   |lede=Actual locks used may be more or less than values in the table, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance.
 
}}
 
}}
 +
| AZ = {{Locking Standard <!-- per nnote - 2017-01-25 -->
 +
  |Fwy=4|Ramp=4|MH=4|mH=3|PS=2|Street=1}}
 +
  
 
| MO = {{Locking Standard <!-- a/p BlueTiger68 MO SM -->
 
| MO = {{Locking Standard <!-- a/p BlueTiger68 MO SM -->
Line 137: Line 143:
 
   |PS=2
 
   |PS=2
 
   }}
 
   }}
 +
| MIDATLANTIC = {{Locking Standard
 +
  |title=Two-Way
 +
  |Fwy=5
 +
  |Ramp=4
 +
  |MH=4
 +
  |mH=3
 +
  |PS=2
 +
  |Street=1
 +
  |title2=One-Way
 +
  |PS2=3
 +
  |Street2=2}}
  
 
| MI = {{Locking Standard  
 
| MI = {{Locking Standard  
Line 168: Line 185:
 
     |title=Statewide
 
     |title=Statewide
 
     |Fwy=5|MH=4|mH=3|PS=2}}
 
     |Fwy=5|MH=4|mH=3|PS=2}}
| ND = {{Locking Standard <!-- As per RC -->
+
| ND = {{Locking Standard <!-- As per bretmcvey 2016-04-26 -->
 
     |title=Statewide
 
     |title=Statewide
     |Fwy=5
+
     |Fwy=4
 
     |Ramp=4
 
     |Ramp=4
 
     |MH=3
 
     |MH=3
Line 177: Line 194:
 
     |Street=1}}
 
     |Street=1}}
 
| WY = {{Locking Standard <!-- Preliminary proposal subject to discussion and approval - TheChrisK, 2015-12-18 -->
 
| WY = {{Locking Standard <!-- Preliminary proposal subject to discussion and approval - TheChrisK, 2015-12-18 -->
   |title=Urban Areas
+
   |title=Statewide
  |title2=Rural Areas
+
 
   |Fwy=4
 
   |Fwy=4
 
   |Ramp=4
 
   |Ramp=4
   |MH=4|MH2=3
+
   |MH=3
   |mH=3|mH2=2
+
   |mH=2
   |PS=2|PS2=1
+
   |PS=2
 
   |Street=1
 
   |Street=1
 
   |note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}}
 
   |note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}}
 +
| AK = {{Locking Standard
 +
<!--per HO discussion with AlanOfTheBerg and AK state manager-->
 +
|title=Statewide|Fwy=4|Ramp=4|MH=3|mH=2|PS=2|Street=1|PLR=2{{ref|PLR}}|append={{note|PLR|1}}This rule should primarily apply to LARGE parking lots such as shopping malls/centers/plazas, tourist attractions/sports/music venues, large office buildings and schools/colleges.}}
 +
| OR = {{Locking Standard <!--As confirmed by AlanOfTheBerg-->
 +
  |title=Statewide
 +
    |Fwy=4
 +
    |Ramp=4
 +
    |MH=3
 +
    |mH=2
 +
    |PS=2
 +
    |Street=1}}
 +
|lede=In {{RootPage2}} we have a set minimum standard for [[Best_map_editing_practice#Locking_Segments|locking roads]] based on the segment type. Any road of a certain segment type must be locked to '''at least''' the [[Your_Rank_and_Points#Map_Editing_Rank|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.
 +
 +
A great time to implement these locks is while performing the [[Functional_Classification|FC Upgrade]] of an area. Lock the roads based on the type after they've been set to [[Road_types/USA#Quick_reference_chart|FC standards]].<!--A/p wiki-->
 
| = {{Mbox|type=critical|text={{Red|Error: The Lock Standard State template requires a state/province abbreviation or other equivalent; none was supplied, so no locking scheme can be generated}}}}
 
| = {{Mbox|type=critical|text={{Red|Error: The Lock Standard State template requires a state/province abbreviation or other equivalent; none was supplied, so no locking scheme can be generated}}}}
 
| {{Mbox|type=critical|text={{Red|The Lock Standard State template cannot display the locking scheme because it does not recognize the state/province/region specified: {{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}}}
 
| {{Mbox|type=critical|text={{Red|The Lock Standard State template cannot display the locking scheme because it does not recognize the state/province/region specified: {{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}}}
 
}}</includeonly>
 
}}</includeonly>

Latest revision as of 22:14, 26 January 2017

Documentation icon Template documentation[view] [edit] [history] [purge]
This template is transcluded into many state pages to define their locking standards. Any errant changes to this page can affect lots of state wiki pages relying on this template. Please be sure you fully comprehend this template and how parser switch functions work before editing it. If you need help please ask someone.


Please do not make changes to any state or regions defined settings without first getting consensus in the local forum, or approval from the RC.

This template simplifies calls to the Locking Standard template. The parameter list is somewhat long, and easy to confuse should there be multiple variations of locking standards within the state. To simplify this, a second template -- this one -- can be used to can the call for each area. You put all the complex code for your states locks in here, and just add the simple one line code to call this template on your states page.

You call this template as follows:

{{Lock Standard State|XY}}
...where XY is use a USPS state abbreviation or the like. But the list of abbreviations "and the like" must be predefined in this template.


Defining a new states locks

The template is a large "switch" statement that shows all the "states" (or provinces, regions, etc.) for which it is programmed.

To program a new state, you must first know how to use the {{Locking Standard}} template -- this template doesn't eliminate that work. This template just self-documents the resulting code, makes your states wiki page code look much cleaner, and less likely to accidentally break. (However, anyone touching the code here can break a lot of state pages!)

Once you have developed the code to define your states locking table using the {{Locking Standard}} template, use the following guidance to add a new state/region/group of localities/etc to this template.

  • Each state abbreviation must be in all UPPER CASE, and entered on a new line starting with a pipe character (the vertical bar |).
    • Multiple states or regions can be set to use a single definition using the "fall through" technique. If you want this state to use the same values as another defined state/region; do not put the equals sign (=) following the state/region name, make sure this state/region name is added above the defined state/region you want to use. When there is no (=) after the name, it will use the next defined set of values below.
    • Do not add any new states below the default settings at the bottom of the template.
  • To define this state put a equals sign (=) after the state abbreviation and then start the {{Locking Standard}} template code.
    • Now add a wiki comment describing the source of the information, your username, and the date. These comments are only visible in the code, and displayed in the wiki, they help to keep track of changes and for maintenance. To start a comment use anything after this is displayed in the wiki.
      • For example
        XX|{{Locking Standard <!-- as per state forum http://www.waze.com/forum/... Username, 2015-01-27 -->
    • On the next line start adding in the parameters to build your state table for the {{Locking Standard}} template. To make this template easy to read you can add line breaks and indents before new parameters. You can start each parameter or group of parameters with the pipe on a new line, and use regular spaces to indent before the pipe, showing context.
    • Remember to end your defining template code with a closing pair of braces (}}).
  • Now add the {{Lock Standard State|XX}} template code to your states wiki page.
  • After saving any changes to this template, please check the output for your state, and all the examples listed in the /doc page, to ensure they are producing the correct output.
    • If you notice that the output for your state or some of the examples listed here in the doc page are wrong, please "UNDO" your changes using the link by your edit on the history tab.
|AB = {{Locking Standard <!--comment explaining source of information, etc., the dashes, ! and LT/GT are part of the wiki code and must be present-->
   |parameterA = value value value
   |parameterB = text text text
   |Fwy = 1 | Fwy2 = 2
   |MH = 4 | mH = 3
   |MH2 = 5 | mH2 = 5}}
|FG = {{Locking Standard <!-- comment explaining source of information, etc., the dashes, ! and LT/GT are part of the wiki code and must be present-->
   |Title1 = value value value
      |Fwy = 1 | MH = 2 | mH = 3
   |Title2 = text text text
      |Fwy2 = 5 |MH2 = 5 | mH2 = 5}}
| CD = {{Locking Standard}} <!--simple case, uses no parameters, only defaults-->
| REGION9
| REGION9PROVINCE1
| REGION9PROVINCE2
| REGION9PROVINCE3 = {{Locking Standard
   |lede=This locking standard applies to the entire Region 9 (all three member provinces, Province1, Province2, Province3)
   |Fwy=5}}
| NEW SMALLVILLE
| NEW BIGVILLE = {{Locking Standard <!--New Smallville and New Bigville share the same setup, so only one of them has to actually have the code (always the last one), and the others don't have an {{=}} {{Locking Standard... the wiki understands to just pick the next one actually specified. (Just as Region 9 above) This is called "Fall through".-->
   |Fwy = 4}}

Examples

Note that due to the peculiarities of the underlying Locking Standard template, the state name is only picked up correctly when used as intended in State Pages. It otherwise picks up the rather nonsensical (in context) name of the current page for the caption/lede.

{{Lock Standard State|CA}}

In Lock Standard State we have a set minimum standard for locking roads based on segment type. 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.

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.

Lock Standard State Minimum Locking Rank Standard
Segment Type Metro Areas  Rural
 Freeway  5
 Ramp  5
 Major Highway  3 2
 Minor Highway  2
 Primary Street  2
 Street  1
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5



{{Lock Standard State|NM}}

Actual locks used may be more or less than values in the table, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance.
Lock Standard State Minimum Locking Rank Standard
Segment Type Default locks
 Freeway  5
 Ramp  4
 Major Highway  4
 Minor Highway  3
 Primary Street  2
 Street  1
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5



{{Lock Standard State|NEW ENGLAND}}

In Lock Standard State we have a set minimum standard for locking roads based on segment type. 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.

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.

Lock Standard State Minimum Locking Rank Standard
Segment Type Statewide
 Freeway  5
 Ramp  Highest rank of connected segments
 Major Highway  3
 Minor Highway  3
 Primary Street  1 (Auto)
 Street  1 (Auto)
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5
 Private Road  1 (Auto)

Note: Do Not Mass Edit just to update locks to these standards, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.

Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of BDP, U-turn prevention, or using micro-doglegs, or other complex intersection setups.



{{Lock Standard State|NORTHEAST}}

In Lock Standard State we have a set minimum standard for locking roads based on segment type. 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.

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.

Lock Standard State Minimum Locking Rank Standard
Segment Type Statewide
 Freeway  5
 Ramp  Highest rank of connected segments
 Major Highway  3
 Minor Highway  3
 Primary Street  1 (Auto)
 Street  1 (Auto)
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5
 Private Road  1 (Auto)

Note: Do Not Mass Edit just to update locks to these standards, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.

Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of BDP, U-turn prevention, or using micro-doglegs, or other complex intersection setups.



{{Lock Standard State|NY}}

In Lock Standard State we have a set minimum standard for locking roads based on segment type. 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.

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.

Lock Standard State Minimum Locking Rank Standard
Segment Type NYC Only  Everywhere Else
 Freeway  5
 Ramp  Highest rank of connected segment
 Major Highway  5 3
 Minor Highway  4 3
 Primary Street  3 1 (Auto)
 Street  1 (Auto)
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5
 Private Road  1 (Auto)

Note: Do Not Mass Edit just to update locks to these standards, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.

Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of BDP, U-turn prevention, or using micro-doglegs, or other complex intersection setups.
The above documentation is transcluded from Template:Lock Standard State/doc.
Please add categories to the /doc subpage.
Subpages of this template.