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

Search results

From waze
Jump to: navigation, search
  • .../></div></div><div>&nbsp;* [https://www.waze.com/forum/viewforum.php?f=141 Standards]<br/></div><div>&nbsp;* [https://www.waze.com/forum/viewforum.php?f=327 Unl = Locking Policy =
    58 KB (9,147 words) - 18:49, 16 December 2017
  • ==== Locking standard ==== ...lidator|WME Validator]] to highlight segments which are locked below these standards using the custom check fields.
    9 KB (1,314 words) - 03:42, 22 February 2016
  • ...cess of adjusting the Segment Lock level in WME down to match the regional standards, or the Rank of an editor to allow them to edit the segment(s).<br><br>See ...standards.<br><br>See the [https://greasyfork.org/en/scripts/9724-locking-standards-tool-lst script home] External page<br>Also see the [http://docs.google.com
    178 KB (27,661 words) - 05:22, 20 May 2017
  • ...want to add a new road. Either way, it is important that you adhere to the standards already set. * [[United Kingdom/Locking Policy|Guide to maximum lock levels]]
    3 KB (373 words) - 21:07, 11 August 2017
  • <onlyinclude>{{{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 loc ...ter they've been set to [[Road types/USA#Public roads|current US road type standards]].}}}
    10 KB (1,066 words) - 07:40, 12 July 2015
  • ...ditor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These s ...locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become
    31 KB (5,225 words) - 08:08, 2 May 2018
  • ==Locking Standard== ...or: red"><b>If the current lock or traffic lock is higher than the minimum standards listed below, please don't lower the lock.</b></span>
    13 KB (1,905 words) - 06:33, 4 May 2015
  • ==== Locking Standard ==== |+ MINNESOTA PLACE LOCK LEVEL STANDARDS
    5 KB (701 words) - 02:22, 6 October 2016
  • === Directionality & Locking === According to the [[FAQ#What_is_a_locked_road_in_Cartouche.3F|FAQ]], locking a road segment has three effects, one of which is to lock directionality.
    24 KB (3,725 words) - 18:31, 1 November 2015
  • ...want to add a new road. Either way, it is important that you adhere to the standards already set. * [[United Kingdom/Locking Policy|Guide to maximum lock levels]]
    2 KB (337 words) - 06:01, 23 April 2018
  • ...a freeway, even if its shield would be a Minor Hwy according to QLD or VIC standards). As stated above: use judgement and discration in combining the shields wi <blockquote><span style="color: blue;">A special note on locking:<br>
    13 KB (2,121 words) - 12:35, 24 July 2014
  • Place Editing in California generally follows the National standards, but please note the following specific local guidelines. ==Locking Standards==
    6 KB (930 words) - 01:46, 7 March 2017
  • #The Base Map does not meet current standards for the Waze Map and the following issues are commonplace: Be sure to follow and understand the local standards for the state in which you are editing. Each state has a Wiki page that ad
    5 KB (819 words) - 03:38, 4 May 2016
  • ...sp; This policy&nbsp;'''is'''&nbsp;a guide for the&nbsp;'''MINIMUM'''&nbsp;locking level to be used for the convenience of the community, plus some notes abou <li>You should not normally be locking segments unless they are&nbsp;''complete'':<ul style="/* insecure input */"
    20 KB (3,432 words) - 13:14, 25 April 2018
  • ...ows the [[USA/Great_Lakes/Test#Minimum_Road_Lock_Standard|GLR road locking standards]] for all roads
    4 KB (678 words) - 22:41, 3 April 2016
  • ...especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become # Enter the correct name and road type for your road, following the standards for your country
    22 KB (2,664 words) - 16:34, 13 February 2015
  • We use the Turkish national standards for abbreviations of the roads, according to</translate> [http://tdk.gov.tr Locking Standard</translate>===
    30 KB (4,816 words) - 03:01, 4 October 2017
  • ...follow the guidelines from the state of [[Connecticut]] until the national standards are complete. === Locking roads ===
    5 KB (743 words) - 08:18, 6 March 2017
  • ==== Locking Standards ====
    5 KB (775 words) - 19:00, 26 March 2016
  • Read up on the general standards and guides referred to here as well as our own guide for editing the Philip * [[Philippines/Locking ]] Why are segments and places locked?
    4 KB (576 words) - 03:19, 15 August 2016
  • ...AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). ...edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details.
    14 KB (2,313 words) - 01:40, 6 February 2017
  • The following defines a set of ''minimum'' locking standards proposed for all '''roads''' within the Great Lakes Region. ...tps://wiki.waze.com/wiki/Road_types/USA#Quick_reference_chart US Road Type Standards].
    4 KB (545 words) - 15:47, 17 January 2016
  • Adhere to national standards for [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|Exit ramps an ===Locking standard===
    7 KB (1,008 words) - 05:48, 24 November 2015
  • {{Locking Standard<!-- per Regional SM Hangout discussion with OrbitC https://www.waz |note={{Red|Do Not Mass Edit just to update locks to these standards}}
    16 KB (2,464 words) - 04:50, 7 March 2017
  • ...roblems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. ...locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become
    25 KB (4,298 words) - 17:18, 25 March 2015
  • === Locking Roads & Places === ...iven because one answer does not fit all situations. General guidance for locking roads to editing ranks for New Mexico is as follows. Lower-level editors c
    20 KB (3,167 words) - 17:37, 6 March 2017
  • # Add railroads to the map, improve existing ones to the standards defined in the [[India Quickstart#Road type|Wiki]] ...the routing, they can be locked to the [[India/Editing/Roads#Lock|locking standards for India]]. Don't forget to add stubs of connected lower-ranked roads, so
    20 KB (3,299 words) - 12:30, 5 June 2017
  • ...want to add a new road. Either way, it is important that you adhere to the standards already set. * [[UK Locking Policy|Guide to maximum lock levels]]
    1 KB (171 words) - 18:32, 23 March 2015
  • === Locking Standard === Washington observes the following locking standards on the following types of road segments. All roads must be locked '''at lea
    4 KB (553 words) - 14:59, 11 July 2016
  • ==== Locking standard ==== In Nebraska, we observe a minimum standard for locking roads based on segment type. Any road of a certain segment type must be loc
    15 KB (2,371 words) - 17:11, 13 July 2016
  • ...xplanatory text above, (and optionally below,) to list the segment locking standards for a state or region. ...atically generates the call to this template.''' It lists all the approved standards for US States. It supports up to three regions within the state as stacked
    17 KB (2,860 words) - 05:41, 2 December 2015
  • === Minimum Road Type Standards === === Road Segment Locking ===
    42 KB (6,504 words) - 18:29, 21 February 2017
  • === Road Lock Standards === == Places Locking Standards==
    40 KB (6,163 words) - 01:15, 17 February 2017
  • ...it will be obvious to other editors that they do not connect, and consider locking them to be sure they stay that way. Otherwise delete the segment. ...dical work that was required to set the road type according to national FC standards.
    49 KB (7,860 words) - 17:05, 21 February 2017
  • === {{@|Locking standards}} ===
    11 KB (1,818 words) - 12:42, 10 September 2016
  • Adhere to national standards for [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|Exit ramps an === Locking Standard ===
    12 KB (1,822 words) - 16:34, 19 September 2016
  • We follow the Northwest region locking standard which is: Idaho uses a literal one-to-one conversion of the FC standards to the roads in Waze. Roads should not be mapped otherwise without discuss
    6 KB (875 words) - 03:27, 7 March 2017
  • ...t other Waze editing topics such as [[map problems]], [[Update requests]], standards for [[Road types and names|labeling roads]], and all the things covered in ...locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become
    25 KB (4,329 words) - 13:32, 30 March 2015
  • === Mississippi Road Segment Locking Guidance === Mississippi provides the following guidance for locking roads based on segment type. Any road of a certain segment type should be l
    5 KB (762 words) - 20:43, 16 July 2016
  • ==== Locking Standard ==== |+ ARIZONA PLACE LOCK LEVEL STANDARDS
    5 KB (850 words) - 02:29, 7 March 2017
  • === Great Lakes Region Standards Proposals === ...ser:Falco sparverius/GLR Proposals/Minimum Road Locks|Minimum Road Locking Standards]]
    3 KB (515 words) - 16:26, 21 August 2016
  • ===Locking=== In Virginia we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be loc
    8 KB (1,211 words) - 03:06, 7 March 2017
  • ...the State FC, the reservation roads in AZ may differ from what Waze common standards may be. The State FC takes into account certain issues on reservation roads ==== Locking Standard ====
    3 KB (526 words) - 02:32, 7 March 2017
  • Pennsylvania standards for places differ in some ways from the US standard. ;locking
    3 KB (472 words) - 14:54, 10 February 2017
  • ...ew Jersey, we follow the general [[Road_types_usa#Quick_reference_chart|US standards for road types]] based on the hybrid rule of FC and Route Type. ===Locking Standards===
    13 KB (1,992 words) - 04:00, 7 March 2017
  • | NORTHEAST = {{Locking Standard<!-- per Regional SM Hangout discussion with OrbitC https://www.waz |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 segmen
    11 KB (1,688 words) - 22:14, 26 January 2017
  • ...xplanatory text above, (and optionally below,) to list the segment locking standards for a state or region. ...atically generates the call to this template.''' It lists all the approved standards for US States. It supports up to three regions within the state as stacked
    17 KB (2,860 words) - 15:01, 27 January 2015
  • ...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 relyin ...t 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
    7 KB (1,102 words) - 23:35, 25 January 2017
  • === Locking Standard === '''Locking Standard'''
    21 KB (3,477 words) - 02:23, 17 February 2017
  • * Although there is a locking standard table, Canada has [[Traffic_locks|Traffic Locks]] (Auto Locks) act ...a "Road Classification" change the locks may be manually set to the below standards, depending on the decision of the Canadian Champs.
    30 KB (4,485 words) - 17:30, 29 January 2016

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)