It should be in the next week. I'm working on a handful of improvements to the turn detection logic and want to finish them off before running the update!

Quick update: I've finished the main changes to the turn detection code (and tested it across London) so should be kicking this off in the next couple of days.

Monthly is too infrequent, bimonthly is hopeless.  I've been waiting to correct a route up NCN 818 since mid Feb and after waiting 10 weeks for an update it still won't route.  Is there going to be another update before June?

I really do not understand why updates cannot be a weekly scripted run.  Delaying and delaying to get the latest feature in is only helpful if a user is waiting for a new feature.  Given that new features are not announced in advance that is highly unlikely to ever be the case.

Sorry Richard, NCN 818 has put me in a bad mood.  You're new turn by turn only (no map) PDF is brilliant.  I used it for an 80km ride recently and your turn instructions were excellent all the way round.

Because money. Preparing the routing takes three plus days of computing on a server with 128GB RAM. If you’re prepared to pay Hetzner £100/month for that server, great, we can have weekly updates. Otherwise I need to do what I do at present, which is run it on a donated server in my office at home. Given the server makes so much noise I can’t easily do any paying work while it’s running, I can’t really afford to wipe out half my working week. 

The routing was last updated the other week or so, so if your NCN 818 update from February isn’t showing up, there’s another reason - what did you edit?

There seems to be a OSM issue with this route, even though Sustrans says it is OK (if somewhat rough), needs someone to check the route on the ground and correct issue on OSM. Apologises if I am in the wrong place. OSM issue:-

Yep, someone’s added mtb:scale=2 to the route in OSM which means “demanding mountain biking”, and cycle.travel won’t route across any such way. It looks like slightly hyperbolic tagging to be honest – it’s a rough track but not that rough.

Hi

These scale based tags such as mtb:scale are always subjective & as you point out, often exaggerated.

https://wiki.openstreetmap.org/wiki/Key:mtb:scale

From the images I struggle to discern the differences. To me, they're all 'I'm not riding that, I'm getting off & pushing'
Would this site be hindered if it ignored such tags using a combination of surface &/or steepness?

Hi Richard,

I've just discovered the 'direct to waypoint' option which solves the NCN818 problem.  I know the track, last June it was very eroded.  The two lines of concrete were fine but there was a deep gulley between them.  Quite tricky to stay on the concrete up such a steep incline but it would be a doddle downhill.  I'll review the tags after this coming weekend.

The direct to waypoint option is also useful for eliminating the overshoots when you put a U-turn in the route.

Out of interest, what processors does your server have?

Regards

Julian

Forgive me for maybe posting in the wrong thread but the new post button and the search feature both seem not to be working.

1.  If I make a change in OSM today, how long till it gets incorporated?

2.  It seemed like cycle.travel was not routing on an obvious route because there was no bicycle tag. By changing the tag to bicycle=yes, will it now utilize this route?

1. somewhere between a few days and about 6-8 weeks, depending on what point in the update cycle we are.

2. probably, but it depends on what other tags are on the route and the nodes along it (c.t won't route through locked gates, for example).

The latest routing update is just uploading so it should be a few hours now.

Europe up now, North America later today.

For anyone new visiting this thread and plans to ride NCN 818. I have 'ridden' it today and the surface was better than expected (judging from comments above). I had to walk about 33% of the unpaved section, but mainly because of gradient rather than bad surface. The thin strip of tarmac remaining from the original road is still mostly rideable. I used 38mm 'gravel bike' tyres. 

I have edited OSM to a lesser MTB scale , now 1 rather than 2.

The general question could probably be avoided if the map followed conventional practice and included a link to the update date with the other links at the top right corner. For the benefit of users like me who took years to realise you could click those links, it should probably be labelled 'Map date'. 

It is probably part of a general site layout issue. It can be quite difficult to find information like that, even if you look for it. Log out, for example is in very small print at the bottom of a page, but not the map page.  I have looked at the page of update dates above, which currently says about every two months, and last done on 29 July, but without the link in this forum discussion I doubt if I will ever find it again.