You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use pfaedle to enhance the VVS (Stuttgart, Germany) GTFS feeds.
However, we get some complaints where the deduced route does not match the real route.
If I read the code correctly, pfaedle would profit from maintained route relations in OSM(?).
To help gathering these, pfaedle could ease the rather tedious creation/maintenance of OSM route relations, if there were an option to generate route relations with OSM way Ids.
Helpful would be as well a report listing the GTFS stop id associated with the matched OSM stop ID.
The text was updated successfully, but these errors were encountered:
We use pfaedle to enhance the VVS (Stuttgart, Germany) GTFS feeds.
However, we get some complaints where the deduced route does not match the real route.
If I read the code correctly, pfaedle would profit from maintained route relations in OSM(?).
To help gathering these, pfaedle could ease the rather tedious creation/maintenance of OSM route relations, if there were an option to generate route relations with OSM way Ids.
Helpful would be as well a report listing the GTFS stop id associated with the matched OSM stop ID.
The text was updated successfully, but these errors were encountered: