CBenson wrote:I'm not at all familiar with the area. However, if I route from Patterson to Modesto with navigation type set to fastest I get the following routes:
This does seem to be a problem to me.
On the second picture you posted, the second and third option are more realistic, with the exception that since I travel between more specific destinations I probably have a slightly faster route.
All of the options on the first picture probably give a fair demonstration of what I tried to illustrate. You can imagine how this plays out to someone who is just driving with Waze on, and using routes to help teach it my preferred route. I know the way so I just turn my way and Waze adjusts, adding a much quicker arrival time.
For someone who doesn't know the way well but has another resource to compare to, or someone who is new to Waze, this might lead them to conclude is not a good navigation app. Because I see Waze as an awesome integration of crowd sourcing, I'm going to work through and try to be part of the solution. The more average consumer might compare this route to what Google maps or Apple Nav gives them and be unhappy with Waze. This is not in our best interest as fellow Waze enthusiasts.
So, as a newer Waze Editor, I'm curious about how this might get solved. Waze has some market share, it would be sad to see it lose too much if that.
Do other Wazers agree that the problem is sufficiently illustrated?
Again, I'll do what I can to help, but that is obviously limited.
There is definitely a demand for a Waze functionality companion app for walkers, joggers and bicyclists.
I manage three deserted parking lots.
