A surface file that imports without an error can still be unsuitable for the next task. When exchanging data from Autodesk Civil 3D, agree the meaning of the data as well as its format.
Agree the exchange specification
Ask the recipient which surface format their application supports and which information they need. Autodesk documents surface export routes including LandXML and DEM for appropriate receiving applications. Choose the route that fits the recipient’s purpose and software.
Record the surface name, revision, units, coordinate reference and vertical reference where relevant. Those details should travel with the file. A filename ending in the expected extension does not communicate every assumption used to create the surface.
Verify the result
- Keep the original project and identify the exact surface being issued.
- Review the boundary and the area intended for exchange.
- Export using the agreed format and settings.
- Import the result into a separate test project or have the recipient validate it.
- Compare known locations and elevations against the source.
Use meaningful control checks
Choose checks distributed across the surface, including an edge and an area with a distinctive feature. Looking at a single familiar point is weaker evidence than checking both horizontal placement and elevation at several known locations.
For example, if a model is intended for preliminary coordination, state that purpose explicitly instead of allowing the recipient to assume it is an approved construction deliverable. Record any excluded area or known limitation in the handover note.
Keep the issued file and validation notes together. They provide a clear reference if the recipient later reports a mismatch or requests a revised export.
Publisher reference: Autodesk: exporting Civil 3D surface data.
Check the Windows platform and subscription details on the Civil 3D product page.