problem with import GPS data

[Rusalka]

I've just started working with ExifTool and first of all, thank you so much Phil for great tool and thank you Bogdan for GUI.

I have a problem with geotagging images from UAV.  Unfortunately, my images are not synchronized with log file (UAV flew too fast and couldn't register images so fast). In the result I have much more coordinates in log file than all images.

At first I used 'DateTime shift' to correct time of all images. Now, when images have the same time like in log file, I want to import GPS data from log file but I have a problem because my log file is not recognized by ExifTool. I tried to convert it to KML but it still doesn't work.

My log file looks like that:

   1 0001   18.721544   50.671879  149  25.21 22/04/2015 07:06:41  25.21    5.90    3.27 ypr

   1 0002   18.721664   50.672028  150  21.94 22/04/2015 07:06:42  21.94    7.33    1.26 ypr

   1 0003   18.721786   50.672173  149  28.36 22/04/2015 07:06:43  28.36    6.42    0.34 ypr

Meaning of columns: flight number E N H ? date time yaw pitch roll (? - I have know idea what it is)


Can anyone help me to sove thi s problem?

Thanks
Monika

[Phil Harvey]

Hi Monika,

Could the "?" be speed?  ... hmm.  probably not, the way it changes.  How about a measure of the distance to the ground?

What type of UAV is this?  I would add support for this format to ExifTool if other people could benefit from it.  If so, I'll need a few more details:  E and N are in degrees?  Are they negative for W and S coordinates?  H is metres or feet?  Relative to what (sea level or ground level)?  Y P R is degrees I assume.  Is Y a compass direction?  If so, what is zero (true north, or magnetic north)?  What direction is positive pitch and positive roll (ExifTool uses upwards and clockwise respectively for other devices).  Also, I would need a sample log file for testing.

- Phil

[Rusalka]

Hi Phil,

The log file is from Bramor gEO.

"?" - it is also yaw

Columns:
1. Number of flight
2. Number of image
3. Longitude (degrees, UTM84)
4. Latitude (degrees, UTM84)
5. Altitude (metres, ground level)
6. Yaw (degrees, compass direction). I don't know if it is true north or magnetic north.
7. Date
8. Time
9. Yaw (degrees)
10. Pitch (degrees)
11. Roll (degrees)

I send you a sample log file (also in kml format).

Thank you for help.
Monika

[Phil Harvey]

Hi Monika,

Doh.  I should have noticed the ? number was the same as yaw.  Silly.

OK, thanks.  I'll see about adding support for this to ExifTool 9.94, which I plan to release in 2 days.

The KML file won't work because the track points are not timestamped.

- Phil

Edit:  Ah.  Could it be the first yaw is the direction of travel, and the second one is the camera orientation?  I will go ahead and assume this unless I hear otherwise.

[Phil Harvey]

One more question:  Is the time in UTC, or local time?

Also, as I mentioned in my edit above, I will interpret the first yaw as the direction of travel, and the second yaw as the camera orientation unless you tell me otherwise.

- Phil

[Rusalka]

The time is in UTC.

I think that your assumption about yaw is correct.

Monika

[Phil Harvey]

Hi Monika,

Excellent, thanks.  I've implemented this already and it will be included in version 9.94, with Saturday as a target release date.

- Phil

[Rusalka]

Hi Phil,

Thank you for your help.

I've just tried a new version and it doesn't work. I'm sure that I did something wrong.

I used a command line: exiftool -geotag "c:\gps logs\test.log" c:\images

and I got warnings for all images:
Warning: Time is too far before track in File:Geotime (ValueConvInv) - c:/images
/DSC02383.JPG
Warning: No writable tags set from c:/images/DSC02383.JPG
Warning: Time is too far before track in File:Geotime (ValueConvInv) - c:/images
/DSC02384.JPG
...

What is wrong?

Monika

[Phil Harvey]

Hi Monika,

Add the -v2 option to your command to see the track start/end times and the image timestamp.  It is likely a timezone problem.  See Geotagging Troubleshooting point number 3 for more help here.

- Phil