31BMSG

You are probably correct, I gave up using the GS routing tool because it shows my home zip code more than 100 miles away from where it's actually at.

I have the same problem north of me in the west Texas oilfields, that's why the CO and all 503 of his caches are on my ignore list. As long as the reviewer approves these and they are in decent shape I don't see any options other than ignoring them. Because of the few caches I've found that were placed by this CO I've learned to delete anything that resembles a power trail from my caching list.

I don't navigate to a cache with the pointer, I navigate by looking at my current location compared to the destination coordinates. I can't speak for the OP but when I posted in the last discussion on this subject precision wasn't a concern, having the GPSr display match how geocaches are normally listed was. I learned to navigate with a GPSr on a handheld that displayed UTM to at least 12 decimals, I want to say it was 14. Very precise, but when navigating to a location where someone had scribbled 11 decimals on a scrap of paper a margin of error was added. The cache page posts coordinates in three decimals, GSAK lists caches in three decimals, what is wrong with asking to have the GPSr display cache coordinates in what has become the standard for displaying cache coordinates? If I drive I-19 south of Tucson the speed limit signs are posted in KPH rather than MPH. KPH to MPH and vice versa is an easy conversion done in your head but I don't have to because I can make a few pushes of a button and the speedometer display matches what is POSTED on the highway signs. I'm sure the Garmin overlords know the best way for me to navigate but when a car speedometer can do something an expensive piece of navigational equipment can't I get aggravated.

I've just returned from a 3300 mile county collecting road trip with no intentions to do this promotion. When I got home and started logging finds I saw that I was two "diamonds" away from completing it so might as well finish. Since I live in a cache poor area my 100 miles search only returned three caches with a diamond and when I looked at the first one on the list I lost interest. Earlier this year the CO logged an OM saying he was removing the cache because mowers kept breaking it, this was followed by six DNF and then flagged for NM 90 days ago, why was this included in a promotion? If the CO didn't get a CHS email then CHS is broken, if he did get an email why include this cache in the promotion? I think the concept is a good idea but it needs some fine tuning, for now I'll go back to ignoring the promotions. I'm going caching tomorrow and if I find what I need fine, if not I'm not too concerned.

If you use the macro StefandD linked to above you don't have to look for or move the files yourself, the macro loads it straight from GSAK to the GPS.

Thanks, I'm on the road right now so any conversation will be hit or miss until I get back home around the first of the month.

I should probably explain what I'm doing. Once I have a list of caches I want to use I add notes, change child waypoints from POI to geocaches, and include spoiler pictures. The only place the modified GPX exists is on my desktop, just drag and drop to the GPSr. I'm wondering if there are phone apps that will do the same, I'm clueless about phone file systems. Apologies to the OP for the hijack I should probably start a new thread with this question.

I've been exploring the phone option but have one question, are GPX files loaded online only or can you load a custom GPX from a computer?

https://www.geocaching.com/geocache/GC7V2QN I did this one yesterday and was surprised how much the pole swayed when I got to the top.

Why would I want more discoveries when I'm already annoyed with the current amount I get?

A second for QMapShack. It has geocache support built in so all you have to do is import a GPX file. Clicking a cache icon gives you cache code, cache name, cache type, D/T, elevation, plus a link to the cache page. The only unsupported systems are 32 bit versions of Windows, Linux, and older versions of OS X. I use this a lot for back country caches, a bit of a learning curve but no harder than GSAK.

And even if there were a valid reason at least post a note on why it's been disabled.

A red GC code is disabled, red with a line through it is archived. To keep from hijacking this thread feel free to send me a message.

Here is a good explanation, http://forums.Groundspeak.com/GC/index.php?s=&showtopic=202244&view=findpost&p=3613478

This is what the Garmin representative said until he walked through the settings and was surprised. All my receivers are set to spanner mode, when they are plugged into my laptop"s USB port they prompt to go to USB mode. Choosing YES allows me to go into USB mode and communicate with Basecamp while choosing NO allows the receiver to remain in spanner (serial) and provide live tracking through USB to the laptop software, no additional cables or hacks required. When the same receivers are set to serial they go straight to USB with no live tracking available. Back to the original subject, no matter if the interface is set to serial or spanner these settings have no effect that I can see. Since it's been a couple of weeks and to make sure I wasn't seeing things I fired up my receivers and laptop this morning to test again. In both spanner and serial I switched minute precision between 2, 3, and 4 digits with no effect, the GPSr stays at 4 digits and my laptop stays at 5. My question to Garmin was since these options are already in the software why not let the user choose what they want to see?

I need help understanding something I encountered today. I have a few trackables that always stay with me and have never been shown to anyone. I've had a few bogus discoveries on some of these but I would just delete the bogus log. I received an email earlier that one of these had been discovered but when I opened the trackable page to delete the log there is no log. When I look at the cacher's "finds" it shows they logged a discovery on 3/10/19 but still no log on my trackable page. How can they get credit for a discovery without leaving a log?

After switching between firmware versions 4.2 and 4.4 it's apparent this setting does nothing. In version 4.2 no matter what this setting is three decimals are displayed, in the latest four decimals are displayed regardless of what is chosen. After I called Garmin a second time about this setting the representative agreed it was not documented but now that makes sense, why document a setting that doesn't work. I'll be sticking with the previous version until things are sorted out.

Before you roll back the version on an Oregon 750 and lose your user settings like I did go to system settings/interface/Garmin spanner/minute precision and you have your choice of 2, 3, or 4 digit precision. The owner's manual doesn't mention this and apparently Garmin is not aware of this setting.

Garmin support replied to my email today and it was pretty clear I didn't explain it well. After calling, the support rep said this is the first he has heard of it and the call ended with basically "we're sorry it no longer does what you purchased it for but it is what it is". Looks like it's time to find a way to roll back this update.

I suspect there are a few that are grandfathered although maybe not officially. I qualified for a challenge last October that took over a year to complete but since the holder of the container is more than 400 miles away I've yet to sign. The container is never actually placed, you have to meet with the cacher in order to sign the log but after a 10 hour round trip in December, where I came up empty handed, I've decided to let this one go.

The support email page.

Well I can't convince the web page I'm not a robot so that will have to wait.

Since the compass doesn't work when stopped I don't use it to search for a cache, only my current coordinates and the coordinates for the cache. If I'm within a minute of the cache I'll occasionally glance at the last three digits to make sure I'm still heading in the right direction, it's an old habit I apparently need to break. When I noticed the four decimal feature I was balancing on the side of a rock and mesquite covered hill trying to find a good route for my next move. I didn't understand why I was now 1500 feet away from the cache before I realized what I was looking at. It's great that accuracy has improved to the point that four decimals can be displayed and I also understand how calculations are more accurate, but I can also understand how someone searching for a cache while trying to keep from rolling downhill could make the same mistake I did. An option to display three or four decimals would be nice.

Regarding point #1 above and supposing the CHS triggered at 60%. I can only speak for my area but some cache owners would wait until their score was 61% before performing maintenance. Why invite a CO to hover above the minimum while they should be attempting to stay at the maximum?

The new API was made available to all API partners around the middle of 2018 with an implementation date of May 2019. Clyde announced it to the GSAK community in June of 2018 so I'm assuming other developers chose not to inform their users? Since this is buried so far behind the scene I would think it would be the developers responsibility to inform their users.