Mod note: Split from RailUK Tickets discussion
Take for instance Marske to Middlesbrough. Two Northern services per hour through most of the day at xx04 and xx27 with return options at xx53 and xx24. Journey time is around twenty minutes. If you search that up in Trainsplit however it only shows an hourly service the xx27s from Marske and the xx53s from Middlesbrough because these are around two or three minutes faster than the other trains (due to having a call at South Bank). But I would expect that 99.9% of passengers would want to see both services rather than only see one service! You can manage to get them to show by selecting cheapest (through most of the day) but obviously the default is "Best Value" which filters out half the trains for the sake of a couple of minutes shorter journey!
You also struggle a little bit at some of the margins. If you search for outward journey with "Best Value" at 0800 the first option it will show is 0913 but there will have been 0804, 0827 and 0904 which I feel should have been shown by a search asking for departures after 0800 but I think this is due to a mixture of Off-Peak becoming available from 0900 (meaning it's ignoring the more expensive 0804 and 0827) and the 0904 being slower than the 0913.
It feels like there needs to be a smidge of optimisation for shorter journeys here perhaps? If you were doing a long distance journey, potentially with changes, then heavy filtering makes sense but in this example of a direct train over a short distance (in both time and mileage) it feels like it should just show all the trains between the specified stations without trying to worry about saving me a couple of minutes but hiding half the services, or hiding three trains after my desired search of 0800 because of the journey time and off-peak/peak fare interaction!
Which reminds me! I think there's another slight problem with the logic Trainsplit applies to search results meaning it excludes good journey options which the passenger would definitely want to know about.There's an issue with the size of search window that Trainsplit uses.
Take for instance Marske to Middlesbrough. Two Northern services per hour through most of the day at xx04 and xx27 with return options at xx53 and xx24. Journey time is around twenty minutes. If you search that up in Trainsplit however it only shows an hourly service the xx27s from Marske and the xx53s from Middlesbrough because these are around two or three minutes faster than the other trains (due to having a call at South Bank). But I would expect that 99.9% of passengers would want to see both services rather than only see one service! You can manage to get them to show by selecting cheapest (through most of the day) but obviously the default is "Best Value" which filters out half the trains for the sake of a couple of minutes shorter journey!
You also struggle a little bit at some of the margins. If you search for outward journey with "Best Value" at 0800 the first option it will show is 0913 but there will have been 0804, 0827 and 0904 which I feel should have been shown by a search asking for departures after 0800 but I think this is due to a mixture of Off-Peak becoming available from 0900 (meaning it's ignoring the more expensive 0804 and 0827) and the 0904 being slower than the 0913.
It feels like there needs to be a smidge of optimisation for shorter journeys here perhaps? If you were doing a long distance journey, potentially with changes, then heavy filtering makes sense but in this example of a direct train over a short distance (in both time and mileage) it feels like it should just show all the trains between the specified stations without trying to worry about saving me a couple of minutes but hiding half the services, or hiding three trains after my desired search of 0800 because of the journey time and off-peak/peak fare interaction!
Last edited by a moderator: