Local Search

  • Wazeopedia, before the public release in May of 2015. PesachZ adapted wiki templates created by kentsmith9 for the Glossary along with extensive enhancements...
    188 KB (950 words) - 03:29, 24 May 2022
  • and you need more information, write the reporter with a question. See templates below. if there is no response in about a week, prompt the reporter again...
    1,014 bytes (3,759 words) - 09:16, 26 February 2015
  • and you need more information, write the reporter with a question. See templates below. if there is no response in about a week, prompt the reporter again...
    9 KB (622 words) - 10:14, 2 January 2016
  • be minimum locked at one rank (level) higher than the above minimums, to protect that vital traffic corridor. Please note that the above lock levels are...
    1,014 bytes (3,173 words) - 01:47, 17 February 2015
  • Pennsylvania (tag Pages using duplicate arguments in template calls)
    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...
    1 KB (4,010 words) - 13:31, 12 February 2020
  • New York (tag Pages using duplicate arguments in template calls)
    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...
    1,014 bytes (5,785 words) - 01:48, 17 February 2015
  • New York/Major roads/Main (tag Pages using duplicate arguments in template calls)
    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...
    10 KB (2,023 words) - 00:47, 15 March 2022
  • prone to editing and major parks can be locked at 4 or 5 as necessary to protect their integrity. Not every camera-looking device at an intersection is a...
    1,014 bytes (3,632 words) - 17:14, 9 December 2015
  • 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...
    1,014 bytes (2,669 words) - 01:45, 17 February 2015
  • prone to editing and major parks can be locked at 4 or 5 as necessary to protect their integrity. When moderating Place Update Requests (PURs), please be...
    1,014 bytes (3,337 words) - 17:00, 17 July 2015
  • permitted to lock places at 2 if you have set place data that needs to be protected from changes by these users. Once Completed (e.g. green in WMEPH, or blue...
    1,014 bytes (2,939 words) - 03:58, 15 April 2015
  • 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...
    1,014 bytes (3,618 words) - 02:43, 5 October 2017
  • 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...
    1,018 bytes (3,598 words) - 01:03, 26 August 2015
  • 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...
    1,014 bytes (2,523 words) - 22:22, 30 September 2015
  • a level higher than 1, once you have verified any information, to help protect from accidental damage through client submissions. The following are recommended...
    1,014 bytes (5,346 words) - 01:52, 17 February 2015
  • 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...
    1,014 bytes (3,256 words) - 01:46, 17 February 2015
  • 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...
    1,014 bytes (4,221 words) - 01:48, 17 February 2015
  • 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...
    1,018 bytes (4,492 words) - 01:46, 17 February 2015
  • Editing restrictions related to user rank are described here. In order to protect the Waze map from inadvertent damage by new editors, it is noted that within...
    1,014 bytes (3,580 words) - 06:06, 7 March 2019
  • 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...
    43 KB (3,526 words) - 02:05, 25 July 2020