How to Build an ArchiCAD Mesh from XYZ Data

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 deciding which points represent the site well enough for the design decision at hand.

For feasibility work, a terrain mesh may need to establish broad falls, access levels and likely cut-and-fill implications. For a detailed landscape package, it may need to show local drainage paths, retaining conditions and transitions at building thresholds. The right workflow starts with clean source data and ends with checks inside ArchiCAD, not with a visually convincing but unverified surface.

That's where Topo-grapher.com comes in, try it out for free

Start with the site decision, not the maximum area

Before generating elevation data, define the model extent around the decision you need to make. Include the building footprint, proposed external works, road connections and enough land beyond the design boundary to understand how water and access approach the site. A tight rectangle around the building can hide an uphill catchment or a road level that drives the entire scheme.

Avoid downloading an unnecessarily large area simply because the data is available. A broad masterplan site may justify it, but a small infill scheme does not need every elevation point for several surrounding blocks. More points create a denser Mesh, longer import times and a heavier BIM file. They do not automatically create a more useful model.

Topo-grapher lets project teams draw a site boundary, generate terrain from available official mapping, LiDAR or photogrammetry sources, then download XYZ data for the modelling environment. The useful part of this approach is control: the chosen boundary and point spacing can reflect the design stage rather than a generic web terrain view.

Prepare XYZ data for ArchiCAD Mesh import

XYZ is a simple format, but it is not self-explanatory. In most survey workflows, the three values represent X coordinate, Y coordinate and Z elevation. X and Y are commonly easting and northing values, while Z is an elevation relative to a defined vertical datum. Confirm this before import. Reversing X and Y, or treating metres as feet, can produce a mesh that looks plausible while being fundamentally wrong.

A clean import file should contain one point per line with three numeric values separated consistently by commas, tabs or spaces, depending on the selected importer settings. Remove headings, descriptive text, blank rows and duplicate records unless your import process specifically accepts them. Keep a copy of the original export before editing it.

Confirm horizontal and vertical reference systems

Coordinate reliability matters more than it first appears. A model positioned close to ArchiCAD's internal origin may be easier to navigate and display, but it still needs a defensible relationship to real-world coordinates for civil, survey and consultant coordination. Set the project Survey Point and document the offset or project location before importing terrain.

Check the horizontal coordinate reference system, the linear units and the vertical datum supplied with the data. An elevation in a national height datum is not necessarily equivalent to an arbitrary project zero or finished floor level. If the architect's benchmark is 100.000 m and the terrain data is referenced to a different datum, establish the conversion deliberately. Do not adjust the whole mesh by eye after import.

For projects using US survey data, also verify whether coordinates are in international feet, US survey feet or metres. The numerical difference can become material across a large site. The same principle applies anywhere a local grid, state plane system or engineering datum is involved.

Create the ArchiCAD Mesh from XYZ data

The exact dialogue wording varies slightly between ArchiCAD versions, but the workflow is consistent: establish project coordinates and units first, then import the survey points to create a Mesh.

1. Set up the model environment

Open the site storey or the storey intended to hold terrain. Confirm the working units under Options and Project Preferences, particularly length and level display. Set the relevant storey elevation so the terrain's Z values make sense in relation to the building model.

If the project uses real-world georeferencing, configure the Survey Point before terrain arrives. This avoids a later round of moving objects, correcting consultant overlays and questioning whether the mesh remains in the same place as the civil drawing.

2. Import the survey points

Use ArchiCAD's survey-data import command, typically found under File, Interoperability, Import Surveyor's Data. Select the XYZ or compatible delimited text file, then map the fields to X, Y and Z when prompted. Confirm the separator, decimal symbol, units and coordinate interpretation before accepting the import.

Create the result as a Mesh rather than treating the points as a temporary reference. Place it on a dedicated terrain layer, such as A-SITE-TERRAIN-EXISTING, and assign an existing-ground surface. This gives the model a predictable structure from the outset and makes it easier to isolate existing terrain from proposed earthworks.

3. Check the mesh before modelling around it

Do not immediately begin placing slabs or external stairs. First, inspect the mesh in plan, 3D and section. Check known spot levels against the source data or a survey drawing. Review the site boundary for unexpected spikes, long triangular facets and gaps. A single bad point can create a dramatic peak that misleads a section through the building.

Use two or three independent checks where possible: a road centreline level, a boundary spot level and a benchmark or survey control point. If the imported mesh is offset vertically by a consistent amount, stop and resolve the datum relationship. If isolated points are wrong, correct or remove them in the source file where practical, then re-import.

Choose point density that ArchiCAD can use

Point spacing is a design decision. For a broad early-stage massing study, a spacing of several metres may represent major landform and access gradients adequately. For a compact residential plot, tighter spacing may be needed to understand garden falls, threshold levels and retaining walls. A detailed LiDAR dataset can contain far more points than an ArchiCAD project needs.

Dense source data also has limitations. LiDAR may capture vegetation, parked vehicles, roof edges or other surface artefacts depending on classification and processing. Photogrammetry can be valuable for general terrain context but may not replace a commissioned topographic survey where construction set-out, legal boundaries or precise drainage design are required.

Use terrain data for the decision it can support. It is highly effective for early grading awareness, site options, building placement and coordination discussions. It should be supplemented by a professional survey and civil information when the project moves into detailed construction design.

Keep the site model editable and coordinated

Treat the imported Mesh as existing ground, not as the final grading solution. Keep proposed terrain in a separate Mesh or a clearly managed set of modifiers and layers. This makes it possible to compare existing and proposed conditions, interrogate cut-and-fill intent and avoid overwriting the source terrain when the landscape design changes.

For a clean working model, use a small number of consistent conventions. Give the mesh a clear ID, record the source date and coordinate reference in project documentation, and retain the original XYZ download with the job files. If the project is shared with consultants, note whether the Mesh uses true survey coordinates or a documented local offset.

Performance should be monitored as the model develops. If orbiting, section generation or teamwork synchronisation becomes slow, reduce terrain density at the source rather than repeatedly simplifying the mesh by hand. Preserve denser data externally for analysis or future reference, while keeping the active ArchiCAD model proportionate to the scope of work.

Common import problems and what they indicate

A mesh that imports far from the building usually points to a coordinate-system mismatch, an unconfigured Survey Point or a local-origin assumption that was never documented. A mesh that is too high or low is more often a vertical datum, storey elevation or units problem. A faceted surface with sharp needles generally indicates outlier elevations, duplicate points or an incorrect delimiter.

If the terrain appears rotated or geographically distorted, check whether X and Y were swapped and whether the export is in projected coordinates rather than latitude and longitude. Raw longitude and latitude values are not a suitable substitute for a projected site-coordinate dataset in a normal BIM terrain workflow.

The most dependable ArchiCAD terrain model is rarely the one with the most data. It is the one whose origin, units, elevation reference and level of detail are understood by everyone using it. Build that discipline into the first import, and the Mesh becomes a practical basis for site design rather than a decorative 3D backdrop.