Lightroom classic (13) custom name City metadata not exported

[rodlaird]

All my photos are GPS tagged and show the LR lookup location information. I wish to export files with "City" as part of custom name. This does not work.

I think there was an issue in the past where LR, despite having the location data resolved from the GPS and allowing its use in search, could not access this for manipulation.

J Friedl put together a metadata wrangler to handle this - but it is not available for current LR versions.

How am I supposed to use location hased information in custom text. The function is there to include this metadata - it should work surely.

Any work-around appreciated. (And no, I am not going to manually type in the location metadata...)

cheers

________________

Windows 11 current version. Latest LR 13

[johnrellis]

There's a long-standing bug where location fields that have been suggested by address lookup, which appear grey italic in the Metadata panel, aren't available to file-renaming templates. See the two workarounds in the third paragraph of this bug report:

https://community.adobe.com/t5/lightroom-classic-bugs/p-inconsistent-handling-of-suggested-addresses...

[johnrellis]

"J Friedl put together a metadata wrangler to handle this - but it is not available for current LR versions."

The plugin is still available and should work with LR 13.3. But note that Google Chrome and Friedl's web site have been arguing in recent years. You need to access Friedl's web site with an HTTP URL, not HTTPS, e.g. 

    http://regex.info/blog/lightroom-goodies/metadata-wrangler

Right now, when I copy and paste that URL, it works fine in Firefox but not Chrome.  

[rodlaird]

Ah! Did not spot the problem with Jeffrey's site. That I think is the best solution 😉

Thanks for the guidance

[rodlaird]

p.s. I misquoted the  Friedl plugin that applies for those interested in this problem. It is

Jeffrey Friedl's Blog » Jeffrey’s “Geoencoding Support” Plugin for Lightroom (regex.info)

I had it installed, but not updated, and had hoped LR had "fixed" the problem. But JF's plugin handles this problem automatically and perfectly. Just a pain that it is necessary at all!