gps-proximity-20091205.29.zip
· Version History
· Update Log via RSS
· Installation instructions
· “Donationware” Registration Info
· More Lightroom Goodies
· All-Plugin Update Log via RSS
· My Photo-Tech Posts
· My Blog
This plugin – for Lightroom 2.0 and later – allows you to find geoencoded images in your Lightroom catalog that are within some specified distance from a location you choose.
The download link is at right. For details on the plugin, 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.)
Availability
This plugin is distributed as “donationware”. I wrote it and 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 costs the minimum 1-cent PayPal fee; any additional donation you'd like to make in encouragement or thanks is optional and completely up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.
Lightroom 3 — Registrations in Lightroom 2.x will not carry over to Lightroom 3 when it is released, so plan that you'll have to re-register if you upgrade to Lightroom 3. (That's for the real Lightroom 3.... registration is not required in the Lightroom 3 Public Beta, but be warned that plugin support is spotty and plugins may not work well there.)
( Update Log via RSS )| 20091205.29 | Minor internal debugging tweaks. |
| 20091027.28 | Fixed an "EXEC" error introduced into the previous version. Also more LR3b fixes. |
| 20091022.27 | Added a first draft of some rudimentary support for Lightroom 3 Beta. See this important note about plugin support in Lightroom 3 Beta and Lightroom 3, including future plans for features and my registration system. |
| 20090714.26 | 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. |
| 20090604.25 | 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. |
| 20090525.24 | 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. |
| 20090521.23 | 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. |
| 20090510.22 | Added a link in the Plugin Manager to the plugin's update-log RSS feed. |
| 20090509.21 | 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. |
| 20090425.20 | 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. |
| 20090313.19 | 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. |
| 20090228.18 | Fixed a bug that caused a plugin crash if my server couldn't be reached during registration. |
| 20090129.17 | Small housekeeping update for the new locales supported by Lightroom 2.3. |
| 20090116.16 | 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. |
| 20090115.15 | Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people. |
| 20090110.14 | 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. |
| 20090107.13 | Can now handle Google-map urls that result from an address lookup. |
| 20081211.12 | Development seems to have settled down, so pushing back the expiration for several months... |
| 20081126.11 | The "within" input box was limited to a maximum value of 100. Hadn't noticed that. Removed the limit. |
| 20081124.10 | 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. |
| 20081121.9 | Fixed attempt to concatenate field 'base' error. Push expiration data back again. |
| 20081117.8 | 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. |
| 20081115.7 | Push out the expiration until the end of the year.... |
| 20081030.6 | Oops, yesterday's push broke it when not using my GPS-Support plugin. I think this'll fix it. |
| 20081030.5 | 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. |
| 20081030.4 | Now properly handles the dialup version of Yahoo! Maps when accepting a url for the search epicenter location. |
| 20081029.3 | 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. |
| 20081022.2 | 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. |
| 20081017.1 | Initial Public Release |
See the known issues before reporting bugs. Also, when reporting bugs, please include the OS, the version number of Lightroom, and the version number of the plugin. Seriously. I need the full version number or I likely can't do anything but ignore the message.
Is there any way to index the GPS data in some way that permits faster searching? ETA for me is 5 minutes to search against 21k images in the catalog.
Not easily… the plugin has to manually check each target image, so the only way to get around things would be for you to select fewer images prior to invoking the search. —Jeffrey
I’ve just found out that Lightroom actually supports plugins now and tried out your GPS search. Very well done, I’ve waited for that feature already… There’s only one problem here: Doing a search on my 3000 photos updates the “within range” field that I can filter on then. Doing another search breaks things when filtering on this: Within range = yes, flagged and unflagged photos, no colour label. The number of results in the metadata columns are inconsistent (usually the number must be the same in every selected row of all columns, but it’s not anymore) and it finds way too few photos. The problem is gone after a Lightroom restart. Lr 2.1 on Windows XP here. Any idea what’s going on there? Screenshot of the invalid programme state upon request via e-mail.
Lovely idea, especially in this day and age of geotagging – which I whole heartily think is a worthwhile activity for future use.
I was wondering if for a potential geotagging plugin you could pull the same api Picasa does for Google Earth (should you go this route for tagging) and pull the info that way.
I use Picasa w/ lightroom – it’s way way faster as a DAM tool and the google earth integration is awesome (if not a little slow for me); I can’t see me leaving Picasa completely as speed in lightroom is a world apart (instant v seconds or minutes to do things) from it, but the more time spent in one application for metadata-ing the files the better in my opinion.
Thanks for this plugin, and the others, they truly make LR a usable product
Jeffrey,
Tried to get this to work last night and kept getting a errors:
[....]
At line 9075: Attempt to access property “data” that’s not declared in Info.lua
All my images tried were d300 nefs and are hard coded withthe GPS using Geosetter taking the data from a Phototrackr GPS.
Any ideas ?
Many thanks in advance
Simon
I introduced an error yesterday, sorry. I just pushed .6 that should fix it. —Jeffrey
Jeffrey
Super thats working now….
Many txs
simon
Hello Jeffrey,
Thank you for this plugin, it’s great!
The searching functionality works well, and the metadata are displayed correctly.
But I have a small problem with the filter’s functionalities of the library: “Meters Away” and “Direction” don’t work. Only the filter “Within Range” works correctly.
I’m working with Windows XP (French) and Lightroom 2.1.
Yes, unfortunately, this is a bug in Lightroom. I reported it some time ago, so here’s hoping that the next update addresses it… —Jeffrey
Working great now against GPS data in the Nikon NEFs I have. Fantastic plug-in! Thanks.
Hi Jeffrey
This concerns GPS proximity search 20081030.6
I am working with LR2.1 Win Vista (in French , so my translation of messages is certainly inaccurate.)
First it’s really great to be able to search from gps coordinates INSIDE LR . Congratulations and thank you for this great work
I have a little problem : when I add “within range” in the library filter, it shows correctly the 17 pics within range (the “YES” filter), but does not select the pics out of range : LR says : “no picture corresponds to the filter”, when I select the “NO” filter . While in the filter its sorts them out correctly ( 17 are well classified within “YES” filter, and 16 are well classified out “NO” filter)
Hi Jeffrey
This concerns GPS proximity search 20081030.6
I am working with LR2.1 Win Vista (in French , so my translation of messages is certainly inaccurate.)
First it’s really great to be able to search from gps coordinates INSIDE LR . Congratulations and thank you for this great work
I have a little problem : when I add “within range” in the library filter, it shows correctly the 17 pics within range (the “YES” filter), but does not select the pics out of range : LR says : “no picture corresponds to the filter”, when I select the “NO” filter . While in the filter its sorts them out correctly ( 17 are well classified within “YES” filter, and 16 are well classified out “NO” filter)
This happens when I select “ALL” in the contry field filter (33 pics)
BUT not when I select “France” in the country field filter , (33 pics) as all were taken in France . In that case every thing works fine !!
This is, unfortunately, a bug in Lightroom. As far as I know, my plugins are the only ones in the world using this “custom metadata” feature, so it hasn’t gotten much testing yet, so my plugins are doing the testing. )-: —Jeffrey
Hi,
I updated the Ver.13 and there seems to be the same problem as I had last version. Here is the log file
Execution/debug log for Jeffrey’s gps plugin for Lightroom, version 20081111.13
Log started November 11, 2008 12:09PM local
November 12, 2008 03:09AM JST
Plugin folder: /Library/Application Support/Adobe/Lightroom/Plug-ins/gps-jfriedl.lrplugin
Lightroom version 2.1.0 build 512205 for Macintosh (Locale: en).
———————————————————————————————-
At line 13192: ?:13280: attempt to index a nil value
+6.2: At line 13192: ?:13280: attempt to index a nil value
Thanks. Lucas
Version 20081030.6
I just installed this for the first time, and receive a bold red mesage “WARNING: this plugin version expires in 4 hours. Please update to a new version soon.”
Is this normal?
btw, great work so far; Lightroom would be a lot less useful without you!
Sorry about that. I guess that plugin has settled down a bit, so hasn’t been updated lately. I’ve pushed a new version. —Jeffrey
On a more general note Jeffrey, why do your plug-ins have an expiry date and do they in reality really expire i.e. stop functioning. If any particular plug-in appears to be working (I use both the GPS Proximity and Flickr plug-ins) is there then any real need to upgrate? Thanks.
I’ve gone over this all before. Yes, they really stop working, and so yes, there is a real need to upgrade. Getting people to upgrade from old versions is the very reason to have it. —Jeffrey
hello… your new registration sucks.
i don´t have paypal and im not going to get an account for a one cent transaction.
PAYPAL SUCKS!!!!
Hi Jeffrey! How about incorporating presets in the Proximity plug-in?
I some older version I could get the GPS data out of a .gpx file.
I used it a lot because I use a Garmin 60CSx while taking pictures.
But with the new version, is this function gone??? Atleast I can’t see how to ímport’a .gpx file anymore… Can you help me because to me, it was a VERY, VERY usefull function!
I don’t think my proximity-search plugin ever did anything with tracklogs…. perhaps you’re thinking of my geoencoding plugin? —Jeffrey