Does MapToNap convert OSM directly to 3D?
It uses OpenStreetMap for mapped site context and builds 3D geometry from that data. Terrain, when enabled, uses a separate regional elevation source.
Home / OpenStreetMap to 3D
OpenStreetMap to 3D
Turn OpenStreetMap context into an architecture-ready 3D model
MapToNap reads the real site from OpenStreetMap, combines it with regional elevation data when terrain is enabled, and builds editable 3D context in the browser. Export the result as Rhino 3DM, OBJ or GLB.
OpenStreetMap contextRegional elevation terrain3DM · OBJ · GLB
Data pipeline
What comes from where
OpenStreetMap
Buildings, roads and paths, water, green areas and mapped tree/context information come from open map data.
Elevation data
Terrain is generated from regional elevation data rather than from OSM building tags.
Rule-based geometry
The result is generated as model geometry, not as an AI image or a textured satellite reconstruction.
From OSM to model
No QGIS setup required for the basic workflow
Search the site
Find the real project location in the browser.
Choose layers and area
Keep only the context layers and extent that matter.
Export to your 3D tool
Download 3DM, OBJ or GLB and continue in the software you already use.
Use the same source twice
3D model + analytical drawings
3D context
Use the site model for massing, urban context and presentation.
39 analysis diagrams
Use the same real location for roads, land use, density, green/water, climate, topography and accessibility diagrams.
Traceable source
Keep OpenStreetMap attribution on map-based outputs and treat the geometry as context rather than verified survey data.
Frequently asked questions
What to know before you export
Do I need QGIS or an OSM download first?
No. The normal workflow starts from an address or location directly in the browser.
What 3D formats can I export?
Rhino 3DM, OBJ and GLB.
Are OSM building heights always available?
No. When height or floor-count tags are missing, MapToNap may estimate building height. The model is intended for architectural context, not survey work.
What attribution is required?
Map-based geometry uses OpenStreetMap data, so keep the OpenStreetMap attribution on relevant project outputs.
Related workflows