There’ve been a trickle of updates over the last year - most of which are not particularly worth a post as are technical and incremental improvements. There has been an update to the public mileage engine and related services as well.

Mileage Engine

Following a number of recent queries about the mileage engine and its logical behaviour, we have made the following changes to the mileage engine:

Free Version

We have removed the ‘weighting’ routes and included all routes by default. The public mileage engine will now always route on the shortest path only. This will predominantly improve handling on the routes towards New Cross Gate from London Bridge. The system will no longer route via more common routes rather than shortest: for instance routes from Meadowhall to Mexborough will now always route avoiding Swinton as the route via Thrybergh is marginally shorter.

Subscription & Industry Version

We have introduced a checkbox that allows users with subscriptions (RMME, journey logging and industry) to use the more timetable biased algorithm. This is checked by default. RailMiles’ journey logging service internally uses this algorithm over any other due to its integration with Realtime Trains and ability to use train paths.

You’ll find this tickbox marked with words similar to “Use same mileage algorithm as journey searching” or “Use schedule pathing biased algorithm”.

Updates

This post was published in categories: RailMiles, RailMiles Mileage Engine