Every page of CityMap3D, the 3D OpenStreetMap map library
The complete list of the site's pages, organised by section.
- From an OpenStreetMap row to a shaded pixel
Spherical cells instead of a Mercator grid, real geometry at every zoom with no raster fallback, a sky computed from your date and place, and a composable shader chain. How CityMap3D turns OpenStreetMap into a 3D globe.
- OpenStreetMap as a 3D globe, not a flat map
No Mercator, no projection distortion, no broken poles. One continuous camera from a doorstep to orbit, on a world that is a real sphere at every scale.
- The map updates itself no refresh
A tile that does not exist yet answers 202, not an error. The client subscribes over WebSocket and the tile lands in the running scene the moment it is ready. No polling, no refresh.
- Restyle the map at runtime, no rebuild
Colour is decided at draw time, not baked into tiles. Set a palette while the scene runs and it reaches every pixel, at every distance, including the sky.
- OpenStreetMap as a 3D globe, not a flat map
- Canvas, scene and camera: what you actually plug in
Give the engine a canvas and a configuration. Replace the camera, drop in your own 3D objects, re-tone the whole output to your palette, and get frame-synced screen positions for your own data.
- What CityMap3D sends, and what it does not
Your points stay in the browser. What travels is the region on screen. One hostname, no third-party calls, infrastructure in the European Union, and a network panel you can check it in.
- What CityMap3D sends, and what it does not
- Which OpenStreetMap tags become 3D geometry
Building heights and levels, ground cover, trees and street lamps placed one by one, named places. The OpenStreetMap tags the pipeline reads, and what each one becomes on screen.