FGW Ticket Booking function ignores Trans-Wilts

[whole diary]

[PhilWakely]

I'm not sure whether this should be posted here or in the 'Fares Fair' board.

I am visiting Chippenham in the middle of next week and thought I'd book tickets from EXD^» (Exeter St Davids - next trains) via Westbury and Melksham. I was very surprised that the FGW^▸ (First Great Western) booking engine does not offer the routing unless I force it - even though it is cheaper (using 2xsingle) and no slower. I first entered EXD to CPM^» (Chippenham - next trains) via WSB^» (Westbury - next trains), but all it offered me was via WSB and BTH^» (Bath Spa - next trains)!

Interestingly though, when forcing the routing via MKM^» (Melksham (Station code) - next trains), it offered me a return leg of CPM - TRO^» (Trowbridge - next trains) - BTH - BRI^» (Bristol Temple Meads - next trains) - EXD !!

Also, when I re-tried EXD to CPM without the 'go via' option, it did offer me the Melksham route. I thought it may have 'remembered' my previous search, so cleared the cache and, surprise, surprise, the Melksham option was no longer available!

Can anybody explain?

[ChrisB]

Doesn't sound that it's loaded as a permitted route - or else all journeys are slower (even by a few minutes) and it's programmed to find the fastest journeys

[PhilWakely]

Oh well - I've forced the routing and, just for the ride on the way home, I've chosen the CPM^» (Chippenham - next trains) - TRO^» (Trowbridge - next trains) - BTH^» (Bath Spa - next trains) - BRI^» (Bristol Temple Meads - next trains) - EXD^» (Exeter St Davids - next trains) routing as I am not in any particular hurry and it is cheaper than CPM - BRI - EXD 

[Ollie]

WebTIS usually presents journey options based on quickest option, that's the only reasoning I could think of for not showing via Melksham by default.

With the full journey details I could have a look in a bit more detail.

[stuving]

Doesn't sound that it's loaded as a permitted route - or else all journeys are slower (even by a few minutes) and it's programmed to find the fastest journeys

Had a quick look on Journey Planner, and for return journeys in the daytime off-peak (which I think the OP^▸ (Original Poster / topic starter) wasn't looking for) it offers all three routeings, plus direct, at the same price. The one direct train is very much quicker, and the Transwilts option slowest despite having fewer changes than going "backwards" to change at Bath.

It's all down to connection times. For the Transwilts it's 45-50 minutes, and at Bristol 30-45, but much less both times to get to Bath and turn back.