UPDATE:
Taken SimonPoole’s suggestion as an invite, sent WeTransfer link to him by PM - avoid more than one mapper working on same item; Simon weeded the .osc file and successfully executed the rest, for which thanks are due.
Opened each of 53 ways and 83 nodes in ‘our’ changeset and found - apart from the edit to a 3885 member relation ‘Functioneel Fietsroute Netwerk Antwerpen’ - four nodes, each at the corner of a house, where the tag bicycle=use_sidepath had been added : looks like something got mixed up there, the houses *are *along the route edited, but there was no intention to edit those houses as this edit was about the new road and cycleway layout on the opposite side than the houses are on.
This means the bulk of the changeset has now been done, and by looking at each way and node havenow completed the rest to the best of my knowledge - which will be limited as I’m a rank beginner.
Have up-delegated Simon’s suggestion to split the cycling net into more, local, relations and combine those in a super-relation to two experienced -many 1000’s of edits- mappers whom I had picked up work with City and province on mapping and cycling infrastructure; they’ve confirmed they’ll follow this up.
**Which leaves the Take Home part of this post : **
1/ it is acceptable to pan along a rural road adding miles of cycleway where there are few side roads, but
2/ in urban areas better to complete work on single intersections, then the stretches between those intersections;
3/ when working on a relation with close to 4000 members do just that one edit and upload : thus minimise chance that s/o else uploads change before you do;
4/ but please also alert the originator that the relation is growing rather large.
**Suggestions for further action / future improvements: **
iD : it would be helpful if the iD editor could flag that I’m editing a large (>1000 members) relation, suggest to save before and after editing this …
iD : it would be helpful if the conflicts could be viewed and somehow remedied : ‘ignore’ (because I didn’t survey that aspect), add a crossing, or remove that particular action from the list of edits to be carried out, then upload again;
OSM : it would be helpful if just that one edited member of the large (say >1000 members or covering over say a square kilometre of area) relation could be inserted into the database, rather than - as I now take it - uploading nearly 4k members …
OSM and each editor : is there a way to flag that a relation covers a lot : a large number of members, a large area - whatever can lead to several mappers working on the same relation at the same time, and the one who uploads last in effect loses their work, please?
Aim of the final point is to prompt the operator / originator of the relation -rather than the mapper who happens to edit part of it- to break it into manageable chunks.
With best regards / met vriendelijke groet,
H4N5