LandXML to PNEZD point file
PNEZD is the most common surveyor point-file layout: Point number, Northing, Easting, Z (elevation), Description, in that column order. It is the default import format for Carlson, a standard option in Trimble and Leica data collectors, and what most COGO and least-squares packages expect when you hand them a comma-delimited point file. LandXML stores the same information, but in a nested XML structure that no field controller reads directly.
This tool bridges the two. It reads each CgPoint's name as the point number, parses the northing, easting and elevation from the coordinate text, and uses the desc (or code) attribute as the description — then writes them out in strict PNEZD column order with a header row. The result imports cleanly without manual column remapping.
Because elevation is the Z column, points with no elevation (2D points) simply get an empty Z field rather than a zero, which keeps them from being misread as ground at datum. Numbers are written without scientific notation so large state-plane coordinates survive the round-trip.
Open the LandXML exporter — free, no upload
Producing a PNEZD file from LandXML
- Drop the LandXML file on the tool.
- Leave the column-order picker on PNEZD (it is the default).
- Click Export CSV to download points_PNEZD.csv.
- In your data collector or COGO software, import as a PNEZD comma-delimited point file.
Questions
Does PNEZD include a header row?
Yes — the first row is Point,Northing,Easting,Elevation,Description. If your importer expects a headerless file, delete that first line; most modern importers let you skip a header row instead.
What's the difference between PNEZD and PENZD?
Column order. PNEZD is Point, Northing, Easting, Z, Desc. PENZD swaps the first two coordinate columns to Point, Easting, Northing, Z, Desc. This tool emits PNEZD and PXYZD; for PENZD, use PXYZD and relabel, since PXYZD already places easting first.
Will descriptions with commas break the CSV?
No. Any field containing a comma, quote or newline is quoted and escaped per RFC 4180, so descriptions like "fence, wood" stay in one column.