Minor bug: route colour changes at via point, not (just) track type.

Example: https://cycle.travel/map/journey/784956

On the web interface, the northern part is coloured green and the southern part is blue. However, the colour changes at the via point, wherever it is, so moving it changes the green/blue split. The whole western (dashed) section should be green/unpaved, I think.

It also changes the paved/unpaved summary on the left.

Can I join separate routes?

We can split routes, either manually or using the function to split at overnight stops, but can we join them? I can't see an obvious way to do it.

Why? Some of the route guides look interesting, but I'd like to be able to combine them into a larger tour. Similarly, some GPX routes published elsewhere are only provided in stages, but the stages rarely align with good campsites, so I prefer to see the whole route in CT and then chop it up myself.

I don't do this a lot, so I'm happy to do it manually, but perhaps there's an existing function I've missed.

Thanks!

App suggestion: indicate walking sections

Hi!

I've just finished the Rebellion Way. Yes, it's a set route (GPX), but using CT makes handling detours easy.

The Rebellion Way has a few short sections where you have to get off and walk. There's a section in Diss, for example, where you have to go the wrong way up a one-way pedestrianised street. The CT planner knows this and marks it as "pushing".

It'd be really helpful if the app could show that something's up here. Another colour would work for me (in the same way that blue and green are used for paved and unpaved surfaces), but a dotted route line might be more accessible. (It does show in the turn-by-turn instructions, but I usually just use the main map display.) The example in Diss is very clearly signposted, but some others I encountered were not.

Thanks!

Is “dim between turns” broken?

I only use “dim between turns” for very long trips, so I can’t say when this started, but for the last couple of days on tour it hasn’t dimmed at any point.

I updated the app (1.7) recently. I’m on a iPhone 15 Pro, and the phone was mostly connected to a dynamo charger. It used to work with this setup.

Is there any other information that might help?

CT routes through access=destination

Hi,

Today's route tried to take me down an "access only" road. OSM seems to indicate this with access=destination. That appears correct according to OSM documentation, but does cycle.travel expect some other tag? It normally only uses restricted roads and tracks if I put an explicit waypoint on them.

I've made an simplified example route.

Thanks!