How it works

How a route comes about.

The technical sequence from the search to recalculation on the way.

  1. Download the area

    For your start location the app downloads the path data and the map of the area to the device. This needs a connection once.

  2. Calculate candidates

    The app sets turning points in different directions around the start and calculates routes on the path network from them, on the device.

  3. Check the routes

    A route counts only if it ends at the start and its length is close to the requested length. Safety rules exclude expressways and major through roads.

  4. Selection

    You get up to 5 routes with length and climb. If none meets every criterion, the app shows the closest ones and labels them.

  5. Navigation and recalculation

    During the run the app guides by voice and map. After repeated deviation it calculates a new remaining route back to the start, with reference to the planned distance, also on the device.

Data sources

TapRun builds on open data. e12.media operates the delivery itself.

Path network and map

OpenStreetMap data, processed by e12.media and loaded as tiles from its own servers. The app does not fetch tiles from OpenStreetMap.

Route calculation

The TapRun RoadTile Engine runs on the device. There is no routing server that the app queries for the search.

Elevation

Public elevation models, built into the path data and loaded with it.

Limits

  • Offline applies inside the downloaded area. If you leave it, recalculation is not possible.
  • The size of the downloaded area may change before release.
  • OpenStreetMap is maintained by volunteers. Closures, roadworks and new paths are not always mapped, and missing sidewalks cannot be detected unless they are mapped.
  • The target distance is a guide. The distance you run can differ depending on GPS accuracy.
  • Flat mode prefers flat routes. It does not guarantee them.

Map data © OpenStreetMap contributors (ODbL). Map design based on OpenMapTiles.