I took delivery of the OpenCycleMap card yesterday thanks - it's working great thanks. I'm now keen to help with the mapping locally, but would like some advice before I wade in ...
I took a brief jaunt out to a part of the cycle network near me this afternoon -
In OSM, the relation now used for most of this stretch is 138421 with name="Wiltshire Cycleway" Network="ncn", Ref=254, which I presume is now correct. There are some short stretches (which I think are borked anyway) there which still have relation 226062 with network=rcn, ref=20 and no name.
If I've understood what's happening here correctly, the ncn 254 bits here are fine, the rcn 20 bits (just these short bits on the section mentioned) are junk and should be removed from the relation?
Would I be right in thinking your cycle map renderer is for the time being automatically rendering anything which is ncn 254 as rcn 20? If so will it be changed soon (if it's appropriate to)?
I'll cycle down to where ncn 254 seems to end at Rode in the next few days and extend from there if possible.
Jim (corshamjim on OSM)
I think I answered my own question - it looks like the ncn 254 section was only mapped on July 17th so I expect it just hasn't been picked up in OpenCycleMap yet. I see the Sustrans map still has at least some sections on their online map labelled as "Regional Route 20" so for the time being I'll go with whatever the signposts on the ground say for my OSM mapping.
EMPLOYEEI’m happy0Hi Jim - I think that's probably best - between the state of flux in the renumbering over this summer, and the update cycle between changes happening on the ground -> OSM -> OpenCycleMap, there's going to be one or two oddities showing up. As for the OpenCycleMap rendering, it doesn't have any special knowledge about the route renumbering, it just trusts whatever is in OpenStreetMap at the point that it fetches new data.