davidpnewton
davidpnewton
To my mind it definitely needs orthogonal tagging to describe situations. In fact I'd argue there is more than one orthogonality needed. Marked/unmarked to describe whether there are markings on...
"I very much doubt, that there are in fact any "uncontrolled" railway crossings, at least not in the Western world, as all "valid" railway crossings are at least signalised, "...
Correct about railway and tram when it comes to tram street running. However again you miss things: https://www.flickr.com/photos/127699427@N02/30906536117 That's a railway station. It's also a tram. Trams on that section...
To my mind it definitely needs orthogonal tagging to describe situations. In fact I'd argue there is more than one orthogonality needed. Marked/unmarked to describe whether there are markings on...
Oops. Yes.
Solution to this? Make running the straighten way routine a pre-requisite for it. Straighten way is already in the software so there's no additional coding required there and running that...
Best workaround would likely be to temporaily split the way(s) so that only one intersection occurs. Not ideal but it allows the desired result to be achieved. I mean the...
You have difficulties. However you understand correctly. For nodes already tagged with highway=crossing the app should ask for the type of kerb.
> > it should not be asked for crossing nodes that are part of a `highway=footway + footway=crossing` > > Why's that? > > My reading of the OP's description...
Erm yeah. That's because I tagged it that way when I solved the Streetcomplete quests. Version 1 created by me 11 months ago was simply a node showing the intersection...