Coordinate

TUCBS coordinate reference systems: EPSG, grids and a common delivery language

10 min read June 14, 2026

The TUCBS CRS document is not only for GIS specialists. It gives survey crews, contractors and data teams a shared language for datum, EPSG and grid information.

Field takeaways

TUCBS defines CRS using datum, ellipsoid, unit and EPSG-like attributes.
Horizontal CRS, vertical datum and grid information should be checked separately.
An EPSG code reduces ambiguity in delivery files.
Grid and sheet information matters in institutional data exchange.
Carry CRS and EPSG notes with MapLab Survey exports.

A shared CRS language

The TUCBS CRS and Geographic Grid document helps institutions describe geospatial data consistently. A delivery file should make datum, units, EPSG and grid context clear.

EPSG reduces guessing

Writing only "TUREF" is not enough. TUREF / TM30, TM33 and TM36 are separate CRS records. Add the EPSG code to file names or delivery notes where possible.

Horizontal and vertical references

Horizontal CRS and elevation reference are separate checks. GNSS ellipsoidal height is not automatically the orthometric elevation used in construction levels.

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

Why does TUCBS matter in the field?

It helps crews deliver CRS, datum, units, grid and elevation information consistently.

Is writing TUREF enough?

No. Add the zone and EPSG code.

What should exports include?

Source, date, EPSG, units and layer definitions.

Technical references

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