Tag busway=opposite_lane not recognized

[Samoth47]

Incredible tool that Relatify is, a life saver to fix and update routes! Thank you!

But I've found myself updating my first route only to find that the tool does not recognize the tag busway=opposite_lane on a one way road, not letting me save my work because "Some ways are not used", "Some stops are not reached" and "The stop point is not reached".
The arrows are pointing in the wrong direction because this road is a one way road, with opposite lane for buses only.

In the meantime, for other people that finds themselves with the same problem as me, you can just add the tag oneway:bus=no to fix the issue in Relatify after reloading the relation.

[Zaczero]

Hello! I haven't used busway tagging but I am going to assume it's similar to cycleway. When it comes to mapping one-ways, oneway:* should be the primary tagging and busway/cycleway just an optional specifier. Otherwise the tagging schema becomes unnecessarily complex for data consumers (e.g., Relatify). I personally think we should fix the data once rather than implement the same fix in all downstream applications. Feel free to discuss 🙂

[Samoth47]

Oh, that's interesting, I didn't know that, seems coherent to me to not support busway=opposite_lane then, but Relatify could potentially be a bit more verbose about the issue, not specifically about this tag, but just saying that if oneway=yes and direction in opposite direction to the flow of the route, then display a message about potential missing oneway:*=no or -1.