Delivery

Map sheets, grids and field data delivery: why old references should not be removed

9 min read June 14, 2026

Modern map tools show continuous data, but sheet names, grid references and source codes still matter for traceability.

Field takeaways

TUCBS treats sheet subdivision and geographic grids as part of data organization.
Legacy sheet names, source codes and scale information should not be discarded.
Sheet information helps when archive data and modern survey data are combined.
DXF, KML, GeoJSON and CSV deliveries can carry sheet references as attributes or notes.
Good layers and notes preserve source memory.

Why sheet names still matter

Modern tools show continuous maps, but archive data, cadastral history and institutional delivery often still need sheet references. Do not delete legacy sheet names or source codes.

TUCBS grids

The TUCBS document describes geographic grids and sheet subdivision down through common map scales. This context helps when old archive data meets new field survey.

How to carry the information

Use DXF layers or notes, KML descriptions, GeoJSON properties and CSV columns to preserve sheet, source and scale information.

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

Is sheet information always required?

Not always, but it is valuable for archive and transformation work.

Where can it be stored?

In layers, notes, KML descriptions, GeoJSON properties or CSV columns.

What is the best field habit?

Keep old source data, new survey data and control points in separate layers.

Technical references

The field guidance in this article is aligned with the technical and official references below.