Delivery

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.

Purpose

A report is the memory of the measurement. It explains how the point was obtained and how it can be checked later.

Header

State project, date, crew, receiver, antenna, correction source, CRS, datum, zone and height reference.

Point table

Include point name, E, N, Z, antenna height, solution status, control residuals, notes and photos where relevant.

Delivery

MapLab Survey can keep layers, notes, photos and exports together so the office can read the report and open the data in CAD/GIS.

In the field · MapLab Survey

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 Survey

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.

Related: Field survey checklist · RTK GNSS field accuracy · Stake-out report · MapLab Survey