Runs locally · No upload

LandXML to CSV — surveyor-ready points without opening Civil 3D

Drop in a .xml or .landxml file from Civil 3D, Carlson, TBC or 12d and pull out clean PNEZD / PXYZD point lists, TIN surface points, parcels and alignments. It parses the real LandXML schema in your browser — so coordinates, point codes and triangles come out right, not flattened into garbage.

  • Files never leave your device
  • No signup, no account
  • No CAD software needed
LandXML · CSV exporter Local

Drop a LandXML file here, or click to choose

.xml · .landxml — exported from Civil 3D, Carlson, TBC, 12d, Surfer…

Point column order
Also export Full

No file is ever uploaded — parsing happens on this page.

Reads LandXML from Autodesk Civil 3D · Carlson · Trimble Business Center · 12d Model
How it works

From LandXML to a point file in three steps

No CAD seat, no add-in, no account. The exporter is the page you're on.

01

Export LandXML

From Civil 3D use Output → Export to LandXML; Carlson, TBC and 12d all have a LandXML export too. You get a single .xml file holding your points, surfaces, parcels and alignments.

02

Parse locally

The page reads the LandXML schema in your browser — CgPoints with their northing/easting/elevation and codes, the TIN's Pnts and Faces, parcel geometry and alignment stationing. Nothing uploads.

03

Pick an order and export

Choose PNEZD or PXYZD column order, tick the entities you need, and download a CSV (or a ZIP of CSVs) ready to import into a data collector, spreadsheet or another design package.

Before & after

The same point — buried in LandXML, and as a clean point file

A generic XML-to-CSV tool dumps the tag soup on the left. This tool produces the point file on the right.

Before — raw LandXML (.xml)

<CgPoints zoneNumber="2"> <CgPoint name="1" code="IP" desc="Found iron pin"> 5012.4400 1024.7700 312.5500 </CgPoint> <CgPoint name="2" code="MAG" desc="Mag nail set"> 5048.1900 1102.3300 311.9800 </CgPoint> </CgPoints>

After — PNEZD CSV

points_PNEZD.csv
PointNorthingEastingElevationDescription
15012.441024.77312.55Found iron pin
25048.191102.33311.98Mag nail set

Northing/easting/elevation read in the correct LandXML order, point name and survey code preserved. Switch to PXYZD and the columns reorder to Point, X (easting), Y (northing), Z.

PNEZD and PXYZD are the two orders field controllers (Trimble, Leica, Carlson) expect. The full version also exports TIN surface points, TIN faces, parcels and alignments.

Why it parses the schema

Built for survey data, not generic XML

Most "XML to CSV" converters walk the tree blindly and emit one column per tag. Run a LandXML file through one and you get a flattened mess: coordinates split across rows, faces detached from points, point codes lost. This tool understands the LandXML schema, so each entity comes out as the record a surveyor actually wants — and it does it in your browser, with no upload.

Zero upload, by architecture

There is no server that receives files. Parsing and CSV generation are client-side code — work offline once the page has loaded.

Correct coordinate order

CgPoint text is read as northing easting elevation, the LandXML default. PNEZD and PXYZD pickers reorder columns for whatever your data collector expects.

TIN points and faces

Surface Pnts export with their ids and coordinates; Faces export as triangle vertex references, so a TIN round-trips into other tools.

Parcels & alignments

Parcel name, type, area and segment count; alignment name, length, start station and station-equation count — summarized to CSV from the CoordGeom.

Pricing

Free for a quick check. $39 once for the full export.

No subscription. Credits never expire.

Free

$0

  • First 25 survey points, PNEZD order
  • Full entity counts and preview
  • 100% local — no upload, no signup
One-time purchase

Full version

$39 once · 1,000 exports

  • Every survey point, no row cap
  • PNEZD and PXYZD column orders
  • TIN surface points and faces
  • Parcel and alignment summaries
  • Multi-file export bundled as a ZIP
Common questions

Answers before you export

What is PNEZD vs PXYZD?

Both are surveyor point-file column orders. PNEZD is Point number, Northing, Easting, Z (elevation), Description. PXYZD is Point, X (easting), Y (northing), Z, Description — the same point, with easting/northing relabeled as X/Y and reordered. Trimble, Leica and Carlson data collectors each expect one of these; pick the one your controller wants and the columns reorder automatically.

Why not just use a generic XML-to-CSV tool?

Generic converters flatten every tag into a column without understanding what a CgPoint, a TIN Face or a CoordGeom is. You end up with coordinates split into the wrong fields, point codes dropped, and faces detached from their points. This tool reads the LandXML schema directly, so northing/easting/elevation, point names, codes and triangle indices all land in the right place.

Do my files get uploaded?

No. Parsing and CSV generation run entirely in your browser using a JavaScript XML parser. You can load this page, disconnect from the internet, and export offline. There is no server that ever receives your survey data.

What does "1,000 exports" mean?

Each export action — one CSV or one ZIP bundle of CSVs from a single file — uses one credit. 1,000 covers far more projects than most surveyors process in a year. Credits never expire and there is no subscription to cancel.

Your survey data stays on your machine. Export it now.