HomeMicrosoft


Windows Maps app Routing??
Ken in Regina
I did a route (in Canada) from Regina, SK, to Cranbrook, BC, to Penticton BC. The resulting route is bizarre!

It routes okay to Cranbrook. But the route to Penticton is nuts. Instead of following BC #3 to Osoyoos and then north a little ways to Penticton it swings way south into the States, almost down to Spokane!!

...ken...
Ken in Regina
It appears to be the maps. They seem to be broken between Creston, BC, and Salmo, BC. Nothing I do will persuade it to take #3 between those two points. Instead it will find some other way around, no matter how wacky it is.

Reminder, this is in the Windows Maps app. I'll try Bing Maps online and the Android HERE WeGo app to see what they do.

...ken...
Ken in Regina
Bing Maps is broken just as badly in that area. The Android HERE WeGo app routes as you would expect. Good thing because without multipoint routing there's no way to force somewhere at least closer to the right route.

...ken...
GoneNomad
BTW, I noticed that choosing any of the "Avoid these while driving" options in Win10Maps (four of which: Ferries, Unpaved Roads, Tunnels & ?"Motorail"?) are not available on bing.com/maps) will *drastically* slow down route calculation.

Makes me think maybe I need a faster tablet after all.
Ken in Regina
Motorail is a train "ferry". That is, for that stage of the journey you load your car onto a rail car in much the same way you would use a ferry.

...ken...
GoneNomad
Quote:
Originally Posted by Ken in Regina
Motorail is a train "ferry". That is, for that stage of the journey you load your car onto a rail car in much the same way you would use a ferry.

...ken...
In the US that's usually called "autotrain"

Win10Maps sure does look & work a LOT like the old "Here" app... even the commencing navigation annunciation ("Here We Go") is too similar to be a coincidence.
GoneNomad
Quote:
Originally Posted by Ken in Regina
It appears to be the maps. They seem to be broken between Creston, BC, and Salmo, BC. Nothing I do will persuade it to take #3 between those two points. Instead it will find some other way around, no matter how wacky it is.

Reminder, this is in the Windows Maps app. I'll try Bing Maps online and the Android HERE WeGo app to see what they do.

...ken...
Didn't you have that same problem on another route in Canada around the same time when we were doing all that testing? Whichever one it was, it "thought" the road (through the boonies) you wanted to take was closed, so it only created routes around it?

BTW, I just checked "wego.here.com" again, compared to what it did last year as detailed in this post, and it appears to still be making the same mistakes on longer routes.

The easy-to-see iconography (that doesn't block the map too much) they use to indicate options when clicking on a point on the map is nice:

...compared to this much larger opaque flag that pops up on bing.com/maps:

(I prefer having the extra options - especially the via point that 'Here' lacks).

Of course it's a moot point for Here (and maybe WinMaps as well) as long as there's no easy way to open a route planned on the website into the nav app.
Attached Images
here-add-point-route.png  
Ken in Regina
Yes, and it was also out in British Columbia. I guess all those mountains must get the routing routine confused.

...ken...
t923347
There is a similar issue with S&T we run into all the time in Arizona.

You can't drive north on I-17 from Phoenix to Flagstaff without being routed off the interstate onto AZ 69 West just south of Coates Junction to Dewey AZ and then back on to I-17 via AZ 169 East. Been like that for at least the last couple of versions of S&T.

You can reverse the route and the calculated trip doesn't have this problem (I-17 all the way).
Ken in Regina
Sounds like they missed joining a couple of segments of one side of the interstate but not the other.

...ken...
laptopgpsworld.com About