Routing (in some countries called navigation) services help people get from one place to another. OpenStreetMap data includes information for routing by many modes including car, foot, bicycle and horse. There are many offline, embedded and web-based routing services using OpenStreetMap data.
For developers this page provides advice on software available for creating new routing applications/deployments and details key OpenStreetMap data that can be used to create better routing engines. A number of mailing lists are also available.
- 1 End users: Routing software
- 2 Mappers: Improving the map data
- 3 Developers
- 3.1 Open source desktop and server software
- 3.2 Mobile device software
- 3.3 Libraries/development tools
- 3.4 Routing considerations
- 3.5 Routing obstacles and other conditions requiring special consideration
- 4 Discontinued Routing Engines
- 5 Mailing lists
- 6 See also
End users: Routing software
See also: List of OSM based Services#Routing
- simply on the OSM homepage (blog post with description)
- Routing/online routers – There are many websites that use OpenStreetMap data to provide online route planners; those with global support are featured below.
- Routing/offline routers – Furthermore several options exist for installing offline navigation software on your handheld device or laptop.
- Navigation apps are available for Android, Apple iOS, Java ME (J2ME) and Openmoko. For other mobile platforms see Software#Mobile Devices.
Mappers: Improving the map data
For routing software to work well, the underlying map data must be of good quality. Essentially this means that ways that should be connected are in fact connected, one-way roads are tagged, turn restrictions are mapped, and so on. You should be familiar with the Map Features used, in particular see OSM tags for routing to understand the tags specific to routing.
Fixing bugs with MapDust
Many of the bugs on MapDust have been added directly from within iOS or Android navigation apps. This makes it a good place to look for improvements to the map data. Some bugs are specifically about one-way roads or turn restrictions, and are marked as such.
Look out for many "poor routing" or "other" bugs in a small area as this may indicate a missing connection between ways. In Potlatch when you select a way you will see all the nodes highlighted. If a node is big and square then it is connected to another way. To improve the quality of OSM data you can use also the reports generated by WayCheck.
Note: Try unchecking the "Hide bugs with default text" on mapdust as many users do not change the default text whilst using the navigation app.
In order to better calculate the fastest route, please consider helping by adding speed data using the maxspeed=* tag. This is especially important where the speed limit differs from the assumed maximum permitted speed for the road type per country and vehicle-type.
- Note: There are some services to help identify missing speed limits.
Often maxspeed is meaningless - see #Average speed.
Checking your fix
After you have fixed an error on the map you will need to wait until the revised version of the map propagates into the routing engine you are using. This delay will depend for each engine on:
- how often it get updates from the database
- how long it needs to update its internal database.
In the case of OSRM used on the map front page it usually gets updates twice a day and then spends 10-12 hours processing the updates. This gives a total delay of anything from 10 to 24 hours from your fix being saved to the map, to working in OSRM.
Open source desktop and server software
- GraphHopper is an open source routing engine for road networks written in Java. Fast and memory efficient (for Android, iOS, desktop and server), used by Cruiser and many others
- OpenTripPlanner site is a multi-modal trip planner supporting OSM data. OTP Deployer makes it easy to deploy your own routing instance.
- BRouter focuses on bike routing and features elevation awareness, alternatives, fully configurable routing profiles and offline routing initially written for Android, but has also a web api. BRouter can also run in QMapShack.
- OptaPlanner is a lightweight, embeddable planning engine which optimizes the Vehicle Routing Problem, the Traveling Salesman Problem and variants. It is based on GraphHopper and Google Maps APIs.
- Open Source Routing Machine
- Valhalla ()
- Routino Flexible router with user selectable routing preferences.
- RoutingKit (BSD license, C++)
- Itinero – (.Net) libraries for routing and transportation optimization problems; formerly part of OsmSharp library
- Mormon ruby version of pyroutelib
Mobile device software
- Guru Maps online & offline routing for iOS & Android
- OsmAnd OSM Map, POI and Routing (car/bike/foot, online&offline) for Android and iOS
- Navit Linux, Windows and portable devices
- GraphHopper Open Source routing library for Desktop, Android and iOS, used by Cruiser
- BRouter focuses on bike routing and features elevation awareness, alternatives, fully configurable routing profiles and offline routing for Android
- OpenTripPlanner_(Android) is an Android app for multi-modal trip planning using any OpenTripPlanner server
- MapFactor Navigator Free for Android and iOS
- MAPS.ME for Android and iOS
- Main article: Frameworks#Navigation
Libraries focused on OSM Routing can be found at Develop/Frameworks. Here some general libs:
- DGLib Directed Graph Library used by Grass's vector network tools (shortest path, traveling salesman, isodistances, Steiner trees; also Addons)
- Graphserver is a webservice providing shortest-path itineraries on TIGER/line road maps, and public transport data in the General Transit Feed Specification format
- osm4routing is a command-line tool for parsing OSM data into a routing graph.
- pgRouting - PostGIS-based routing engine. Special tool osm2pgrouting for importing OSM data to internal graph structure. Works directly on top of SQL database tables.
- Libosmscout offers simple, high-level interfaces to offline rendering and routing functionalities based on OpenStreetMap data
- Spatialite Spatialite has its own routing engine VirtualNetwork and a spatialite_osm_net tool for building a routable network directly from OSM data. Routing can use either Dijkstra or A* algorithm.
- GraphHopper routing engine with Java API.
- Valhalla is a free, open-source routing service that lets you integrate routing and navigation into a web or mobile application.
- The default-protocol is the API v0.6 spoken by the main servers. If can contain all data there is in OSM. Get Planet.osm dump.
The order of values for the highway-tag ordered by assumed speed is:
|Type||Description (mainly valid in Western Europe)|
|motorway||Usually the maxspeed can be kept for long distances, but these roads can be sensitive to long traffic jams. Usually forbidden for slow traffic (pedestrians, cyclists, agricultural, ...)|
|trunk||Similar to motorways, but these roads can have level crossings, so the stretches where the maximum speed can be reached are shorter. Best avoided when using slow vehicles (sometimes forbidden, depending on the local legislation).|
|primary||Connecting roads between cities, towns and villages. The classification depends mostly on the importance of the areas they connect. This is often also reflected in the number of lanes and the general traffic throughput, but the speed for these classifications is mostly comparable. Usually around 90-100 km/h in the countryside, and 50 (or even 30) km/h when crossing a residential center.|
|motorway_link||Used for on- and off-ramps or complete motorway junctions. Reachable speed depends a lot on curvature, usually around 60-90 km/h|
|trunk_link||In contrast to motorway junctions, these link roads are often very short pieces (f.e. allowing one to turn right without stopping at a traffic light). The speed on these road pieces is very slow, as these often need to give way to the other traffic.|
|unclassified||These roads usually connect farms, isolated houses and small hamlets through the countryside to bigger residential areas. Due to lack of traffic signs, they often have a speed limit way faster than can be driven safely. Speed on a well-maintained but unfamiliar unclassified road will rarely exceed 50 km/h.|
|residential||Residential roads are found in a residential area, so usually have a speed limit of 50 km/h to 30 km/h, with a lot of traffic calming features.|
|living_street||Living streets are streets where slow traffic has absolute right-of-way. The speed limit is normally around 20 km/h. Through-going traffic is absolutely discouraged (and often impossible).|
|service||Service roads are usually found on private property or parking lots. The driver has to pay attention to manoeuvring vehicles, and must wait often.|
|track||Tracks are roads of agricultural purpose. They usually connect fields to farms. The surface sometimes makes them inaccessible for regular cars, or at least limits the speeds to a very slow pace. Tracks should always be avoided for through-going traffic.|
|pedestrian||Pedestrian roads are normally forbidden for motorised vehicles, but can be allowed on certain hours (f.e. early in the morning), or for certain purposes (like delivering goods to shops). Even when allowed, only pedestrian speed is advisable. Cycling can also be forbidden on pedestrian highways.|
This is highly country specific and rather useless without country specific values. For example in Germany primary roads allow 100km/h both legally and as a realistic speed while minor motorway_link(s) are built to allow a recommended speed of 60 km/h, only major motorway_links allow a realistic speed of 80 or 100. For more information see OSM_tags_for_routing/Maxspeed#Additional_information_for_selected_countries
The number of lanes of a highway is directly tagged in OSM and has a major influence on the average speed (fastest route) and fuel-consumption (most efficient route). There is no simple mapping to speed unfortunately, in many cases more lanes only indicate more congestion.
Other factors, in our case more difficult to measure, which determine the average speed are the width of pavement, condition of the network (roadworks, surface type and surface smoothness - especially in ex-USSR), Levels of Service (LOS), minimal radius curve, banked turns, visibility based on curves and gradients, etc.
Same as curves, inclines may decrease the speed of traffic. In winter of when lots of hgv is present the hindrance is also on the descending way. While some inclines are explicitly tagged, in some cases utilization of additional informations such as ele=* and height elevation profile from DEM data could prove useful.
See also turning radius=*
In some studies about the accessibility  develop models that assume a certain speed of travel depending on the degree of sinuosity of the track and certain characteristics of this one. By means of the sinuosity index (observed line distance/expected line distance ) for every section it is possible to obtain a speed estimated according to the degree of winding of the road and type of route. This needs to take into account the visibility around corners (determined by vegetation, embankments, cuttings, cliffs,...) and road width. The model is more precise if the excessively large arcs are avoided provided that a long curve can be equal to many small curves along a way, giving similar values of sinuosity for both routes. Some countries use these values to divide sections of roads and put speed limits (but this is not usual).
On the other hand, geographical approaches like that of the space syntax presuppose that, in urban environments, pedestrians and drivers are influenced at the moment of choosing theirs paths for the visibility of the route. In this respect a pedestrian who moves, for example, from the point A to the point B will select principally wide and rectilinear streets, squares or avenues with a wide visual field, avoiding crossed by winding and narrow streets, even when the latter route is somewhat shorter.
Crossings, junctions and lane changes
Certain cost should be assumed for:
- crossing higher-class roads
- changing to and from lower-class roads
- lane changes
- traffic-signals, see also Key:traffic_signals:direction
OpenStreetMap data will need average/realistic speed values for routing.
- maxspeed:practical=* is a rejected but nevertheless used proposal to tag estimated average speed values (with the possibility to specify day/night/rush hour values) in areas where official speed limits are largely meaningless and road/track type information insufficient to derive meaningful travel speed estimates.
- Speedcollector is a currently defunct service to collect real-world measurements, while it might be possible to derive average speed per way from stored tracks.
- Global Statistical Speed Matrix is a proposed concept (no current signs of life?) to extract speed information from NMEA/GPX tracks and store them efficiently in a database to make collected data useful for routing purposes.
- For an upper limit, see maxspeed=*
- bicycle=* for bicycle specific access=*
- highway=cycleway for separated cycle-ways
- cycleway=* for on-street cycle facilities
- see also hiking
Routing obstacles and other conditions requiring special consideration
- crossing=* - pedestrian or other crossing, slowdown
Discontinued Routing Engines
- Main article: Discontinued Routing Engines
The following mailing lists are relevant to routing
- osm-routing 'Discussion about Routing with vector Data. Especially concerning OSM Data' Note that it is nearly inactive, it is likely that osm-talk or osm-dev will be preferable for most topics.
- osm-accessibility For all kinds of disabilities this concerns the proposal and use of tags that are of special interest for disabled persons. Special maps shall be created with this data.
- OSM tags for routing - What data is stored in OpenStreetMap that you can use when routing?
- CartoType, cartotype.com
- Rollstuhlfahrer-Routing - German project for wheelchair routing (now wheelchair routing has been improved and integrated into https://openrouteservice.org)
- Routing problems - Are there any problems that can't be solved using least-cost routing? Do we have any suggestions for solving those problems?
- Routing profiles - Which categories of people want to generate routes, and what are their specific needs? What weights should we use when a 'horse who's scared of traffic lights but likes walking in the forest' asks for a route? How do we choose the best route for a cyclist with slick tires and no lights at night?
- Sample driving instructions
- TIGER fixup - Fixing routing in the U.S. Starting with basic interstate routes: TIGER fixup/250 cities
- Train routing- How can we do routing on public transport networks, and other scheduled services?
- Guidelines for pedestrian navigation - How to map roads, footways etc. so that accurate and realistic pedestrian routes can be produced
- LoroDux - Pedestrian routing for mobile devices for the blind
- Taxi to... - a funny approach to long-distance routing comparison
- Video: Google Tech Talk - Peter Sanders - Fast Route Planning
- Leaflet Routing Machine