Drone data

Drone photo metadata, and what goes wrong with it

Your drone wrote more into each photo than the picture. These guides read what is there and what it means when it is missing, wrong or not what your processing software assumed. Every one ends with your own files open in the browser.

Guides

Export drone photo positions to KML, CSV or GeoJSONThree one-click exports from your own images, what each file actually contains, and the traps on the way in.Your drone photos have no GPSWhich of your images actually lost their coordinates, what the pattern tells you, and what fixes each cause.RTK fixed, float or none: reading the flag out of your own imagesWhat RtkFlag 50, 34 and 16 mean, and how to count how many of your images actually held fix.Your map is in the wrong place: the drone, the datum, or the basemap?Diagnose a shifted orthomosaic from the size, uniformity and direction of the offset.

The tools these end at

The metadata viewer reads EXIF and XMP from a whole folder at once: GPS, RTK and PPK status, the three altitude fields, gimbal angles, camera settings and per-image ground sampling distance. It plots the positions on a map and exports them as CSV, KML or GeoJSON. The files are parsed in your browser and never uploaded.

The Map Lab takes the same dataset further: images, ground control points and the flight path on one map, so a gap in coverage or a cluster of dropped geotags is visible rather than inferred.

Where the problem turns out to be a coordinate system rather than the aircraft, the coordinate systems guides carry that side of it - datums, zones, and why heights are the error that survives review.