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
The ID of SiteConnection is built from the two relevant StopPlaces. However, it is possible to have multiple Connections between two StopPlaces (as it seems). This may be a problem in the GTFS, but it results in an id conflict in the resulting. Or some information was lost. In any case in the resulting correspondances.xml file, there should only be one SiteConnection element with a given id.
(note: I edited your comment to improve the rendering of the XML extract you provided)
This looks like a bug to me. Even if the origin GTFS have duplicated transfers rules (which seems possible from the specification, but probably is dubious), we might be able to remove the duplicate rules when we generate the SiteConnection. Not sure if we'll be able to fix that quickly though.
No problem there. We are not in a hurry. :-) It might be that in the original data there was more data for the transfers (e.g. platforms) that was omitted when writing to GTFS.
The ID of SiteConnection is built from the two relevant StopPlaces. However, it is possible to have multiple Connections between two StopPlaces (as it seems). This may be a problem in the GTFS, but it results in an id conflict in the resulting. Or some information was lost. In any case in the resulting correspondances.xml file, there should only be one SiteConnection element with a given id.
We used https://data.oebb.at/oebb?dataset=uddi:cd36722f-1b9a-11e8-8087-b71b4f81793a for the transform
The text was updated successfully, but these errors were encountered: