@Robin: of course you are always responsible for your own actions, including breaking traffic (or Darwin's
) law. My point was and is that Waze was definitely wrong in the two occasions I mentioned. Maybe the turn was messed up, but the ramp was one way, nothing more, nothing less...ergo you can never give directions to drive against traffic. Maybe even more so on ramps or freeways. Again, I am a huge fan of Waze and will always defend it's ideas and community, but that's exactly where this comes from...i am concerned for Waze's future if these basic errors happen to 'the common public'. I don't have the statistics but for every comment I make to point to errors or suggestions there's 10 or more first-timers who won't give Waze a second thought and we will never get the critical mass in Holland. The best way to do that is to make correct and efficient routing the highest priority and cherish the community (who make the maps routable) like a newborn.
I am not a newbie and, though not as much as you, have done my share of editting and I know for a fact that e.g. the left turn at Machinekade was correctly restricted by disabling all turns at the junction except the one I manually allowed and making the road 'no entrance'.
So, to stay in sync with the sunny weather outside, this a serious concern that should get proper investigation. If it was me who did something wrong, I'd be more than happy to know that, if it's the maps I'll me happy to spend more time in checking every single turn and road segment. But since it happened on turns that definitively were restricted I am almost sure something is/was wrong in the routing algorithm or the client (but routing is serverside, right?)