> ## Documentation Index
> Fetch the complete documentation index at: https://docu.truemetrics.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Last Meter Visualisation and Routing

> Five ways to bring parking places, entrances and walk paths to your couriers: from data in your own map to a drop-in replacement for Google Maps.

## The main idea

Most navigation apps can only navigate to a generic coordinate. They do not know where couriers
really park, which door they really use, or how they walk from one to the other. That is the **last meter**, and it is where
couriers lose time searching.

truemetrics learns the last meter from your couriers' own deliveries (recorded by the
[truemetrics SDK](https://docu.truemetrics.cloud/with_agent.md), keyed by the address IDs you send as [metadata](https://docu.truemetrics.cloud/metadata.md)). For
every stop it knows:

* **Waypoint:** where the approach leaves the street. A navigation should route here, not to the address pin.
* **Parking:** where couriers really park, reached from the waypoint.
* **Entrance:** the door that is really used.
* **Walk path:** the way on foot from the parking to the entrance.
* **Building:** the building the entrance belongs to.

## Five ways to use it

You decide how the last meter reaches the courier: as data in your own map (option 1), or with the
truemetrics last meter module inside your app, which brings the map, the routing and the best
practices with it (option 2), or with the truemetrics standalone navigation app instead of Google
Maps or Waze (option 3).

![Diagram of the options: 1A export to your backend, 1B REST API, 2 module in your app with point-to-point navigation off or on, 3 standalone navigation app with app switch](https://mintcdn.com/truemetrics-18/6N6gbkxH4WLMTMIN/images/lastmeter/options_overview.svg?fit=max\&auto=format\&n=6N6gbkxH4WLMTMIN\&q=85\&s=f781203fa32234beab4fea595681d4fe)

Where the last meter comes from, and who draws it

> [card] [1A · Your map, data from your backend](https://docu.truemetrics.cloud/Introduction_to_lastmeter_visualisation.md#1a-data-from-your-own-backend)
>
> truemetrics exports parking places, entrances, waypoints and walk paths to your backend. Your
> backend hands them to the courier app with the tour, your map draws them.

> [card] [1B · Your map, data from the REST API](https://docu.truemetrics.cloud/Introduction_to_lastmeter_visualisation.md#1b-data-from-the-truemetrics-rest-api)
>
> Your app asks the truemetrics REST API per stop and gets ready-styled GeoJSON (or a PNG) for
> your own map.

> [card] [2 · Module in your app](https://docu.truemetrics.cloud/navigation_module.md)
>
> The truemetrics module shows the stop's last meter and the courier's position inside your app.
> Point-to-point navigation can be off (your navigation stays as it is) or on (turn-by-turn to the
> waypoint, into the parking, arrival at the door): one flag, `routing`.

> [card] [3 · Standalone navigation app](https://docu.truemetrics.cloud/navigation_app.md)
>
> The truemetrics standalone navigation app replaces Google Maps or Waze. Your courier app sends
> the stop as it does to Google Maps and gets the courier back on arrival.

## Comparison

<table>
  <thead>
    <tr>
      <th />

      <th>**1A** own map, own backend</th>
      <th>**1B** own map, REST API</th>
      <th>**2** module in your app</th>
      <th>**3** standalone app</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>**Integration effort**</td>
      <td>●●●●●</td>
      <td>●●●●○</td>
      <td>●●○○○</td>
      <td>●○○○○</td>
    </tr>

    <tr>
      <td>**You build**</td>
      <td>Import, delivery to devices, map, styling</td>
      <td>Map, styling, one request per stop</td>
      <td>A place in your screen</td>
      <td>Extras on your Google Maps call</td>
    </tr>

    <tr>
      <td>**Best practices**</td>
      <td>Yours to implement</td>
      <td>Yours to implement; styling hints included</td>
      <td>Built in; with navigation on, plus routing to the parking</td>
      <td>Built in, plus the way back</td>
    </tr>

    <tr>
      <td>**Routing**</td>
      <td>Your own</td>
      <td>Your own</td>
      <td>Off: your own\
      On: truemetrics routing\*</td>
      <td>truemetrics routing\*</td>
    </tr>

    <tr>
      <td>**Flexibility**</td>
      <td>Full</td>
      <td>Full</td>
      <td>Your screen, truemetrics map</td>
      <td>None</td>
    </tr>

    <tr>
      <td>**Control**</td>
      <td>●●●●●</td>
      <td>●●●●○</td>
      <td>Off: ●●●○○\
      On: ●●○○○</td>
      <td>●●○○○</td>
    </tr>

    <tr>
      <td>**Platforms**</td>
      <td>Any</td>
      <td>Any</td>
      <td>Android</td>
      <td>Android</td>
    </tr>
  </tbody>
</table>

\* Optionally with your own routing server.

**Integration effort**: what it takes to get the last meter in front of the courier. **Flexibility**:
how freely you shape the look and the flow. **Control**: how much of the data and the logic lives in
your own systems: with 1A a full copy of the data is yours and nothing is asked of truemetrics at
delivery time; with 2 (navigation on) and 3 the drive itself runs in truemetrics software, as it runs in Google
Maps today.

### Which one fits

* **You keep your navigation** (Google Maps, HERE, your own) and your own map, with full control
  over data and design: **1A**, if your backend already distributes tours to the devices; **1B**,
  if the app may ask truemetrics directly.
* **You want the last meter shown the way couriers read it best, inside your own app, with little
  work**: **2**. Point-to-point navigation off, next to the navigation you have; on, navigation
  made for the last meter inside your app.
* **Your couriers drive with Google Maps or Waze today**: **3**. The fewest changes, and the
  courier gets routing to the parking, the walk to the entrance and the way back to your app.

Options can be combined: for example 1B in a dispatcher dashboard and 3 on the courier phones.

## What every option needs

**1. truemetrics SDK in your courier app**

The last meter is learned from your own deliveries: record with the truemetrics SDK and send one
metadata event per delivery with a stable `address_id`. See [Integrate with an AI agent](https://docu.truemetrics.cloud/with_agent.md).

**2. An API key**

Your truemetrics contact issues it and enables it for the options you use. It scopes all data to
your account.

**3. Your stop identifiers**

Each stop is looked up by the `address_id` you send as metadata: typically your address
identifier or route point identifier.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.