Our maps are made using open data from OpenStreetMap, licensed under the Open Database Licence; with additional UK data from Ordnance Survey, licensed under the Open Government Licence (© Crown copyright and database right 2016), and additional Canadian data from StatCan (Geography Division, Statistics Canada). UK traffic data is from the Department for Transport under the Open Government Licence. Additional US data from federal sources.
OpenStreetMap is made by people like you. If a cycle path, road, pub or café is missing, just head in and add it. It’ll then be available to thousands of other cyclists using cycle.travel, OpenCycleMap, CycleStreets, Sustrans’ printed maps and many other projects: we all take the same data and add our own spin to it.
Here at cycle.travel we’ve supported OpenStreetMap since its first months back in 2004; we’ve mapped countless miles of cycle routes and contributed a lot of the code that’s been used in the project over the years.
We aim to take updates from OpenStreetMap every month: it then takes around three days to do all the calculations to find the best routes. Here’s the date on which we last updated the data.
We do a lot of processing work to make the raw OSM map as useful as possible for cyclists. If you’re editing OSM, here are some of the things to keep in mind:
We also use Ordnance Survey data for UK built-up areas, Corine data for European built-up areas, and government open data for North America. We use both Ordnance Survey and NASA data for elevation.
If you find something missing or misleading in our maps and directions, head over to OpenStreetMap to fix it. But if OSM’s right, and cycle.travel isn’t doing what you’d expect with the data, we want to know. Post in the cycle.travel site forum and let us know what you think.
Once you’ve planned a route, click the GPS button on the left to download it. There are lots of different formats of GPS file: we generally recommend a ‘GPX track’ which works on pretty much anything, but if you have a newer Garmin or Wahoo, you might want to choose a ‘TCX course’.
For a Garmin, you then need to connect your unit to the computer via USB, and copy the file across to the ‘NewFiles’ folder (cycling Garmin units: instructions) or the ‘GPX’ folder (eTrex units: instructions).
We don’t have any experience with Wahoo GPS units, but we’re told you can email the file to your phone, click ‘Open in…’ to open it in the Wahoo app, and then it’ll appear on your GPS. If you have any experience getting this running, let us know!
Unfortunately not. cycle.travel’s route-planner works by pre-calculating all the best routes for cycling. This means that it can be blisteringly fast – even when calculating a 1,000-mile route – and that you can drag the routes in real time.
The downside is that, because everything’s pre-calculated, you can’t change the weightings for each type of road when you ask for a route. In theory we could pre-calculate a second set of weightings such as a “no off-road” planner, but since the routing data is very memory-hungry (32GB RAM for Western Europe and North America), we’d need to rent a new high-speed server for each set – which would get very expensive very quickly...
Our priority is to make cycle.travel’s default routes as good as they can be, while making it easy for you to adjust the route (by dragging) if there are sections you want to avoid. In addition, we’re currently working on a feature that will let you turn the route-planner off between any two points, so (for example) you can plan a short stretch on a busy road even if cycle.travel doesn’t recommend it.
(If you want to read up on the maths behind cycle.travel’s super-fast routing algorithm, it’s known as Contraction Hierarchies.)
We’re developing an iPhone app at the moment and plan for it to be available later in 2018, with Android to follow afterwards.
Not officially. Our hardware is dedicated to serving visitors to cycle.travel. Our (significant) costs are covered by advertising and the little commission from hotel bookings, so we can only provide the maps and routing on this site. If you do really want to use our mapping and routing, drop us a line and we can chat.
If you’re looking for custom development work on cycle routing or cartography, our editor Richard Fairhurst would be delighted to talk to you. If you are looking for an off-the-shelf UK cycle routing API, we recommend you talk to the lovely people at CycleStreets. If you are looking for map tiles, talk to the equally nice people at Thunderforest.