Page 1 of 1

Feature request: don't suggest destination when routed

Posted: Wed Nov 07, 2012 12:05 am
by rafaelds
Just now I was driving back from the mall. It was 9:30pm. I chose navigate 'home', and around a minute later, when I was already merging onto a highway Waze prompts me "Good evening! Driving to work?". Obviously I couldn't interact, so off to work I was routed.

I hate guts the "Driving to" suggestions by themselves. If they pop-up while I'm already on a route, don't even mention it. Can we please stop this bullshit things instead of adding this nonsense mega-social integration, dear devs? I'd be even willing to pay for Waze if it were nicer to me...

Re: Feature request: don't suggest destination when routed

Posted: Wed Nov 07, 2012 4:50 pm
by AlanOfTheBerg
If you turn off "Auto-learn routes to frequent destinations" it will not pop up the "are you driving to xxx?" at all, which is what the OP is referring to.

Re: Feature request: don't suggest destination when routed

Posted: Sun Nov 11, 2012 1:32 pm
by harling
To add to the confusion, the client seems to consider itself to be not routing when it is waiting on the routing server; e.g., when a new destination has been selected, or when the driver leaves the current route and causes it to recalculate.

[In that state, the Settings menu does not include (for example) the "Stop routing" option. Which means if the client is constantly recalculating because you are driving away from the selected destination, it can be very difficult to catch it at just the right moment to tell it to stop.]

Re: Feature request: don't suggest destination when routed

Posted: Wed Nov 07, 2012 1:10 am
by iainhouse
This is caused by the "Auto-learn routes to frequent destinations" (In Settings, Advanced). And it's not a new thing - it was in the previous version of the client.

It's very misleading. It learns destinations that you normally travel to from particular starting points. So if you use Waze for your daily commute, it will soon learn that you normally go to work from home and vice versa. Every time you leave home it will offer to route to work and every time you leave work it will offer to route to home.

Waze does not learn routes. Once you have accepted the destination, it then uses its normal routing algorithms to work out the best route - but the route provided is not based on any personal "learning", except to the extent that your travel along that route is just part of the mass of data that Waze has from all the users travelling in the area.

It's possible that Waze may learn more than just 2 "routes". I don't know because, like you, I found it more trouble than help and turned that setting off after it learned home<->work and work<->home. :)

Feature request: don't suggest destination when routed

Posted: Wed Nov 07, 2012 2:17 am
by kentsmith9
This is different. A route is ALREADY in process or in use and the nav tries to offer another. I agree this should not happen.

Re: Feature request: don't suggest destination when routed

Posted: Sat Nov 10, 2012 6:53 pm
by kentsmith9
Exactly. I think most users would be interested in the "auto learn route" option, but it should not make a suggestion if you are currently routed somewhere. It should be easy enough to change since the client knows the status of whether it is being routed somewhere or not, and the current behavior seems nonsensical.

Feature request: don't suggest destination when routed

Posted: Sat Nov 17, 2012 8:16 pm
by kentsmith9
I just noticed a few days ago a route change is causing the question of auto destination to pop up. Maybe that is what you are talking about.

Re: Feature request: don't suggest destination when routed

Posted: Sat Nov 10, 2012 3:32 pm
by rafaelds
Indeed, Alan. But as Kent said, the issue is that this is happening when a route has already been established. Which does not make much sense to me. Meanwhile, I have disabled the "auto-learn" option.

Re: Feature request: don't suggest destination when routed

Posted: Mon Nov 12, 2012 3:56 pm
by WeeeZer14
rafaelds wrote:the issue is that this is happening when a route has already been established.
I'm pretty sure Perlin had mentioned that they were working on preventing that from happening. I can't find the post now though.