Eight mistakes people make importing site data into Civil 3D, QGIS and ArcGIS

A downloaded shapefile that lands in the wrong ocean, a TIN that imports as a flat plane, contours that float 20 metres above the DEM: almost every one of these is a set-up error, not a data error. The data is usually fine. The workflow around it is where the day gets lost.

Here are the mistakes that come up most often when engineers, surveyors and GIS people pull QLD, NSW and VIC site data into Civil 3D, QGIS or ArcGIS for early set-up, and what to do instead.

1. Importing before you've confirmed the coordinate system

The single most common failure. A shapefile carries its geometry, but the projection lives in a separate .prj file that is easy to lose, ignore, or get wrong. Import it blind and your site can land hundreds of kilometres off, or worse, sit in roughly the right spot but subtly misaligned with everything else.

Before anything else, know whether your data is in MGA2020, the older GDA94, or a local grid, and set your drawing or project to match. In Civil 3D, assign the coordinate zone on the drawing first, then bring data in. In QGIS and ArcGIS, set the project CRS deliberately rather than trusting the first layer's guess. The coordinate system setup walkthrough covers the MGA/GDA/AHD combinations you'll actually see across the three states.

2. Assuming a DXF carries a coordinate reference

DXF is a drawing format. It stores coordinates as plain numbers with no projection information attached. So a cadastre DXF that opens perfectly in AutoCAD will drop into QGIS at those raw coordinates with no idea what they mean.

When you take DXF into a GIS, you have to tell the software what CRS those numbers are in. Get that declaration right and everything snaps into place. This is exactly why a Shapefile or GeoPackage is often the better choice for GIS work, while DXF is the natural pick for CAD. Match the format to the destination.

3. Treating horizontal and vertical datums as the same problem

Getting the map projection right does not mean your heights are right. Elevation in Australia is referenced to AHD (Australian Height Datum), and that is a separate matter from the horizontal MGA grid. It's possible to have a perfectly positioned surface whose levels are meaningless because the vertical datum was never confirmed.

For any design work touching levels - drainage, earthworks, floor heights - confirm the surface is in AHD before you start setting datums off it.

4. Loading a raw LiDAR DEM and generating contours at a silly interval

A bare-earth DEM out of QLD or NSW LiDAR is a beautiful thing, but generate contours straight off it at 0.25 metres and you get a hairball of noisy, wobbling lines that are useless for a concept plan. The raw grid captures every tiny surface ripple.

Smooth the surface or pick an interval that suits the job and the slope of the site. The contour interval guide walks through choosing something readable for design rather than dumping everything the DEM contains.

5. Building a Civil 3D surface from a TIN when a TIN already exists

When elevation comes out as a TIN in DXF, that surface is already triangulated. Import it, snap the faces to a surface definition, and you're done. Re-triangulating the points from scratch throws away the good triangulation you were handed and can introduce breakline errors that weren't there.

If your export gives you a TIN, treat it as a surface to attach, not a point cloud to rebuild.

6. Trusting cadastre boundaries as survey-accurate setout

Digital cadastre is a fantastic desktop layer. It is not a survey. The lot boundaries you download are a spatial representation, generally fit for planning, extent checks and early massing, but they can differ from a marked, surveyed boundary by a meaningful margin.

Use cadastre to understand the shape and rough position of a lot, to check easements and adjoining parcels, and to set up a desktop review. Do not use it to place a fence or a building setback to the millimetre. If you need the boundary certain, that's a licensed survey. The piece on getting cadastre into Civil 3D and QGIS goes into where the digital layer helps and where it stops.

7. Overlaying a KMZ or georeferenced JPG and treating it as measurable data

Imagery and KMZ overlays are for context and quick visual checks. A georeferenced JPG has real-world position, but it's a picture, not vector geometry you can snap to or query. A KMZ is designed for Google Earth and web viewers, not for pulling coordinates into a design.

Use the imagery to orient yourself and sanity-check that your vector data sits where it should. Do your measuring on the vector and raster elevation datasets that are built for it.

8. Mixing datasets from different sources and vintages without checking they line up

Contours from one capture, cadastre from another, imagery from a third, and none of them quite agree. Vintage matters: a subdivision might exist on the cadastre but not yet on the imagery, or an old DEM might predate an earthworked pad. Stack them without a quick alignment check and you'll design off a version of the site that no longer exists.

Bring in each layer, confirm they share a CRS, then eyeball them together before you trust the set. A road centreline, a fence line, a building footprint - pick a feature that appears on more than one layer and confirm it lands in the same place across all of them.

The quick set-up habit

Most of these mistakes disappear if you do three things in order: confirm the horizontal CRS, confirm the vertical datum, then load one layer at a time and check it lands where it should before adding the next. Two minutes of checking saves an afternoon of chasing a site that's floating in the wrong hemisphere.

When the source data comes out already labelled with its coordinate system and in a format that suits the destination, that set-up gets a lot shorter. Export site data for any address or see a sample export to check the formats and datums before you commit a job to them.

LayeredGeo lets you download QLD, NSW and VIC site data - contours, cadastre and more - in DXF, Shapefile, GeoPackage, KMZ and raster formats, ready for Civil 3D, QGIS and ArcGIS.

About this article. This article was drafted by an AI writing tool using LayeredGeo's data and published automatically. It is general information about how property and ground conditions are commonly assessed in Australia. It is not engineering, planning, legal or financial advice, it is not specific to any property, and it may contain errors or be out of date. 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