Sent a 12d file but don't have 12d? How to open .12da files in AutoCAD or BricsCAD

It usually arrives as a line in an email: "12d data attached." The surveyor or the road designer has done the right thing and issued their model, and now there's a .12daz file sitting in your inbox. If you run 12d Model, great - you drag it in and get on with your day. If you don't, you're stuck looking at a file that nothing on your machine will open.

This comes up constantly for geotechnical engineers, structural engineers, builders, project managers and smaller civil consultancies. 12d Model dominates civil design and survey in Australia, but a licence costs serious money, and plenty of people who need to read 12d data have no reason to produce it. There is no free 12d viewer that opens these archives.

The good news: a 12d archive is not a locked box. The design geometry inside it can be extracted into a DXF - the universal CAD exchange format - and interrogated in whatever you already run: AutoCAD, BricsCAD, Civil 3D, MicroStation, ZWCAD, DraftSight, even QGIS. We built a free tool that does exactly that: the 12d Model to DXF converter.

What a .12da file actually is

A .12da file is a 12d ASCII archive - 12d Model's native way of handing over project data. It's a structured text dump of everything the sender chose to share: road design strings, alignments, survey pick-up, contours, tins, pipes, sometimes whole plot sheets. A .12daz is the same archive, zipped (they compress extremely well - a 30 MB .12daz can be a gigabyte of text inside).

The core currency of 12d is the string: a named line with coordinates and levels, living in a named model (12d's version of a layer). A design handover typically contains dozens of models and tens of thousands of strings - control line alignments, edge-of-bitumen strings, batters, kerb returns, drainage, the lot. The geometry is real design geometry: alignments carry their arcs, transition spirals and vertical curves, and design strings carry true reduced levels, usually on MGA coordinates.

That's exactly the information you want when you're checking a driveway grade against the road design, setting a floor level, positioning boreholes along an alignment, or working out how much of a batter lands on your site. It's all in the file. You just can't see it.

Getting it into AutoCAD or BricsCAD

The converter works in two steps, because a full handover archive usually contains far more than you need.

Inspect. Upload the .12da or .12daz and the tool parses it and lists every model inside - grouped into control lines, design strings, sections, survey, surfaces and so on, with string counts, level ranges, and which control line each design model hangs off. This alone answers the first question you'd ask in 12d: what did they actually send me?

Select and export. Tick the models you want - typically the control lines and finished design strings, skipping the working models and plot sheets - and download a DXF. A built-in plan preview shows the selected linework before you commit, coloured by model or by elevation.

The DXF you get keeps the structure of the 12d data rather than flattening it:

• One DXF layer per 12d model (or per string if you prefer), so you can freeze what you don't need, exactly as the designer organised it
• 3D polylines at true coordinates and levels - no transformation, no scaling. If the design is on MGA2020, the DXF lands on MGA2020, and snapping to a vertex reads the actual design RL
• Curves sampled properly. Alignments defined by intersection points are reconstructed through their arcs, spirals and parabolic vertical curves, and arc segments in ordinary strings are densified at the chord interval stored in the file itself
• 12d names preserved. Every entity carries its original string name, model and type as XDATA, so nothing loses its identity in the trip
• A manifest listing every string exported and anything skipped, so you can confirm nothing important was silently dropped

Open the result in AutoCAD or BricsCAD and it behaves like any drawing: measure offsets from the control line, run a quick surface check against your survey, list a string's levels, overlay your own design. In Civil 3D you can go further and rebuild alignments from the polylines if you need station-offset reporting.

What doesn't come across

Honesty matters with format conversion, so: a DXF is geometry, not a 12d project. Triangulated surfaces (tins) are deliberately skipped - they're enormous, and if you genuinely need the surface rather than its strings and contours, ask the sender for a LandXML export instead. 12d attribute data beyond name/model/type, apply-many-function templates and plot frames don't translate to CAD entities either.

And the usual caveat applies to anything extracted from a handover file: check the linework against the issued drawings before you use it for setout or construction. The converter reports everything it extracts and skips precisely so you can make that check.

Try it

The 12d Model to DXF converter is free - three conversions a day with files up to 50 MB, or unlimited with a free LayeredGeo account (which also lifts the cap to 200 MB). Files are processed on upload and deleted within 30 minutes; your design data isn't kept.

And if you're reviewing a design, you probably want the site context to go with it - cadastral boundaries, LiDAR contours, geology and watercourses clipped to the job, delivered as DXF or Shapefile in your project datum. That's what LayeredGeo GIS Export does, for any QLD or NSW site.

← All articles