Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by wwp

  1. Here's something that should be easy: Could we please make logs on caches stop eating quotation marks?? It's really annoying to "put something in quotes" in a log, and go back to the log and find them missing (often at the cost of understandability). I realize one can use two ticks (apostrophes, whatever) to emulate a quote mark but ... come on. There's just no good reason for this limitation. Thanks!
  2. quote:Originally posted by Warm Fuzzies - Fuzzy:Hm, I just noticed a potential snag when I got your reply. When I send email through the site, it gets my username attached to it, and not the name I display in the forums. You just got a vote from parkrrrr; it was from me. Yeah, same thing with us (Jay, Caine & Becca, account name 'wwp'). Don't throw away the votes!
  3. If you're a unix geek, we've put together a perl script that will take a tracklog (in gpx format) and a bunch of pictures (with timestamps in EXIF tags), and identify the location of each picture and save it to a file. May work under windows, but no promises (and no GUI). You can get it at http://www.lupine.org/locstamp Enjoy.
  4. We like our gearpaw. You should like it, too.
  5. A bit back we stumbled across a piece of software on the 'net that would take the track log from a GPS, a directory full of digital camera photos, and annotate the photos with the GPS coordinates where they were (probably) taken, based on the timestamps in the photos and the GPS logs. We thought this was pretty durned nifty. ... and then we found out that it was more than $200! So Jay spent an afternoon whipping up a perl script to accomplish the same thing. It isn't nearly as pretty as the other software, but seems to work, so far. We thought we'd share a preliminary version of the script, on the off chance that it would be useful to someone (and the very off chance that someone wanted to help improve it). Basically, you just feed it a list of your track logs (saved from expertgps in .gpx format), a list of your images, and it compares timestamps and adds a .txt (or whatever extension you specify) file alongside the image containing the (probable) coordinates at which the image was taken. It's in perl, and I'd be really suprised if you could get it to work on anything but a *nix box, right now. There's no inherent reason it -couldn't- work on windows, if it has the right modules, but that's completely and totally untested. You need to have the XML:OM module (and the XML libraries it needs) installed to run this (consult www.cpan.org). "perldoc locstamp" will give usage instructions. The URL: http://www.lupine.org/locstamp Disclaimer: It's been lightly tested so far, but that's it. If it crashes and burns, destroys your computer, and makes you grow three heads and feathers, don't complain to me (though we'd appreciate a bug report Enjoy.
  6. A thought... It might be worth considering making the limit on queries "the larger of 500, and the number of finds you have" ... e.g. I get a limit of 500 (with my monster load of 33 finds), Marky gets a limit of ... what's he up to now? 1600? :> This way most users would still keep a reasonable limit, but hardcore cachers can 'earn' the right to bigger queries, which is something that's (arguably) only really useful to those with lots of finds anyhow. Not always the case, but I'd bet that it's usually the case. It would let them get lists of all their finds, and generate larger lists of caches-yet-to-visit (which I imagine gets more and more useful as one's radius of caches found increases). Just a thought. :>
  7. Ah, but see, if the page says "the cache isn't there", I can see it -- but my software can't, because everyone says that in slightly different ways. If there was an actual flag (presumably sent as part of the Pocket Queries gpx files), my software could filter based on whether or not a cache is actually there, rather than (essentially) guessing, based on finding certain keywords in the text. This isn't a problem when I'm actually out caching (because I always read the cache descriptions first), but when planning my trips, it's a huge pain. When I plan my trips, I pull up maps (in mapsource or Streets&Trips) of all the caches I haven't found (which I can tell from the gpx files), and start looking for clusters of caches that I can go get -- drive up, pick up 4 or 5 caches, and head out. With the 'not really there' caches still present, finding these clusters is much harder... e.g. I have more than once run into clusters of half a dozen caches where all but one weren't actually there... It's certainly not a life or death problem, but it is a pain, that I'm sure is going to get worse over time.
  8. Could we please, pretty please, with sugar on top, have a flag that cache owners could add to their pages that indicates that the cache isn't actually at the coordinates on the cache page? Right now, since we still have many caches to find, we tend to sit down in Streets&Trips and scope out areas with a number of caches in close proximity ... and it's really frustrating to spend a lot of time looking at interesting areas, only to find out that half the caches there aren't actually _there_. If I could filter on "cache isn't there", it'd be much easier to see what caches are actually available...
  • Create New...