Layer use in the field: keeping survey, parcel, photo and design data separate
Field data quality depends on layers, not only coordinates.
Field takeaways
- Keep parcel reference, measured detail and design in separate layers.
- Photos and notes carry field decisions to the office.
- Do not mix target and staked points.
- Layer names should be short and meaningful.
- MapLab Survey supports layered delivery.
Layers turn measurements into a project
Separating features by type is what lets you show, hide, style and export them independently later. Everything captured into one layer has to be sorted by hand in the office.
Name them for the recipient
Use names that mean something to whoever opens the file, not abbreviations that made sense in the field.
Reference layers stay separate
Keep imported parcel boundaries, plans and previous surveys in their own layers, clearly distinct from what you measured today. Mixing the two is how a reference line ends up quoted as a survey result.
Decide the structure before you start
Restructuring layers after two hundred features is slower than planning them in five minutes beforehand.
See it in action
MapLab Survey | Professional Mobile GIS, GPS Surveying & Land Measurement App
Visit the YouTube channel ->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
Why use layers?
To preserve meaning and reduce office confusion.
Should parcel and measured data share a layer?
Preferably no.
Should targets and staked points be separate?
Yes.
Do layers help DXF?
Yes.
Technical references
The field guidance in this article is aligned with the technical and official references below.
Related: GIS data collection · Point line polygon · NetCAD QGIS AutoCAD export · MapLab Survey