How to share and back up a MapLab Survey project file
Sharing and backing up field data is as important as collecting it. Project files, exports, photos and reports need structure.
Field takeaways
- Delivery folders should include project, date and CRS information.
- KML, DXF, GeoJSON and CSV serve different use cases.
- Photo to point relation should survive sharing.
- Backup should not wait until the end of the day.
- MapLab Survey helps organize project data and exports.
Project or export
If the recipient will keep working, they need the project, which carries layers, notes and photos. If they only need to review it or drop it into CAD, a clean export is smaller and easier to handle.
Before you send
Check the layer names and delete tests and drafts. What is obvious to you is noise to whoever opens it next.
Copy first, then share
Save a copy before sharing. A project that comes back edited by someone else should not overwrite yours. Use a fixed naming pattern with site, date, coordinate system and version number: files called "final" and "final 2" look clear the day they are made and become unsolvable months later.
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 is a MapLab Survey project shared?
Through export formats and reports depending on the job.
How should field data be backed up?
With project, exports, reports and photos together.
Should photos be sent separately?
Only if point relation is preserved.
Should CRS be written?
Yes.
Technical references
The field guidance in this article is aligned with the technical and official references below.
Related: Field data backup · Field delivery package · QGIS NetCAD AutoCAD export · MapLab Survey