6.3. Camera positions converter

Writes the camera (photo) positions of a DJI flight in the format a photogrammetry package imports, in EGSA87 or WGS84, with or without accuracies.

6.3.1. Source

DJI PPK result: cameras_EGSA87_full.csv from the DJI PPK tool. It holds both EGSA87 and WGS84 positions. (The short cameras_EGSA87.csv has no WGS84 columns and can only give EGSA87.)
Drone MRK file: The drone’s own on-board RTK positions from the flight folder’s .MRK, for flights flown with network RTK and not post-processed. For EGSA87 output choose the transformation and geoid: with HEPOS network RTK use HEPOS and the HEPOS geoid. On the reference flight these positions came within a few centimetres of the PPK result.

6.3.2. Formats

Format	File
Agisoft Metashape	`#Label,Easting,Northing,Altitude` and `Accuracy_X/Y/Z` (WGS84: Longitude, Latitude). Import with Reference > Import and set the columns and the coordinate system (EPSG:2100 or WGS84).
Pix4D	`Image name,X,Y,Z,Accuracy Horz,Accuracy Vert` (WGS84: Latitude, Longitude, Altitude). Import as the image geolocation file.
RealityCapture	`Name,X,Y,Alt` / `Name,Lat,Lon,Alt`, a flight log; no accuracies.
OpenDroneMap (geo.txt)	First line `EPSG:2100` or `EPSG:4326`, then `name x y z` (WGS84: longitude first); no accuracies (ODM only takes them together with camera angles).
Generic CSV	`photo,E,N,H,sdE,sdN,sdH` / `photo,lat,lon,h_ell,...`

Heights: EGSA87 output has the orthometric H (as cameras_EGSA87.csv), WGS84 output the ellipsoidal h. Set the photogrammetry project’s vertical reference to match.

6.3.3. Options

Write accuracy columns, at least (m) – the per-photo standard deviations, each raised to at least this value. RTKLIB’s and the drone’s own values are optimistic (a few mm); 0.01-0.02 m keeps the photogrammetry adjustment from treating the cameras as fixed.
Only fixed positions – leaves out photos whose position is float or single.

The preview shows the first 300 lines; Save as writes the file (default name and folder next to the source).