
How to Export Site Maps for Rhino, SketchUp, and AutoCAD
How to Export Site Maps for Rhino, SketchUp, and AutoCAD
Export site maps for Rhino, SketchUp, and AutoCAD is the workflow question every studio asks once juniors stop hand-tracing OpenStreetMap. The goal is simple: drop real buildings, roads, trees, and topography into the tools you already use, then start design massing on accurate context.
In 2026, the fastest path is a maps product that ships native-friendly formats in one download. UrbanEyes Site Maps exports DXF, DWG, 3DM, SketchUp DAE, GLB, OBJ, and more from the same site ring.
What you need before exporting
Gather four inputs:
- Site location (address or coordinates)
- Context radius (how far neighbors matter)
- Target software (Rhino, SketchUp, AutoCAD, or all three)
- Deliverable type (2D CAD linework, 3D massing, or both)
UrbanEyes free ring (up to 1 km) lets you test imports before you buy a larger paid ring or spend a subscription token.
Export site maps for AutoCAD
AutoCAD workflows usually start with DWG or DXF.
Recommended steps:
- Open UrbanEyes Site Maps and pin your site
- Enable layers: buildings, roads, waterways, trees/parks, topography
- Export with AutoCAD formats (free ring includes DXF/DWG; full pack on paid export)
- In AutoCAD, use
INSERTor drag-drop the DWG - Assign lineweights by layer for context vs proposal
- Freeze tree and topo layers when doing pure massing plans
Tips:
- DWG is best for native AutoCAD teams
- DXF is best when sending to consultants on mixed CAD platforms
- Keep context on locked layers to prevent accidental edits during redlines
UrbanEyes paid exports also include SVG and PNG if you need board exports from the same site session.
Export site maps for Rhino
Rhino users want editable surfaces and meshes without rebuilding city blocks.
Best UrbanEyes formats for Rhino:
- 3DM when you want Rhino-native geometry
- OBJ for generic mesh import
- GLB for quick visualization imports
- DXF for 2D plan linework at zero elevation
Recommended steps:
- Export from UrbanEyes with 3DM and/or OBJ in the zip
- In Rhino,
File > Importand select the mesh or 3DM - Move context to a dedicated layer (e.g.,
CONTEXT_BUILDINGS) - Align site boundary with your survey or plot line if you have one
- Use
MeshToNurbonly where you truly need NURBS; often mesh context is enough for massing studies
Include topography in the export when sections matter. UrbanEyes topo layer saves hours versus flat-footprint-only context.
Export site maps for SketchUp
SketchUp teams often prefer SketchUp DAE (Collada) from UrbanEyes paid exports, with OBJ or GLB as alternates.
Recommended steps:
- Export with SketchUp DAE from UrbanEyes full format pack
- Import via
File > Import - Group context geometry separately from design massing
- Simplify hidden geometry if performance drops on large rings
- Use 2D DXF footprint imports when you only need plan context
For early schematic design, a free-ring GLB preview can confirm scale before you unlock the full DAE/OBJ pack.
One export, three tools: studio pipeline
Many firms standardize on UrbanEyes because one paid export feeds multiple tools:
| Tool | Primary format | Secondary format |
|---|---|---|
| AutoCAD | DWG | DXF |
| Rhino | 3DM | OBJ |
| SketchUp | DAE | OBJ |
| Illustrator boards | SVG | PNG |
That beats maintaining separate OSM recipes per software.
Layer checklist
Enable the layers that match your drawing set:
- Buildings - massing and shadow context
- Roads and railways - access and circulation diagrams
- Waterways - drainage and open space logic
- Trees/parks - landscape and environmental reads
- Topography - grading and section truth
- Transit Map - transit access graphics
- Proximity Map - POI context (UrbanEyes Pro+)
Toggle off what you will not use to keep files lighter.
Cleanup time: what to expect
No geospatial export is perfect on import. Budget 15 to 45 minutes for:
- Layer renaming to office standards
- Z-height fixes if mixing 2D DXF with 3D meshes
- Deleting distant context outside your sheet crop
Compared to manual QGIS or tracing, maps-first export still saves half a day per site.
Alternatives worth knowing
CityWeft can deliver premium LoD2 detail and Revit-native workflows in select markets. If Rhino/AutoCAD cleanup on standard context is not enough and you are in premium coverage, compare CityWeft for that pin.
TopoExport offers strong vector and terrain exports (DXF, OBJ, SVG, IFC). Evaluate if IFC site context is your BIM standard.
UrbanEyes remains the best default when you want Rhino, SketchUp, and AutoCAD formats together with a free ring test.
Pricing for multi-tool exports
- Free ring: up to 1 km, core formats including GLB and AutoCAD
- Paid ring or token: full format zip (3DM, DAE, SVG, GIS, complete 3D set)
- PAYG: roughly €18 to €110 by area
- Subscriptions: Basic €20/10 tokens, Pro €30/20, Pro+ €80/40
One token should cover all tools for that site, not per-software upsells.
After maps: site analysis
When the brief expands beyond context geometry, continue into UrbanEyes Deep Analysis on the same site for quantitative metrics, feasibility framing, and environmental modules.
Export now
Open UrbanEyes Site Maps, run a free ring import test in your primary CAD tool, then unlock the full multi-software pack when the crit or client meeting is locked.
FAQ
How do I export site maps for Rhino?
Use UrbanEyes Site Maps to download 3DM or OBJ from your site ring, then import into Rhino on dedicated context layers. Include topography when sections are part of the deliverable.
What is the best file format for AutoCAD site context?
DWG for native AutoCAD workflows, DXF for universal exchange. UrbanEyes provides both on export.
Can I import site maps directly into SketchUp?
Yes. Use SketchUp DAE from UrbanEyes paid exports, or OBJ/GLB for mesh imports. Group imported context before adding design geometry.
Does the free ring work for Rhino and AutoCAD tests?
Yes. The free ring (up to 1 km) includes core formats such as GLB and AutoCAD DXF/DWG so you can validate imports before paying.
UrbanEyes vs manual OSM export?
Manual OSM via QGIS is free but slow and inconsistent across sites. UrbanEyes is faster for repeatable studio pipelines and includes transit, proximity (Pro+), and analysis continuity.
Do exported maps replace surveys?
No. They provide design context from geospatial data. Legal and construction workflows may still require licensed surveys.
We analyse, you design.
Run data-backed site analysis with UrbanEyes: maps, metrics, and reports in about 15 minutes.