I am a refugee from Microsoft Pro Photo Tools which has recently stopped providing reverse GPS (at least for me). I used it because it was the only product I could find that provided street level information.

After a mostly fruitless search, I found your LR plugin. Wonderful!

However, I have a suggestion. You fill out the sublocation field as the entire “address”. What I want and need is only the street level address part, like Pro Photo Tools did. Geosetter also only puts the lowest level information there (sometimes useful but mostly just a repeat of the city).

but I would really prefer the sublocation to be the sublocation as I understand it should be. Here is the IPTC description:

“Enter the name of the location shown in the image. This sublocation name could be the name of a specific area within a city (Manhattan) or the name of a well-known location (Pyramids of Giza) or (natural) monument outside a city (Grand Canyon). Sublocation is the most specific term, at the fourth level of a top-down geographical hierarchy if it is inside a city or at the third level if outside a city.”

I have a number of scripts that rely on these all being parts of the total address, which of course could be rewritten with some effort. But mostly I don’t believe this concatenation is what sublocation should contain.

Thanks for all your work to provide much-needed tools for Lightroom!

Judy

I don’t think I’ll be able to make that change… the code is very fragile, owning to the really vague nature of reverse geocoding to begin with, a compounded by the wide variety of location types throughout the world, all mixed in with a healthy dose of randomness from Google that can’t be easily explained. The plugin is using an old Google API, and perhaps it’ll be more regular when I upgrade, but for now I’m reticent to touch that code. —Jeffrey

Thank you for your speedy reply.

As for a) I thought the GPS log contains the right time; when adding the GPS coordinates it could update the time stamp at the same time, based on the “Compensate for the camera’s clock” value (not the fuzziness value).
More detailed: I already know the compensation value; why use LR to adjust, when I geo-encode and know the difference that need to be applied.

When you say: “The “compensate…” option in the tracklog tab is for people too lazy to do it the right way.” Are you implying that I should change the time of the images first (after I have established the time difference), and then use your plug-in to add the lon/lat?

Yes. Better still would be to just set your camer’s clock properly, but if you hadn’t and realize the mistake while in Lightroom, use Lightroom’s normal facilities to fix the time. Lightroom doesn’t let a plugin update the time. —Jeffrey

Hence, where I am coming from: I tell the plug-in the time difference, and it updates the lat/lon as well as corrects the time stamp in one go

It seems a workflow thing; I am an automation guy let the computer do whatever it can LOL

No worries, just a thought and bouncing ideas…

Keep up the good work!

Cheers,
MaxG, Brisbane, Australia

Thank you for a great plug-in!
I read the docu and screens and wonder about the following:
a) Why is the image taken time stamp not adjusted to the GPS track log? I did not see it changing when geo-coding the selected images. What am I missing? And in case the plug-in does not do it, are you planning to implement this feature? — I feel silly overlooking something )
b) Is there a way to get the location info (populated via reverse Google geo server) into the keywords?
c) Maybe b) can be expanded with a config dialog, as in which field goes where in the keyword tree. Example: I use Word location | Continent | Australia | Far-North Queensland | Cairns, compared to AU| Australia | Cairns.

To come back to this great plug-in… it demonstrates how some simple lon / lat information can become so much more with all the linkages you have established. Simply great work!!

Cheers,
MaxG, Brisbane, Australia

I don’t know what you mean in item “a)”… why should the image’s time be adjusted by the plugin? If the image’s time is incorrect, it’s probably a good idea to correct it whether you’re going to geoencode or not, but geoencoding will be wrong if your camera clock was incorrect and you don’t fix it. (The “compensate…” option in the tracklog tab is for people too lazy to do it the right way.) As for “b)” and “c)”, there’s no interaction with keywords. —Jeffrey

The plugin has always done exactly that. I use the term “fuzziness” for what you call “interpolation threshold”. —Jeffrey

I don’t know what gets installed with your dmg, but if it’s an app, you’d need to point the plugin at the actual executable within it. —Jeffrey

I don’t quite understand the reference to Google Earth, but you can clear the shadow data from the Geoencoding Dialog’s “Un-Encode’ tab. —Jeffrey

Ideally you’d want to use the plugin with a tracklog made while you took the photos, and so an iPhone app might be used to create the tracklog (though I’m not familiar with those apps in particular). Personally I use a dedicated GPS unit, but plenty use iPhone-created tracklogs successfully. —Jeffrey

“Bulk Reverse Geoencode” treats each photo individually.

The second suggestion has to do with once you have clicked the “City, Etc… from GPS” button within the “Interactive” tab, I wish that the address that typically populates above the “Location” block would automatically fill in the “Location” block. Right now I am having to manually highlight the address, and then copy and paste it into the “Location”block. Any help or future time saving tips are welcome….

Thanks again for all your help and plugins…..you truly have a passion that is inspiring to many across the world. Keep it up!

Google’s data is very fuzzy for the address/location, so it’s hard to be consistent… sometimes the plugin does fill in the location data, but it all depends on how the data is returned by Google. I’ve made some adjustments and so the next version of the plugin will be a bit more aggressive about filling in the location field with something. —Jeffrey

You can essentially do the same thing with the plugin’s “Geoencode selected photos from Google Earth” feature. On a Mac you can even set a keyboard shortcut for it so that simply tapping one key combo and the currently-selected image is geoencoded with the current location from Earth. It’s about as seemless an integration as Lightroom allows. —Jeffrey