DXF vs KML vs LandXML: Choosing Survey Export Formats

A practical decision table

Use DXF when the recipient needs a CAD-oriented drawing review of points or generated geometry. Use KML when the clearest question is “where is this?” in a geographic viewer. Use KMZ when that geographic handoff is easier as a packaged file. Use LandXML when the receiving workflow expects a supported structured land or surface exchange. If two needs are equally important, agree on a primary deliverable and provide the source context rather than sending an unexplained bundle of formats.

Before delivery, test the chosen output with the receiving user’s actual software and a known coordinate. This small check catches more practical issues than a format discussion alone. Record the result, units, and any compatibility limitation in the handoff note.

Start with the handoff purpose

There is no universally best survey export format. The right choice depends on who receives the file, what they need to inspect, and which attributes must remain understandable. A CAD-oriented handoff may favour DXF, a geographic review may favour KML or KMZ, and a surface-oriented workflow may call for LandXML. Treat the format as part of the communication plan, not as a last-minute button choice.

Before exporting, write down the source coordinate context, units, intended recipient, and whether the deliverable needs points, contours, a TIN surface, or a geographic overlay. This short note prevents a technically valid file from becoming an ambiguous handoff.

DXF, KML, KMZ, and LandXML in practice

DXF for CAD-oriented review

DXF is a practical choice when the next step is a drawing or CAD review. It can be suitable for point and geometry handoffs where the receiving team needs to inspect locations, labels, or generated contours in a drawing environment. Confirm insertion units and coordinate context because a correct-looking drawing can still be shifted or scaled in the receiving setup.

KML for a geographic view

KML is useful when a reviewer needs to see survey points or related outputs in a geographic viewer. It communicates location well and can make a site easier to discuss with people who do not work in a CAD drawing every day. Validate the datum, axis order, and known control points before treating the overlay as meaningful.

KMZ for a packaged geographic handoff

KMZ is a compressed package built around KML content and may be convenient when the handoff includes related assets. Use it when the receiving workflow expects a packaged Google Earth-oriented file. Keep the source point file and coordinate notes available because packaging does not resolve an incorrect reference system.

LandXML for surface-oriented workflows

LandXML can be appropriate when the downstream workflow expects a structured land or surface exchange. Confirm what the receiving software supports and whether the output contains the surface information the recipient expects. Do not assume that every LandXML consumer interprets units, surfaces, and metadata identically.

Step-by-step format selection workflow

1. Define the reviewer’s question

Is the next person checking point locations, drafting geometry, discussing the site on a map, or continuing a surface workflow? Write the question in one sentence. It usually points to a sensible first format.

2. Prepare and inspect the source

Import the supported survey point file into the TopoAssist browser workspace. Map fields, confirm coordinate-system information, and check several known elevations and coordinates. Generate contours or inspect the associated TIN surface when those results are part of the intended handoff.

3. Choose the narrowest useful output

Choose DXF for a CAD-oriented need, KML or KMZ for a geographic-view need, or LandXML for a supported surface exchange. Preparing the narrowest useful output keeps the handoff easier to interpret and reduces unnecessary assumptions.

4. Validate in the receiving workflow

Open the actual file where it will be used. Check extent, units, labels, surface or contour behaviour, and at least two known points. If the result fails a check, return to the source and coordinate context rather than hiding the discrepancy in the receiving software.

5. Share the context

Send the source filename, coordinate-system choice, units, preparation date, and any limitations or flagged areas with the export. A short context note often prevents more rework than adding another format.

Common mistakes and practical tips

• Choosing by habit: start with the receiving question, not the format you used last time.
• Mixing geographic and projected context: record the reference and units before export.
• Sending every available format: provide the one the recipient can interpret, plus source context.
• Assuming LandXML compatibility: check the receiving software’s supported surface and metadata behaviour.
• Skipping a known-point test: verify location and scale in the actual receiving workflow.

Limitations and verification note

TopoAssist supports a focused browser workflow for reviewing survey points, generating related results, and preparing supported outputs. Availability and downstream interpretation can vary by current access and receiving software. No export format proves survey accuracy; retain the original observations and apply the project’s required professional checks.

Choose for the next workflow

DXF is commonly selected for CAD-oriented work. KML or KMZ can support a geographic-view workflow. LandXML is a surface format that may be useful where a downstream surface workflow calls for it. TopoAssist prepares these supported outputs when current access permits them.

Format selection does not remove the need to review source data and coordinate-system information. The receiving workflow should also validate that the output meets its needs.

Questions to ask before exporting

Keep the source context with the output

FAQ

Related resources

Explore survey data for AutoCAD, review LandXML export, read DXF export guidance, review features, or see pricing.