Journey Planner help

The routing data for CycleStreets is based on the maps proved by the Open Street Map (OSM) project.

How CycleStreets interprets OSM data

The table that shows the relation between OSM highway features and our Provision Types:

Latest update of OSM data

This section summarises the most recent refresh of map data from the Open Street Map (OSM) project.

Currently the import is triggered manually, and it takes over 12 hours to complete. We usually run these updates about once a week.

Import log:

Import began at Fri, 23 Jul 2010 18:07:28 +0100.

Download site: http://download.geofabrik.de/osm/europe/, file: british_isles.osm.bz2 completed after 0.1 hours.

Extraction from the download via Osmosis took 3.9 hours.

Building the routing system took 14.1 hours to complete.

Optimisation took 13.5 hours. Compression ratio: nodes 579%, legs 277%.
Foundation Zone: UK and Ireland

Definition: compression ratio.

Namefinder Nominatim

CycleStreets has now switched to using http://wiki.openstreetmap.org/wiki/Nominatim to look up placenames. We use their live service to provide the results.

Tags used by CycleStreets

This is a new section of the help pages (introduced 21 Dec 2009) and will fill up with more info over time, in response to feedback.

One way streets

Icon http://wiki.openstreetmap.org/wiki/Key:cycleway

Ways that are marked as oneway=yes, but which also have the following tags are imported as 2-way streets, for cycling:

cycleway=opposite_lane
cycleway=opposite_track
cycleway=opposite

An example: http://www.openstreetmap.org/browse/way/4937416

To handle false one way streets: Split the way at the edge of the cycle plug. The cycle plug becomes highway=.., oneway=yes, cycelway=opposite*. The cycleway=opposite/opposite_lane/opposite_track overrides the oneway tag for most other modes of transport.

See http://www.openstreetmap.org/browse/way/4338252 for a longer example.

Traffic Signals

Icon http://wiki.openstreetmap.org/wiki/Tag:highway%3Dtraffic_signals

Any node that has highway=traffic_signals is interpreted by default as a traffic light controlled junction.

Nodes tagged crossing=traffic_signals are interpreted as traffic light controlled crossings, such as a pelican or toucan crossing.

Crossings

Icon http://wiki.openstreetmap.org/wiki/Crossing

Whese a way is tagged with highway=crossing, CycleStreets interprets this as a zebra crossing. If it also has bicycle=yes it is interpreted as a toucan crossing.

We welcome your feedback, especially to report bugs or give us route feedback.
My comments relate to: *





Your comments: *
URL of page: * http://www.cyclestreets.net/journey/help/osmconversion/
How did you find out about CycleStreets?:
Your name:
Our ref:

* Items marked with an asterisk [*] are required fields and must be fully completed.