🗺️ Apple Maps

Places and routes, as a mesh node. With the instance's MapKit key — team id, key id, the .p8, set by an administrator in Administration › Maps — the page becomes Apple Maps: search anything, read the coordinates, and plan a route between two places.

What you get

Place search names, POIs and addresses through /v1/search, with formatted addresses, coordinates to five decimals and Apple's POI categories
Directions set From and To (free text or lat,lon) and the first route renders with distance and duration
Geocoding the model speaks /v1/geocode and /v1/reverseGeocode too — the same parser covers all three, ready for other plugins to call
Honest failure a bad key, a key without MapKit JS, a rate limit, an expired access token — each renders a diagnosis naming exactly what to check

What it needs

An Apple Developer Program membership: an administrator creates a key with MapKit JS enabled and enters its three pieces (team id, key id, the .p8 text) once, in Administration › Maps — people do not enter a key of their own. The mesh signs a short-lived ES256 auth token from it server-side and exchanges it for Apple's access token, per fetch — the key itself never travels.

Nothing is installed into your space and there is no personal setup: once the instance's key is set in Administration › Maps, the Apple Maps page works for everyone who has access. Full details in the guide.

Reconnecting…
The connection to the server was interrupted. Trying to restore it…
Trying again…
The connection could not be restored. Reloading the page…
The server was updated. Reloading the page to pick up the latest version.