Cycle Travel Question

[roubaixtuesday]

What Wahoo model/ edition are to using?

Roam v2

[Rob D]

Hi all, esp Richard. I've just been notified of the updates to CT, which looks to be really useful. Nice to see the cobbles/setts issue we had in Spain recently has been sorted.

So well done Richard - and thank you!

Rob

[pal]

Some feedback for Richard on the latest tweaks to the Altitude Algorithm: I just planned and rode a trip from Hexham to Berwick -- a little bit over 120km of the sort of constant sharp up-and-downs which (as I understand it) are particularly difficult to map for height. CT predicted: 1700m of climbing. My garmin said: 1731m (and about 10m of that will be me coming out of the station the wrong way and having to go over an extra railway bridge ) Chapeau!

[Psamathe]

Some feedback for Richard on the latest tweaks to the Altitude Algorithm: I just planned and rode a trip from Hexham to Berwick -- a little bit over 120km of the sort of constant sharp up-and-downs which (as I understand it) are particularly difficult to map for height. CT predicted: 1700m of climbing. My garmin said: 1731m (and about 10m of that will be me coming out of the station the wrong way and having to go over an extra railway bridge :wink: ) Chapeau!

My personal view of altitude estimates is that they should be treated an a dimesnionless number, ie as an index for comparison only on the same platform.

Over last month I've been downloading next stage routes from cycle.travel to my Garmin and just looking at the Garmin estimates for the sme route and in Garmin Connect app in the smartphone the route ascent might be 300m but once it gets to the GPS that might become 700m (same route just one "estimate" in the Garmin Connect app, other estimate on the Garmin Edge GPS). Same happens on pretty well all routes.

Ian

[ChrisF]

Does anyone know how to add a short gravel section to a route that has otherwise been defined as paved only? I have a route here https://cycle.travel/map/journey/641222 but there's an awkward section at km 25 that could be avoided by a short section of gravel. If I change the option to gravel, a huge amount of the route is also changed, which I don't want to do.

[Psamathe]

Does anyone know how to add a short gravel section to a route that has otherwise been defined as paved only? I have a route here https://cycle.travel/map/journey/641222 but there's an awkward section at km 25 that could be avoided by a short section of gravel. If I change the option to gravel, a huge amount of the route is also changed, which I don't want to do.

Idea: Practicality depends on how long/complex the route is: Create the route set as "Paved only", add a number of "Via Points" along that route to fix it to the "Paved Only" route (flick between "Any" and "Paved only" to see what changes and thus where the "Via Points" are needed). Then switch to any and if necessary drag the route to the short section of gravel.

Ian

[nirakaro]

I'm struggling to edit my route on the app: when I try to drag the blue circle of a via point around, it works occasionally, but usually it just moves the map across the screen. I can't see what makes the difference?

[Rob D]

That's a coincidence, I had the same issue, but on the website. It was ok when using it in Spain in June but yesterday, planning routes in Albania, Macedonia and Greece, found it really difficult to drag the route.

Another thing: having produced a route, looked at the elevation profile and saved it, when I went back later to check the elevation etc, got a message up saying something like 'Can't find route profile, check all the waypoints are paved'. It was a paved route I'd specified. I'll try again later and try to put in the exact wording.

Any ideas?

[Richard Fairhurst]

On the iPhone app you need to hold your finger down for a short while and then drag. This is to prevent every single finger swipe on the screen changing the route. (I think Android is the same but I’m away from home right now and don’t have an Android phone with me to refresh my memory!)

Currently, on the website, the route is recalculated when you ask for elevation. This means that if the OSM map data has changed such that one of the via points is now on a road that has been marked as unpaved, it won’t calculate a route. The apps already don’t do this and it’s on my list to fix for the website but I haven’t had the time yet.

[Rob D]

Thanks Richard. Mine's Android and holding down on the route often didn't work. Quite frustrating, as it worked ok 2 months ago.

Re the elevation issue, it was only a few minutes from saving a route to re-opening it, so I don't see what might've changed in that short time. It happened many times.

[Rob D]

This is the message, using the phone to access my saved routes on the website: 'Sorry, couldn't find a route between those places. Check your points are on paved roads/paths'.

I have made 2 routes from Skopje to Athens. This happened just now on one of them.

Interestingly, in several places, the CT route avoids the nearby national cycle route - the red dotted line. I wonder if it's not paved?

[geocycle]

Some feedback for Richard on the latest tweaks to the Altitude Algorithm: I just planned and rode a trip from Hexham to Berwick -- a little bit over 120km of the sort of constant sharp up-and-downs which (as I understand it) are particularly difficult to map for height. CT predicted: 1700m of climbing. My garmin said: 1731m (and about 10m of that will be me coming out of the station the wrong way and having to go over an extra railway bridge ) Chapeau!

+1 There is now good agreement between the CT calculation and the wahoo measurements of the hills of the western Dales. Thanks you for the upgrade Richard.

[Rob D]

For our Oct/Nov trip to Albania, Macedonia and Greece, I've just been advised that some borders will not allow cyclists across. I'm using CT for route planning but does anyone know if it takes into account restricted borders?

Thanks.

[roubaixtuesday]

For our Oct/Nov trip to Albania, Macedonia and Greece, I've just been advised that some borders will not allow cyclists across. I'm using CT for route planning but does anyone know if it takes into account restricted borders?

Thanks.

The one closed border we crossed (with police permission) cycle.travel would not allow; I forced it with the direct to next stop option.

[Rob D]

That's good, thanks. Will be interested to hear Richard's comments on the issue.