Skip to content
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

Cancelled connections and platform changes #183

Open
ShiroYacha opened this issue Nov 4, 2017 · 8 comments
Open

Cancelled connections and platform changes #183

ShiroYacha opened this issue Nov 4, 2017 · 8 comments

Comments

@ShiroYacha
Copy link

Hi,

This is more like a question then an issue. Is there anyway to identify cancelled connections? I have read that you are merging your info with GTFS-RT from transport.opendata.swiss, but seems they do not provide any information on service alerts...

Thanks!

@helbling
Copy link

helbling commented Nov 4, 2017

We from timetable.search.ch are still developing the gtfsrt integration.
This turned out to be quite complicated.

We expect it to be ready soon. Cancelled connections are supported.
They even have dynamic additional trips which are often necessary when there is some replacement service.

What do you mean by service alerts?

@ShiroYacha
Copy link
Author

Hi, I mean in this document https://opentransportdata.swiss/de/cookbook/gtfs-rt/ they only provide trip update but no service alert which is basically cancelled trains etc... Which gtfsrt data/api are you guys using for integration?

@helbling
Copy link

helbling commented Nov 4, 2017

Yes, we are using this gtfsrt api. Cancelled trains are specified in "trip updates" as well (don't know if they have them for all the transport companies they support in gtfsrt).

We also have something similar to the service alerts which is this system: http://fahrplan.sbb.ch/bin/help.exe/en?tpl=showmap_external
Look for the key disruptions in the json returned by the timetable.search.ch api.
This key is only returned whenever there is some disruption at all.

@ShiroYacha
Copy link
Author

Indeed there are some schedules marked as "CANCELED" in the trip_update... However, there are so few that I think it might not be exhaustive even for all the companies that supported GTFS-RT... I will take a look into http://fahrplan.sbb.ch/bin/help.exe/en?tpl=showmap_external

Thanks for the info

@ShiroYacha ShiroYacha changed the title Cancelled connections Cancelled connections and platform changes Nov 9, 2017
@ShiroYacha
Copy link
Author

ShiroYacha commented Nov 9, 2017

Hi,

I am also looking at platform changes. If I understand correctly, platform changes are not yet integrated in transport.opendata.ch? I am looking into GTFS-RT, but it seems that this is not explicitely reported either there (actually, if they list a stop_id, and there is a platform change, the data seems to be correct judging by the platform number in the id, e.g. 8502202:0:5; however, it seems that there is no trigger for this type of changes)...

How do you deal with these kinds of changes?

Thanks!

@helbling
Copy link

hi
I have enabled track changes as experimental opt-in on the timetable.search.ch API.
If you add &show_trackchanges=1 changed tracks are considered. Changed tracks are returned in the same field normal planned tracks are returned and an exclamation mark is appended.

@hb9tst
Copy link

hb9tst commented Feb 20, 2020

Are there news about this? Two years passed but it still looks like the real time data is not available (neither on transport.search.ch nor via the opendata API). For instance, tonight the IC5 from Neuchâtel to Lausanne at 19:03 is cancelled (which appears on the SBB timetable):
Cancelled train on SBB web site

But this is not visible from transport.search.ch...
Same train on transport.search.ch, no trace of cancellation

@schafran
Copy link

Are there any news on this? timetable.search.ch seems to have the information about cancelled connections, however I see no info about cancellations on the connections api endpoint.
Is there any other way I can find whether a connection is cancelled or not? Delay seems to be working fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants