Route guidesRoutes Map
Mobile appApp Log in

Involuntary route changes

2 Oct 2024
Find a better bike route. Try our map & route-planner »

Become a supporter

I've recently had a problem with a lot of my routes where I have loaded a previously saved route, paved only in this example("Set to paved only" is greyed out on the drop-down menu), and when I have added a via point the route immediately changes. The same thing happens when I load a route and use Download For GPS. The route immediately changes and that is then uploaded to the GPS.

Original saved route:

Route after adding a via point:

Same original route when using Download For GPS.

I can't work out what I am doing wrong for this to happen.

Thanks for any help

Nick

Comments

Wed 2 Oct 2024, 19:42

Could you say what that route is called (and make sure it’s public) so I can take a look?

Wed 2 Oct 2024, 19:47

Thanks Richard! It's called CarltonMarshes, 60 mile route.

Thu 3 Oct 2024, 17:01

Very sorry Richard, the example above is for a route called Reedham. 

Fri 4 Oct 2024, 18:28

Thanks – that’s really helpful!

It looks like there was a particular issue if you saved a circular route, then reloaded it later and tried to add via points to it. I have now fixed this for circular routes saved from now on, but it won’t fix it for existing saved circular routes I’m afraid.

Above and beyond this, there’s always the possibility that adding via points to a previously saved route will change the route – there’s a section in the FAQ explaining why.

Fri 4 Oct 2024, 19:10

Thanks Richard! Do changes to the underlying maps etc account for the second example where I load a route, not make any changes to it at all, then on using Download For Gps the route immediately changes and is downloaded like that?

Thanks

Nick

Sun 6 Oct 2024, 17:52

Which download format are you using?

Mon 7 Oct 2024, 00:12

Ah yes, sorry! It's Send To Garmin Connect.

Mon 7 Oct 2024, 11:26

Ah, that makes sense. Historically c.t has had to recalculate the route because Garmin Connect requires elevation data to be sent across.

I’ve just fixed that so that if you send a route from the map page, it won’t recalculate the route when fetching the elevation. Hopefully this should fix it for you.

(I haven’t had chance to do the same when sending from the Journeys page yet, so best to just send from the map page for now.)

Mon 7 Oct 2024, 21:21

Brilliant, thank you Richard!

Enter to search, Esc to cancel