I sent you some feedback on a routing failure because I didn't want to post exactly where I live here.
I think you need pricing. Works offline is cool, but why not pull in the pricing if people are online? Train fares are so variable depending on time of day, especially if they go via London. I could have a trip that could be £300 cheaper by taking a 30 minute longer trip that avoids London. I need pricing to get my best journey.
Thank you for the feedback, pricing is definitely next on my to do list if I can make it work.
I'm looking at how to add price data to railraptor, but it might mean sacrificing the fully-offline capability... once I have prices it should absolutely be possible to build a filter along the lines of "find me the cheapest popular destinations that are at least 50 miles away".
Some feedback: I don't think it can route through London as it isn't aware of tube connections between stations? And the classic stress test of Penzance to Thurso is too long for the routing algorithm, but I imagine that's beyond scope?
Pricing would make this a super useful tool!
The routeing data is pretty complex - there are layers on layers of data files and rules to cover all the edge cases and weird stations/routes. It's been really fun to dig into it.
I'll look into adding more possible connections to see if it can find the Penzance route - I'd be curious to know if anyone has ever actually completed the 27 hour journey!