Contours or DEM? Choosing between vector contours and raster elevation for site set-up
There is a moment early on almost every site set-up where the same question comes up: do you pull down contours, or do you pull down the underlying elevation grid? Both describe the same terrain. Both come from the same LiDAR. But they behave very differently once they land in your software, and picking the wrong one costs you an afternoon of remodelling.
This is a comparison worth getting right, because the two formats are not interchangeable. A DXF full of contour polylines and a GeoTIFF DEM (Digital Elevation Model) each have jobs they do well and jobs they do badly. Here is how they stack up, and which one to reach for depending on where the data is going.
The two things you can actually download
When you export elevation data for a QLD or NSW site, you are usually choosing between two representations of the same LiDAR-derived surface.
Vector contours are lines of equal elevation, delivered as polylines in DXF, or as features in a Shapefile or GeoPackage. Each line carries an elevation value. They are a derived product: someone chose a contour interval and generated lines from a grid.
A DEM raster is the grid itself. A GeoTIFF (or similar raster) where every cell holds a height value, typically at 1 m ground resolution across much of the populated coast. It is the closer thing to the raw surface, and everything else, contours included, can be generated from it.
The distinction matters because a contour set has already had a decision baked into it. If you download 0.5 m contours you cannot get 0.25 m detail back out of them. A DEM keeps your options open.
Where each one shines
Contours are immediately readable. Drop them into a drawing and an engineer or surveyor reads the terrain at a glance: ridges, gullies, batters, the fall across the pad. They plot cleanly, they annotate cleanly, and they are what a set of drawings ultimately needs to show.
A DEM is the better raw material. It builds a surface (a TIN or grid) in Civil 3D or QGIS without you tracing anything, drives cut and fill volumes, generates slope and aspect analysis, and lets you re-contour at any interval you like after the fact. If you are doing genuine terrain analysis rather than just drawing lines, the raster wins.
The catch with a DEM is bulk. A 1 m raster over a large site or a whole estate is a heavy file, and older CAD workflows are happier with vectors than rasters. The catch with contours is the opposite: they are light and tidy, but they have thrown away information, and their usefulness is locked to the interval someone already chose. If that interval is wrong for your job, you are stuck.
Contours vs DEM raster, side by side
| Axis | Vector contours (DXF / SHP / GPKG) | DEM raster (GeoTIFF) |
|---|---|---|
| What it is | Lines of equal height, one interval baked in | Full elevation grid, every cell a height |
| Best for | Drawings, quick terrain read, annotation | Surface building, volumes, slope analysis |
| Re-interval later | No, locked to what you downloaded | Yes, re-contour at any interval |
| Detail retained | Only what the interval captures | Full grid resolution (often 1 m) |
| File size | Light | Heavy over large areas |
| Civil 3D | Import polylines, add elevation as feature lines | Import as surface directly |
| QGIS / ArcGIS | Loads as vector layer | Loads as raster, drives analysis tools |
| Coordinate handling | Needs correct CRS on import | Georeferenced, but check datum |
Which should you pick
For most early site set-up and desktop review, download the DEM raster and generate contours from it in your own software. It gives you the surface for volumes and slope, and you control the contour interval instead of inheriting someone else's. This is the flexible starting point, and it future-proofs the job when the design scope shifts.
There is one honest exception. If all you need is a quick visual read of the fall across a block, for a feasibility sketch or a listing review, and you are working in a vector-only workflow, grab the contours at a sensible interval and move on. It is faster, lighter, and enough. Deciding what interval counts as sensible is its own small skill, and choosing the right contour interval is worth a read before you commit.
One more thing that will save you grief regardless of which you pick: sort out the datum and projection at import, not later. Elevation values are tied to AHD (Australian Height Datum), and horizontal positions to MGA2020 or GDA94, and a surface that lands in the wrong place is a surface you will rebuild. Getting the coordinate system right for QLD and NSW site data up front removes the single most common cause of an elevation set that will not line up with the cadastre.
Common questions
Can I convert a DEM to contours in Civil 3D or QGIS?
Yes, and it is the recommended path. In Civil 3D you build a surface from the raster, then generate contours at whatever interval and smoothing you want. In QGIS the Raster to Contour tool does it in one step. Going the other way, contours back to a good DEM, is far messier and loses detail, which is why downloading the grid gives you more room to move.
What DEM resolution do I get for QLD and NSW sites?
Much of the populated coast and urban footprint is covered by 1 m LiDAR-derived DEM, which is ample for site set-up, pad design and preliminary earthworks. Coverage and vintage vary by area, and some regional or older captures are coarser, so it is worth confirming the resolution for your specific address before you rely on it for volumes.
Is a DEM accurate enough to design footings or drainage?
It is excellent for early design, feasibility and desktop review, but it is a surface model, not a survey pickup. For detailed design and setout you still want a ground survey to confirm levels and features the LiDAR cannot see under vegetation or structures. Treat the DEM as your fast, reliable starting surface, then verify on the ground where the design demands it.
When you want the elevation grid and the contours ready to drop straight into your surface, you can export site data for any address or see a sample export to check the formats before you commit.
LayeredGeo lets you download QLD and NSW site data - contours, cadastre and more - in DXF, Shapefile, GeoPackage, KMZ and raster formats, ready for Civil 3D, QGIS and ArcGIS.
LayeredGeo Export
Need this data in CAD or GIS?
Download cadastre, contours, aerial imagery and planning layers for any QLD or NSW site as DXF, Shapefile or GeoPackage - ready for Civil 3D, QGIS or ArcGIS. $15 per site, no account needed.
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.
Related articles
Flood overlays versus actual flood risk: reading the mapping like a planner
Flood overlays, DFE, PMF and hydraulic categories all mean different things. A technical guide to reading QLD and NSW flood mapping and its real limits.
23 July 2026Reading groundwater and bore records: what they tell you about a site before you dig
How to check groundwater depth and bore records in QLD and NSW, why the water table matters for footings, and what a desktop report reveals before you build.
20 July 2026How to spot a steep or sloping block from a listing before you inspect
Learn to read slope and terrain risk on realestate.com.au and domain.com.au listings before you inspect — the clues photos hide and what steep ground costs.