Construction Architect/Architectural Technologist. Founder of Topo-grapher, making accurate site terrain accessible to architects without GIS. Studied in Edinburgh, Copenhagen and Iceland.
A campus masterplan terrain modelling example becomes useful when it tests decisions that a flat base plan conceals: whether a new faculty building can meet an existing path, where accessible routes begin to exceed workable gradients, and how runoff moves between buildings. For a multi-building site, terrain is not
Yes, BIM models retain coordinates. Where they lose them is in transit: a DWG exported without shared coordinates, an IFC written at the internal origin, a SketchUp model whose geolocation was never switched on. So the useful question is not whether a model can retain coordinates, but which exchange is
A site grading model can look convincing and still be wrong where it matters: at the building threshold, along an accessible route, or at the low point where water will collect. Before adjusting contours or proposing finished levels, establish whether the terrain beneath the model is accurate, traceable and usable
A terrain model can look convincing and still be useless for design. If the surface has no dependable levels, arrives in the wrong coordinate system, or contains far more points than the authoring model can handle, it will not support drainage studies, retaining-wall levels, accessibility routes or civil coordination.
"Terrain automation" usually gets sold as one button that turns an address into a finished site model. No such button exists, in Revit or anywhere else. What can be automated is narrower and more useful: getting clean elevation points, turning them into a Toposolid without hand-placing anything,
A terrain model can look convincing and still be wrong where it matters: at a threshold level, a drainage fall, a retaining wall, or the tie-in between an existing road and a proposed entrance. This elevation data quality guide explains what to check before elevation points enter Revit, SketchUp,
A terrain model can be geometrically accurate and still be wrong by several feet. The usual cause is not poor LiDAR or a bad import. It is a vertical datum mismatch. This vertical datum guide explains what that means in practical BIM terms, where errors enter the workflow, and how
A terrain model can look convincing and still be wrong where the project needs it most: at kerbs, drainage swales, retaining edges and the ground beneath trees. The choice between LiDAR versus photogrammetry elevations determines whether your BIM site model represents bare earth, visible surfaces, or a mixture of both.
Most terrain generator comparisons rank tools by how good the 3D preview looks. That is the wrong test for BIM. A beautiful mesh that arrives in the wrong place, at an unknown resolution, as geometry you cannot edit, costs more time than it saves. This comparison looks at the tools
A 500-hectare masterplan can look convincing with a coarse terrain surface and still fail the first meaningful test: can the team identify where water moves, where streets meet existing ground, and where development parcels need cut or fill? Masterplan elevation resolution determines whether the model answers those questions or
When imported terrain lands in the wrong place, the instinct is to grab it and move it until it lines up. It works for the afternoon. Then the survey is revised, the civil engineer links their model, or someone exports IFC, and the terrain is wrong again, by exactly the
A site model that looks right but sits in the wrong place is a coordination problem waiting to happen. Site topography BIM is not simply about placing contours beneath a building. It is about converting real elevation information into an editable terrain model with reliable coordinates, sensible point density and