Railways, the application of the federation
The application shows the trains due at a station, keeps the ones you are waiting for, notifies you when a schedule you watch changes, and sends a fault report to the cooperative that operates the line.
- 0 accounts
- 3 screens
- 145 stations
- 4.1 MB installed
What it does
-
Wait
Trains added to a wait list
Pick a train from a departure board and add it to the list. The application then follows that journey: where the train is, when it is due at your station, and how far it may be.
A wait ends when the train arrives, and the entry clears itself.
-
Watch
Schedules watched for changes
Watch a section, a route, or one daily service. If the timetable or platform change, or if the service is cancelled, the application will notify you.
A watch is checked against the timetable, so it stays valid whether or not a train is running at the time.
-
Report
Faults reported from the platform
If there is a broken lift, a dark passage, a door that will not close or a heater running during the summer, you can write a report from where you are standing, add the station and the vehicle if you know it, and send.
The report reaches the route group that operates the line. Reports and answers are published together under Article 61(2).
The figures on the screen
Two sources sit behind every screen. Podnik publishes where each rail vehicle is and when it expects to reach the next stops. The federation publishes the timetable, the platforms, and the changes the route groups decide.
An estimate has its margin. A departure shows a time and, beside it, an estimate on the time difference between the actual departure and the list. The margin widens on a long run and after a stop is missed. When no vehicle is reporting, the screen falls back to the published time and marks that there is no estimate.
A schedule change names its author. Changes come from the assembly of a route group or from its duty office, and the notice names which one, with the date it was decided.
What it stores about you
The wait list and the watches stay on the device. The application asks the two sources the same questions any other client asks, and neither of them require authentication. There is no account to make and no history kept on a server.
A report only contains what you write. Station, vehicle, time and your text. No device identifier and no location trace are attached. You may leave a way to be reached or you may leave none and the answer is published either way.
The gate record belongs to the card. Records are written at the gates and at the machines. The application reads no card and writes none. To read the last ninety days on a card, take it to any machine on a concourse.
Getting it
-
On the standard handset
The brick ships with it, and it updates with the rest of the system.
-
On a handset from outside
Download the package from apk.nrf.rof/railways and install it. The signature to check it against is printed beside the download and posted at the ticket halls. It runs on LineageOS and on stock Android 9 upward.
-
From source
The tree is at source.nrf.rof/railways-app, with the build instructions and the release signatures beside it. The developer pages list everything else that is published.
-
Or another client
The two sources are open to anyone under Article 10. Four other clients exist, one of them a departure board that a commune hangs in a shelter.
Without a handset
-
At the station
Every concourse machine shows the same departure board as the flip boards on the platform and you can write a report from there.
-
By telephone
The short code 118 reaches a person at the route group. They read the board out and file a report for you, and the answer reaches you the same way.
-
On paper
The printed timetable is issued twice a year, free at any station. Change sheets are posted in the ticket hall on the day they take effect.