https://www.waze.com/editor/?zoom=5&lat=-37.830755&lon=145.015142&env=row
I had a look at this one and could not see an immediate answer any suggestions please
Sam
Your point being…? 
The wazer claims the app took him out of his way, I just wanted an idea of some techniques for solving this kind of routing puzzle lol.
BTW i could not find you question you wanted an answer for so maybe you could give me a clue was it about being an official Area manager?
It looks to me that unfortunately Waze just made a one time bad decision that time with the routing. The data in the editor looks fine, so I can’t understand why Waze would direct this person onto the Yarra Bvd towards Richmond when the driver wanted to go to Toorak. I recommend closing as not identified and request the problem be re-reported if it happens again, in which case some wiping and re-mapping of roads may be the only solution.
Sorry Sam for not being more specific, but I didn’t see a map problem and had the UR off, so I didn’t see any problem at all, asking what you needed help for :mrgreen:
OK, now for business.
First you did an excellent job in contacting the reporter - even if we can’t solve a problem we are to give feedback to show the reporting makes sense and somebody really cares. So that’s a must for an AM, RM, CM and a nice to do from any editor having the chance to edit a place where a problem occurs.
For the problem itself: after having the junction itself ruled out as source of the trouble (I agree with you on that, I didn’t really change anything, I just killed an unneeded junction) we would have to know, where the reporter was going to, for we should try to recreate the whole routing. From what we see from the users drive and his answers we still don’t know his destination, also time of day would be useful.
Then we try to recreate the situation by getting routes from the ramp to the destination.
The problem might be in one of the segments - inappropriate speed data can be as effective as a broken road…
I.e. I see an average speed of 22, 6, 17, 28, 16, 16 and finally 40 kmh on the route the reporter took vs. 48 kmh on the route Waze provided. That could explain Waze suggesting a longer but faster route.
Unfortunately I can’t make out from the drives, if the reporters anyway drove to the point Waze was guiding him to, there seems no common goal :lol:
That describes it 
So I really would like to know, what the reporter told Waze where he wanted to go.
Thing is: if you can’t recreate the failure it might not longer exist and therefore can’t be traced either.
Hope I gave you a more useful answer now, but I really didn’t understand the question first (map problem does not equalize update request)
Thanks I assumed you would see the map problem so it makes perfect sense to ask what I was banging on about. lol
Sam
Thanks I have give the waver a link to the answers hopefully he will understand some of the wisdom available to help him have a great experience with waze.
Thanks for your help
Hi guys! I am the reporter. I was headed from burwood to werribee and had avoid tolls turned on. I had a bit of brain fade and missed the toorak road exit which i normally take and waze routes me fine. so I took the next exit at Yarra Blvd. The way Waze normally takes me is along Alexandra Ave, so long story short. Waze routed me to go left from the exit onto Yarra Blvd and loop around up to swan street and finally back down to Grange road and across the river. Instead, i just turned right and then left onto Grange road and over the river… heaps shorter and quicker! I checked out the map in the editor too and couldn’t see a problem. The only thing that might be the cause from what i can see was how far off the road my actual route seemed to be.
Caradellino: which junction did you kill?
Sorry for the delay…here I am now
I just killed a unneeded junction node in the off-ramp before the split - no influence on the problem at hand.
Getting the whole picture now, I guess I might offer an explanation for the strange routing:
It has nothing to do with the map, it’s more about how the client works. When you start a route Waze calculates a variaty of possible routes and selects the best (given the parameters you set, what you consider best: shortest way or shortest time). This is quite time consuming, so Waze memorizes the “best route” and from that moment on Waze does not recalculate, it just tries to bring you back to your original route (remember: it’s already been calculated as the best one).
Usually this works quite fine, but once in a while this system leads to a kind of stubborn behavior and questionable routing. If you had stopped navigation and again requested a route to your original target, you would have got a more logical routing, most probably the way you took.
You might give it a try on the live map
that makes sense, thanks for the reply. 