LonelyCache

rocketsciguy wrote:...and download a GPX as well....

rocketsciguy wrote:

rocketsciguy wrote:...and download a GPX as well....

Okay, GPX is asking too much, but how about creating or adding to a Bookmark list? I know there's an API interface for that. One could then create a Pocket Query based on that bookmark list and download a GPX. LonelyCache just pushes the bookmark list and leaves the hard work of compiling and delivering a GPX to Groundspeak. Just a thought....

Corfman Clan wrote:Revamped how a user's session data is stored and managed. Session data includes a logged in user's LonelyCache profile data and Geocaching.com profile data. This was needed to be able to add member features that take advantage of the Geocaching.com Live API.

Corfman Clan wrote:

rocketsciguy wrote:Tried the Most Wanted list. Cool! I have my new wish list! But I immediately notice a glaring omission. There is a 3.75+ year-old unfound puzzle cache less than one mile from my home coords (sadly not owned by me), which is not on my Ignore List... and it doesn't show on my Most Wanted. To me it was a "CP/Mile" score of 524, so I don't know if that makes it fall off the top of the chart (overflow error? ) or if there is a catch that prevents caches from showing that are less than 1 mile away.

The cache should be included in the list. Would you pm me with your home coordinates, your user name, and the cache in question and I'll investigate why it isn't showing up.

One note, for caches less than a mile away, 1 is used for the divisor, not the actual distance. Basically, if dist < 1 mile, use nfCPs otherwise use nfCPs / dist. It didn't make a lot of sense to inflate the Pts/mile for caches very close and it was a nice way to avoid the divide by zero error for a cache at the same location.

Corfman Clan wrote:

Corfman Clan wrote:

rocketsciguy wrote:Tried the Most Wanted list. Cool! I have my new wish list! But I immediately notice a glaring omission. There is a 3.75+ year-old unfound puzzle cache less than one mile from my home coords (sadly not owned by me), which is not on my Ignore List... and it doesn't show on my Most Wanted. To me it was a "CP/Mile" score of 524, so I don't know if that makes it fall off the top of the chart (overflow error? ) or if there is a catch that prevents caches from showing that are less than 1 mile away.

The cache should be included in the list. Would you pm me with your home coordinates, your user name, and the cache in question and I'll investigate why it isn't showing up.

One note, for caches less than a mile away, 1 is used for the divisor, not the actual distance. Basically, if dist < 1 mile, use nfCPs otherwise use nfCPs / dist. It didn't make a lot of sense to inflate the Pts/mile for caches very close and it was a nice way to avoid the divide by zero error for a cache at the same location.

I should have mentioned this in the release notes, but Premium Member Only caches will only show up on a Premium Member's Most Wanted list. The release notes have been edited to reflect this.

rocketsciguy wrote:Now that you mention it, I don't see any Premium Member Only caches on my list (including the one that caught my attention), but I am a Premium Member so they should be there. Anyone else not seeing or seeing Premium caches?

• Retrieving Geocaching.com profile information is no longer dependent on logging in with the exact user name as on Geocaching.com. That is, it is no longer case sensitive, nor is having leading and trailing space an issue.
• Corrected the problem where Premium Member Only caches were being excluded from Premium members and included for Basic members.
• When you update your profile to update your recent finds, a job to do that will be initiated immediately instead of having to wait for the next user session to occur.

Corfman Clan wrote:I have updated the site with fixes for some of the issues with this release:

• Retrieving Geocaching.com profile information is no longer dependent on logging in with the exact user name as on Geocaching.com. That is, it is no longer case sensitive, nor is having leading and trailing space an issue.
• Corrected the problem where Premium Member Only caches were being excluded from Premium members and included for Basic members.
• When you update your profile to update your recent finds, a job to do that will be initiated immediately instead of having to wait for the next user session to occur.

ktTris wrote:Merry Christmas!
I'm not getting today's finds. I'm not expecting help today, just posting the info.