LocationInfo Filelist (Google Pixel Pro 7)

[Philshappy]

Is there a reason why the LocationInfo columns is not always showing the updated Country and State. The two screenshots show the metadata is present in both photos but not displayed in the LocationInfo. If I create a custom user than the info is show in both. Attached are screen shots showing the LocationInfo columns and the metadata.

Version 6_30 is awesome. Thanks!

[FrankBijnen]

What are the filetypes?

Background: If you select 'LocationInfo' then GUI tries to read the data directly from the file, and it does not use ExifTool to speed things up. In the Metadata panel and the 'custom user' you see ExifTool generated data. But GUI knows only how to read a few filetypes, compared to ExifTool.

Possible workaround: Preferences/Other Check 'Filelist: Enable Camera Settings, Location info and About Photo for all file types.

[Philshappy]

All file are jpg. The files but 2 different cameras, Canon PowerShot G9 X Mark II shows the location data, Pixel 7 Pro does not. The workaround did not fix it. Its not a problem for me I can use the custom user, just thought you might want to know and possible look into it for a future release. Also, I really like the custom user list so maybe add the ability to have 2-3 custom lists like the workspace which allows more than 1.

---

From: FrankBijnen @.> Sent: Saturday, March 16, 2024 1:42 PM To: FrankBijnen/ExifToolGui @.> Cc: Philshappy @.>; Author @.> Subject: Re: [FrankBijnen/ExifToolGui] LocationInfo Filelist (Issue #356)

What are the filetypes?

Background: If you select 'LocationInfo' then GUI tries to read the data directly from the file, and it does not use ExifTool to speed things up. In the Metadata panel and the 'custom user' you see ExifTool generated data. But GUI knows only how to read a few filetypes, compared to ExifTool.

Poosbile workaround: Preferences/Other Check 'Filelist: Enable Camera Settings, Location info and About Photo for all file types.

— Reply to this email directly, view it on GitHubhttps://github.com/FrankBijnen/ExifToolGui/issues/356#issuecomment-2002124440, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDSLPUXYFJ2UMXUUCMD5TZ3YYSVC7AVCNFSM6AAAAABEZRZRBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGEZDINBUGA. You are receiving this because you authored the thread.Message ID: @.***>

[FrankBijnen]

Ah.It seems file type related. Would you mind sharing a Pixel Pro 7 sample?

And I would like to know how did you update the City, Country etc?

This form? and what were your parms?

[Philshappy]

Default was the settings when I first noted the issue.

Changed is the settings changed to match your email.

The other screen shot is the geotag results.

To determine the location I used your tool, since the photo already had the geolocation, i clicked show on map, then geotag.

I also included the photo.

---

From: FrankBijnen @.> Sent: Saturday, March 16, 2024 2:03 PM To: FrankBijnen/ExifToolGui @.> Cc: Philshappy @.>; Author @.> Subject: Re: [FrankBijnen/ExifToolGui] LocationInfo Filelist (Issue #356)

Ah.It seems file type related. Would you mind sharing a Pixel Pro 7 sample?

And I would like to know how did you update the City, Country etc?

This form? and what were your parms? a.jpg (view on web)https://github.com/FrankBijnen/ExifToolGui/assets/63312605/e4738a86-b1a2-495f-8c66-bcf241180ada

— Reply to this email directly, view it on GitHubhttps://github.com/FrankBijnen/ExifToolGui/issues/356#issuecomment-2002131347, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDSLPUVJCT5WHILWXMZ33UTYYSXQ5AVCNFSM6AAAAABEZRZRBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGEZTCMZUG4. You are receiving this because you authored the thread.

[FrankBijnen]

Sorry, but I see no screenshots, nor image. If you reply by email, Github removes all attachments,

Still no idea what's going on. Some more questions.

• So you did not use 'Modify/Update City etc..', but you used the 'Geotag files' button?
• And what was the provider you did choose? 'ExifTool', Overpass or Geocode?
• Can you do it again and first open the log Window. You can send the commands, output and errors as text.
• Oh and very important. Did it work in the previous version?

Thanks in advance, Frank

[Philshappy]

This was the settings when i noted the issue.

This is the settings after you sent me an email and I changed it to match yours.

They produced the same results.

This is the geotag results.

To determine the location I used your tool, since the photo already had the geolocation, i clicked show on map, then geotag.

This is the photo.

[Philshappy]

So you did not use 'Modify/Update City etc..', but you used the 'Geotag files' button? Correct

And what was the provider you did choose? 'ExifTool', Overpass or Geocode? Both Exif and overpass, same results

Can you do it again and first open the log Window. You can send the commands, output and errors as text. Will do.

Oh and very important. Did it work in the previous version? No it did not

[Philshappy]

-echo4 {ready17} -CHARSET FILENAME=UTF8 -CHARSET UTF8 -v0 -overwrite_original -sep -m -c %.6f° -API WindowsWideFile=1 -a -Gps= --GPSversion* -GPS:GpsLatitudeRef=N -GPS:GpsLatitude=40.607575 -GPS:GpsLongitudeRef=W -GPS:GpsLongitude=111.483303 -QuickTime:GPSCoordinates='40.60757, -111.4833, 0' -xmp:CountryCode=US -xmp:Country=United States -xmp:State=Utah -xmp:City=Park City -xmp:LocationShownCountryCode=US -xmp:LocationShownCountryName=United States -xmp:LocationShownProvinceState=Utah -xmp:LocationShownCity=Park City -xmp:LocationShownSublocation= PXL_IMG1.jpg -execute17

[Philshappy]

It appears that the tool is saving the correct data, as i can see it in the metadata and my custom user filelist.

[Philshappy]

It appears that the tool is saving the correct data, as i can see it in the metadata and my custom user filelist.

[FrankBijnen]

Thanks a lot. I'm able to reproduce it now, with the picture you sent. Will dive into it.

[FrankBijnen]

@Philshappy I have uploaded a patched version to my onedrive. https://1drv.ms/f/s!AhVJC-QzM33pknOS7KwBi09lgNql?e=n7ztFX

Can you confirm that that works? (You will need to check Preferences/Other Check 'Filelist: Enable Camera Settings, Location info and About Photo for all file types.)

Frank

[Philshappy]

Yes it worked after enabling Preferences/Other Check 'Filelist: Enable Camera Settings, Location info and About Photo for all file types.

[Philshappy]

Just curious why the canon photos worked fine but the pixel photos did not. Are you planning to release this fix now or wait, should I just keep using the patched version.

[FrankBijnen]

Very good news that it works now! Thanks for confirming.

Planning:

• At the moment I dont want to release a new version. You can keep using the patched versions.
• I will commit the changes to Github, close the issue. Will be available in a next release.
• Your remark about saving the custom filelist settings I will not forget. I will add it to an existing issue. https://github.com/FrankBijnen/ExifToolGui/issues/351 Also next release
• Non technical reason: Now that spring has arrived I want to slow down with GUI development anyway.

Explanations:

• The Pixel 7 pro stores the 'XMP data' differently. (It looks encrypted to me) Good news is that ExifTool knows how to handle it.

• As explained earlier GUI tries to read the data directly from the file, to speed things up. If it finds that it can not handle the file the method that does that returns 'Unsupported' and GUI calls upon ExifTool to get the data.

• For the data in 'Location Info', you need the info from 2 groups: ExifIFD and XMP. ExifIFD can be read by GUI.

• There were 2 things that went wrong in GUI.

• 1) In the case that XMP data could be read, but was 'encrypted', the method still returned 'Supported'.

• 2) GUI only checked for ExifIFD=supported, and not for XMP=supported, and failed to call upon ExifTool.

Note: the column 'GPS' was correctly displayed, that info comes from ExifIFD

Frank

[FrankBijnen]

@Philshappy

Just one more remark I kept forgetting to make. In one of your screenshots I saw that you use ExifTool Version 12.77. To use the 'Exiftool geocode provider' you need ExifTool Version 12.79.

[Philshappy]

Thanks for explaining it. GUI was using Exiftool 12.79 and not 12.77 I am guessing that 12.77 was used earlier and somehow got recorded in the metadata, maybe when I first updated the location data.

---

From: FrankBijnen @.> Sent: Sunday, March 17, 2024 4:47 AM To: FrankBijnen/ExifToolGui @.> Cc: Philshappy @.>; Mention @.> Subject: Re: [FrankBijnen/ExifToolGui] LocationInfo Filelist (Issue #356)

@Philshappyhttps://github.com/Philshappy

Just one more remark I kept forgetting to make. In one of your screenshots I saw that you use ExifTool Version 12.77. To use the 'Exiftool geocode provider' you need ExifTool Version 12.79.

— Reply to this email directly, view it on GitHubhttps://github.com/FrankBijnen/ExifToolGui/issues/356#issuecomment-2002425889, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDSLPUWBRX7E6Y22ZJ3XSLTYYV7G3AVCNFSM6AAAAABEZRZRBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGQZDKOBYHE. You are receiving this because you were mentioned.Message ID: @.***>

[FrankBijnen]

OK. Must be my age.

But the story is not over yet! I couldn't let go and wanted to know why ExifTool was able to read the XMP. As it turns out in your sample there a 3 XMP sections. 1st = a 'normal' section. 2nd and 3rd are 'extended'. What I described earlier as encrypted.

What GUI did was read the last section, and it couldn't cope with that. I have changed the code to check for the 'type of the XMP' and it now reads the 1st and skips the other 2. For an end-user may be not that interesting, but the advantage is that it processes the file(s) much faster, and you dont need to enable the checkbox in Preferences

Will be in a next release, and thanks for your help! Frank

[Philshappy]

I have also noted that some of the XMP metadata is unique to the maker and therefore I have used the '' in front of the command to find it or modify it. For example the metadata CanonTimeZone:TimeZone is unique to Canon or NikonTimeZone:TimeZone is unique to Nikon so now when saving to workspace I save -:TimeZone and it finds either of them.