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
  • ...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 ==== |+ 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
  • ...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
  • {{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

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