Benelux Roads (General)
Since the takeover by Google, Waze is using the search function of Google. When looking up for an address, the Google database will be searched for the right coordinates. If there is a match, Google will return these coordinates to the Waze routing server and will plan the fastest route to the nearest segment.
Since November 2014, the search function uses the Waze database first. If there is no match, the search will continue and uses the Google database as backup.
Keep It Simple/Stupid (KISS)
" As simple as possible, as complex as necessary "
KISS is keeping the road geometry as simple as possible, without losing the essential driving instructions.
More info KISS
Filter lanes are NOT mapped.
Filter lanes don't fit the KISS principle because they are the cause of very complex situations that are hard to manage, while they don't add a lot of value in most routing instructions. Short segments and extra splits can have a negative influence on routing (extra penalty, incorrect average speeds, ...).
Of course, there is always an exception. If the choice of a filter lane must be made more than 50 meter before coming to the crossing AND the main road and filter lane are divided by obstacles (concrete blocks, ...), it should be mapped.
There are roads that could be classified by multiple street types. We think of ring roads (R-roads) which sometimes can also be a N-road categorized as Major Highway. For example, the ring road of Leuven, the R23, has long segments which are also N2 or N3. In these cases we categorize the ring road as Major Highway.
Ring roads which are also freeways, like the R0 of Brussels, are categorized as Freeway.
If you want to add a roundabout, you firstly draw the roads as a normal crossroad, but don't connect the roads/segments. Secondly you draw the roundabout and WME will connect the crossing roads automaticly.
If you want to adjust a roundabout (extra connections), you have to remove the roundabout completly and redo the whole roundabout as described earlier. When the live map is generated, every exit gets a number. Adding an extra segment/exit, will mess up the numbering of the exits and could corrupt the roundabout.
A roundabout must always get a cityname but never a streetname. The reason for this has to do with the navigationinstructions and road announcements.
A roundabout always gets categorized as the type of the passing throuhg road and gets locked on level 3 or higher.
Notice : Be carefull using certain sources for editing the map; some policies or conditions restrict the use or duplication of the data and could lead to a complete deletion of the country map.
Citynames of BeNeLux are locked and can be consulted. For The Netherlands this can be found via Staatsalmanak.
To add a cityname to a segment, this can only be done in a certain area of the city.
To determine the borders of every city, consult the map of ViaMichelin. You can search it based on the cityname, but also based on the zip code. Searching based on the zip code can come in handy if you search for citynames which exist on multiple places.
There can be situations where it's not clear. For example, it's possible a city is devided in two, in ViaMichelin. We refer to the Wallon city of Geest-Gérompont-Petit-Rosière. We input the city as one city.
It's also possible the by ViaMichelin used name is different than the name in the list. Stick to the names in the list! Adding a new cityname, non existend on the list, will result in an error when you try to save in WME.
All segments should get a cityname, and most segments also get a streetname. When entering the streetname, we use the streetname in the official language of the area.
For the 19 cities in Brussels area where 2 official languages exist, we use the French version. As a reference, you can find the official language in the citynames list.
As there is a cityname and streetname, it's possible there is also a road number. This road number is positioned before the streetname. Some examples:
N200 - S103 - Haarlemmerweg N68 - E421 - Route d'Eupen N451 - Kieldrechtsebaan
Since november 2014 it is possible to search for housenumbers which are inputted via the Waze Map Editor and saved in the Waze database. To support this functionality, Waze imported housenumber data from external sources, in multiple countries, like The Netherlands. This was not the case in Belgium or Luxemburg.
When searching for an address in the Waze app or Livemap, Waze will use the following order to present the results: 1. Manual created housenumbers 2. Google Maps database 3. Imported housenumber data
Bottom line: if you notice a wrongly positioned address/housenumber in the app or livemap, you can change it via the Waze Map Editor. This will result to a primarly suggested, correct location.
Depending on the importance of a road, it will be used by more Wazers, an error in editing will be more painfull and routing could start doing some really weird things. To prevent this not wanted situations, some of the most important roads are locked on a certain level, in the Waze Map Editor.
The correct lock-level can be found on the pages of the road types. These are mainly used all over BeNeLux.
- If your own level isn't high enough, you can lock on your max level, and/or you can ask for help.
- If the aerials or streetview deviates from the real situation, it's ok to lock 1 level higher, as a special notice.
- Complex situations can be secured by a higher level-lock.
- Segments subject of roadworks can be locked 1 level higher, as a special notice.
- Segments with a time-based restriction, should be locked on level 3.
If you want to edit a segment which is locked hihger than your level, you can request an unlock via the forum. When requesting an unlock, report the reason for the request and a Permalink to the subjected segments you want unlocked.
Waze is a very dynamic organisation with a non-stop development of changing and new added features. The road infrastructure is also changing and new situations and tools are being used to manage traffic.
To be able to work on a same way in the community, with these changing or new features and situations, we try to develop new conventions and guidelines which need to be tested. To have a clear overview of what is being tested or what is a temporary convention, we created this section...
TBSR / Road closures
We are experimenting with a with Waze staff shared spreadsheet where we can describe and ask certain segments to be 'road closed' from hour and date x to hour and date y. This is updated on a different way as the tile builds, and should be faster / more dynamic. The advantages are that road closures are viewable and noticeble on the map in the client, but not in WME, as for TBSR which are viewable in WME but not in the app. Both are used in the routing algorithm, so that should be the same. TBSR are more flexible in a way, as you can organise them in a repeating order.
If the method of sharing a spreadsheet and the follow up by Waze staff is effectively, we can start using it more common. For this, a new form has been created, so everyone can provide the needed information to get a segment 'road closed'.