Lightroom: Inconsistent handling of suggested addresses

  • 5
  • Problem
  • Updated 3 months ago
  • In Progress
LR treats location fields (Sublocation, City, Country, etc.) that have been "suggested" by Address Lookup inconsistently -- while some parts of LR recognize the suggested values, other parts behave as if the fields are empty.  Smart collections, filters, and exporting of metadata recognize the suggestions. But Save Metadata To File, file renaming templates, and the SDK's photo:getFormattedMetadata() behave as if the location fields were empty.

These are bugs -- there's no sensible design rationale for the inconsistencies. All parts of LR should recognize the suggested address fields. The bugs were reported years ago in other topics but were buried in long threads:

https://feedback.photoshop.com/photoshop_family/topics/lightroom_improve_control_over_reverse_geocod...
https://feedback.photoshop.com/photoshop_family/topics/sdk_inconsistent_handling_of_uncommitted_loca...

The longstanding working around is to "commit" each location in each photo by clicking on the field's label in the Metadata panel.  Alternatively, the Any Tag plugin provides a command for batch-committing all fields in multiple photos at once.

To reproduce:

1. Drag a photo with no GPS coordinates and empty location fields onto some point in Map.

2. In Library, observe that that Metadata > Location shows the suggested address fields in grey font.

3. Do Metadata > Save Metadata To File and use Exiftool to observe that LR hasn't saved the location fields to the file's metadata (Sublocation, City, State/Province, Country, ISO Country Code).

4. Create a file renaming template "City Country":



Do Library > Rename Photo and observe that the new filename uses the empty string for City and Country.   

Export the photo using the export option Rename To: City Country; observe that the exported filename similarly uses the empty string for City and Country.

5. Use my free Show Catalog Metadata plugin to examine the results of the SDK's photo:getFormattedMetadata(). Observe that the fields "location", "city", "stateProvince", "country", and "isoCountryCode" return empty strings.

6. Make a smart collection to match City to the photo's suggested city:



(In this case, "Whitby".) Observe that the smart collection correctly matches the photo.

7. In the Metadata browser of the Library Filter bar, add the City column and select the suggested city of the photo. Observe that the photo is correctly matched and displayed.

8. Export the photo as a JPEG with the option Include: All Metadata and Remove Location Info unchecked.Use Exiftool to observe that the photo's metadata correctly includes the suggested values of the location fields.

Tested on LR 7.5 / Macos 10.13.6.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3870 Posts
  • 1023 Reply Likes

Posted 3 months ago

  • 5
Photo of John R. Ellis

John R. Ellis, Champion

  • 3870 Posts
  • 1023 Reply Likes
This reply was created from a merged topic originally titled Lightroom SDK: Inconsistent handling of uncommitted location fields.

The SDK provides plugins with inconsistent views of uncommitted location fields. catalog:findPhotos() accesses the uncommitted values of "location", "city", "state", and "country", wherease photo:getRawMetadata() returns the empty string for uncommitted values of those fields.

This makes it harder for plugins to return consistent results to users.
Photo of G0apher

G0apher, Employee

  • 37 Posts
  • 18 Reply Likes
Thanks, John for reporting this inconsistency - I agree the behaviour should be the same across. Could you please file a bug?
Photo of John R. Ellis

John R. Ellis, Champion

  • 3857 Posts
  • 1011 Reply Likes
I don't have access to the bug-reporting tool, so I won't be able to do it.
Photo of G0apher

G0apher, Employee

  • 37 Posts
  • 18 Reply Likes
ok. I have logged the same, and we will investigate a fix.