The view should now filter out all lines that are not supposed to appear at a specific stop:
Also updated the routing database so it’s not completely relying on the data from the 32bit version imported back in 2017. 
2 Likes
Should only appear on the first startup after an update.
This should come in one if the next releases.
2 Likes
@cypherpunk thanks for the update but unfortunately the filter has now removed Bakerloo Line Underground trains from both of the two entries for Underground Lines at Paddington.
As you identified the Bakerloo line seems to be included in the API under Hammersmith and City in the data returned by TfL. It’s something for TfL to fix I think.
By the way the search facility on the App is excellent but is literal when it comes to punctuation (apostrophes and periods).
Enter “Kings Cross” and you will get nothing returned because TfL spell “King’s Cross” with an apostrophe. Not sure how you get round this but being able to find points that contain punctuation when they are omitted from the search string would be really helpful. Having worked on Grays Inn Road, which is sometimes referred to as Gray’s Inn Road (How TfL spell it but not how the Council write the road signs!) I know that it is a subject for pedants to enjoy but a nightmare for programmers!
Great work though and thank you again for what you’re doing.
1 Like
Live updates on the Bakerloo Line seem to disabled at the moment, according to the TfL site:
" Live Updates
Live updates are not available for this location at the moment. Please see Timetables to check the frequency of your service."
I will try to replicate the issue as soon as the necessary data becomes available again.
2 Likes
1 Like
I learned to hate SOAP but it looks like integrating National Rail departures into MultiModal could actually be done:
2 Likes
National Rail support is (partially) integrated from version 0.12 on.
3 Likes
I’ve cobbled together a GTFS importer for MultiModal, should anyone be interested in making MM work outside London/UK:
2 Likes
I’ve added some additional information to the National Rail page in MultiModal, like number of carriages (where available) etc.
I’m not yet sure where to put long text fields like “reason for cancellation” etc.
Fantastic to see the speed of development in MultiModal. Great work!
The reason for cancellation could go in the “route” screen where the expected arrival times are shown. Perhaps as an additional piece of text at the end of the page. If the train is cancelled then at some point on the route list it will progress no further having been cancelled and having the reason there on that page might be helpful.
On a separate point relating to this screen showing the route and arrival times, the data for my line doesn’t show.
I live on the Tattenham Corner line which is unusual in that the line starts in London (London Bridge or London Victoria) as a train for both Caterham and Tattenham Corner with the train splitting at Purley. At Purley the front carriages go to Caterham and the back carriages go to Tattenham Corner.
Here’s the train in MultiModal correctly showing as going to Caterham and Tattenham Corner at London Bridge. (The NationalRail App only shows the Caterham part)
When you select the train however the App can’t display the data as it is expecting a single list whereas there will be a number of elements making up the different sections of the train.
In a similar way the return journey involves joining two trains, one from Tattenham Corner and the other from Caterham when they join together at Purley.
Screenshot showing no station list for the Caterham and Tattenham Corner line train.
Now if you could show both sections of the train in MultiModal and allow swiping between each part of the train that really would be great @cypherpunk 
As it turned out I had to rewrite large parts of the XML parser but the page should not crash any more:
1 Like
Brilliant! Thanks so much for this. Great to see the dividing trains in 0.24
That’s actually what I ended up doing.
Also the line at the left should now better represent the origin/destination points (by ending in a circle)
1 Like
Really nice. Almost makes you want to wish for a train to be cancelled! 
Hi @cypherpunk Great to have the active cover now. It could be helpful to include the station name or name of the stop whose data is listed, at the top of the cover before the service arrivals are listed.
It’s good to be able to refresh the cover service data by tapping on the cover but if space allows I wonder if you could show how up to date the info is please? A timer from when the data was last refreshed could be added (at the end / bottom of the cover)?
When heading to a stop to catch a service it’s sometimes difficult to remember to refresh the data giving the cover the chance of misleading you into how much time you have to catch the service. An auto refresh of the cover or a timer on how long since the last refresh could help you from missing the service.
Development is certainly moving at pace! 
I’ve been thinking about this when I’ve been designing the cover view but ultimately decided against it. It seemed to me like a waste of valuable space (especially with busy stations) as I thought for it to be very unlikely for someone not to remember which station they’re monitoring as it’s always exactly the same stop/station used on the cover as on the “regular” departures page (where the name is always present at the top).
But I may rethink my decision should this really be an issue for someone.
I agree, some kind of indicator would be a good idea. Plus configurable auto refresh.
1 Like
Now it is possible to filter trains at a busy station to only show trains that stop at a specific station.
Active cover also became a little more lively 
, but no auto update yet.
(Does not work with some destinations, e.g. Tattenham Corner, as TfL insists there are no train services running to/from this station)
1 Like