photools.com Community

Will this same fix also correct the apparent bug with the Longitude setting?  In my current files, anytime I process a Metadata Write-Back for a file it appears the existing directional coordinate is being changed to an incorrect heading.

For example,

• Original Longitude = 123 deg 57'49.47" W
  
• Adjusted Longitude = 123 deg 57'49.47" S
  

Quote from: Nyet_Banya_2 on October 03, 2023, 03:03:22 PMWill this same fix also correct the apparent bug with the Longitude setting?  In my current files, anytime I process a Metadata Write-...

This seems to be something different and was not reported before (except for a post that might mention this from today).
I'll make this a separate bug report.

Under which condition does this happen?

I enter lat=34.5 and lon=-118.5 for a file.
The formatted values are 34 deg 30' 0.00" N and 118 deg 30' 0.00" W, which is correct.
I write back the file and the coordinates stay the same in the database.
Checking the coordinates in the file shows the same result:

[GPS]          GPS Longitude Ref              : West
[GPS]          GPS Longitude                  : 118 deg 30' 0.00"
[XMP-iptcExt]  Location Created GPS Longitude  : 118 deg 30' 0.00" W
[XMP-drone-dji] Longitude                      : 118 deg 14' 33.51" W
[XMP-exif]      GPS Longitude                  : 118 deg 30' 0.00" W
[Composite]    GPS Longitude                  : 118 deg 30' 0.00" W
[Composite]    GPS Longitude Ref              : West
and using the -n parameter to output numeric values:
[GPS]          GPS Longitude Ref              : W
[GPS]          GPS Longitude                  : 118.5
[XMP-iptcExt]  Location Created GPS Longitude  : -118.5
[XMP-drone-dji] Longitude                      : -118.242643
[XMP-exif]      GPS Longitude                  : -118.5
[Composite]    GPS Longitude                  : -118.5
[Composite]    GPS Longitude Ref              : W
I move the pin of the file in the Map Panel to update lat/lon and write-back.
Again, the longitude remains W (-118...) and does not switch.

Maybe this is something I have fixed already for the new release or there is something specific I have to do to reproduce this?

Hi Mario,
Indeed, looks same as the issue I spoke about earlier (13621). (https://www.photools.com/community/index.php/topic,13621.0.html)

Attached a zipped CR2 image that resides in my database for years, without changes to GPS data. When *displaying* data formatted, it shows wrong Longitude and Altitude. XMP and variable show correct settings.

I will send the CR2 file to your support mail address (if that can help). Note: in 2023.2 this was not an issue

ger

Thanks for sending the sample file.
I could not reproduce the problem with the upcoming release so it appears to be fixed.

IMatch shows this for your CR2 file:

Image1.jpg

which matches the coordinates in the file (raw and formatted).

If you experienced this issue, it is sufficient to select the affected files and press Shift+Ctrl+F5 and select the "Reload Metadata". If the file is pending, write back before.

Thanks Mario, eagerly looking forward to the update...

Quote from: Ger on October 03, 2023, 06:10:10 PMThanks Mario, eagerly looking forward to the update...

IMatch 2023.3.4 has been released a few minutes ago. Enjoy!

Mario,
I installed 2023.4 and the database seems to be ok again.

Steps taken
- Writeback pending metadata (solving 13621) (https://www.photools.com/community/index.php/topic,13621.0.html)
- Database Tools > Database Diagnostics: all errors disappeared
- Identified all images with wrong longitude display value. Reload metadata
- this caused a lot of files pending writeback (InstanceID, Creatertool values)
- Writeback pending metadata
- Database Tools > Database Diagnostics: no errors
- Database Tools > Database Optimize

Seems we're back in business again!

Thanks!

Very good! Thanks for the feedback.

Quote from: Mario on October 03, 2023, 03:29:49 PMUnder which condition does this happen?

Maybe this is something I have fixed already for the new release or there is something specific I have to do to reproduce this?

The latest update-- IMatch 2023, Version 2023.3.4 -- properly fixed the longitudinal problem I was experiencing.  Thank you.

Very good. Thanks for the feedback.