Topography and Tree Maps for Site Design

Topography and tree maps for site design combine elevation logic with existing vegetation so architects and landscape designers do not treat ground and canopy as afterthoughts. Contours inform access, drainage, and section quality; tree layers inform shade, wind microclimates, and retention of mature canopy during masterplanning.

In 2026 the practical workflow is exporting both layers from one site ring on UrbanEyes Site Maps, then combining them with building and road context in CAD or Rhino.

Why topography maps matter beyond "pretty contours"

Topography maps answer design questions early:

• Where is cut and fill likely expensive?
• Which entries respect grade without long ramps?
• How do sections read against real ground, not a flat assumption?
• Where does surface water prefer to move?

Without topo, studios draw convincing plans on imaginary flat sites - then pay for redesign when reality returns in DD.

UrbanEyes includes a topography layer in standard site maps exports alongside buildings and infrastructure.

Why tree maps matter for architecture and landscape

Tree maps are not decoration. They support:

• Shade and comfort diagrams for public realm
• Existing canopy retention during campus or hospital expansions
• Setback and root zone discussions with landscape consultants
• Visual corridor protection along streets and waterways

UrbanEyes provides trees/parks as a dedicated layer you toggle before export.

Layer stack for site design exports

Recommended UrbanEyes layer combo for landscape-architecture collaboration:

Layer	Design use
Topography	Grading, sections, drainage concept
Trees/parks	Canopy, open space, green infrastructure
Buildings	Massing and shadow context
Roads/railways	Access and noise edges
Waterways	Riparian buffers and flood intuition
Transit Map	Pedestrian connection to stops

On Pro+, add Proximity Map when POI context (schools, healthcare, retail) informs program placement near green networks.

Export formats for topo and trees

Different collaborators need different files from the same export:

• DXF/DWG - topo contours and tree symbols in AutoCAD
• SVG/PNG - board diagrams with styled green and contour linework
• GeoJSON - GIS analysis of slopes or tree counts
• OBJ/3DM/GLB - 3D terrain meshes with massing for Rhino studies

UrbanEyes paid exports bundle these with the full format list: PNG, SVG, GeoJSON, KMZ, DXF, DWG, GLB, glTF, OBJ, STL, PLY, 3DM, SketchUp DAE.

Workflow: from maps to design diagrams

1. Pin site on UrbanEyes Site Maps
2. Set ring: free up to 1 km for studies; paid for campus-scale
3. Enable topography, trees/parks, buildings, roads, waterways
4. Export and import into Rhino or AutoCAD
5. Generate contour + tree diagram for early client read
6. Overlay proposal paths and building pads respecting grade
7. Optional: run UrbanEyes Deep Analysis for environmental narrative beyond static maps

CAD and Rhino tips for topo + trees

AutoCAD:

• Put contours on TOPO_MAJOR and TOPO_MINOR layers if your export allows separation; otherwise filter by elevation labels
• Use tree blocks on VEG_EXISTING with uniform crown diameter for schematic work
• Freeze buildings when presenting pure landscape strategy

Rhino:

• Import 3D terrain mesh; use Contour command to validate against 2D DXF if needed
• Place tree proxies as simplified meshes or circles for sun studies
• Align site boundary with survey when available; treat geospatial topo as design context

Budget cleanup time. Even strong exports need 20 to 40 minutes of layer hygiene.

Competitor context (fair comparison)

TopoExport built its reputation on territory-scale topography exports with vector and mesh formats (DXF, OBJ, SVG, IFC). For very large topo-first masterplans, run a parallel export and compare contour smoothness and area pricing.

CityWeft emphasizes premium urban 3D and infrastructure in select markets. It can excel on built-form detail where LoD2 data exists; tree and topo packaging should be validated per site against UrbanEyes layer toggles.

UrbanEyes wins for many teams when topo, trees, buildings, transit, and proximity (Pro+) must ship in one architect-friendly zip with a free ring test.

When topo/tree maps are not enough

Geospatial topo does not replace:

• Geotechnical borings
• Arborist surveys for protected specimens
• Engineering grading plans
• Legal wetland delineations

Say so on your boards. Jurors and clients respect accurate scope statements.

Pricing for landscape-heavy exports

• Free ring (1 km): early topo/tree reads with core formats
• PAYG: ~€18 to €110 for larger sites
• Pro+ (€80/40 tokens): high volume plus Proximity Map for program + green network diagrams

Landscape studios exporting many campuses per month often land on Pro or Pro+ once PAYG math exceeds subscription cost.

Diagram types to build from one export

1. Contour + tree plan (1:500 or 1:1000)
2. Section cut through topo with building massing
3. Canopy retention plan highlighting trees kept vs removed in proposal
4. Green connection diagram linking parks, waterways, and transit stops

Using one UrbanEyes export keeps scale and north alignment consistent across all four.

Start your topo and tree export

Open UrbanEyes Site Maps, enable topography and trees/parks on a free ring, and build your first graded section before you lock schematic massing.

FAQ

What are topography and tree maps in site design?

They are map layers showing ground elevation (contours or terrain meshes) and existing vegetation (trees and parks) used to inform grading, drainage, shade, and open-space design decisions.

Does UrbanEyes include topography and trees?

Yes. Topography and trees/parks are standard toggleable layers in UrbanEyes Site Maps exports alongside buildings, roads, railways, waterways, and Transit Map.

What is the best format for topo in Rhino?

Use 3D mesh formats such as OBJ, 3DM, or GLB from UrbanEyes paid exports, with DXF contours as a 2D check. TopoExport is an alternative when territory-scale IFC or mesh packaging is your firm standard.

Can I export tree maps for free?

The free ring (up to 1 km) supports core formats for testing. Full SVG, GeoJSON, and complete 3D/CAD packs unlock on paid rings or subscription tokens.

How accurate is geospatial topography?

It is strong for early design context. Engineering and construction grading require site-specific survey and geotechnical work.

UrbanEyes vs TopoExport for topography maps?

TopoExport is terrain-first with strong vector and mesh exports. UrbanEyes combines topo with architecture-oriented layers, transit, proximity on Pro+, and continuity into UrbanEyes site analysis.