Hosted Photon geocoding for Reitti
Reitti is a self-hosted location history and timeline app with first-class support for Photon. ChibiGeo is a hosted Photon endpoint — flat-rate, EU-only, hard-capped — that Reitti's Photon provider talks to natively.
Reitti's Photon service doesn't have a separate API-key field, so you carry your ChibiGeo key in the base URL as a path segment. That's all it takes — no Reitti changes, no patched build.
Prerequisites
- A running Reitti instance.
- A ChibiGeo API key (
ck_…). The Self-Hoster plan (€9.99/mo) covers supported self-hosted apps like Reitti. Get one at app.chibigeo.com.
Configuration
In Reitti: Settings → Geocoding → Add service, choose type Photon, and set:
| Field | Value |
|---|---|
| Service Name | ChibiGeo |
| URL / Base URL | https://app.chibigeo.com/v1/photon/ck_your_key_here |
| Limit (optional) | 10 |
| Search Distance / radius (optional) | 1 |
Note the key is part of the base URL. Reitti builds each request as
{base_url}/reverse?lon={lng}&lat={lat}&layer=house&layer=locality, so with the
key in the path it sends:
GET https://app.chibigeo.com/v1/photon/ck_your_key_here/reverse?lon=…&lat=…&layer=house&layer=locality
ChibiGeo reads the key from the path, authenticates, and returns the address.
Every parameter Reitti sends (lon, lat, layer, radius, limit) is on
ChibiGeo's allowlist.
Verifying it works
Use the geocoding service's Test button in Reitti — it calls the same path. Or check from a shell:
curl "https://app.chibigeo.com/v1/photon/ck_your_key_here/reverse?lon=13.377&lat=52.516&layer=house&layer=locality&limit=10"
You should get a GeoJSON FeatureCollection with populated properties
(name, city, country). Then run a geocode pass over your places in Reitti.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
401 invalid_api_key | Wrong key in the base URL | Re-copy the key; ensure the base URL is …/v1/photon/<key> |
401 missing_api_key | Key segment missing | The base URL must include /v1/photon/<key>, not just /v1/photon |
429 | Monthly cap reached | ChibiGeo hard-caps rather than billing overage — raise the plan |
| Places stay unnamed | Photon provider not primary/enabled | Enable the service and run a geocode pass |
Why ChibiGeo
- vs
photon.komoot.io: a real cap and rate limit you can rely on, EU-only hosting, a status page. See photon.komoot.io rate limits. - vs self-hosting Photon: no ~95 GB planet index, no 64 GB RAM. See what it takes to self-host Photon.