|This new page is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. This content is open to changes from anyone during construction. If you would like to make changes or have questions, please post a message in this forum. Please use the talk page for thoughts and ideas on setting up this content.|
Map tiles are part of the core of the Waze Map.
Theory of operation
The Waze map is divided into a grid using 1km-square areas which are called tiles or map tiles. Changes to the map are processed on a per-tile basis. Changes to any part of a map tile causes Waze to mark the tile as changed and it will be rebuilt in the next map update cycle.
When certain items in the map are edited, they cause the Waze system to incorporate the changes from the offline editor database into the live map database during an update cycle. That process will only include changes from map tiles that trigger the tile for an update. Not everything that gets edited will trigger an update.
Note that because some things do not trigger updates on their own, the system will also cycle through a percentage of the tiles each map update cycle and eventually update all the tiles. The process generally takes 10+ days.
The following edits are known to trigger a map update for anything else changes in the same map tile.
- Junction Arrows (standard and scheduled restrictions)
- Segment restrictions (scheduled)
- Road elevation
- Road locks
- Changes to Street/Alternate/City/State name
- Adding toll indicator
- Geometry changes to a segment
- Adding a new road through WME
- Adding a new road by paving in the client after the back end system processes the drive (a few days).
No update triggered
The following edits will not trigger a map update. Therefore to get any of these changes to be seen in the live map, one of the previously mentioned edits must take place in that map tile.