Reading the replies, it seems the open question is whether we should solely rely on the order of ways in a relation, or on a key value to deduce/specify the direction in which the signposts are visible. I'm open for either solution.
My question is: If you we use "forward|backward|both" as the value in for example designated_direction=*", to what does forward relate? How do you know what forward is? On Thu, 2 May 2019 11:35:38 +0200, Tobias Wrede <[email protected]> wrote: > Am 30.04.2019 um 20:18 schrieb s8evq: > > - bidirectional=no > > - signed_oneway=yes > > - signed_direction=yes > > - designated_direction=forward|both|backward > > - signed=forward|backward|both|none > > > > Personally, I like signed_direction=yes. It's simple and avoids using the > > word oneway. > > Also, using the value forward|backward might not be necessary, as it's > > possible to deduce this from the order of ways in the relation. > > > signed_direction=yes is not intuitive in my opinion. Mappers might apply > it ("yes, there is a signed direction") but might forget to put the > members in the right order. Having a forward|backward|both|none in there > might make it more obvious to take care to apply the tag correctly. > > Tobias > > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
