navi-server

Pre-built routing packs for the Navi navigation app — graph, POI, wetland/hazard, and elevation-aware costing — derived from OpenStreetMap extracts. This host is not a general map-tile or basemap server.

What you get

Each published region is a set of binary packs plus JSON manifests that Navi can download and use for offline routing. Content includes routing geometry (profiles such as car / truck / foot / bicycle), named POIs and barrier data, and wetland/hazard rings used in costing — not a Protomaps-style labeled-region or park-boundary basemap layer.

Format details live in the repo: docs/pack-formats.md (graph / POI-barrier / wetland archives and magic bytes).

URL layout

Packs are nested under Geofabrik download paths — the same continent/country/region hierarchy the Navi app uses in its download menu (for example europe/norway/vestlandet or north-america/us/west-virginia). 

GET /current.json
GET /packs/<geofabrik-path>/<generation>/manifest.json
GET /packs/<geofabrik-path>/<generation>/<stem>.navi-manifest.json
GET /packs/<geofabrik-path>/<generation>/<stem>.navi-graph-*.rkyv
GET /packs/<geofabrik-path>/<generation>/<stem>.navi-poi-barrier.rkyv
GET /packs/<geofabrik-path>/<generation>/<stem>.navi-wetland*.rkyv

Start at /current.json for the live catalog (generation id and per-region manifest_url). Then fetch that region’s manifest.json and the files it lists (sha256 digests included). The convert-style <stem>-latest.navi-manifest.json sits beside those packs in the same generation folder.

How to fetch a region

  1. GET /current.json and pick a region entry.
  2. GET its manifest_url (under /packs/…/).
  3. Download each file named in the manifest; verify sha256.

Clients use ordinary HTTP GET/HEAD only — no auth handshake and no upload API on this vhost. Full contract: docs/client-fetch.md in the navi-server repository.

Update cadence

Packs are baked periodically, not live. A production weekly timer can refresh configured regions (for example smoke / Hedmark-style pipelines) when operators enable it. Wider planet leaf builds are occasional full-tree runs, not a continuously refreshed feed. Treat freshness as “last successful bake,” not real-time OSM.

Optional DATEX (Norway)

This host may also cache NPRA DATEX II snapshots under /datex/ for Navi clients. That feature is off by default, separate from routing packs, and holds credentials only on the server. See docs/datex-npra.md in the repository.