By Coulter Heiberger · Updated
Real terrain and context for Rhino: a finished mesh for direct modeling, raw layers for parametric Grasshopper work.
Rhino gives you two good ways to work with a real site: import a finished terrain mesh and model against it, or feed the raw layers into Grasshopper and build the terrain parametrically. A Mantle Place bundle supports both from one download. For direct modeling, take the OBJ or glTF terrain, imagery draped and included at no extra cost, and import it at real-world scale. For parametric work, the same bundle carries the ingredients Grasshopper wants: a heightmap PNG to drive a surface, DXF contours to loft or patch, and GeoJSON vectors for the roads and footprints that populate a definition. The manual alternative is assembling those layers from separate portals and reconciling their projections before anything reaches the canvas.
Rhino 8 does not import a DEM or GeoTIFF natively, so bring the terrain in as a mesh: import an OBJ or glTF terrain, both of which Rhino 8 reads, then add context from DXF contours and vector layers. A Mantle Place bundle carries all of them for the area you draw, clipped to one extent.
Yes. The Heron plugin, built on GDAL, imports DEM and GeoTIFF terrain as a mesh clipped to a boundary, and Gismo builds terrain and buildings from a location and a radius. Without a plugin, Rhino’s Heightfield command turns a grayscale heightmap image into a surface or mesh.
Yes. The data is not locked to Rhino or Grasshopper: the meshes, contours, and vectors open in Revit, Blender, Unreal, and more, so a parametric study and the presentation model share one georeferenced site.
Define the extent the study needs. For parametric site work, err generous, since Grasshopper makes cropping easy later.
One bundle serves both workflows: in your vault, download Everything for the meshed terrain, the heightmap, the contours, and CAD linework.
Import the OBJ or glTF terrain into Rhino; it arrives at real-world scale with the aerial imagery as its texture.
Reference the DXF contours as curves, sample the heightmap PNG to drive a surface, and bring the vector layers in for streets and footprints.
Cut, project, and rebuild against the terrain, or wire it into the definition so every design option sits on the real ground.
Use the mesh when the terrain is context to model against; rebuild from the heightmap or contours when the definition needs to resample, deform, or analyze the surface parametrically.
The heightmap PNG for surface generation, DXF contour curves, and Drawings/Linework.dxf with streets, buildings, and water on named layers in real coordinates; GeoJSON vectors and the DEM GeoTIFF are there too when a plugin like Heron should read the source data.
Yes. The bundle is georeferenced and unit-consistent, so the mesh and the contours arrive at true dimensions. Set your model units to meters and the site measures correctly.
Draw your area, read its Site Brief, and download a bundle you keep: terrain, imagery, CAD drawings, and more, ready for Unreal, Revit, Rhino, and more. $5 plus $2 per square kilometer, and 2 km² and under is free.
Native plugins: Mantle Place for Unreal and Mantle Place for Revit.
Enter the curator