I changed it. only some useless junctions has to be removed.
Next week monday Jubeltunnel and Wettunnel in Brussels wil close until Sept 15th . Shouldn’t they be ‘disabled’ on the map ?
More Info: http://www.tunnels2012.be/
Good idea to do so 
Could somebody either unlock the N43 or rename the city from Beveren (Leie) to Beveren-Leie, i have already named a bunch of roads around there.
This is how it should be named according to a paper map i have here from the city. (as well as wikipedia link)
https://world.waze.com/editor/?zoom=2&lat=50.87273&lon=3.34843&layers=BFTFTTTFTTFTTTTTTTTTFT
Thanks
//edit
Some other problem i had last week was driving on this part https://world.waze.com/editor/?zoom=5&lat=50.94047&lon=3.39411&layers=BFTFTTTFTTFTTTTTTTTTFT
Waze was showing the route coming from the south on the tieltstraat, turning into brouwerijstraat.
However waze did not recognize that as a turn and simple assumed that was a twist in the road (and because of that never said turn right, so i passed the turn) how can i make sure that it says turn right there? (I assume if i needed routing that would continue on the tieltstraat it would have said turn left at brouwerijstraat)
I hope i made the problem clear enough
I think you didn’t read the sticky topics about citynames and the Belgium wiki. This is how it should be written! 
So please change the roads with the correct cityname…
I’ve seen it yesterday (I’m AM for that region since yesterday).
I named the roads, wich may convince Waze it is a turn. Maybe the TR weren’t OK when the last update went live, but now they’re alright.
If the problem persists after the next update (check status.waze.com for the timing) let me know.
I had read it and also checked the via michelin map, which also said beveren-leie, but i didnt read the part where the waze names arent the same.
Does anyone know where that list of names came from and why they are different from the naming that you can find on every other map?
I’ll let you know when i pass there again in a few weeks
This list is based on the Belgium post list. We customised it at some points.
If you look as example for Beveren-leie in gmaps, you won’t find it. On gmaps it’s Beveren, Warengem. So your statement is incorrect. Belgium post has à nice and complete list. No double names that can give problems. So with this list everybody knows what cityname to use…you can use zipcode instead of cityname to find out the correct cityname, etc…
I’d still have to disagree though, it’s not that i want to be annoying or anything but i do believe that the only valid name should be the one thats on the streetsigns as well google street view
So when you see a streetsign waze should show the same cityname.
There is also a Beveren (Roeselare) in the list of city names, that one is correct though street view beveren roeselare
So if its the parent city you want to show it should be Beveren-Leie (Waregem)
@evilburt:
Please do not hijack the topic of this thread. This is the place to discuss practical solutions for small and local mapproblems. The topic you are adressing was discussed Ad Nauseam in this thread.
Hello,
There are inexisting speed cam near Alleur.
So, the two speed cam in the permalink below are no longer there.
Only 1 of those are visible in the app. The other is not approved by an editor. I would like to ask fvwazing to look at this. He approved the visible one…
I would like to ask to leave it there for now…it lookslike there’s a problem with the speedcam layer in this area. I would like to use this as an example for Waze devs.
Thanks for that
Oops, only now reading this. My locking-super-powers struck again… Manuel, did you write support yet?
Yep I did…but the approved cam gives also problems with the other cams (when zoom out) in that area…
Can you remove this section of road? Someone has removed the split road, but probably couldn’t remove this locked section.
https://world.waze.com/editor/?zoom=5&lat=51.1594&lon=2.93737&layers=BFTFTTTFTTFTTTTTTTTTFT
Also unlock, or remove split road here:
https://world.waze.com/editor/?zoom=6&lat=51.1538&lon=2.94744&layers=BFTFTTTFTTFTTTTTTTTTFT
Done!
I was able to unsplit it, but someone with local rights still needs to check TR’s and delete superfluous junctions. All segments are unlocked.