Example gallery
Each recipe runs live at the top of its own page, above the code that drew it. Copy the fence and it compiles.
Start with Render a map if nothing is installed yet. Every recipe links the guide behind it, so the longer explanation is one click away.
Put a map on the page
Render a map
A client, a terrain, a camera.
Open the map on your own style
Skip the terrain manifest entirely.
Add the control stack
Zoom, compass, geolocation, three panels.
Add a place search box
A live search bar in the stack.
Open street view from the map
Drag a handle onto a road.
Let readers switch terrain
The base map and overlay picker.
Expose unit and language preferences
Units, slope, temperature, language.
Show an itinerary
Show an elevation profile
An id, a client, a curve.
Sync an elevation profile with a map
Scrub the chart, move the marker.
List an itinerary's segments
Every leg, in the shipped columns.
Highlight a segment on the map
Hover a row, light a leg.
List segments without a table
The studio's own segment rows.
List an itinerary's waypoints
Distance, elevation, services.
Build a race course page
Cut-off times and a service filter.
List waypoints without a table
The studio's own waypoint rows.
Show a waypoint card
One place, fully stated.
Draw your own waypoint card
The same facts, your markup.
Build an editor
Put studio chrome over a map
The studio's lists beside the route.
Assemble a full studio
One tool bus under every surface.
Run a whole application
A recipe is one composition. The SDK's repository also holds whole applications under examples/, and its README says what each one shows. Each of those listed here is built by a real bundler or run by node, and quoted by a package README byte for byte.
Each of the listed applications is also installed outside the repository, from the install line its package's README states, then built and type-checked there. An install line that brings too little fails that check before it reaches you.