My images are geotagged. With Lightroom 5, I can reverse geocode the images to have Country, State and City in the IPTC fields. However, unless I go in each field, they are greyed. When I want to export the images, I want to use the naming convention Country-State-City-incremental number.jpg for each image, but unless the fields have been edited, lightroom ignore the fileds (and hence put ---1.jpg). Any idea how I can confirm the location without having to go to each image and edit the fields?
Unfortunately, you will confirm the location. You can do this by selecting all of the files (probably best done in Map module) then clicking on the field name for sublocation, city, etc. I'm sugesting that you do it the Map module because you can auto select co-located images by clicking the flag on the map.
That means that I need to go in each picture (or group of picture taken in the same location) and confirm each of the fields independently? That is rathe cumbersome and I wonder why Adobe did not implement a one-click confirmation of reverse geocoded information.
Yes, each picture or group.
Not all of the data returned by reverese geocoding is correct and/or acceptbale to the user. Personally I don't use reverse geocoding as I think current behaviour slows down the workflow without actually being more accurtae than the info I would insert manually.
I agree that reverse geocoding data need to be reviewed. In my case, 85+ of the data is correct and this would be easier to validate this info with a single key combination rather than having to click in 4 field per image. Adobe is confident enough with the data to use it in filters without it being reviewed by the user, so why not in export and/or other functions? This still puzzles me. This will give the user the option to review, or trust the data retrieved.
Same bug here. You can't "validate" or confirm in bulk the values automatically reverse-geocoded for a field (e.g. Country, which is very very likely to be correctly filled automatically).
Even worse, trying to edit manually any of these fields (e.g. to add a custom, more refined 'Sublocation') empties all the other automatically-filled ones, making reverse geocoding almost useless.