Trying to figure out whether this is an issue with Osmose or not. There’s a route_master relation in South Australia for the 863 route, that contains 6 route relations. Two of these also have ref=863
(one for reach direction), and then there’s two more directional sets for refs 863F and T863, which are limited stop/express variations of the same route.
Osmose flags this as an issue because the ref doesn’t match, which is correct, however I’m unsure as to which of these would be correct:
- Osmose is incorrect and the
ref=
tagging is valid - The
ref
tag on the route_master should include all 3 refs (ref=863;863F;T863
) - The route_master should be split into three, one for each
ref=
Can’t find any answer from looking here and on the wiki, not sure if it’s ever been a problem before. I can understand Osmose having an issue, however I’m unsure whether having the multiple values in the ref
tag is valid since I’ve generally seen consensus for ref:[entity]=
when multiple references exist.