dfx

mep

I'm willing to bet the opposite. One of the recent updates (I think it was when the GPS firmware moved to 5.0) already made the issue much better, but it's still popping up occasionally. It's probably their attempt of smoothing out small coordinate fluctuations to give better, more consistent readings. Which works quite well most of the time, but is overdoing it from time to time.

To me personally, there's a strict distinction between cache listing and actual (physical) cache. Therefore, strictly speaking, a replacement cache is never the same cache, but the same cache listing can still be used for it, in the same manner that the same cache can be used for a different cache listing (not necessarily at the same time, but even that is possible with different listing sites). So the question should really be: when should a cache (be it the same one or a different one) get a new listing made for it? I vaguely agree with the "experience" aspect, but I'd rather call it the setup. The setup as intended by the CO.

And the worse the reception conditions are, the faster you can walk for it to stick...

Is that the one that only allows one check per 10 minutes and then blocks you for an hour after 3 tries or something?

Connect the Dakota to the netbook. Watch the file manager for a new drive called GARMIN to appear. The contents of that drive may also just pop up as a new window. You will also see that drive under the "places" menu. Create, run and download a pocket query from gc.com as usual. They come as a .zip file. Save the .zip file anywhere you'd like, for example on your desktop. Open the .zip file in the archive manager. (You can also skip the explicit save step and just open it directly.) You will see two .gpx files. Choose to extract those files, as destination select the GARMIN drive, then the Garmin directory, and then the GPX directory. Extract. Eject the GARMIN drive in the file manager. Unplug the Dakota and turn it on. You're done. --------- Schliess das Dakota ans Netbook an. Beobachte den Dateimanager, es wird dort ein neues Laufwerk GARMIN erscheinen. Dieses wird auch im "Orte" Menue erscheinen. Es kann auch sein, dass der Inhalt dieses Laufwerks automatisch als neues Fenster erscheint. Erstelle eine PQ wie sonst auch. Lade das Ergebnis runter, das ist dann eine .zip-Datei. Speicher diese irgendwo, wo du sie findest, zB am Desktop/Arbeitsflaeche. Oeffne diese .zip-Datei im Archivmanager. Du kannst auch das explizite Abspeichern ueberspringen und die Datei direkt im Archivmanager aufmachen. Du siehst dann dort zwei .gpx-Dateien. Waehle "Entpacken", und als Ziel suchst du dir erst das Laufwerk GARMIN aus, dann dort das Verzeichnis Garmin und dann das Verzeichnis GPX. Entpacke die Dateien dort rein. Wirf das Laufwerk im Dateimanager sauber aus. Steck das Dakota ab und schalt es ein. Fertig. Es gibt hier uebrigens auch ein deutschsprachiges Forum: http://forums.Groundspeak.com/GC/index.php?showforum=29

It's dead, Jim.

Just did this one via the offcial gc app. Still nothing...

I just looked up GC2BA4D using c:geo (with that option checked). Does it show up in your audit log? --Larry Edit to add: Silly me, I also accessed the cache via my PC's Web browser, a few minutes later. You might now see two audit log entries from me. Actually shows 3 visits from you.

As a secondary test, just viewed the last one you gave me with a smartphone app, something else some have said won't show. You did show up on my audit log. Very likely you view the cache page, if not, let me know. Depending on how you've set up the app (I'm referring to the "Identify c:geo as an ordinary webbrowser" setting, which is checked by default), accesses via c:geo WILL show up in the audit log. Just now, I called up a cache in c:geo and it immediately showed up in the new "Recently Viewed Caches" list on the profile page. Assuming that cache page access is what triggers an entry in the audit log.... I'll leave formal testing to those more interested in the results. --Larry In the case of c:geo, I'd wager that it shows up in the audit log even with that option disabled.

I only gave GC2BA4D - nothing there still.

That's some interesting interpretation of the word "extreme". How is something extreme if most people can do it with little effort? Shouldn't the scale go from "no effort required" to "a lot of effort required"? The far end of the scale would then be the extreme, meaning that those caches require the most effort of them all, with none requiring more than them. And caches that are nigh impossible to get to sure fit the bill. There's nothing subjective to it. Unless of course you're talking "extreme within your own abilities".... (and btw, a 50 ft dive is not a good idea to do after only a day of training, even though some people still do it unfortunately...)

No activity on my listing from any of you.

30 pixels is valuable screen estate?

JPEG tagging happens through the EXIF header. While EXIF theoretically can be put into WAV files, it's an extremely uncommon thing to do, I'd be surprised if there was any software to support that at all. For MP3 files, you'd use the ID3 header. I don't know if ID3 actually provides support for location information, but it's always possible to create your own tags within ID3. An option that's always available is to just rename the file and encode location information into the file names. Just remember that WAV files by default don't contain any metadata, so for georeferencing them you have to use the file modification timestamp, and you need to be careful to preserve that when copying files etc.

Just got home from work and DL'd the test PQ into GSAK. Let me know if my view shows up in your audit log. thanks. Nothing as of right now...

I live near Toronto, Ontario, and with WAAS on it does not even get a signal, even leaving it on for an hour in an open area. I turn WAAS off, and it works like a charm. Sounds like you have some more serious problems with your GPS. With my Oregon, I can easily get a WAAS lock almost anywhere between here (Burlington) and Mississauga and beyond. And when it doesn't have a WAAS lock, well then it just doesn't. No harm done.

15-18 feet can be considered normal, but it seems like a bit too much. Under good reception conditions, you should be able to get at least within 10 feet. Things to consider here: Firmware, check that you have the latest. Check that you have WAAS/EGNOS enabled. Understand that it can take the unit 15-20 minutes to download all the necessary data from the satellites. While the unit will have GPS reception pretty much right after turning it on, the satellite constellation data it's then using will just be predicted data, based on the last known actual data. The longer it has been since you've last used it, the more inaccurate this predicted data will be, which means the location readings you get will also be inaccurate, even though the "accuracy" reading the unit gives you doesn't reflect this. This effect can be noticeable even after only 24 hours of not having used the unit. Rule of thumb: if you want the most accuracy, turn the unit on and wait at least 15 minutes before using it. Obviously, the unit will need a good view of the sky during this time. The compass calibration has nothing to do with all of that.

... if it actually was real, that is. What proof do you have that this is a liar's cache? No proof, just going by what's posted on the cache page (esp. in the logs), and by gut feeling.

I'm already 100% IPv6 enabled (but only because I've set up a tunnel for our home LAN - our ISP doesn't do IPv6 yet )

This is exactly what we use and couldn't be happier. Me too, the 2500 mah....best I've ever used and on electronic compass units calibration is seldom necessary. 2500? I thought 2000 mAh is the most they had.

... if it actually was real, that is.

Only in the sense that they need the actual, real coordinates of any stages (including the final) the multi or the puzzle might have. Not in the sense that they need to be given an explanation of how a puzzle can be solved, or what the answers to any field questions are.

The most extreme caches - by far - I know of are http://coord.info/GC2WGV2 and http://coord.info/GC2WGTQ

And then there's special cases like this for this.