Coordinate

TUREF, UTM, ITRF: how to choose the right coordinate system in Türkiye

A good field point is not enough. The reference frame, zone and units matter just as much. Modern work in Türkiye commonly uses TUREF-based projected coordinates, while older archives may still contain ED50.

Field takeaways

  • A coordinate reference system is more than a projection name; datum, ellipsoid, units and EPSG code matter.
  • TUCBS lists TUREF/TM27 to TUREF/TM45 as EPSG:5253 to EPSG:5259.
  • 3-degree Gauss-Kruger zones are separate records, listed as EPSG:5269 to EPSG:5275.
  • ED50 to TUREF is not a casual shift. Transformation quality depends on method and control.
  • Keep the EPSG code with MapLab Survey exports to reduce CAD/GIS placement errors.

Datum and projection are not the same thing

Asked "which coordinate system?", the field answer is usually one word: TUREF, UTM, ED50, TM33. Technically the package is fuller — in the TUCBS registry the datum, ellipsoid, unit and EPSG code travel together. TUREF and ED50 belong to the reference side; TM and UTM to the projection side. "The coordinates are right but the file opens in the wrong place" is almost always a CRS problem, not a measurement problem.

Why TUREF matters in Türkiye

Modern large-scale map production in Türkiye runs on TUREF-based systems, with GNSS tied to the national frame through TUTGA and TUSAGA-Aktif. The receiver gives a position; the specification usually demands "TUREF, this zone, metres". Write the datum, zone, EPSG and height reference down before starting, then test the first measurement on a known point.

The zones go from TM27 to TM45

TUCBS lists TUREF / TM systems with central meridians every three degrees from 27 to 45 — EPSG:5253 through EPSG:5259. Writing "TUREF" alone is not enough: TM30 and TM36 both look like metres, and the same point gets different plane coordinates in each. The same data in the wrong zone shifts by metres.

UTM is not 3-degree Gauss-Kruger

UTM works in 6-degree zones, while much local production in Türkiye uses 3-degree slices; TUCBS lists those zones separately as EPSG:5269 to EPSG:5275. One crew says "3-degree", another "TM33", a third assumes WGS84 — the argument ends when the delivery note carries an explicit EPSG code.

The ED50 trap

Old sheets, municipal archives and legacy point lists often live in ED50, and moving them to TUREF is not one constant shift. HGM's ED50-TUREF study shows the result depends on the method and the control point distribution. On critical work use the authority's transformation or shared control points — the archive sheet's own quality can outweigh the transformation.

The practical rule

Separate the sources first: new GNSS measurement, old ED50 base, an institutional TM project, a KML for Google Earth. Keep the datum, zone, unit and height reference in the filename and delivery note of every export — and do not go into production without a control point. One point in the right place is encouraging; two inside tolerance is confidence.

In the field · MapLab Survey

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 EPSG codes?

They identify the CRS more clearly than a name alone.

Are TUREF and WGS84 the same?

They should not be treated as identical in precise work.

What is EPSG:5254?

It is TUREF / TM30 in the TUCBS record.

How should ED50 be handled?

Use known transformation parameters, reliable shared control or an official workflow.

Share this article WhatsApp Telegram LinkedIn

Related: ED50 to TUREF · Transformation report · TUCBS CRS · MapLab Survey