How to back up field survey data and prevent data loss
Field data without backup is almost as risky as data never captured.
Field takeaways
- Copy field files to a second location at the end of the day.
- Store exports with project names.
- Photos must keep point/layer relation.
- Use local backup offline and sync later.
- MapLab Survey project/export structure helps backup.
One copy is no copy
A day of fieldwork lives on one phone until you do something about it. Phones are dropped, stolen and wiped. Export at the end of each day and put the file somewhere that is not the same device.
Export in a format you can still read
Keep the project file for continued work, but also export a neutral format such as CSV, GeoJSON or DXF. Application formats change between versions; plain formats stay readable.
Name it so it survives
Include the site, the date and the coordinate system in the filename. A backup you cannot identify is only marginally better than no backup, because nobody trusts a file they cannot place.
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
When should field data be backed up?
Before leaving and during long days.
Which files?
Project, exports, reports and photos.
Can backup work offline?
Yes, locally.
Can photos be separate?
Yes, if links/context are preserved.
Technical references
The field guidance in this article is aligned with the technical and official references below.
Related: Offline maps · Field delivery package · Measurement report · MapLab Survey