BlackRose67

For the last half hour we've been having issues of being logged out of the site and then getting "500 server error" messages when trying to log back in. If we get logged in, we get booted back out when we go to view another page on the site. Site is also slow to respond. Anyone else seeing this?

Twice so far. The first time, someone else was at my cache when someone passing by saw them and called it in. I just happened to go there to do some log maintenance after the event rush from the previous two days. As I was heading up them embankment, I saw a police car parked behind my vehicle. Was told to remove the cache, so I had to archive it. Second time was more humourous while caching in downtown Ottawa: I was standing under a large pine tree thinking I was out of sight. My torso was hidden, but as I discovered my legs were in full view. Next thing I know, a light brown pickup truck pulls up. Me: "Hi, how's it going?" Officer: "Good. What are you doing?" Me: "Looking for a geocache." Officer: "In there?" Me: "Yes." Officer: "OK, at least I know what you're doing." and off he went. Good to know the RCMP know about geocaching.

Whatever was going on has now cleared, working again for me.

I'm trying to download my PQ's and also log today's find via the API and I am getting timeout errors. Anyone else seeing this?

5 Lesser-Known Souvenirs Geo-Medics! The DNF Squad A Life of a ‘Change’ The FTF-Hunter The one with the guy on the floatie.

If the cache was archived and the container was never retrieved, and if the cache truly is still in place, it's fair game.

My 650 froze so often I returned it to Garmin after 11 months. Many people said theirs was fine. Garmin replaced it with a brand new one - which did exactly the same thing. Sometimes I would be removing batteries and putting them back in 3 times an hour. (I'm fairly sure it's power related as when the batteries discharge somewhat it actually gets more stable) I get that occasionally on my 600. There is no rhyme or reason to it. Sometimes I can go all day with no issues, other times I need to pull the batteries several times an outing. (For the record, my GPSMAP 62s also did this, so I think it's a common element in some of the firmwares). My caching buddy uses "find next closest" quite a bit, and you have to wait a bit before actually pressing it. I think the device takes a bit to mark the cache as being found. We both use GGZ files when we load our devices with GSAK.

Are you using GC Little Helper? If I disable GCLH, it displays correctly in Chrome. As far as I can tell, this only started happening after my laptop updated to Windows 10 Anniversary edition. GCLH hasn't been updated since June of July, so not sure why this is happening now.

I've got 8 GB of RAM on my laptop; I ended up with an out of memory error running the query.

I have my own account, and my wife has her own. I started caching several years before she did, and I also cache much more than she does, so we have separate accounts.

It's not so much trusting it over the GPS, it's using that info in GSAK to figure which GPS is reporting the more accurate value. I don't have topo maps for my Oregon, so it's all I have access. The Oregon 600 was reporting 97 meters at the posted (top of the drumlin) while the Nuvi was reporting 105 meters. GSAK indicated that the posted was at 97 meters. GSAK gets it's elevation data from Mapquest, USGS, SRTM, Google, and Aster (in that order).

I'm surprised you could get that many loaded on the eTrex 20. Mine would having problems indexing the GPX file if I had more than 1500 caches in the GPX file on the external microSD card. I now use an Oregon 600 GPS, and use GGZ files. I don't worry about the number of caches loaded from GSAK anymore. As was mentioned previously, without buying a newer GPS that supports GGZ files, putting caches on multiple microSD cards is really your only option.

Right, and that's how it should be. In many cases it's meaningless, and in some it's a potential spoiler (eg, steep terrain changes at GZ). In the case of wilderness caches where it is potentially useful, the cacher probably already has topo maps stored in the gpsr. It can be helpful as well. I did an earthcache yesterday that required noting elevation. Our car GPS (Nuvi 2595LMT) and Oregon 600 showed elevation numbers that were about 5 meters off from each other. The elevation value in GSAK told me which device was reporting the more accurate value.

I checked today's update, and while sitting still the compass shows zeroes for my current location, but as soon as I start moving it updates to proper coordinates.

Seems to be a new feature in the iPhone app(s). It's not happening with the Android version of the "new" app.

Possibly related to this issue (coordinates are all zero on the compass screen); http://forums.Groundspeak.com/GC/index.php?showtopic=341552

what was the issue with his iPhone? It's not a Android. +1000

never mind, varies by seller and model

The only current app to connect Bluetooth to these handhelds is Connect and it is available in Android. Tried connecting to Garmin Connect with my 600 today. It doesn't work. I "forgot" the pairing and then tried to pair again. My phone sees the 600 but it won't pair with it now (it will pair with other devices). My OTG cable and adapter works fine when in the field, so that will have to be my solution when away from my computer.

It's probably due to the new Android app not even offering the option to log NM/TD/OM logs, so it is showing everything that is not a Found It/Did Not Find/Write Note as Write Note. Even the Published entry shows as Write Note.

I just tried it, and I have the same issue.

Somehow I was able to pair my Sony Xperia Z3 smartphone with my Oregon 600, but that's about it. I don't even recall how I did it now. But since there are no Android apps from Garmin that will talk with the Oregon, I've stopped looking. Not sure if Garmin Connect would work.

I had submitted a waymark for an abandoned mid-1800s cemetary in the woods. I had mentioned that there was an effort to clear some of the fallen tree debris from around the cairns. The result? Denied because they no longer consider the cemetary to be abandoned. Not worth the hassle; I archived the Waymark and won't bother with it again.

Looks good in general, but I see that it doesn't render at all for my area once you zoom in to an acceptable level.

I set my 600 to MTP to see what would happen. It still mounts in Windows 10 fine, but the GSAK and the Garmin Export macro cannot see the drive letters, so it won't work for me that way. I even tried setting my GPS as a Monterra in GSAK, but no dice.