Convert Topcon (GTS / comma) to CSV
Topcon instruments and controllers commonly export coordinates as a simple comma-delimited file: one row per point, with the point number first, then northing, easting, elevation, and a feature code. It is the coordinate format that GTS-7 and related controllers write, and it looks deceptively like a plain CSV — until you try to import it and the column order doesn't match what your software expects.
This tool reads each row by position, so it knows the second field is northing and the third is easting regardless of how your spreadsheet would guess. It then writes the point file in the exact column order your controller or COGO package wants — PNEZD or PXYZD — with the feature code in the Description column.
A leading header row, if present, is ignored, and any row with non-numeric coordinates is skipped with a warning rather than corrupting the output. Add a points DXF in the same export. Parsing is entirely in your browser; nothing is uploaded.
Open the converter — free, no upload
How to convert a Topcon coordinate file to CSV
- Export coordinates from the Topcon instrument or controller as its comma-delimited file.
- Drop it on the tool. If auto-detect picks the wrong format, choose Topcon (GTS / comma) from the dropdown.
- Confirm the point count, then choose PNEZD or PXYZD order.
- Export the CSV, optionally with a points DXF.
Questions
What column order does the Topcon file use?
The tool reads it as point number, northing, easting, elevation, code. You then export in whichever order your target software wants — PNEZD keeps northing first, PXYZD leads with easting relabeled as X.
Isn't this just a CSV already?
It looks like one, but the column meaning matters. Reading it by position and re-emitting a labelled PNEZD/PXYZD file means it imports cleanly into a data collector or COGO package without manual remapping.
What happens to a header row or a bad row?
A leading header line is ignored, and any row whose coordinates aren't numeric is skipped and noted in the warnings, so one stray line can't break the whole export.