MAPS

MRK → GGRS87 (ΕΓΣΑ87)

DJI camera positions · HEPOS times and check for PPK · point conversions
© MAPS
MAPS tools
version 2.6-web
HEPOS 7 param. + grid + GEOID_GR
ΕΛ

Flights folder (searches all subfolders) — files are not uploaded anywhere; only your browser reads them

or drag the folder here
No folder selected
Files for:
Min. accuracy (m) σH σV Other RTK network shift (m): dE dN dH
Loading grids…
–Photos
–FIX
–Reduced accuracy
–No position

Flights folder — same as the Drone tab (reads times only) · you can also drag it here

No folder selected
Flight (folder)DateStartEndDur.ShotsDrone receiver (.OBS)
–
DOWNLOAD FROM HEPOS
–
Choose a folder and press “Read times”.
Margin ±' rate s

1 · HEPOS base files you downloaded (.zip / .gz / .??o / .rnx) — checks that they cover the whole flight · choose or drag them here

2 · PPK processing

PPK processing (RTKLIB engine) runs in the Windows program MAPS_MRK_to_EGSA87.exe (in Greek), tab “PPK · HEPOS”, step 2. A browser cannot run RTKLIB.

Points (name, x, y, z) — from a file (choose or drag it here) or paste. Comma, semicolon, tab or spaces.

From → To
e.g. GGRS87 ground control points → UTM 34N for Terra (h = H + geoid). x/y columns are also recognised when swapped (N, E or λ, φ).

What it does

Converts DJI camera positions (.MRK) to GGRS87 with the model of HEPOS (the Greek GNSS reference network): HTRS07 → 7 parameters → TM87 → grid correction δE/δN, and orthometric height H = h − N (GEOID_GR). Same code as the Windows program, tested to produce exactly the same files.

Drone · MRK

  • Choose the folder with all your flights (e.g. “DJI PHOTOS”). It finds every .MRK in the subfolders and matches each record to its photo (shot number + time).
  • The MRK φ, λ, h are already the sensor centre (CMOS) — no antenna offset is needed. The EXIF holds the same values.
  • FLOAT/SINGLE shots or shots with a position jump get a large uncertainty; 1–2 bad shots are corrected by interpolation from the neighbouring FIX shots.
  • Photos with no MRK record take their position from the EXIF (error 5 m / 30 m), so they are not lost.
  • Chrome / Edge: asks for edit permission and writes the results inside the folder, like the exe. Firefox: the results download as one ZIP (and one by one from the buttons).
  • Other RTK network shift: if you flew with another network (e.g. SmartNet), the difference (HEPOS − other) at a known GGRS87 point.

Output files

  • _EGSA87.txt: name, E, N, H, σH, σV (for any software) · _Pix4D.csv: Image → From File “X, Y, Z” · _Metashape.txt: Reference → Import, EPSG:2100 · _3DSurvey.txt: Import camera positions (TAB) · _Terra_WGS84 / _Terra_UTM34: positions for DJI Terra with ellipsoidal h.
  • _report.csv: detailed report per shot · _map.html: map of the shots · _PPK_times_HEPOS.txt: which hours to download.

PPK · HEPOS

  • “Read times” → date, times (Greek time and UTC), hourly files, DOY and the HEPOS form: Date as month/day, Start in GPS time, Duration, Interval and the VRS position at the centre of the flight.
  • In HEPOS: VRS at the centre of the flight, RINEX 2.11, rate 5 s.
  • “Base files” checks that the RINEX files you downloaded cover the whole log of the drone receiver. Processing runs in the exe.

Points

  • Any direction between WGS84 φ,λ,h · UTM 34N · UTM 35N · GGRS87 (E, N, orthometric H). In WGS84/UTM, h is ellipsoidal.
  • e.g. the field crew’s GGRS87 X,Y,Z ground control points → UTM 34N for import into Terra.

Only in the Windows program (MAPS_MRK_to_EGSA87.exe, in Greek)

  • PPK processing (RTKLIB)
  • Conversion of Terra results to GGRS87: LAS/LAZ point clouds, XYZ, DXF, orthophoto maps/DSM GeoTIFF
  • Contour lines from LiDAR L2 / DTM

These process files of many GB and need executables; in a browser they would be slow or impossible.