Creation of catalog place labels from IPTC location fields

[lnh]

I'm trying to develop a new workflow which includes geocoding/reverse geocoding by first using Geosetter before importing the files in PS.

Geosetter first geocodes lat/long and reverse geocode location info into the IPTC fields (Country Name, State, City ...). I then import the files into PS, and indeed the lat/long/location data sits within the metadata. The problem is that you then have to manually assign the Place labels for those files even though the files are already coded with location information (from Geosetter). I've also tried having Geosetter generate keywords from these fields. From reading previous discussions and my own test, since Geosetter doesn't generate hierarchical keywords, this approach won't work either.

Looking back at a post from Idimager Pro, it appears that a script existed called "Place finder labels" which would read the IPTC fields and generate a label. Does anyone know if this script also works in PS, and if so, where can you find this script today? Given that the PS developer suggests using Geosetter, I'd like to find the best possible way of integrating the workflow between the two tools.

A second question... I've also tried geocoding/reverse geocoding in Lightroom 4.x. Has anyone had any more success getting these files into PS with the appropriate labels? I'm finding the geocode/reverse geocode data is there similar to Geosetter, but haven't had any more luck auto generating labels. I can't find a function inside Lightroom which will make hierarchical keywords out of location information.

[lnh]

A little bit of progress...

Found the "Place Finder Labels" file at: http://repository.idimager.com/cgi-bin/ ... df944b6ef7

However, when you try to run it in Photo Supreme you get the error, "Unknown member identifier: 'ParamContent'. Source position: 130,50"

If anyone out there is familiar with Idimager and PS scripting and could help debug this script is would be appreciated. Having this automation available would be very nice.

[Hert]

Attached is a version that works in PSU

Place Finder Labels.psc

(5.89 KiB) Downloaded 324 times

Hope that helps
Hert

[lnh]

Hert,

Thank you very much! Makes life easier for sure.

I don't always populate the "location" field of the IPTC data as it's often a duplicate of the "city" field anyways. You end up with an "unknown" label if it's left empty. I'm going take a look at the code to see if there is a way of suppressing the "location" field if it's empty. Either way it's not a big deal to delete them afterwards.

I get good results if I import without versions. If I version on import I was getting an error "List index(1) out of bounds(0)" when clicking on one of the version micro tabs. To be honest, I'm not exactly sure if that was from the import + script run or if I was just running into some general versioning issue. Have to try several more cases to see if I can figure out what was going on.

My other question has to do with the difference between how things are labeled natively within Photo Supreme vs. imported metadata. I've also noticed this when moving images from Lightroom to Photo Supreme as well. Labels always seem to be made for all the levels of a hierarchy when importing whereas if you label directly within Photo Supreme you're just seeing the single level of the hierarchy you set (usually the deepest level). Is this just the way it works, or is there a setting I can use to change this?

[Hert]

If I version on import I was getting an error "List index(1) out of bounds(0)" when clicking on one of the version micro tabs.

If you think you've encountered a bug then you can report it in Mantis at http://bugs.idimager.com

Labels always seem to be made for all the levels of a hierarchy when importing whereas if you label directly within Photo Supreme you're just seeing the single level of the hierarchy you set

On import, catalog labels are created for the keywords (and Lightroom keywords) that are in the file. If you get labels for every level of the hierarchy for images that are written with Lightroom, then Lightroom wrote such keywords which are then created by PSU on import.
If you like to assign the complete parent hierarchy when assigning a low level catalog label then configure that catalog label to also assign its parent labels. Do that in the details of a catalog label (right click -> Details) and set the field "Also assign its parents" to YES

Hope that helps
Hert