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 CSV works well
Many target points start in a spreadsheet. CSV turns that table into a simple field file. The important parts are stable column count, clear headers, decimal format and CRS notes.
Recommended fields
Use point_name, east_x, north_y, z and note. Avoid ambiguous X/Y labels when the project team may read them differently.
Field workflow
Import the CSV, test one or two known points, then use the list for navigation or stake-out. Store staked points separately from design targets.
Measure, check and deliver in the right format.
MapLab Survey is a mobile field app for RTK/GNSS points, drawings, area/volume calculations, coordinate conversion and export to DXF, KML/KMZ, GeoJSON and CSV. Capture, calculation and export can work offline; live NTRIP corrections and online basemaps need connectivity.
Get MapLab SurveyFrequently 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