View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000964||GeoSetter||Image Data||public||2012-07-07 19:27||2012-07-08 20:58|
|Status||resolved||Resolution||no change required|
|Product Version||3.4.16 beta|
|Target Version||Fixed in Version|
|Summary||0000964: Incorrect altitude being picked from GPS track log|
|Description||I am using version 4.4.16 (build 2119).|
When trying to geotag NEF files from a GPX tracklog generated by BT747, the altitude is tagged incorrectly.
Altitude is being stored as a negative value (which in itself is not a problem) but the value is also incorrect. I have converted the GPX tracklog to csv to make sure that the numbers are different.
|Additional Information||Attached is a screenshot of the altitude tagged in Geosetter, a jpg conversion of the NEF file, the GPX and corresponding CSV file with the tracklog.|
|Tags||altitude, BT747, NEF|
Geosetter Matis Report.zip (1,972,048 bytes)
Perhaps I am doing something horrible wrong... This is the first time that I use Geosetter. Apologies in advance if that is the case.
Just bought my first GPS logger and am just getting into the world of geotagging my photographs.
Excellent program btw. Kodus and many thanks!
||The altitude value of -8,6 m is correct. The taken time is 18:06:57; I assume that this time is CESZ. A GPS logger always is using UTC time. Therefore you have to look in your GPX file for the time 16:06:57. There you will see that the altitude ist -8,6m (see attached picture)|
Mantis964.png (1,834,087 bytes)
||You are correct, the time is CET. Looking at the raw logger data from the csv file, the heights are all above 30m for the time period between 16:05 to 16:07 (see attached picture).|
Heights.png (231,921 bytes)
Heights.png (231,921 bytes)
I've just looked into the GPX file itself, and the altitude is -8,6m. Here is the data of the trackpoint:
<trkpt lat="55.690304" lon="12.598939" >
This is the value for the altitude: <ele>-8.6</ele>, and the data is -8,6. I don't know how you've created the CSV file, but I assume the data is wrong.
Just did some digging into the software that exported the GPX and CSV files. The GPX file elevation is corrected from WGS84 to MSL which is why there is a difference.
Thanks for the assistance; MSL elevation is what I am looking for. Geosetter is doing precisely what it should.
||BTW, GeoSetter can correct the altitude values. Select all images where altitude values should be corrected. Then select "Edit | Edit Data" and select the Tab "Location". Here press the button "Get All from Web" in the section Altitude. Doing this, GeoSetter querys the altitude values from GeoNames.org. In your example the altitude will be 3,0m.|
Noted, thanks. I shall probably end up using the built in feature in Geosetter as you suggest. But first I plan to take my phone to the same spot where the photograph was taken to double check the elevation. -8,6 seems too low since I was standing at a height overlooking the harbour by about 3-4 meters.
Perhaps my GPS logger is not recording data accurately.
Please close the bug ticket. I don't see any way for me to do it.
|2012-07-07 19:27||henrymuppet||New Issue|
|2012-07-07 19:27||henrymuppet||File Added: Geosetter Matis Report.zip|
|2012-07-07 19:29||henrymuppet||Tag Attached: altitude|
|2012-07-07 19:29||henrymuppet||Tag Attached: BT747|
|2012-07-07 19:29||henrymuppet||Tag Attached: NEF|
|2012-07-07 19:31||henrymuppet||Note Added: 0001801|
|2012-07-07 22:16||heiko||Note Added: 0001802|
|2012-07-07 22:17||heiko||File Added: Mantis964.png|
|2012-07-07 22:25||henrymuppet||Note Added: 0001803|
|2012-07-07 22:25||henrymuppet||File Added: Heights.png|
|2012-07-07 22:53||heiko||Note Added: 0001804|
|2012-07-07 23:11||henrymuppet||Note Added: 0001805|
|2012-07-07 23:24||heiko||Note Added: 0001806|
|2012-07-08 16:46||henrymuppet||Note Added: 0001808|
|2012-07-08 20:58||heiko||Status||new => resolved|
|2012-07-08 20:58||heiko||Resolution||open => no change required|
|2012-07-08 20:58||heiko||Assigned To||=> heiko|