How to prepare a CSV coordinate list for field stake-out
CSV looks simple, but a clean point list can turn a design table into field targets in minutes.
Field takeaways
- Use clear column names such as point_name, x, y, z and note.
- Clarify E/N or X/Y order, especially in projected coordinates.
- Do not mix TUREF/TM metres and WGS84 degrees without labels.
- Keep target, control and information points in separate layers.
- MapLab Survey connects CSV points to navigation, notes and export.
Why stake-out lists start as CSV
On most sites the target points begin life in a spreadsheet: axis points, pegs, borehole locations, pipeline bends, candidate parcel corners. CSV turns that table into a plain text file any field tool can read. RFC 4180 defines the common conventions; what matters in the field is simpler — the file arrives with a stable column count, clean headers and the right separator.
The recommended columns
- point_name — the target name the stake-out screen will show, e.g. A-101.
- east_x — the easting, confirmed against the project note.
- north_y — the northing.
- z — the level or ellipsoidal height, which always needs a note.
- note — one phrase that makes the field decision easier, e.g. "axis point".
X Y or Y X?
Column order is one of the most painful subjects in the field. Some files use X as easting and Y as northing; other habits write X as northing. The point may not land hundreds of kilometres away, so the error can pass unnoticed — and still send you to the wrong spot. The cure is naming the columns explicitly, "east_x" and "north_y", and adding the EPSG code to the file note.
Test before you stake
After importing the CSV into MapLab Survey, do not treat the points as stake-out targets yet. Test one or two control points on the ground first. If the points sit in the right area, the right order and the right layer, move on to navigation. Record the staked points on their own layer: the design target and the executed point share a name but carry different status.
Put information in the filename
A good name looks like "siteA_stakeout_TM33_rev04.csv"; a bad one looks like "coords_final.csv". Whoever opens the file at the office should see the coordinate system and the revision without asking.
Try these steps on your own phone.
MapLab Survey handles RTK/GNSS point capture, drawing, area and volume calculations and coordinate conversion, then exports to DXF, KML/KMZ, GeoJSON, Shapefile, GeoPackage, NCZ or CSV. Capture, calculation and export work offline. Live NTRIP corrections and online basemaps need a connection.
Frequently asked questions
Which columns should a coordinate CSV include?
Point name, east/X, north/Y, Z and note are a practical base.
Comma or semicolon?
Use the delimiter your software expects and check decimal notation.
Can TUREF coordinates be written in CSV?
Yes, with EPSG/zone and coordinate order clearly noted.
Can CSV be used for stake-out?
Yes, after control checks.
Technical references
The field guidance in this article is aligned with the technical and official references below.
Related: Go to coordinate · Stake-out · Stake-out report · MapLab Survey