Timeline for Georeference single drone image from EXIF data
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21, 2022 at 0:45 | comment | added | Houska | @Khaled, I’m traveling and don’t have my notes, but I believe I felt the same as you from the definitions but either my DJI Spark or Mavic Mini didn’t populate it or populated incorrectly. One of the frustrations is the lack of standardization of drone EXIF tags (as well as sensor diameter meaning etc). Will need to check live on your drone. | |
| Aug 19, 2022 at 22:56 | comment | added | Khaled | @Houska could you please explain why did you choose FlightYawAngle from EXIF and not GimbalYawAngle. My understaining: the camera is mounted on gimbal and the gimbal yaw angle is independant from drone itself, it is positive angle clockwise varying from -180 to 180 degrees from North but which North, magnetic or geographic like the one used on maps, no idea. | |
| Oct 13, 2021 at 13:47 | history | edited | Houska | CC BY-SA 4.0 |
Explain what I meant
|
| Aug 19, 2021 at 14:38 | comment | added | Houska | I thought about it briefly, but ran out of steam/interest before thinking too much. Adjusting for terrain via a single point, whether the drone position or an approximation of the centre of the image, shouldn't be too hard. Reflecting the differences in the DEM across the image, e.g. if one corner is higher than another, would be a hassle. | |
| Aug 19, 2021 at 8:08 | comment | added | dmjf08 | Thank you for sharing the results of your work. I used it for an Android project and I'm interested in integrating a DEM to have a more correct projection of the image. Have you thought about it ? | |
| Apr 2, 2021 at 10:48 | vote | accept | Houska | ||
| Mar 4, 2021 at 23:57 | history | answered | Houska | CC BY-SA 4.0 |