Corfman Clan

Actually, you can retrieve data for 30 caches in one API call, so you should be able to get all the favorite points for 1000 caches in 34 API calls. One is limited to 30 API calls per minute, so to update 1000 caches will take just over a minute to perform. Ok, in that case GSAK or the macro could be improved Actually, I think you just need to learn how to use GSAK and the macro. They work just fine. If you have questions about how to use them, then check out the GSAK forum.

Do you realize that the cache's coordinates have nothing to do with what state it is in? It's all up to the cache owner to specify the state. For example, I can hide a cache in Arizona and set the state to Maryland.

Actually, you can retrieve data for 30 caches in one API call, so you should be able to get all the favorite points for 1000 caches in 34 API calls. One is limited to 30 API calls per minute, so to update 1000 caches will take just over a minute to perform.

The above is wrong. Favorites are not included in pocket query results but they are included in the API call for retrieving cache details

pssh... programmers don't care. It's a problem to solve. Even if it's never used, it's a thinking exercise, hones the logic centers of the brain ;D and it's fun! Too many programmers have a bad habit of over complicating the problem. That's what I see happening here. Also, if I have found a single cache in Oklahoma and get an Oklahoma souvenir, should the souvenir really be taken from me if the cache is moved to Texas? I would hope not since I did find a cache in Oklahoma.

Actually no - as long as Groundspeak's rules for the log are follow, that the name is in the log book and the challenge is qualified - doesn't matter if the CO doesn't like the order, it's still a valid find. Well perhaps for newer challenge caches, but this isn't necessarily the case for older challenge caches.

Personally, like DanOCan, I avoid the situation by not pre-signing challenge caches. I've found upwards of 150 challenge caches and this hasn't hampered me a bit. That being said, I have pre-signed one because I was with a couple of friends and we went to it, but once I do qualify for it I probably will go and sign it again before I log a find. That won't be easy either as it's on top of Picket Post Mountain Arizona Benchmark Challenge-Dedicated

I may want to gift a geocacher a premium membership if it will be expiring soon. Is there any way to tell when a user's premium membership will expire without asking?

I wasn´t going to answer but I thought this might be actually important: 1) So you find (physically) an archived cache by chance or just because you like to search for archived caches. 2) Since you can´t adopt because the CO is absent you create a new GC. 3) You say the hidden date is the date the original CO first placed it. If you can´t see a problem in this I can: a ) The cache is not your property, it is the COs or their inheritances. b ) You actually hide (the new/old cache) in some specific date, that for me is the new hiding date since you are now claiming to be the new owner, even without the old owner permit. Soon enough, if cases like these go public, we will start to see many old caches reborn like phoenix, from the aches, just go to the original place of the cache and say: "I found the old cache, it was so damaged that I replaced with a new one but since the cache is archived a created a new GC code with the old date"... GAME ON!!! Lots of old caches can be just reborn with new GC codes but maintaining the dates... Can´t you see a problem in this... well I can! Well, I found the cache before it was archived. I figured there was no way it was muggled, so I checked on it a bit after five years from when it was archived and sure enough, there it was. I contacted the original owner and was given permission to relist it. It's the exact cache that I found in 2003, not a replacement. None of your so called problems are applicable here. So what's the problem?

Why is that wrong? Why shouldn't it be allowed? Read the cache description and it makes perfectly good sense to set the placed date as it is. I've done it myself twice. Once was for re-listing a cache that was previously archived: what a view! The other was more for fun and the theme of the cache: Diez años en la fabricación

I also noticed I have distance and direction on new cache notification. What other caches are you speaking of? If, "Needs Archived", Needs Maintenance", or "Disabled" notifications are the issue, aren't they your own or one on a watch list? Don't you already know where they are? No, these are not notifications of my logs or logs on my caches, they're notifications of other peoples logs. I have notifications set up for when somebody archives a cache, or disables it, or enables it, or reports a cache needs maintenance, etc.

Didn't catch that when the change was made. That makes notifications - a premium feature - rather useless for the FTF crowd. It is in new cache notifications, just not the others. For example, those generated for "Needs Maintenance," "Needs Archived," "Disabled", etc.

It is available with the new cache notifications, but not for any of the "log" notifications.

When the Email notifications were revamped, the distance and direction was removed from the notification. Distance and direction are very useful to have and should be added back.

Or just use a modern mail client... I do have one. Two in fact. HTML is still unwelcome as it gives me NOTHING I need. It's a solution without a problem. And someone backing this whole move thinks it's a great idea, that's possibly what's the most galling thing of all. Well, it would help with the readability of html emails

It's in the subject of the new ones, but often clipped from the right, depending upon your news reader. It definitely would be a good plan to include in the body of the email. It is in subject of the newly published cache notification, but not in any of the others.

Or just use a modern mail client...

I really miss the distance/direction in the notifications. It was at the top and easy to spot and I could decide at a glance if I cared about the notification or not.

Ninety percent of bikers are well mannered riders most of the time, even if they ignore stop signs and such, as they usually do it safely. Then there is that 10% that rides alongside someone, instead of single file, blocking the road. Cars will back up behind them somewhere where its unsafe to pass, and the roadway speed will be suddenly reduced to 15mph for everyone. And it's never people in street clothes riding ordinary bikes, but always someone in a skintight outfit on a thousand dollar bike, looking for attention, or conflict. Bikers ride motorcycles. Cyclists ride bicycles. If you don't know the difference, then perhaps you shouldn't make such comments. But perhaps that is the point.

Try to move it within a mile of your home coordinates. That would be neat!

If the shortest path to the cache at S38 is up over the north pole, it will pull your centroid north. That somehow depends on how the cache centroid is defined and computed. Which definition is used? Agreed. What exactly is the centroid of a sphere? Should it be kept on the surface of the sphere or somewhere inside the sphere?

No, it wouldn't change anything. The owner of a grid challenge doesn't have to accept historical ratings, even if they're listed in the logs. In addition, most of those modeled after the original Well Rounded Cacher Challenge, disallow including caches that have had their D/T ratings changed. Though a problem with that is that there is no reasonable way to know if a cache's D/T rating has changed. The OP would help with this, but I imagine the application for the request is extremely limited and probably not worth the effort.

It would be nice to have an option to turn off the email that is sent when a pocket query is run.

As the owner of a "third party leaderboard", two cats, and a dog, I find this discussion interesting. I'm not sure how I could ignore a cacher's finds and still maintain valid statistics. There has been requests to ignore "armchair" cachers since bogus finds do have an effect on the statistics.

I have a SPOT too. I've had to use the "hey, I'm not hurt, I'm just having technical difficulties..." button once. Cedar Basin North