JeremyR

Oh, I see... I was thinking about when people reference TBs in the log text... A way of stopping/reducing occasions when people mistakenly put tracking numbers vice TB numbers in Found It logs would be very useful though - it happens often and unless the trackable owner is on the ball, they probably won't ever realise their tracking number is in public view. Perhaps a message should be displayed on the TB log page so when new users log their first retrieve/grab operation, they would be instructed which is the appropriate number to mention publicly.

I was wondering the same to be honest. RSS is a 'pull' technology (the reader program has to request the data and the server then sends it). Low volume notifications (like new cache notifications) are better suited to 'push' technologies like email* (like the current system), SMS, etc... Considering that you may only get a handful of notifications a week (leaving aside people who have their notification area set to 50 miles and covering an entire metro area), it would be far more costly (bandwidth, processing) to do it with RSS... * (In before someone points it out) yes, yes, I know typical email isn't strictly pushed but to all intents and purposes, the way it's used today, it is a lot more push than RSS

How does this work, exactly? I had a quick play about and I couldn't find where/when this message appears. Although difficult, some means of alerting people to the fact that they're about to post a tracking number in a public log would be much appreciated - I see it very frequently, just this afternoon in fact... [edit] Although re-reading the OP, it's not quite clear if this problem was even what you were talking about... [edit2] I'm still my own best friend and long may that continue

Why? Assuming the Pre has some kind of persistent storage available to hold a cache database (or a GPX file, etc) then how is it unworkable? 1) User uploads PQs for appropriate area(s) to the device. 2) User wants to cache and starts app. 3) App polls the GPS, searches the caches it knows about for the nearest few, displays results. 4) Etc. Only difference between using an API and a stored PQ is the addition of step 1 and the possibility that the data might be out of date if the user doesn't keep on top of updating it. A minor PITA, yes but both are things that geocachers are used to doing so they probably wouldn't object...

You're right, it does put GC.com in the minority of 'user generated content' sites that don't support API access and yes, I'm with you, I'd love to see one and all the creative ways that people would use it BUT Groundspeak have long made it crystal clear that a public/free API will not be forthcoming, so basically, you're stuck with using PQs to do such tasks (unless of course, you have an awful lot of cash to splash). It's a limitation but not unworkable. You can still do neat things with them

The OP has changed quite a bit since I first looked at this thread. It would be better to put additional questions in a reply to the thread rather than edit your original post. I'd never have noticed it changed if it hadn't been pointed out, especially since (under my forum preferences) we're on the second page. To answer the newest question about the word 'talk', erm... Does that matter?

I've never had the auto-correct feature working either, on this forum or on others running totally different software, neither in EST/EDT nor GMT/BST. Just set the DST tickbox manually - it's a minute of your time and only twice a year The 'ranks' you talk of - do you mean 'Geocacher', 'Premium Member, 'Charter Member', etc? 'Geocachers' are free accounts, 'Premium members' are, well, guess... Someone will be along shortly to make a witty comment about Charter Members and how special they are. You can't see other peoples selection in the GPS device fields. At least, not as far as I can see. Edit for fat-fingered typo...

The reason Raine gave was what I assumed to be the reason that it was taken away in the first place; making the archived cache listings readily accessible is just asking people to go and find them, especially when [unspoken truth] most caches archived for reasons other than muggling are probably still in-place [/unspoken truth]. Although in the precise circumstance that was mentioned, I thought that was what 'Retract' was for, no? The removal of archived caches from searches was before my time - what was the reason given for taking the feature away at the time?

/me idly wonders what would happen if you replaced the film tub with a Lock&Lock, the one tablet with lots of tablets (or some bicarb of soda) and the water with perhaps... vinegar

Google Earth is pretty accurate *most of the time* sometimes it's a bit out - you can tell when because the white road lines won't match up with the actual road on the photo (it's probably the photo that's out, not the drawn line). Assuming the roads match up with where they're supposed to be in the area of your cache, there's no reason at all why you can't use it for a bit of quick coordinate verification. Don't use it for getting initial coordinates though

If you know some details about it (the name would be handy, part of the description also works) then some 'creative' Googling will find some archived caches.

Not only do you have to remove them one-by-one, but you have to confirm it too. It's just a watch list action, not critical (or irrevocable) in any way so confirmation shouldn't really be needed - it just makes things cumbersome. Remove > Yes > Remove > Yes > Remove > Yes... Etc...

Yes, yes, I noticed that after I picked it, screenshotted it, saved it and uploaded it and couldn't be bothered picking a different one. I suspect my point remains valid, however...

Piglet's Pot ticks most of these boxes, if not all. It's on an 'easy' hill (Catbells). You can park near Hawes End at roughly NY 246 211 and walk about a mile to the cache (just beyond the summit). It's found about 6-7 times a month lately and is a decent size box. Alternatively, you can catch a launch from Keswick to Hawes End and walk up from where the boat drops you. (Edit to add: also, if you go up on a good day weather-wise, the views are stunning despite being a relatively low fell )

You could try asking at NWCaching? Several Mancunian members there...

A quick glimpse at Google Map on the cache page should be all that's needed to determine whether the area is residential or not. For example: Residential: Not Residential: You need to read the listings and other associated data (attributes, map, prior logs) before deciding if a cache is right for you, especially if there's a type of cache you really don't want to do.

Technically, yes, but the likelihood of that happening is slim to nil. In order to be arrested for trespassing whilst geocaching, the following would have to happen: - Cache is placed without permission of land owner (never happens, right?! ) - Land owner gets cross. - Geocacher is asked to leave by the land owner. - Geocacher doesn't leave. - Land owner calls police. - Police arrive... eventually (not exactly a high-priority call out). - Police ask geocacher to leave. - Geocacher still refuses to leave. - Trespass is now aggravated and geocacher gets arrested. Honestly, if you haven't found it, signed it and moved on by the time all that has happened, something's wrong with your geoskills As mentioned, trespass is only immediately criminal if law (or by-law) makes it so. Railways, nuclear sites, government or military installations, etc, etc...

Nope, it's not published yet. Almost certainly, the TB has been dropped in by the owner in readiness for the cache's release. Good news is that should mean it will move on quickly (with one of the first few finders).

[Edit] Never mind... replied way after the explanation was given. That'll teach me to refresh before replying after leaving the computer for a bit, huh?

Ad. Block. Plus. 'Nuff said. I have it set up to block Quantserve & Google Analytics on GC.com (and hundreds of thousands of other major websites)

Thing is that from a database POV, that one addition to the query doubles the complexity of the search and the hit on the server. Limited server resources is what started this whole thing off... I'll be very happy just to see it back again without any additional perks...

And now it is again, thanks chaps

Yep, I've often wondered that. I have to use 5 separate notifications to be told about all physical caches and Earthcaches in my area. It's not a big deal since it's 10 minutes to set it and forget it but it is a minor thing...

Very strange, I see it too. It wasn't like it yesterday, and it's weird, for sure. I blew up the icon scaling to see what was written in the little bars and the icons are for cache sizes (orange one reads 'micro', blue one reads 'medium', yellow reads 'small' and so on) however the icon that is displayed is dependant on the cache type so traditionals all have the orange 'micro' icon, multis have the blue 'medium' icon, puzzles have a yellow 'small' icon, LB Hybrids have a white 'virtual' icon. Earthcaches seem to have the correct icons still. The icons' urls' still point to a file on geocaching.com so either Google have mucked up the Geocache handler and are using the wrong icon URLs (there was a minor GE update over the last day or so) OR Groundspeak have changed the files that live at the URLs that used to house the cache type icons. I have no idea which is the case but I guess whoever's error it is, it'll be fixed quite quickly. I've put some screenshots below to show what I'm on about: Edit to add: For clarity, the yellow cache in the first pic is a regular puzzle cache, the orange one is a regular traditional, the blue one is a regular multicache and the white 'virtual' icon is actually a regular letterbox hybrid cache. Edit to add 2: To complete the list, virtual caches are appearing with a green 'large' icon. Events and Mega Events get a white 'unknown' icon. Webcams, CITO Events and the remaining Project APE cache all get their correct icons.

<googles> Heheheh... I hadn't heard that one before