How to prepare a field delivery package
After field measurement, the real value is a delivery package that others can understand.
Field takeaways
- Delivery should state CRS and data source.
- KML, DXF, GeoJSON and CSV serve different users.
- Photos and notes preserve context.
- Layer names should be meaningful.
- MapLab Survey exports multiple formats from one project.
Ask what they will open it with
The right package depends entirely on the destination software. Agree the format before the fieldwork, not after.
Include the metadata
Coordinate system, date, method, equipment and who did the work. A delivery without these creates a round of questions that costs more than writing them.
Clean before you send
Remove test features and drafts, and give layers names that mean something outside your own head.
Include a readable summary
One page describing what was measured, what was checked and what the known limitations are. It is the part most people actually read, and it prevents the data being used for something it cannot support.
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
What should delivery include?
Report, CRS note, export files and photos.
KML or DXF?
KML for viewing, DXF for CAD.
Why CSV?
For point table checks.
Can MapLab Survey help?
Yes.
Technical references
The field guidance in this article is aligned with the technical and official references below.
Related: Measurement report · Field layers · NetCAD QGIS AutoCAD export · MapLab Survey