Basecamp routing calculations don't make sense

Former Member
Former Member
I noticed that 2WHEELSFORFUN started a similar thread.

I just created a 2-point route in Basecamp from Hamilton, ON (Canada) to Narvon (Lancaster, PA), using the Driving profile. The resulting route makes absolutely no sense. Basecamp routed along I90 from Buffalo, NY to Syracuse, NY and then down via Reading, PA. That is a HUGE detour and I can only explain this by thinking that Basecamp loves interstates. Exactly the same route is created if I use the Truck, RV or Motorcycle profile! I have no avoidances set in the profiles except ferries & day-time closures.

If I create the same route directly on my Nuvi 2797, I get close to a perfect route that is much shorter and faster, going south along US15 to Lancaster.

Any ideas?
Klaus

PART 2: I just did the same route in Mapsource. With my normal route preferences (the Road Selection slider in the middle), it pretty well duplicates what my 1490 and the 2797 achieve - a route going south on US15. Selecting "fastest" or "shortest" results in only minor changes. If I move the Road Selection slider to the far right (Highways only), then Mapsource will duplicate the same route that Basecamp comes up with, going via Syracuse. This route is 43 mi longer and takes 32 min more time than the optimum one down US15.

NOTE TO DEVELOPERS: It appears that Mapsource's auto routing is much more flexible and better. How about incorporating a similar Road Selection slider in Basecamp. Right now the routing leans strongly toward highways. By the way, this particular route generated by Basecamp does NOT change whether I select "fastest" or "shortest".

Klaus