Verify the drawing in three dimensions
A top view can make a fully elevated drawing look identical to a flattened one. Read the entity data before relying on the appearance of a plot. In an ASCII DXF, group codes identify individual values. For the lightweight polyline the elevation field applies to the complete path, while the vertex fields describe coordinates in the object’s plane. A separate closed flag tells the receiving application whether it should draw the final edge back to the first point. A sensible inspection therefore includes height, layer and closure.
Decide which information belongs in the receiving model. The index layer establishes prominent reference elevations. The lighter lines fill in the vertical steps between them. Elevation text, the border and the north/scale graphics support a person reading the sheet. If a modeler selects every entity as terrain input, those supporting marks can become spurious edges. Freeze the annotation layers during geometry selection and restore them when plotting.
The insertion-unit header documents the coordinate convention for software that reads it. It does not document a project’s horizontal reference system or the origin of a local survey. Supply that information separately when an architect must align your contours with a footprint that was drawn in another coordinate system.
DXF polyline fields to inspect
| Parameter | Specification |
| Entity type | LWPOLYLINE |
|---|
| Subclass | AcDbPolyline |
|---|
| Group 38 | Elevation |
|---|
| Group 90 | Number of vertices |
|---|
| Group 70, bit 1 | Closed |
Worked examples
A five-meter design background
Imagine a sheet that covers levels 110 through 145 meters. At five meter spacing, 125 meters is an index elevation and 130 meters is intermediate. Select one of each after import. Check that their distinct layer memberships survive even if the office template applies a single display color to both.
A millimeter coordination drawing
A 32 meter width should measure 32,000 in a drawing whose coordinate values are millimeters. An elevation of 18 meters corresponds to 18,000 in those same units. Check a width and a height together. A file that passes a horizontal check can still be wrong if someone scaled only the plan.
Open curves at a survey edge
A long hillside may send all of its contours through the western edge of the frame. Leave those paths open in a background used for grading. Joining the loose ends across the site would add a fictitious terrace. If a presentation needs a border, keep the frame on its own layer.
Working procedure
- Set the working unit. Identify the unit used in the receiving drawing and choose the DXF unit accordingly. Record the interval independently. A dimensioned reference rectangle provides a quick scale check if downstream staff insert the result as a block or combine it with older unitless linework.
- Tune the geometry. Start with no corner smoothing and inspect a stream crossing or other tight bend. Compare a small simplification tolerance against the original outline at plotting scale. Do the comparison on the same elevation so a different contour does not masquerade as a change caused by filtering.
- Open and interrogate the file. Examine the header unit and select a contour entity. Inspect its layer, elevation and closure. Orbit the drawing or switch to a side view and measure the separation between successive levels. When possible, compare that difference with a numeric interval from the proof summary.
- Package the drawing background. Keep the export and note the source, extent, unit, interval and date alongside it. Record any later translation that moves local coordinates into the project grid. Ask the recipient to measure a shared reference line after attachment, especially where the host drawing already contains a scaled external reference.
When to use this workflow
Existing-conditions underlay
Contour geometry can sit below section markers, layout dimensions and building footprints. Assign a muted plot style to intermediate lines and a stronger lineweight to index contours. Place the exported file as a separate drawing reference when your team needs to replace the terrain without disturbing annotations.
Survey handoff checks
A drawing technician can audit a handful of entity values without processing the entire terrain. Pick one closed loop, one open line and two neighboring heights. Together they reveal common transfer mistakes involving closure, units, flattening and accidental inclusion of the boundary as a terrain line.
Technical questions
Why does Properties call my contour a lightweight polyline?
A contour has a single height along its entire length. The DXF lightweight polyline stores its plan vertices together with one elevation field. With the normal pointing along positive Z, that field places every vertex in the correct horizontal plane while keeping the drawing economical.
Can I use an index label as the elevation input?
Read the elevation from the polyline itself. A text entity records a human-readable callout, and its insertion point can move during annotation. Selecting the underlying contour confirms the numerical height that downstream geometry operations will actually receive.
What should I do if an external reference appears tiny?
Measure the same known span in the exported drawing and in the host. A factor of one thousand suggests a millimeter-to-meter interpretation. Check the source and host insertion settings before applying a manual scale, then repeat the check on a known vertical interval.
Should I join two segments that have the same Z?
Only join endpoints when the source supports continuous geometry between them. Two nearby hilltops routinely produce isolated loops at the same level. Joining them across a saddle creates a feature absent from the terrain and can mislead anyone who later builds a surface from the drawing.