(→Wiki) |
(→Wiki) |
||
| Line 23: | Line 23: | ||
** [https://www.waze.com/forum/viewtopic.php?f=129&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] | ** [https://www.waze.com/forum/viewtopic.php?f=129&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] | ||
*[[Scripts]] | *[[Scripts]] | ||
*[[Speed limits/USA]] | |||
=== Other === | === Other === | ||
Revision as of 00:21, 3 March 2016
| Wiki content is written and maintained by Waze community members. It may not be accurate or complete. |
Important Links
Editor
Forums
- Colorado
- US Unlock and Update Requests
- US Regions, Coordinators and Experts
- Waze Map Editor
- Road Shields In US States, which contains some useful information for abbreviations and regular expressions.
Wiki
- Colorado
- Places
- How Waze determines turn / keep / exit maneuvers
- Road Naming (USA)
- Scripts
- Speed limits/USA
Other
- Closure Form - forum source : Road Closures Form for All Editors
- Closure Forms for Review - forum source : Road Closures Form for All Editors
- Community Role: State Manager (SM)
- wiki Templates
Cool Scripts
Fixing URs and MPs
From somewhere in the wiki:
If you find something which indeed needs fixing (disconnected street, bad TR, etc), do so and mark Solved. (Just make sure you're not undoing a recent change to the map which may not yet be reflected in imagery or street view, as one editor did to a recent carefully researched change of mine)
If you find something explainable, but for which nothing can be changed on the map, such as lost GPS signal in hills/tall buildings, or Frequently Ignored routing to an alley, etc. mark Not Identified.
WME_Speed
 |
Troyv can be reached by private message.
|
