-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{"detail":"Relation is empty, which is not supported"} #87
Comments
Hi! If you provide the number of this bus route in OSM, it will be easier to find the problem :) |
Hi Marek, this is the route I first had the issue with: https://www.openstreetmap.org/relation/18336141, tags: The route I created a year ago but worked in Relatify is this: https://www.openstreetmap.org/relation/16358587, tags: from=Cirencester (Cirencester College or Kingshill School) Thanks a lot. |
In my opinion, there should be no errors in this bus route. I don't know why Realtify has such a message. I think that the author of the application, when he finds a moment, will try to solve this problem. @Zaczero, please check this relation #18336141: Thanks! |
Hi, I have the same error message with these relations: |
Same issue |
Can't figure out if I'm dumb as hell or this is a bug of some sort, but this error message keeps popping up whenever I enter relation IDs into Relatify, despite the said relations all having at least one way with no role and a bus stop node with a platform role.
Initially I thought I may just need to give it a moment as said on the wiki page, but it's been almost 4 hours since I made the first route. Then I realised the routes started on a highway=service without bus=designated, so added the latter but still no avail.
Strangely, as a test I upgraded a route I traced in iD over a year ago to PTv2 and it opened up in Relatify without issue within seconds of publishing my changeset.
The text was updated successfully, but these errors were encountered: