mapmap.ai

MapMap: a self-hosted multi-modal routing platform — cars, trucks (with first-class ADR dangerous-goods support), bicycles, pedestrians and motor scooters. Tools: `route` computes turn-by-turn routes (costing "auto", "truck", "bicycle", "pedestrian" or "motor_scooter" — pass a `truck` profile with dimensions and the ADR declaration to apply dimensional and hazmat restrictions to the search (see `applied_adr.tunnel_enforcement` for what a returned route does and does not prove), `pedestrian` options for lit-street preference, wheelchair/blind profiles and hiking difficulty, or `bicycle` options for bicycle type and road/surface/hill preferences; every one of these costings accepts `rationale: true` for an honest why-this-route explanation derived by route divergence); `search_along_route` finds POIs along a route with each one's real engine-computed detour cost ("coffee, adds 4 min"); `cheapest_fuel_along_route` ranks fuel stations along a route cheapest-first from live open-data price feeds (UK, FR, DE) with engine-computed detours, a 24-hour staleness flag and the saving vs the cheapest on-route baseline; `nearby_places` finds places near a point by category — cafes, fuel, EV charging, parking, pharmacies — and/or by name or brand ("the nearest Lloyds bank"), nearest first with distance in metres; both `nearby_places` and `reverse_geocode` can answer egocentrically — pass `heading_deg` (and optionally `fov_deg`) and every result carries a `direction` phrased from where the user is standing ("ahead and slightly to your right, about 80 metres"), which is what a voice or wearable client should read out instead of coordinates; `route` also takes `landmarks: true` for turn instructions anchored to recognisable places ("Turn right just after the Shell garage") alongside the engine's own, which is what a driver or a voice client actually navigates by; `plan_day` turns an itinerary (names or coordinates, dwell times, optional optimisation) into one navigable multi-stop route with per-stop ETAs; `check_adr_tunnel` answers whether a dangerous-goods load may pass a tunnel of a given ADR category (pure ADR 8.6.4 lookup, no network, conservative worst-case reading); `check_clearance_on_route` measures a vehicle's overhead clearance along a route against surveyed point cloud geometry, returning pass, fail, indeterminate or no_verdict with the limiting point, its measured headroom, the uncertainty bound on it and a link to that view. Read the honesty carefully on that one: it measures physical geometry from a dated survey, it is never a signed or posted height, and ground the survey did not cover comes back as `not_surveyed_m` and is never judged, so a pass is possible over complete coverage and nowhere else. It is the measured counterpart to the routing answer, which avoids what the map has tagged and nothing more, so reach for it whenever an unchanged truck route is about to be read as a clearance (the mapmap://guide/clearance resource sets out why those are two different claims); `geocode` turns place names into coordinates; `reverse_geocode` turns coordinates into the nearest places (addresses, POIs and localities, nearest first, with distance in metres and POI opening hours/contact details where known); `matrix` computes many-to-many travel time/distance matrices in any costing; `reachable_area` computes isochrones — walkability/cyclability rings — as GeoJSON; `optimise_routes` solves multi-vehicle, multi-stop route optimisation (VRP: vehicles with capacities/skills/time windows, jobs and pickup-delivery shipments) — the travel-time matrix is computed by our routing engine, so passing costing "truck" with a `truck` profile makes the whole plan respect dimensional and ADR dangerous-goods restrictions. Map styling (MapMap Studio): `list_style_layers` lists the themable palette slots, skeleton layer ids and source-layers (local, always works); `create_style` publishes a new hosted style; `get_style` fetches a style's theme and latest style URL; `set_palette` and `set_layer_paint` publish a new immutable style version with recoloured palette slots or a changed layer paint property. Attribution is enforced on every compiled style. Feedback: `report_map_issue` queues a first-party map/live-world mismatch observation for human review (never edits the map); `submit_integration_retro` sends MapMap a structured integration retro — only the schema's structured fields, never conversation or code — to be called at most once, after an integration works or is abandoned, and only if the developer has approved sending feedback. Coordinates are WGS84 decimal degrees; distances are metres and durations seconds unless a field name says otherwise.