Turn by turn omission - crossroads near Crediton

I sometimes notice that the combination of OSM/cycle.travel/my Wahoo Elemnt Bolt v2 doesn't handle parts of routes correctly but I don't know which is to blame!

I will give examples like this as I notice them.

On my ride yesterday a crossroads was not picked up. The Wahoo told me to carry on for 3.3 km, with no warning that I had a junction to stop at along the way!

It was obvious on a sunny afternoon but might not have been at night or in misty conditions.

Cragg Vale hill climb

This is the official Cragg Vale hill climb route. There is a very gentle slope up to the start of this from the sign in Mytholmroyd but I time myself on this section. It is 7.7 km in length with an average gradient of 3.8%. There is a steeper section at 8-9% for a few hundred metres mid-climb but overall this is a fairly gentle climb. The main difficulty is that the second half is over exposed moorland and there is usually a cross-headwind up there which can sometimes be tougher than the climb itself!

Auto-save?

Hi Richard.

I often forget to save a route after editing it and when I come back later my changes have been lost. I just did it again when my laptop prompted me to restart after an update.

Could you add an auto-save feature so that cycle.travel can come back exactly where it was when last shut down?

Thanks.

Cue sheet oddity

I was recently in Devon and wanted to test my Wahoo GPS with a cue sheet generated by cycle.travel so I planned a little loop round lanes that I know near Crediton. I was riding east from Shobrooke towards Thorverton and spotted something odd which would have confused me greatly if I didn't already know the roads there...

The road I was on comes to a T-junction at Raddon Cross with the road coming down from Raddon Hill. I needed to take a right and very shortly after that a left. The cue sheet just instructed me to take a left, as if my road had priority at the junction and I was bearing right. If I had obeyed the left turn instruction I would have in fact headed north up the hill.

I thought that the problem was probably caused by somebody making a mistake on OSM but that looks ok (Raddon Hill road straight through, others stop at it)?

If there is something wrong on OSM could somebody please explain it so I learn how to fix that kind of thing in the future - thanks.

I worked out how to correct a couple of mistakes I found in OSM-Todmorden and cycle.travel picked up my changes a week or so later.

BST used for timestamps?

I just saved a route that I was working on. It was saved at 23:25 on Tuesday but c.t. is showing it as having been saved at 00:25 on Wednesday! Windows correctly showed it as 23:25.

It isn't super-important to me to have it fixed but it might be something to take a look at?