Documentation menu

Live demos

Every public demo the site serves, grouped by what it demonstrates: 3D turn-by-turn navigation, analysis over open data, point clouds in the browser, and surface-aware routing from a MapMap Roadside capture. All of them are served by the same self-hosted MapMap stack as the API: vector tiles, routing, guidance and map styling. No Google services are involved at any layer.

Unlisted sales demos, staging-only viewers and anything not on this page are deliberately not enumerated here.

Two live turn-by-turn drives rendered in 3D, plus an instrument-cluster framing for automotive evaluation.

London: /demo/london-3d. Westminster Bridge to Trafalgar Square. Buildings at surveyed LIDAR heights, live TfL bus positions, Thames vessels from AIS, weather that matches the sky.
Manhattan: /demo/manhattan-3d. Columbus Circle to the Chrysler Building, with live MTA buses. Click a bus to overlay its real route.
Cluster: /demo/cluster. The London or Manhattan drive letterboxed to a 12.3 inch instrument cluster (1920 x 720) in a dashboard bezel. This is the automotive door-opener; see /solutions/automotive.

Both drives keep navigating while you interact: drag to look around, scroll to zoom, and use Re-centre to return to the chase camera. The URL parameters and the scene3d theme block below apply to these three pages only.

Analysis over open data

Each of these is the analysis API run over a published dataset and mapped, so the working can be checked against the source.

15-minute access: /demo/access-explorer. How much of Brighton & Hove, York and Cambridge can reach a GP practice main site within 15 minutes on foot, by bike or by car. Open NHS and ONS data through the isochrone API, precomputed.
EV charging gaps: /demo/ev-gaps. Drive-time coverage of every public charge point in East Lindsey, Herefordshire and Stoke-on-Trent, with the share of residents left outside it.
What if the bridge closed?: /demo/scenario. Close Worcester's one city-centre river crossing and watch the routing engine divert six journeys live, with a receipt of what each diversion costs. Or draw your own closure anywhere on the map.
Tallinn surface quality: /demo/tallinn-surface. Every path in Tallinn with a rated surface, and two wheelchair routing engines side by side: one reads the surface quality, one ignores it.

Point clouds

Open-licensed survey point clouds drawn inside a MapMap map by the @mapmap/points SDK. The index at /demo/lidar lists all seven scenes:

Scene	What it is
/demo/lidar/vienna	A 600 m run up Schillgasse in Floridsdorf, from the City of Vienna's Kappazunder mobile-mapping survey.
/demo/lidar/san-francisco	A square kilometre over Chinatown and Nob Hill, from the USGS 3D Elevation Program.
/demo/lidar/tower-bridge	Tower Bridge, the Pool of London and the City cluster behind it, from the Environment Agency's National LIDAR Programme.
/demo/lidar/brighton	Brighton seafront, Palace Pier and the Royal Pavilion quarter, from the same Environment Agency programme.
/demo/lidar/saitama	The Kurazukuri merchant street in Kawagoe, from Saitama Prefecture's open road point cloud.
/demo/lidar/montreal	23.7 million points of downtown Montreal, streamed live from a 233 MB COPC file rather than a baked payload.
/demo/lidar/osaka-kyobashi	A railway viaduct measured over a four-lane street in Osaka, where OpenStreetMap records no height limit.

/demo/vienna is the same Vienna scene on its own route: 5.5 million points on a MapMap basemap, kept because it is the SDK walkthrough the docs and the SDK's own examples link to.

Every scene carries its source's required attribution on the canvas, and no viewer control removes it. Scenes on other licences are not served here.

Roadside

Surface-aware cycle routing: /demo/roadside-cycle. Two bicycle routes between the same points, computed by the routing engine and scored against the surface defects logged by one MapMap Roadside pass through Brighton. The headline is the surface score, not a defect count.

URL parameters

London, Manhattan and the cluster only. All parameters compose.

Parameter	Values	Effect
`time`	`day`, `dusk`, `night`, `dawn`	Light preset. Omit it and the scene follows the real sun at the city's location.
`vehicle`	`truck`	London only. Routes the same endpoints through truck costing with a declared 4.5 m, 18 t vehicle. The engine routes via Victoria Embankment instead of Whitehall, with an HGV chip on the HUD.
`city`	`manhattan`	Cluster only. Swaps the London drive for the Manhattan one.
`embed`	`1`	Cluster only. Strips the page's own bezel and caption so the display fills the viewport, for embedding in an iframe that draws its own frame.
`style`	a hosted style id	Restyles the scene from a MapMap Studio style: the building palette slot tints the facades, and water, park, sky and road colours recolour the basemap. If the theme carries an explicit `extra.scene3d` block (below), its values apply on top of the derived colours.
`lit`	`0` to `3`	Multiplies the fraction of lit windows after dark.
`warmth`	`0.7` to `1.3`	Shifts the lit-window colour temperature, cool to sodium.

Examples:

text

/demo/cluster?city=manhattan&time=night
/demo/cluster?vehicle=truck&time=dusk
/demo/london-3d?time=day&style=<your-style-id>

The scene3d theme block

A hosted theme's extra.scene3d object gives a style explicit control of the 3D scene, beyond what the palette derivation infers. All fields are optional and validated individually; a malformed field is ignored rather than breaking the drive. URL parameters win over the block.

json

{
  "extra": {
    "scene3d": {
      "wallTint": "#8a4b3c",
      "lightPreset": "dusk",
      "lit": 1.6,
      "warmth": 1.15
    }
  }
}

Field	Type	Effect
`wallTint`	`#rrggbb`	Mixed into every facade family's wall colour (overrides the building palette slot).
`lightPreset`	`day`, `dusk`, `night`, `dawn`	Carried with the theme for Studio; scene re-timing from it is in progress.
`lit`	number, 0 to 3	Multiplies the lit-window fraction after dark.
`warmth`	number, 0.7 to 1.3	Lit-window colour temperature, cool to sodium.

The block rides the theme document's opaque extra field, so it works on every existing gateway version and never affects compiled MapLibre output.

What the demos are, honestly

The 3D drives: one scripted corridor per city, not a product surface: the rest of the planet renders as the standard map. The buses and vessels are only ever real vehicles from live feeds; when an upstream feed is down, they are absent rather than simulated. The truck route is baked from the engine's own truck-costing response; the keyless demo proxy the website uses speaks car costing only.

The analysis demos: the isochrones are precomputed, not recomputed per visitor, so a demo shows the state of the network on the day it was baked rather than today's. The scenario demo is the exception: closures you draw are routed live.

The point clouds: each one is a dated third-party survey, published under its own open licence, rendered as captured. Nothing is inferred, filled in or smoothed, and a scene proves what the survey saw on its own date and nothing about the same street now.

The Roadside demo: one capture pass through one city. It shows what a surface-aware cost function does to a route, not a survey of Brighton.

The same routing is available at POST /route with costing: "truck" and costing_options.truck dimensions; see the API reference.
The isochrones behind the analysis demos are POST /isochrone; see analysis APIs.
Scene restyling comes from MapMap Studio hosted styles.
The cluster framing and the automotive pitch live at /solutions/automotive.