Queensland Globe data into Civil 3D and QGIS: a worked example

To set up a design model for a Queensland lot, you need two base layers first: the cadastral boundary and a ground surface. Both are published by the Queensland Government, and both can be viewed on the Queensland Globe. Getting them out of a web viewer and into Civil 3D or QGIS in the right format and the right coordinate system is where early site set-up either goes smoothly or costs an afternoon. This worked example follows one hypothetical job through that process.

The site is invented for illustration: a sloping infill block in a Sunshine Coast suburb, roughly 800 square metres, falling from a street at the front to a drainage line along the rear. No real address, lot number or measurement here is real. The point is the order of operations and what each layer changes about the set-up.

The job: a sloping infill block on the Sunshine Coast

The brief is a knock-down rebuild. The designer needs a boundary to work inside, a ground surface to set floor levels and driveway grades against, and enough context to brief a surveyor and a geotechnical engineer before anyone visits. The desktop set-up has to produce a model that is correct enough to scope the real survey, not to replace it.

On the Sunshine Coast, the mapped geology under the eastern suburbs is often Myrtle Creek Sandstone or Landsborough Sandstone with pockets of alluvium along the creek lines. That matters later for the geotechnical brief, but the elevation data is what sets the earthworks assumption, so that comes first.

Step 1: confirm the lot on Queensland Globe

Find the lot on plan

The first task is identifying the correct parcel. Searching the address on Queensland Globe returns the lot on plan, for example a lot number and a registered plan number. That lot-on-plan reference, not the street address, is what the cadastral dataset keys on. A separate guide on finding property boundaries and lot on plan in Queensland Globe covers the viewer itself.

Write the lot on plan down. When the boundary layer comes out as a shapefile, you want to confirm the right polygon came with it rather than a neighbour's.

Note what the viewer shows and does not

The Globe shows the boundary as a line drawn from the Digital Cadastral Database. That line is a legal and administrative record, not a surveyed set-out. It can sit a metre or more from the true corner pegs. Treat it as planning-grade. Any design that relies on a boundary offset still needs an identification survey.

Before Step 2: where the files come from

Queensland Globe is a viewer. It does not give you LiDAR downloads, and it does not produce DXF or GeoPackage files of the lot or the ground surface. The files in Steps 2 and 3 come from other places:

  • Cadastre. The Queensland cadastral parcel data can be downloaded from QSpatial, the state's spatial data portal. It arrives as a statewide or regional dataset, not cut to your lot, usually in a GIS format such as Shapefile or File Geodatabase. You clip it to your lot yourself.
  • Elevation. LiDAR and DEM data come from ELVIS, the free national elevation service run by Geoscience Australia. It sends whole tiles, not a file cut to your lot. See ELVIS LiDAR download versus a clipped site elevation export.
  • Ready-made DXF, GeoPackage, GeoTIFF and contours. If you want the lot boundary and the ground surface already clipped and delivered in the formats below, that needs a LayeredGeo site export. Otherwise you convert them yourself, as set out in Steps 2 and 3.

Step 2: get the cadastre out as a vector file

The boundary is a vector dataset, so it can be held in the usual vector formats: Shapefile, DXF, GeoPackage or KMZ. Which one depends on where it is going.

Target software Best format Why
Civil 3D DXF Opens as linework directly, no import dialogue
QGIS GeoPackage or Shapefile Keeps attributes like lot on plan and area
ArcGIS Shapefile or GeoPackage Native attribute handling
Quick visual check KMZ Opens in Google Earth over imagery

For this job the designer is modelling in Civil 3D, so a DXF of the boundary drops straight in as polylines. The lot on plan and area ride along better in a GeoPackage, so a second copy in that format goes to the QGIS project used for the desktop review.

If you start from the QSpatial download instead of an export, the steps are: load it in QGIS, filter to your lot on plan so only that polygon is left, and use Export > Save Features As to write a GeoPackage (keeping attributes) or a DXF (linework only). Check the coordinate system first, as set out in Step 4. The mechanics of each format are covered in getting cadastre and lot boundaries into Civil 3D and QGIS.

Step 3: choose the elevation data and its format

Elevation is where format discipline matters most, because the ground surface does not come out as a vector by default.

Queensland LiDAR is published as a raster DEM: a georeferenced grid of ground levels, normally a GeoTIFF or similar grid file. Download it from ELVIS, which is where the ground levels come from. A TIN surface, if you want a triangulated surface rather than a grid, is a separate product made from that grid, and can be held as DXF. Contours derived from the DEM are vector linework in DXF, Shapefile, GeoPackage or KMZ. Those are three different products from the same source, and picking the wrong one wastes a step.

If you work from the ELVIS download yourself, the steps are:

  1. Mosaic the tiles and clip the result to your lot plus a margin, so the surface extends past the boundary.
  2. Confirm it is a bare-earth DEM, not a surface model that includes roofs and trees.
  3. Reproject it to MGA2020 Zone 56 if it is not already (see Step 4).
  4. Generate contours from the clipped DEM (in QGIS, the contour tool in the Raster menu, or the equivalent in Civil 3D), then save them as DXF or GeoPackage. A TIN is built in Civil 3D from the DEM or from points.

A LayeredGeo site export delivers the GeoTIFF, TIN and contours already clipped to the lot, so these steps are only needed if you start from ELVIS.

For a Civil 3D earthworks model, there are two sensible paths:

  • Bring in the GeoTIFF DEM and build a surface from the raster. This keeps the full grid resolution.
  • Bring in a TIN as DXF and use it directly as a surface definition.

For this sloping block the designer takes the GeoTIFF for the surface and also pulls 0.5 metre contours as DXF for a quick read of the fall before the model is built. On a block dropping several metres front to back, that interval shows the drainage line clearly without drowning the drawing in lines. Interval choice is its own decision, set out in choosing the right contour interval.

Step 4: get the coordinate system right before anything aligns

Queensland site data is published in GDA2020, projected to MGA2020 in the relevant zone. The Sunshine Coast sits in MGA2020 Zone 56. Heights are to the Australian Height Datum, AHD.

Check the coordinate system of each file at the source before you use it. Data copied or exported from a web viewer is often in EPSG:3857 (Web Mercator), the system web maps use. If a boundary or contour file is in EPSG:3857, reproject it to GDA2020 / MGA Zone 56 (EPSG:7856) before you export it to DXF. In QGIS that means saving a new copy with the target CRS selected, not just changing the project setting. Files already in EPSG:7856 should be left as they are.

Setting the drawing or project coordinate system does not transform the data. It only tells the software how to read the coordinates already in the file, so a 3857 file placed in a 7856 drawing will still land in the wrong place, or metres off. In Civil 3D, set the drawing's coordinate system to MGA2020 Zone 56 before importing either layer. In QGIS, set the project CRS to EPSG:7856 so the GeoTIFF and the GeoPackage overlay correctly. The full reasoning on datums is in getting the coordinate system right for QLD, NSW and VIC site data.

A quick check: once both layers are in, the cadastral polygon should sit over the DEM with the street edge roughly along the high side. If the boundary floats in empty space, the CRS is wrong, not the data.

Step 5: read what the set-up tells you, and what it does not

With the boundary, the DEM surface and the contours aligned, the desktop model now answers the early questions:

  • Fall across the lot. The contours confirm the drop from street to rear and show whether the fall is even or steepens near the drainage line. That sets the cut-and-fill and retaining assumption.
  • The low corner. The rear, near the creek, is the low point. That flags a check against the council flood overlay and the alluvial geology before footings are priced.
  • Driveway grade. A first pass at the driveway can be set against the DEM to see whether the street-to-garage grade is workable.

What the set-up does not give is a surveyed surface. LiDAR ground levels are accurate to a published vertical tolerance, not to survey pickup. The DEM does not capture the exact pad level, the invert of the creek, or the true boundary corners. It is enough to scope the detail survey and brief the geotechnical investigation, and no further. For a knock-down rebuild, the real site costs still turn on that fieldwork, as set out in the hidden site costs of a knock down rebuild.

The desktop model's job on this block is to say: order a detail and boundary survey, scope the geotechnical holes toward the alluvial rear, and check the flood overlay on the low corner. That is the whole value of getting the base layers in early.

If you would rather pull a clipped, CAD-ready boundary and elevation set for a Queensland address than piece it together from the viewer, you can export site data for any address or see a sample export first.

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.

LayeredGeo Export

Need this data in CAD or GIS?

Download current cadastre, terrain, geology, soils, planning, hazard, heritage, easement and available imagery layers for a QLD, NSW, VIC, SA, ACT or TAS site in their supported GIS, CAD and raster outputs. $15 per site, no account needed.

Export site data → See a sample export

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