CBenson wrote:It might be related to road types, but there is a beta livemap that is intended to avoid this problem and it also can't find the same routes.
I can also route from North Carolina to Springfield, MA on my phone.
Riamus wrote:My guess is that it will relate to which roads it wants to route over, so it may or may not work depending on starting point. If you were to get somewhere that overlaps the suggested route from Allentown, PA to Springfield, MA, can you route it? That is if you're not too far away to do so, of course. I think it will fail if you are at a point that would use the same route that I'm trying to use. I'm just not sure. I really need to route there in a couple of weeks and this is going to be a problem. I would rather use Waze than Google on the trip.
Riamus wrote:I'm not sure if this is a routing engine problem or a problem with the roads, but I can route all over as long as I avoid SW Connecticut. For example, I can route to northern Michigan, which is a longer route. I can also route to NW Massachusetts, which bypasses CT.
Riamus wrote:That said, it does appear that there is still a limit on how far you can route. I can route somewhat over 1000 miles (Oklahoma City, OK or Houston, TX), but I can't route all the way to CA or even to CO.
0-15 km - All road types are allows for routing.
15-20 km - All road types except Streets.
20-30 km - All road types except Streets and Primary streets.
30-200 km - Only Minor, Major, and Freeways.
more than 200 km - only Freeways.
Riamus wrote:Ok, thanks for the explanation. That makes sense, though Waze should really be designed to be able to fall back on other road types if there isn't a connection.
Riamus wrote: Oh well, I guess I don't have any options. I was hoping to use the "pick up" option so those I'm visiting can get an ETA.
Users browsing this forum: Google [Bot]