The Streets basemap with the ground under it: shaded relief, contour lines with their heights, and 3D terrain, worldwide. The map is touring the Alpe d'Huez by itself; drag it to take over.
Nobody ships a terrain tileset. They ship a route planner where the col is visibly a col, a trail page with the ridge in relief, a ride card that tilts into the valley. This is what Outdoor looks like from the outside.
Streets and Outdoor are one basemap; Outdoor adds shaded relief and contour lines from worldwide elevation data. The valley, the hairpins and the ridge appear without a single extra request from your side.
Real roofs on the same map
© OpenStreetMap contributorsThe lines are computed from the elevation tiles on the visitor's machine, so they stay crisp at every zoom, carry their heights, and follow the terrain when the camera tilts into 3D.
The same data, as an APIOne map session, the terrain switched on
same session as Streets
same monthly pool
Terrain rides in the same map session as the basemap. Turn on hillshade, contours and 3D and the session is still one unit; only a call to the Elevation API is its own.
See what a month costsimport { Map, MapStyle } from '@rijwind/sdk'; const map = new Map({ container: 'map', style: MapStyle.OUTDOOR, // relief + contour lines center: [6.05, 45.07], zoom: 13, }); map.setTerrain3D(true); // same session, same unit
The SDK turns on relief and contours with the style, and 3D with one call. Bring your own MapLibre instead and the docs carry the manual terrain and contour setup.
Read the styles guideOpening any map issues one short-lived session, and it signs the elevation archive alongside the basemap. Outdoor just uses it. Switch from Streets to Outdoor, tilt into 3D: same session, same unit.
Everything a developer scans a product page for, in one place, without the adjectives.
Numbers as of September 2026. The pricing page has the full ladder.
The Streets basemap with terrain on top: shaded relief that shows the shape of the land, contour lines with their heights, and optional 3D so the camera can tilt into a valley. Same roads, water, places and labels as Streets, so nothing you built on Streets changes.
Cycling and hiking apps, route planners that want the climb visible before the ride, trail and park websites, outdoor gear brands, ski and mountain-bike resorts, and any product where the ground matters more than the street grid.
Like every style: one unit per map session. Terrain rides in the same session as the basemap, so relief, contours and 3D add nothing. Ten thousand sessions a month are free; paid plans start at five euros.
They are computed in the visitor's browser from the same elevation tiles that shade the relief, rather than pre-drawn as a tileset. That is why they stay sharp at any zoom, carry height labels, and drape correctly over 3D terrain. It also means they need a browser with WebGL, like the rest of the map.
Worldwide elevation on a grid of about 30 metres. Mountains, valleys, ridges and rolling hills read clearly; a single embankment or a cutting narrower than the grid is smoothed. Finer national elevation data, down to a metre in some countries, is planned but not in yet.
Yes. The Elevation API samples the same terrain for points or along a route, so a profile chart under the map matches the relief on it. That is a separate request and costs one unit per call.
Outdoor is relief and contours on the street basemap, not a full topographic map yet. There are no ski pistes, lifts, or hiking and cycling route networks drawn as layers, and no surface colouring for paths. Those are on the list, but do not buy this page expecting them today.
No. The SDK sets the style and 3D with one option and one call. With your own MapLibre you add the terrain source, the hillshade layer and the contour generator yourself; the docs carry the exact setup, and it is a few dozen lines.
Yes. The free plan includes 10,000 units a month with no card and no sales call, which is 10,000 map sessions if that is all you spend them on. It is a hard cap, so a traffic spike cannot produce a bill.
Tiles, terrain included, come from a European CDN and the session is issued from the European Union, end to end. No part of the path touches a US-controlled provider. We publish a DPA and a full sub-processor list.
The basemap underneath, in five colour variants.
The same terrain as numbers: points and route profiles.
Bike and foot routes to draw on the relief.
Imagery worldwide, aerial photography at street zoom.
One unit pool, one table, a cap you set.
Sessions, units and where the data lives.
Ten thousand sessions a month, free. The same key covers search, routing and elevation when you get to them.