Waze continues to think that Philadelphians should not travel that far south.

See discussion here and here.

CBenson wrote:Waze continues to think that Philadelphians should not travel that far south.

See discussion here and here.

I'm sitting in my office in Bensalem, PA which is directly north of Philadelphia. I-95 is one block away.

I was able to get a route on my phone to Nags Head, NC from here, which is good news for this thread.

As far as the other two listed above, I was able to get a route to Williamsburg, VA but not to Hatteras, NC. It's possible the FC updates we've done have helped or that routing errors have been fixed.

Not sure about specific methods of route debugging, but one thing to consider with a rank/penalty-based system for navigation, like Waze uses, as that your options for available routes become more and more limited the longer a trip you try to navigate. If several of these now-limited road choices are traffic-clogged at the time, it can really wreak havoc on Waze. Keep in mind that Waze is tuned for optimal routing in the distance ranges you'd expect people to commute to work, since that is the use case Waze is designed for. I think if your trip is over a certain distance, like well over 100 miles, Waze will pull you toward freeways no matter how far out of the way they may be.

One immediate possible solution (workaround) is to either enter waypoints about 100 miles apart along a longer trip, or just enter each waypoint as a destination. Of course this involves doing a little research to find good waypoints about 100 miles apart, but I just chalk it up to the growing pains of a product that has started to move beyond its initial design.

Oddly enough, it doesn't think North Jerseyans should travel there either: Newark, NJ to Nags Head, NC fails too. This is really starting to look like a route-complexity timeout/overflow issue.

To Nags Head, NC from:
Atlanta, GA: OK
Nashville, TN: OK
Chicago, IL: Fail
Cincinnati, OH: OK
Pittsburgh, PA: OK
Wilmington, DE: OK
Atlantic City, NJ: OK
Trenton, NJ: Fail
New York, NY: Fail
Albany, NY: Fail
Boston, MA: Fail

Seems like at a certain distance where the route largely involves significant urban area, routing fails. Also, at such long distances, one little rogue red arrow (by mistake, perhaps) along the "through path" of an Interstate freeway somewhere can easily spell complete catastrophe...

Google wanted Waze so that it would be off the market. If Facebook, Microsoft, or Apple had purchased Waze, it would have further diluted Google's map proposition.

Oddly, I just tried the route on my phone - failure from north Jersey, as PS says. I then tried the Livemap link in the OP (7.5 hours), then reversed it (about 10 minutes longer trip). Took a god long time to find the routes, though. Not the first time Livemap has succeeded where the client did not.

When I changed the time in Livemap from NOW (6pm) to 08:00, it died. Spun the finding route wheel for a minute (far less than the time it took to find a successful route), then suddenly stopped at displayed the plain "find an address interface." It lost both "dropped pins." That's really weird, maybe the server returned an unhandled error, and that's the default Livemap action for an unhandled exception.

I did run the route for 10:00 PM, to avoid traffic.

People like Waze and want to contribute their traffic data every time they drive.
So Waze needs to make clear that it is still the choice for drives under 100 miles.

Until it gets Google-sized resources, it will be hampered searching for good longer routes.
If it fails grow up within 3 years, I fear Google might just make Waze disappear -- all Google really wanted was the traffic reporting, anyway. Which would be a shame, because Google should want the active map editors, too.