AbsoluteAltitude is also bad, often equal to 1.2. The RelativeAltitude provides the barometric altitude difference between the actual position and the take-off position. However, DJI uses two other tags for altitudes: RelativeAltitude and AbsoluteAltitude. The GPSAltitude tag is also buggy, sometimes it appears as a very large negative number. It can list all tags with the exiftool -listg command.Ģ. These Latitude/Longitude tags are unusual, we don't see them normally, they seem to be in excess and are nor found by some EXIF tools. The problem is that neither Pix4D or Photoscan read Latitude/Longitude, they use GPS-prefixed ones. However, the Latitude/Longitude tags are ok. It looks that some of the GPS-prefixed EXIF tags are incorrect, I don't know why. DJI records Latitude and Longitudes at two different EXIF tags IDs (!): GPSLatitude/GPSLongitude and Latitude/Longitude. Here is what happens and the solution I found:ġ. Having had the same problem as everybody and knowing that DJI is not looking into it seriously, I have finally solved it, not without serious work on the image files themselves.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |