On 8/4/2015 4:59 PM, Martijn van Exel wrote:
Also, please even if you see the crossing rendered, do go in and
check, because I have seen more than once that the crossing node is
not a shared node between way and rail. (Hint, use 'j' to join node to
way and 'm' to merge nodes that are (almost) on top of each other.)
I noticed something interesting about JOSM - if I select an
intersection that may or may not have 2 duplicate nodes, in some cases
where there were 2 nodes, the JOSM 'M' command has no effect the first
time. Now I always watch and try again if the merge was ignored. But
that can be another post-challenge fixup - duplicate nodes on rail crossing.
Other notes:
Please don't (C)ombine sections of railway unless there is a good
reason. I don't know if anyone is combining currently, but there was a
long span across South Dakota spanning 2 counties and 400 nodes which
was shifted (perhaps to correct a local problem). Mappers fixed
various crossings, and the long way was shifted 2 more times. I finally
just manually reviewed and fixed the entire shifted way.
https://www.openstreetmap.org/changeset/33235552
_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
