【實用交通運輸app】BRouter Offline Navigation|最夯免費app-綠色工廠好玩App

Configurable, elevation-aware (bike-) Router for OFFLINE Navigation based on Open-Street-Map ( OSM) Data. Works in conjunction with a (OSM-) Map Application, e.g. OsmAnd, Locus-Maps or Oruxmaps.

See http://brouter.de/brouter for more documenation

See http://brouter.de/brouter-web for an online version.

*** If you do not know one of OsmAnd, Locus-Maps or Oruxmaps, then the BRouter-App is useless for you. Download only if you are willing to spend some time to understand the setup. No one-star reviews from the unpatient please! email for problems ***

BRouter does only the plain route-calculation and does not display a map or the calculated route on it's own and therefore works only together with a Map Application. There are two different methods for the interfacing between BRouter and the Map application: BRouter offers a service interface that is called by the map application without a need to start the BRouter-App. This way, BRouter is a routing service very much like an online routing service, including dynamic recalculations if you get off the track. The other mode of operation is to start the BRouter-App and use waypoints from the map application's waypoint database to define your route. The calculated route is then written as a GPX file (including the elevation profile) to the map-application's tracks directory.

Locus and Oruxmaps support both the service interface and the interface via the wayoint database in their current versions available on Google Play. OsmAnd supports the service interface starting from version 1.7, while the waypoint interface is supported in older revisions as well.

The service interface uses a timeout of 60s, limiting it's use to distances of about 50km, but using the BRouter App you are able to calculate much longer distances. But even long-distance tracks can be followed via the service interface (including dynamic recalculations). This is done by pre-calculating a route for your destination once using the BRouter App and assigning it to a routing mode via the "Server-Mode" Button. This feature is called "timeout-free recalculations".

The route calculation, no matter if via the service interface or via the BRouter App, also considers nogo areas that can be defined as waypoints with a special naming convention (e.g. "nogo200" for 200m radius). This way it is possible to account for actual obstacles, but this feature can also be used to enforce personal preferences.

The Google-Play Version of BRouter contains a download manager that assists downloading the required routing data files.The download manager is called on the first start of the app, and later on it is offered if internet access is available. If you do not want to allow internet access (that is needed by download manager only), you can use the pure offline APK from the distribution ZIP from the project homepage.

The mapping from one of the 6 routing modes (car/bike/foot * fast/short), that are used traditionally by routing services, and BRouter's concept of fully configurable routing profiles get's the following default mapping after the installation of BRouter:

car-fast -> car-test

car-short -> moped

bike-fast -> fastbike

bike-short -> trekking

foot-fast -> shortest

foot-short -> shortest

This mapping, however, can by changed anytime via the "Server-Mode" Button of the BRouter App. But also the routing profile definitions can be changed or new ones can be created.

Routing for cars is is currently available only in an experimental state ("car-test") and is not recommend. For example, turn-restriction are not taken into account. Car routing for longer distances needs the the download of the "carsubset" datafiles, while for bike routing, you only need the normal ("full") routing data files.