Menu
Civil survey data guide visual

Civil survey data guide

This guide helps project teams clarify the site data, drawings and deliverables needed for engineering and civil survey support.

Discuss this requirement

Most disputes on a civil project trace back not to the field measurement itself but to the data — the wrong datum, an undefined coordinate string, a point cloud nobody can open, or a "final" surface that turns out to be a draft. This guide explains what a civil survey deliverable should actually contain, in which formats, on which Australian datums, and to what accuracy — so the data your design, machine-control and as-built workflows depend on arrives clean, defensible and usable the first time.

Key takeaways

  • Specify the deliverable, datum and format up front, not after the crew demobilises. Every civil survey should be tied to GDA2020 horizontal, the correct MGA2020 zone, and AHD heights, with the coordinate system, units and combined scale factor stated in writing.
  • The three formats that move civil data are LandXML (surfaces, alignments, design-to-as-built), DWG/DXF (CAD detail and feature strings) and E57/LAS/LAZ (point clouds). Machine control adds TIN/GENIO/TRB surface exports for Trimble, Topcon and Leica iCON systems.
  • Match accuracy to purpose: detail/setout survey holds 5-15 mm with a Leica TS16 or Trimble total station; terrestrial scanning (Leica RTC360, FARO) registers to 3-6 mm; UAV photogrammetry on a DJI M350 RTK lands at 20-50 mm — and CASA CASR Part 101 governs the flight.
  • A survey deliverable is only defensible if it carries its metadata: datum and zone, achieved accuracy against independent checkpoints, control schedule, capture date, instrument and operator. Bare points with no provenance are not survey-grade.
  • Realistic budgets: a small detail/feature-and-level survey runs AUD $2,000-$6,000; a registered point cloud capture $5,000-$20,000+; ongoing as-built and machine-control data packages are usually priced per visit or per hectare.
  • For setout, volumes, as-constructed and design surfaces tied to a verified control network, the right partner is an engineering surveyor — see engineering and civil survey services.

What a civil survey deliverable actually is

A "survey" handed to a civil team is rarely a single file. A complete deliverable for a typical Australian civil package is a coordinated set:

  • A feature and level survey (detail survey) — surveyed strings and points for kerbs, edges, services, structures, levels and surface breaklines, delivered as DWG/DXF and usually a LandXML surface.
  • A control schedule — the permanent marks (PMs), benchmarks and site control the survey is hung off, with coordinates, datum, zone and uncertainty.
  • A surface model (DTM/TIN) for earthworks design, volume calculation and machine control.
  • An alignment (horizontal and vertical geometry) for roads, drains, rail or pipelines, in LandXML.
  • A report — methodology, instruments, achieved accuracy against checkpoints, datum and capture date.

The single most common failure is treating the CAD drawing as the deliverable and ignoring the rest. A DWG with no defined coordinate system, no surface and no control schedule cannot be reliably set out, compared to design, or defended in a claim. The data is the asset; the drawing is one view of it.

Datums, coordinates and the GDA2020 trap

Every Australian civil survey deliverable must be referenced to a defined, documented coordinate framework. Get this wrong and everything downstream — design overlay, machine control, volumes, as-builts — is wrong by a fixed offset that is hard to spot until it is expensive.

Horizontal datum. The national datum is GDA2020, projected to the relevant MGA2020 zone (Universal Transverse Mercator) — for example Zone 50 across the Pilbara and most of WA, Zone 55 through Victoria and central NSW/QLD, Zone 56 along much of the NSW and southern QLD coast. Many established sites still hold legacy GDA94 data; the two datums differ by roughly 1.8 m, so mixing them silently shifts an entire job. Confirm the datum in writing before anyone mobilises.

Vertical datum. Heights should be on the Australian Height Datum (AHD), derived through the site benchmark network and validated to ICSM SP1, which gives the positional-uncertainty framework Australian surveyors work to. AHD and ellipsoidal (GNSS) heights are not interchangeable — a deliverable must state which it carries.

Site grids and scale factor. Many large civil and industrial sites run a local mine or plant grid rather than raw MGA. When they do, the deliverable must state the transformation to MGA2020/AHD and the combined scale factor applied; over a long alignment, an unstated scale factor introduces a real and growing length error. Pin this down before the design model is built, not after the bulk earthworks are out of tolerance.

Survey data formats explained

Choosing the right format for each component is what makes data flow between the surveyor, the designer and the machine-control system without manual re-keying or loss.

Format What it carries Typical use
LandXML Surfaces, alignments, parcels, survey points Design surfaces, as-built comparison, software-neutral exchange
DWG / DXF CAD linework, feature strings, annotation Detail surveys, design drawings, services plans
E57 Registered point cloud + imagery + scan positions Terrestrial scan deliverables (RTC360, FARO)
LAS / LAZ Classified point cloud (LAZ = compressed) UAV LiDAR, large topographic clouds
TIN / GENIO / TRB Triangulated surfaces for grade control Trimble, Topcon, Leica iCON machine control
CSV / TXT (PENZD) Point, Easting, Northing, Z, Description Setout strings, control schedules, GNSS exports
RCP / RCS Indexed point cloud Autodesk Civil 3D / Revit coordination

A practical rule: deliver LandXML for surfaces and alignments (it survives the trip between Civil 3D, 12d Model and Trimble Business Center), DWG for detail, and E57 or LAZ for clouds. Ask for the machine-control surface in the native format your grade-control fleet runs — supplying a designer's TIN that has not been prepared for the machine is a frequent cause of avoidable site rework.

Accuracy classes and the right instrument

Accuracy is a specification, not an instrument brand. The instrument is chosen to meet the stated tolerance and conditions.

Survey type Instrument Typical accuracy Suited to
Detail / setout / as-built Leica TS16, Trimble S-series total station 5-15 mm Kerb, services, structures, setout
Control / monitoring Leica MS60 MultiStation, GNSS RTK sub-mm to a few mm Site control, deformation, alignment
Terrestrial laser scan Leica RTC360, FARO Focus 3-6 mm (registered) As-builts, clash, complex geometry
UAV photogrammetry DJI M350 RTK 20-50 mm H Stockpiles, earthworks, topo over area
UAV LiDAR LiDAR payload on M350-class airframe 30-80 mm Vegetated bare-earth, large topo

The trap is over- or under-specifying. Setting out a building grid to ±5 mm with a total station is correct; trying to do it from a 40 mm photogrammetry surface is not. Conversely, flying a 200-hectare stockpile field with a total station wastes days when a UAV captures it in hours. Aerial work over a live civil or industrial site is regulated under CASA CASR Part 101, generally requiring an operator certificate (ReOC) and a licensed remote pilot, plus airspace approvals near aerodromes — factor that lead time into the program.

Always insist on independent checkpoints: control points withheld from the adjustment or scan registration, then re-measured to report the achieved accuracy honestly, rather than quoting only the software's optimistic internal residuals.

Survey data acceptance checklist

Run this checklist before you sign off any civil survey deliverable. A "no" anywhere is a reason to send it back, not a reason to start designing on it.

Datum and coordinates

  • Horizontal datum stated as GDA2020 with the correct MGA2020 zone (or local grid with documented transformation)
  • Vertical datum stated as AHD, with benchmark source identified
  • Units and combined scale factor stated; ground vs grid distance clarified
  • No GDA94/GDA2020 mismatch against existing site data

Files and formats

  • Surfaces and alignments delivered as LandXML, open without errors
  • Detail/linework as DWG/DXF with a defined coordinate system, not floating geometry
  • Point cloud as E57 (registered) or LAS/LAZ (classified) and openable
  • Machine-control surface in the native fleet format (Trimble/Topcon/Leica iCON)
  • File naming, layers and feature codes match the agreed standard

Quality and provenance

  • Control schedule included (marks, coordinates, datum, uncertainty)
  • Achieved accuracy reported against independent checkpoints, not just internal residuals
  • Capture date, instrument, operator and methodology recorded
  • Surface is the final version, not a working draft, and clearly marked as such
  • Deliverable accompanied by a survey report referencing ICSM SP1 where relevant

Costs and turnaround

Civil survey data is priced on field time, mobilisation and processing — not on the number of files. Indicative Australian ranges:

Deliverable Indicative cost (AUD) Typical turnaround
Feature and level / detail survey (small site) $2,000-$6,000 2-5 business days
Set out / as-constructed visit $1,200-$3,500 per visit 1-3 days
Registered terrestrial point cloud $5,000-$20,000+ 3-10 business days
UAV topo / stockpile capture $1,500-$3,500 (single day) 2-5 business days
Machine-control surface package per hectare or per visit 1-5 business days

Two cost drivers dominate. Processing lead time — registered clouds, LandXML surfaces and as-built comparisons take days to weeks after the crew leaves site, so agree turnaround before demobilisation. Mobilisation — FIFO and remote regional access can add 25-100% to a metropolitan rate, which is why batching survey scopes into a single visit almost always reduces unit cost. Bundling detail, control validation and a scan into one mobilisation, as covered in our engineering and civil survey work, is usually the most economical route.

Frequently asked questions

What file format should I ask for from a civil surveyor?

Request LandXML for any surface or alignment, DWG/DXF for detail and linework, and E57 (or LAS/LAZ) for point clouds. If you run grade control, also ask for the surface in your fleet's native format (Trimble, Topcon or Leica iCON). LandXML is the safest exchange format because it survives the trip between Civil 3D, 12d Model and Trimble Business Center without losing surface or geometry definitions.

What is the difference between GDA94 and GDA2020, and why does it matter?

They are two versions of Australia's horizontal datum, separated by roughly 1.8 m. If your design model is on GDA2020 and a legacy site plan is on GDA94 — or vice versa — every feature is offset by that distance, which is more than enough to fail setout, miss services or blow earthworks volumes. Always confirm the datum and MGA2020 zone in writing before work starts and before overlaying any existing data.

How accurate does a civil survey need to be?

It depends entirely on the task. Building setout and structural as-builts typically need 5-15 mm from a total station; volumetrics and broad topography tolerate 20-50 mm from a UAV; deformation monitoring and alignment demand sub-millimetre to low-millimetre control. Specify the tolerance against the deliverable's purpose and require the surveyor to report achieved accuracy against independent checkpoints.

Can I use a drone survey for setout and design surfaces?

For earthworks design surfaces, stockpile volumes and broad topography, yes — a DJI M350 RTK with proper ground control delivers a usable 20-50 mm surface quickly. For precise setout, building grids and structural as-builts, no — those need total-station or scan-grade accuracy. UAV work is also regulated under CASA CASR Part 101, so commercial flights require an operator certificate, a licensed pilot and airspace approvals near aerodromes.

What metadata should accompany the data?

At minimum: the horizontal datum and MGA2020 zone, the vertical datum (AHD) and benchmark source, the combined scale factor, the control schedule, the achieved accuracy against checkpoints, and the capture date, instrument and operator. Data without this provenance cannot be defended in a claim or reliably compared with a future survey.

Talk to ISS

If you need civil survey data you can build on — correct datum, the right formats, verified control and reported accuracy — Industrial Spatial Solutions can scope, capture and deliver it across Australian civil and industrial sites. Call us on 0407 057 015 or contact the team to define your deliverables, datums and tolerances before mobilisation, so the data lands on spec the first time. For setout, as-constructed and design-surface work, start with our engineering and civil survey services.

Survey services this guide supports

Move from planning information into the related service or quote path that fits the requirement.

Use this guide to prepare a survey enquiry

Send the details ISS needs to assess the survey requirement.

Include the service type, location, timeframe, drawings or photos, required outputs and any access constraints.