Construction Architect/Architectural Technologist. Founder of Topo-grapher, making accurate site terrain accessible to architects without GIS. Studied in Edinburgh, Copenhagen and Iceland.
Stop manually tracing contour lines in Revit. Learn how to turn elevation survey data into an editable native Revit Toposolid using Topo-grapher in minutes. If you have ever tried to build accurate terrain in Revit, SketchUp, or Rhino by hand, you already know the feeling: it’s slow, it’
A site model can look correct on screen and still be wrong by several metres. That usually happens when terrain, survey information and the building model were created in different reference systems. A reliable BIM coordinate system for site work prevents that problem before it reaches drawings, consultant exchanges or
A terrain model can look convincing and still be useless for drainage decisions. If its points are too sparse, its coordinates are uncertain, or its elevations have been flattened during import, the model may hide the shallow low point that directs water towards a building entrance. Drainage analysis using terrain
A 200-acre masterplan can fail in two opposite ways before design has properly begun: the terrain model is so sparse that a drainage swale disappears, or so dense that every Revit operation grinds to a halt. Terrain point density for masterplans is the practical decision between those two extremes.
A terrain model can look perfectly credible in Revit, Rhino, or SketchUp while being inaccurate enough to compromise a drainage route, retaining-wall height, or accessible ramp slope. For site models, LiDAR accuracy is not a single number you check before downloading a file. It is the combination of the
A site model can look convincing while being wrong in the ways that matter. A coarse mesh may hide a drainage swale, a misplaced coordinate system can put the survey kilometres from the building, and an unfiltered point cloud can make Revit slow before the design work has started. GIS
A Grasshopper terrain from elevation data is only as useful as the coordinate logic behind it. A visually convincing mesh can still be wrong by several metres, sit at the wrong datum, or become too heavy to support a workable Rhino file. For site analysis, grading studies, drainage checks and
A Rhino NURBS terrain from points is useful when the site model needs to do more than look convincing in a rendering. It needs to carry dependable spot levels, support section studies, inform drainage decisions and sit in the same coordinate logic as the wider project. The quality of the
A site model is only useful when it can be trusted. An ArchiCAD Mesh from XYZ data should retain meaningful levels, sit in the right coordinate system and remain light enough to edit without slowing every plan, section and 3D view. The challenge is not simply importing points. It is
A site model becomes misleading the moment it extends beyond the land you are actually designing. A broad terrain surface may look convincing in an early rendering, but it can hide the levels that matter: the pavement fall at an entrance, the low point beside a retaining wall, or the