How to prepare a GNSS survey report that can be trusted
A good report defends the measurement by showing method, corrections, CRS, antenna height and control.
Field takeaways
- A GNSS report should state method, date, crew, receiver, corrections and CRS.
- Antenna height, fix status, observation time and control residuals are critical.
- CRS should be written with EPSG or clear datum/zone notes.
- Photos and notes connect the report to the ground.
- MapLab Survey keeps observations, notes, photos and exports together.
What the report is for
The report is not just the file handed to the client. It is the memory of the measurement: when the crew changes, when a dispute starts, when the office drawing does not fit the site, or when someone returns to the same point months later. Official mapping regulations put weight on standards and responsibility for exactly this reason — the record is part of the work.
What belongs in the header
- Project name and work item.
- Survey date, time window and crew.
- Receiver, antenna, connection and correction source.
- Coordinate system, datum, zone and EPSG code where known.
- Height reference: ellipsoidal height or orthometric level?
What belongs in the point table
Point name (matching the CAD/GIS name and the mark on the ground), E, N and Z, the antenna height, the solution status — fixed, float or autonomous — the control point difference, and a note or photo giving the point its physical context. Each field answers a question someone will eventually ask; leaving one out means answering from memory.
The delivery package
Split the measurements into layers: control, measured detail, stake-out targets, executed points, photo notes. Build the report as PDF/Excel/TXT and produce KML/KMZ, DXF, GeoJSON or CSV from the same job. The package works when the report reads well, the file opens, the point can be found on the ground and the coordinate system is understood.
Sentences that weaken a report
"Measured with GPS" is weak on its own. "RTK fixed, network correction, TM33, antenna height 2.000 m, horizontal difference at the control point 0.018 m" is strong. A professional report does not come from a fancy template — it comes from leaving the measurement's trail open.
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
How should CRS be written?
State datum, projection, zone and EPSG if available.
Is antenna height needed?
Yes, especially for vertical interpretation.
Is fixed status enough?
No. It should be supported by control and repeat checks.
Can MapLab Survey help reporting?
Yes, by keeping observations, notes, photos and exports together.
Technical references
The field guidance in this article is aligned with the technical and official references below.
- Harita Genel Müdürlüğü, Büyük Ölçekli Harita ve Harita Bilgileri Üretim Yönetmeliği
- TUSAGA-Aktif resmi portalı
- NOAA NGS, User Guidelines for Single Base Real Time GNSS Positioning
- TUCBS Koordinat Referans Sistemleri ve Coğrafi Grid Sistemleri Kayıt Dokümanı
- MapLab Survey App Store sayfası
- MapLab Survey Google Play sayfası
Related: Field survey checklist · RTK GNSS field accuracy · Stake-out report · MapLab Survey