This plugin allows you to
find geoencoded images in your Lightroom catalog that are within some
specified distance from a location you choose.
This plugin works in
(though some features may be missing in older versions of Lightroom).
The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.
For details, see the Announcement and
Instructions, and the version history below.
(This plugin works with images that have already been geoencoded: if you'd like to geoencode images,
see my Geoencoding Support plugin.)
This plugin is distributed as “donationware”. I have chosen
to make it available for free — everyone can use it forever, without
cost of any kind — but unless registered, its functionality is
somewhat reduced after six weeks.
Registration is done via PayPal, and if you choose to register, it costs
the minimum 1-cent PayPal fee; any amount you'd like to add beyond PayPal's
sliding fees as a gift to me is completely optional, and completely
Note: a Lightroom major upgrade, such as
from Lr4 to Lr5, de-registers the plugin in the upgraded version, so if you
want to maintain registration, a new ($0.01 if you like) registration code
is needed in the upgraded version. It makes for a hassle every couple of
years, I know. Sorry. See this
note for details.
For details on plugin registration and on how I came into this hobby of
Lightroom plugin development, see my Plugin
Update Log via RSS
The new fast proximity search added in 20130929.63 would finish silently (wouldn't report "no images found") if
there were none in range, but some were sort of close.
Added a new "File > Plugin Extras" menu item: "Fast Full-Catalog Proximity Search", to
isolate all photos in your catalog that are geoencoded within X distance of the current photo.
In Lightroom 5 on OSX it's ridiculously fast (a second or two). On Windows or older versions
of Lightroom, it takes longer... two and a half minutes to search 130,000 photos on my circa 2010 laptop.
Oops, fix a bug introduced in the previous update
Changed all distance calculations from spherical geometry to ellipsoidal geometry,
raising the level of accuracy from "way more than good enough" to "ridiculously overprecise".
Apparently, a recent change broke things on Lr2, which some folks apparently still use.
Fix an "attempt to perform arithmetic on field" error.
Update to handle the Mac App Store version of Lightroom.
Tweak for Lr4.1RC2.
Enhanced the send-log dialog to hopefully make reports more meaningful to me,
yielding, I hope, the ability to respond more sensibly to more reports.
Had broken registrations in Lr2; Update to the debug logging to better track down timing issues that might arise.
Considering the utility of the Map Module in Lr4, I don't intend to really support this plugin for Lr4 and beyond, but
in order to at least let it run, I've had to adapt for Lightroom APIs being discontinued in Lr4.
Update for Lr4 beta: explain in the plugin manager that the plugin can't be registered in the beta.
When doing a plugin upgrade, offer the ability to flush all the old copies of the plugin.
Added a system-clock check and reports to the user if the system clock is more than a minute out of
date. An incorrect system clock can cause problems with various kinds of communication and authentication
with some of my plugins, so I've just gone ahead and added this to every plugin.
Had issues with the registration button sometimes not showing.
For Lr3, now offer the option to populate a collection with in-range images, that then can be
sorted by distance from the search epicenter.
Replaced the ugly reporting dialog shown after a search with a different ugly reporting dialog.
Now remembers the search epicenter input text from invocation to invocation.
Canceling a search now really cancels everything, rather than merely leaving the results where they were when
cancel was hit.
In Lr3.2 or later, returned the most-selected-image thumbnail that went missing in Lr3.0.
Made the revalidation process much simpler, doing away with the silly need for a revalidation file.
Discovered a bug in my plugin build system that caused horribly difficult-to-track-down errors in one plugin,
so am pushing out rebuilt versions of all plugins just in case.
Added code to allow plugin revalidation after having been locked due to a bad Lightroom serial number.
Discovered a nasty build bug; pushing a new version in case it affects this plugin.
This version can be registered in
Lightroom 3. It can run in Lightroom 2 or Lightroom 3; it does not work in the Lr3 betas.
It uses my new registration system when run on Lightroom 3,
which avoids some of the silly issues of the old one. Please take care to note
the details on the registration
page: use of this version (or later) of the plugin in Lightroom 3 requires a new
registration code, even if you had registered some older version of the plugin.
Oops, introduced a bug that caused the plugin to become disabled on Windows if it was enabled
when LR started.
Wholesale changes that attempt to honor the user's locale settings for numeric display (e.g. Europeans
writing 3,14156 for pi). I've probably missed some spots, so let me know if you find some.
Tidied up the UI a bit.
Completely changed how the one-click upgrade applies the newly-downloaded zip file, in the hopes that
it'll work for more people. Rather than unzipping over the old copy, it now unzips to a temporary
folder, then moves the old folder out of the way and the new folder into place. Prior versions' folders
are now maintained (with the version number in the folder) in case you want to revert a version; you
may want to clear them out from time to time. Of course, it won't take affect until you try to upgrade
after having upgraded to or beyond this version.
Fixed an "EXEC" error introduced into the previous version. Also more LR3b fixes.
Enhanced the one-click upgrade stuff quite a bit, now
detecting ahead of time when it will fail because the plugin is installed where Lightroom
can't write (if Lightroom can't write to it, it can't update itself). I
also added a progress bar, and now download in smaller chunks to avoid 'out
of memory' errors on the larger plugins. Do remember that this new functionality becomes
available after you upgrade to or past this version, when you then upgrade with it.
It seems that the thumbnail being used to illustrate the "most-selected" image was, in some cases,
taking over the entire screen. I think I've fixed it.
Added an "import location from Google Earth" button, as well as a "Show Crosshair Target in Google Earth"
button. The crosshair target is really helpful when pinpointing a spot exactly, and it's much nicer, I think,
than others I've seen.
Renamed the plugin label from "GPS Proximity Search" to "Proximity Search", since GPS isn't really
a synonym for "geoencoded location".
Fixed a "loadstring" error some users got.
Added a link in the Plugin Manager to the plugin's update-log RSS feed.
Redid the internals so that proximity searches on small groups of images
(say, several thousand images or less) are now much, much faster.
Added the thumbnail of the most-selected image to the dialog.
Removed the plugin expiration, which I should have done before, but apparently forgot.
Tweaked how the plugin tries to update itself during the one-click upgrade process,
to hopefully get things working for those few Windows users that have never had it work. Crossing
fingers. We'll see.
It seems that PayPal doesn't give everyone a "Unique Transaction ID" in the
registration confirmation mail; some people get a "Receipt Number". So, the registration dialog now
accepts that as well.
Fixed a bug that caused a plugin crash if my server couldn't be reached during registration.
Small housekeeping update for the new locales supported by Lightroom 2.3.
It turns out that the automatic upgrade stuff doesn't work if the plugin folder has been renamed from its original. That should generally not happen, but it's possible, so the plugin now checks its own location reports the issue to the user if it finds it.
Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people.
Added a checkbox in the Plugin Manager to turn on enhanced debugging (more stuff in the plugin's debugging log), and added a button in the same place that sends your log to me. Particularly for “the upgrade button doesn't work” and “error while uploading” type issues, this should be useful for debugging.
Can now handle Google-map urls that result from an address lookup.
Development seems to have settled down, so pushing back the expiration for several months...
The "within" input box was limited to a maximum value of 100. Hadn't noticed that. Removed the limit.
Perhaps fixed a problem whereby the "Upgrade Now" button didn't work for some Windows users. We'll see whether it works when those users upgrade from this version to whatever version is next.
Fixed attempt to concatenate field 'base' error. Push expiration data back again.
No new functionality in this version, but a huge upheaval in the underlying code to repair an unfortunate design choice I made early on
in the development that had limiting consequences I'd not foreseen. There are likely bugs introduced in this version, and as such, it
has a short expiration date to encourage updates as those bugs are reported and fixed. If you do run into an error, please send (via email) the log referenced in the upper-right of the Plugin Manager. Thanks.
Push out the expiration until the end of the year....
Fixed a crash introduced in the previous version. Now handles urls from non-US versions of Yahoo! Maps.
Fixed a few bugs in the latitude/longitude parsing code, so that it now actually handles hand-written lat/long pairs the way it was documented to handle them before.
Now properly handles the dialup version of Yahoo! Maps when accepting a url for the search epicenter location.
Now compatible with my GPS-Support plugin.
I also removed the "View location in..." plugin-extra items from this plugin, because I moved them to the new one.
Added the "GPS Proximity Results" metadata tagset, so now now the results view is a bit cleaner than using the "All Plug-in Metadata" tagset.