From OpenStreetMap Wiki
(Redirected from JA:Routing)
Jump to: navigation, search
利用できる言語 — Routing
· Afrikaans · Alemannisch · aragonés · asturianu · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · Bân-lâm-gú · Basa Jawa · Basa Sunda · Baso Minangkabau · bosanski · brezhoneg · català · čeština · corsu · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · Kurdî · latviešu · Lëtzebuergesch · lietuvių · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk bokmål · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tagalog · Tiếng Việt · Türkçe · Vahcuengh · vèneto · Wolof · Yorùbá · Zazaki · српски / srpski · беларуская · български · қазақша · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · मराठी · हिन्दी · भोजपुरी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · བོད་ཡིག · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ ⵜⴰⵏⴰⵡⴰⵢⵜ‎ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 中文(繁體)‎ · 吴语 · 粵語 · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް
Skobbler Navigation (online turn-by-turn navigation app for iOS).

経路探索(ルーティング、ナビゲーション)サービスは人々がある場所から別の場所へたどり着くのを手助けしてくれます。 OpenStreetMap データは車、徒歩、自転車及び乗馬といった多くのモードで経路探索のための情報を含んでいます。 OpenStreetMap データを使っている多くのオフライン、組み込み型及びWebベースの経路探索サービスがあります。

このページでは、開発者向けに新しい経路探索アプリケーションの開発や配布ができるソフトウェアのアドバイスや、経路探索エンジンをより良くするために使われる OpenStreetMap データの詳細なキーを提供しています。数多くのメーリングリストも利用可能です。

エンドユーザー向け: 経路探索ソフトウェア

List of OSM based Services#Routing も参照してください

マッパー向け: 地図データを改良する

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タグ to understand the tags specific to routing.

Fixing bugs with MapDust

Showing how to determine connected and unconnected nodes in Potlatch

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 that thre is 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: ITO World provide a number of services to help identify missing speed limits.

Often maxspeed is meaningless - see #Average speed.


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.


GraphHopper で生成されたローマへの道の画像



  • Traveling salesman という経路探索アプリケーションはユーザインタフェース以外の全ての基本部分で使われている osmNavigation ライブラリを含んでいます。全ての重要な部分はプラグイン経由で交換することができます。
  • OpenTripPlanner site is a multi-modal trip planner supporting OSM data. OTP Deployer makes it easy to deploy your own routing instance.
  • GraphHopper is an open source routing engine for road networks written in Java. Fast and memory efficient (for Android, iOS, desktop and server).
  • BRouter focuses on bike routing and features elevation awareness, alternatives, fully configurable routing profiles and offline routing initially written for Android, but has now also a web api
  • Cruiser は地図と経路探索のアプリケーションです。





  • Mormon ruby version of pyroutelib




  • OsmAnd OSM Map, POI and Routing (car/bike/foot, online&offline) for Android
  • ZANavi Android
  • Navit Linux, Windows and portable devices
  • GraphHopper Open Source routing library for Desktop, Android and iOS.
  • 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
  • Cruiser は地図と経路探索のアプリケーションです。



Libraries focused on OSM Routing can be found at Develop/Frameworks. Here some general libs:

  • DGLib Directed Graph Library は Grassベクターネットワークツールです(最短経路、巡回セールスマン、 isodistances、 Steiner trees、 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.
  • ffwdme.js is a JavaScript toolkit that aims to bring interactive GPS driving directions to the mobile browser.
  • Valhalla is a free, open-source routing service that lets you integrate routing and navigation into a web or mobile application.




The order of values for the highway-tag ordered by assumed speed is:

種別 説明(主に西欧でいえること)
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


道路の車線数は OSM で直接タグ付けされ、平均速度(最短経路)及び燃料消費(最も効率的な経路)に関して大きな影響を持っています。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.

OpenStreetMap において、このモデルは速度に関するデータが無い経路(例: highway=unclassified)にとっては興味深いものになるでしょう。


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.


turning radius=* も参照してください

In some studies about the accessibility [2] 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.


Certain cost should be assumed for:

  • crossing higher-class roads
  • changing to and from lower-class roads
  • u-turns
  • lane changes


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.



- ハイキングを参照



  • crossing=* - 歩行者などの横断歩道、速度が低下



  • osm-routing 'ベクターデータでの経路探索についての議論。特に OSM データに関して'
  • osm-accessibility このMLでは、障害のある人々にとって特に有用な、あらゆる種類のアクセシビリティに関する提案、およびタグの使用法について議論されています。このデータを元に、特別なマップを作成することができるでしょう。