> ## Content Index > Fetch the complete content index at: https://topographer-com.ghost.io/llms.txt > Use this file to discover other available public pages before exploring further. # Create XYZ Contours for BIM Site Models - URL: https://topographer-com.ghost.io/create-xyz-contours-for-bim-site-models/ - Published: 2026-08-23T07:48:07.000Z - Updated: 2026-08-23T07:48:07.000Z - Author: Aki Olafsson Create XYZ contours from a controlled set of real-world elevation points, not from a screenshot, a generic web mesh, or an over-dense terrain file that slows the model down. For architects and landscape teams, the contour drawing is only as useful as the XYZ data beneath it: point spacing, coordinate system, survey extent and vertical accuracy all affect the result. The practical objective is not simply to make lines appear across a site plan. It is to create a terrain model that can be edited, checked against design levels and used for decisions about access, drainage, retaining edges and building placement. That requires a workflow that begins with dependable source data and ends with contours at a sensible interval for the project stage. ## Create XYZ contours from the right terrain data An XYZ file contains three values for every surveyed or sampled location: X and Y define the point position, while Z defines elevation. When those points are triangulated into a surface, contour lines can be generated wherever the surface crosses a chosen elevation interval. This sounds straightforward, but the source and preparation matter. A terrain viewer may provide a convincing shaded landscape while offering no editable coordinates, no stated vertical reference and no way to assess point density. That is inadequate when the model must support proposed floor levels, accessible routes or early grading studies. Use source elevation data with known geographic coverage and resolution. Official national mapping, LiDAR and photogrammetry datasets are commonly appropriate sources, although their suitability depends on the location and project scale. LiDAR can capture detailed ground variation, but it can also include noise, vegetation artefacts or excessive point counts if it has not been filtered and prepared for a design workflow. Before generating data, define the site boundary tightly. Include the building footprint, likely external works and enough surrounding land to understand drainage paths and connecting levels. Do not download a whole neighbourhood merely because it is available. Large extents create unnecessary points, make surfaces harder to inspect and can obscure the local slope conditions that matter most. Topo-grapher is designed for this step: draw a boundary, generate terrain data, then download editable XYZ points for the modelling environment already used by the team. The output is more useful than a visual terrain tile because the points retain real-world positions that can be checked and coordinated. ## Set point spacing before you create the surface Point spacing is the main control between terrain fidelity and model performance. A very dense point cloud may be appropriate for a small landscape feature, a detailed cut-and-fill study or a complex rocky site. It is usually unnecessary for a concept-stage Revit model covering several hectares. For early massing and site feasibility, use a spacing that communicates the broad landform without creating thousands of tiny triangles. As the design becomes more dependent on local levels, increase density only around the building platform, paths, terraces, retaining structures and drainage routes. A variable-density approach is often more useful than treating the entire site at one resolution. There is also a difference between visual smoothness and engineering confidence. Increasing point density does not correct poor source data, wrong coordinate settings or a boundary that excludes a critical high point. Check the elevation range before modelling. If the lowest and highest values do not align with known spot levels, road kerbs or survey information, stop and investigate before creating contours. ### Choose a contour interval that matches the decision Contour intervals should suit the scale of the drawing and the question being asked. At a broad masterplanning scale, 1 m or 2 m major contours may show the overall structure of the site clearly. For a residential plot or a public-realm scheme with shallow falls, 0.25 m or 0.5 m intervals can reveal practical constraints that a 1 m interval hides. Closer intervals are not automatically better. A 0.1 m contour interval on low-resolution source data can imply precision that the dataset does not support. It may also turn a drawing into an unreadable collection of lines. Use labelled major contours for orientation and lighter minor contours only where they improve interpretation. For slope-sensitive work, supplement contours with spot levels. Contours show shape, but they do not always make a local threshold level, channel invert or accessible gradient obvious. A few controlled spot elevations around entries, road interfaces and proposed drainage routes are usually more informative than dozens of extra contour lines. ## Build the terrain surface in the target software Once the XYZ points are available, create a triangulated terrain surface in the software where the design will be developed. The exact command varies, but the principle is consistent: import points using the correct units and coordinate interpretation, build the surface, then inspect it before generating contour graphics. In Rhino and Grasshopper, [XYZ points](https://topo-grapher.com/topography-for-rhino.html?ref=topographer-com.ghost.io) can be used to construct a mesh or surface for further analysis. Check for long, unrealistic triangles at the edge of the model, particularly where the site boundary is irregular. These edge triangles can pull contours across areas that are outside the actual terrain capture. Clipping the surface to a clean boundary normally solves the issue. In SketchUp, [terrain meshes](https://topo-grapher.com/topography-for-sketchup.html?ref=topographer-com.ghost.io) should be kept manageable. Overly dense imported geometry makes ordinary modelling operations slow and can make grading edits difficult. Use the source point set to create the base terrain, then reserve detailed local geometry for areas where the design genuinely needs it. In Revit, terrain data should support the intended [Toposolid workflow](https://topo-grapher.com/topography-for-revit.html?ref=topographer-com.ghost.io) rather than burden it. Large point sets can affect responsiveness, especially when the model includes linked consultant files, detailed families and multiple views. Start with an efficient terrain definition and create separate local detail only where needed. The building model benefits from a stable site context, not a maximum-resolution landscape scan. For Archicad, use the XYZ data to form a Mesh with a controlled number of points and confirm the project survey point and elevation reference before placing it. A correctly shaped mesh at the wrong datum is still wrong for coordination. ## Generate and check the contour output After the surface is created, set the major and minor contour intervals in the software's terrain display settings. Then inspect the contour pattern, not just the final graphic style. Natural ground generally produces continuous lines that respond logically to ridges, valleys and drainage directions. Sudden isolated loops, sharp spikes or parallel bands that ignore visible site conditions can indicate bad points or triangulation errors. Pay particular attention to boundaries, buildings and tree-covered areas. Source datasets may represent ground, vegetation or a combination depending on processing. If a contour rises sharply around a tree line or crosses through an existing building, do not assume it describes the finished ground surface. Compare it with available survey information and remove or correct anomalies where the model will inform design decisions. Also verify units. A metres-versus-millimetres import error is easy to identify once noticed, but costly if it reaches a shared model. Check a known elevation, confirm horizontal coordinates align with mapping or project control, and document the vertical datum used by the terrain data. This is particularly relevant when coordinating with civil engineers or combining local survey information with regional elevation data. ## Use contours as a design control, not decoration A good contour model lets the project team test whether the architecture belongs to the site. It can show whether an entrance will need excessive ramps, whether a proposed terrace cuts across a drainage path, or whether a retaining edge follows the land efficiently. It also makes early conversations with civil and landscape consultants more specific because everyone can refer to the same terrain geometry and elevations. Do not treat generated contours as final grading design. Publicly available elevation data and broad-area LiDAR are valuable for feasibility, concept development and coordinated modelling, but detailed construction decisions may require a current site survey and civil-engineering design. The required confidence level depends on the project risk, the accuracy of the available data and how much the proposed works alter the ground. The useful next step is to place a few proposed levels against the contour model: finished floor level, accessible entrance level, road tie-in, terrace edge and a likely drainage outfall. If those levels work together before the model becomes detailed, the terrain has already done its job.