Bicycler wrote:I don't have any problem at all with the rate of updating. I have no desire to bring about Richard's deafening by server noise
viewtopic.php?f=16&t=83831&p=956095&hilit=server#p956095 I would just find it helpful to be able to check the date of the current import. A footnote or simple changelog would suffice.
Good idea! I've just added a page to list that:
http://cycle.travel/map/info . It automatically changes whenever I update the maps (it's the timestamp of the last download).
SA_SA_SA wrote:Is it much work to add optional intermediate text boxes for 'via' points (like the way google maps allows new destination text boxes to be added (and moved between start and destination if needed)?
When you say routes are precalculated, is that a subset of the most likely routes, surely 2^Possible start and end points in UK is a huge number?
Adding intermediate text boxes is definitely on the to-do list. It's not a trivial change, but on the other hand it'll give me the opportunity to add drop-down autocomplete to the placename entry, which I've wanted to do for a while. So watch this space.
The precalculation uses an algorithm called Contraction Hierarchies, which essentially relies on the fact that optimal routes cluster onto a network after a while. It's easiest to think of for driving routes - no matter where in Oxfordshire you start, if you're going to Scotland, you'll ultimately end up on the M40 and then the M6 before long. If you're curious, Dennis Luxen, the creator of OSRM (the core routing software that cycle.travel uses), gave a good talk on it at an OpenStreetMap conference a couple of years ago:
https://www.youtube.com/watch?v=2Pt_LnQjywc . He's a clever guy - shortly afterwards he was hired by Apple...