CBenson wrote:Why is this bizarre? This is exactly what the PtP/driven ratio pruning does. If the route is too circuitous the driven distance is too high compared to the point to point distance and waze doesn't find the route.
Pretty much that. The ratio probably needs to be adjusted again by Waze.
It also demonstrates what I mentioned earlier that paved mountain roads that connect significant locations (eg towns) should be typed as Primary at a minimum.
Course, in this case, even 'primary' isn't enough for Corral Bottom and Underwood mountain, or for the end-around using highways. Yeah, I mean, I know by demonstration that if I typed all paved rural roads as minor highways, I'd avoid this problem completely, but I don't think that's really ideal and is probably torture on the routing engine; some roads are gravel, and some are practically highways; and sometimes the fastest way from point A to B is way around the bend at C.
I think why I called this behavior 'bizarre' is not so much because it doesn't make logical sense. It's because intuitively, I as a user of the app would expect that Waze shouldn't lose the ability to route to a destination as I near it. As it is, I could start in Crescent City, CA, stop for lunch in Big Bar, and suddenly, I'm stuck there because Waze won't find a route through to Hyampom. I also called it bizarre on the notion that returning 'some route', any
route, circuitous or not, is better than Waze returning 'I can't find a route'' from a user standpoint.
I know as far as rural areas go, this is the part where we go back to discussion about Waze being a commute and not a nav app, but if given the choice between Waze being able to route point to point more than 1000 miles (few can drive further than that in a single day anyway) or high ratio/short distance routes working, I'd pick this one.
Probably the ratio being as low as it is now saves a ton of CPU cycles in urban areas, where there really are eight different ways to get from point A to B, so I'm not sure it needs to be increased across the board for all queries. What I'm thinking is adding a pretty simple if/then to the engine that goes like this:
IF (engine returns 'no route found at all')
THEN (increase/double/whatever the ratio and try again)
(and if that fails)
NOW return 'No route found' to the user.
If I try routing from Big Bar or Burnt Ranch to Hyampom, after a tiles refresh (so I know it's not cached yet), the answer 'No route found' comes back VERY quickly, so I suspect it just hits the wall of 'Sure, I see routes, but the ratio is too high. Nope.' The loop above I bet would nail this.