SA site data into Civil 3D and QGIS: a setup checklist

Setting up an early site model for an Adelaide block means getting three datasets right before anything else: an elevation surface, design contours, and the cadastral lot boundary, all referenced to the same coordinate system. Get the datum and zone wrong and every downstream calculation inherits the error. This checklist runs through what to gather, what format to pull it in, and the SA-specific traps, so your first surface and boundary load clean.

Work through it in order. The stages are: confirm the coordinate system, bring in elevation, bring in cadastre, then sanity-check against the ground and the planning context.

Stage 1: lock the coordinate system first

• Set the horizontal datum to GDA2020. South Australian government elevation and cadastre are published on GDA2020. Adelaide sits in MGA zone 54. The Eyre Peninsula and the far west cross into zone 53, so confirm the zone for a regional lot rather than assuming 54.
• Set the vertical datum to AHD. South Australian LiDAR-derived elevation is reduced to the Australian Height Datum. Civil 3D and QGIS both need this stated explicitly or a surface will sit at an arbitrary offset.
• Decide whether you need the GDA94 to GDA2020 shift. If you are merging older survey data captured on GDA94, apply the national transformation grid rather than a block shift. The two datums differ by roughly 1.8 metres on the ground in SA.
• Record the EPSG code once. For Adelaide that is EPSG:7854 (GDA2020 / MGA zone 54). Set it as the project CRS so every later import inherits it.

Stage 2: bring in the elevation surface

• Choose contours or a DEM, not both by default. Vector contours import as linework; a DEM imports as a raster grid you build a TIN from. If you are unsure which suits the task, contours or DEM for site set-up compares the two.
• Pull the DEM as a GeoTIFF. Raster elevation and TIN surfaces come out in dataset-specific formats, not the full vector set. A GeoTIFF carries its own georeferencing, so QGIS and ArcGIS place it without a world file.
• Pull a TIN surface as DXF if Civil 3D is the destination. The TIN export is DXF-only. Import it as a surface definition rather than tracing contours by hand.
• Set a contour interval that matches the terrain. The Adelaide plains are flat enough that a 0.25 metre or 0.5 metre interval reveals grade; the Adelaide Hills need a wider interval to stay readable. Choosing a contour interval walks through the trade-off.
• Clip to the site plus a buffer. A clipped export around the lot loads far faster than a statewide tile and keeps the file size workable.

Stage 3: bring in cadastre and lot boundaries

• Pull the cadastre as the vector format your tool prefers. Lot boundaries are available as Shapefile, DXF, GeoPackage or KMZ. Use DXF for Civil 3D, GeoPackage or Shapefile for QGIS and ArcGIS, and KMZ only for a quick visual check in Google Earth.
• Confirm the boundary is survey-accurate, not indicative. The published cadastral layer is a spatial representation. It is not a substitute for a surveyed boundary or the plan of division. Treat it as a planning-stage approximation.
• Check the lot against the title reference. Match the parcel to the certificate of title and the deposited plan number before you design to it. This is also the boundary the Form 1 vendor statement describes, so cross-reference the two.
• Load easements if the dataset includes them. Drainage and services easements on an Adelaide infill block constrain where a footing or detention tank can go.

Stage 4: sanity-check against the ground and the code

• Overlay elevation on cadastre and look for a mismatch. If contours and boundary do not line up, one layer is in the wrong CRS. Fix it now, not after the design model is built.
• Note the fall across the lot. A flat reading on the Adelaide plains still matters: low-lying land near the Torrens, Sturt or Gawler catchments carries flood exposure that elevation alone will flag.
• Flag the reactive clay question early. Much of metropolitan Adelaide sits on expansive clay, and the site class drives the footing design. The data export scopes the site; it does not classify it. For how the clay behaves by location, see Adelaide soil types by suburb.
• Check the Planning and Design Code overlays for the zone. The Code (administered through the SA planning portal) carries the hazard and character overlays that constrain what you can build. Confirm the zone and overlays before the concept layout is fixed.
• Record the source and date of every layer. A desktop set-up sets expectations and scopes the field investigation. It is not engineering advice for the lot, and nothing in it replaces a surveyed boundary or a site classification.

Run this before the first design model and the project starts on a shared, correctly referenced base rather than a stack of mismatched layers.

You can export site data for any address in SA, or see a sample export to check the formats and coordinate system before you commit.

LayeredGeo lets you download site data for Queensland, New South Wales, Victoria, South Australia, the ACT and Tasmania - contours, cadastre and more - in DXF, Shapefile, GeoPackage, KMZ and raster formats, ready for Civil 3D, QGIS and ArcGIS.

About this article. Published by LayeredGeo. It is general information about how property and ground conditions are assessed in Australia, not engineering, planning, legal or financial advice, and it is not specific to any property. Check anything that matters against the source dataset or a suitably qualified professional before you rely on it. If you spot something wrong, tell us at hello@layeredgeo.com.au and we will fix it.

← All articles