LonelyCache

LonelyCache provides a data export service. This service allows, for example, a user to import LonelyCache data into a GSAK database. Data exported are a geocache's GC Code, Current Cache Points (cCP), Next Find Cache Points (nfCP), DGP Region, and County. Currently this service is unlimited and offered to everyone.

Soon, the data export service will be limited to only registered and active LonelyCache members. An active member is simply one that has used the LonelyCache website as an authenticated user within the past seven days. Currently, I don't know what "soon" is other than it is the next time I update the LonelyCache website. That may be tomorrow or a couple weeks from now.

The GSAK macro, LonelyCacheImport, has been updated and is compatible with how the data export service works now and how it will work when this change occurs. The updated macro is available here on GSAK. If you use this macro, I suggest updating sooner than later so as to avoid any interruption with the data export service.

I debated long and hard with whether I should make this change, but in the end, I think it is necessary. There are some usage requirements LonelyCache is held to by the API partner agreement with Geocaching HQ so I think it's important that all use gets counted.

Russell

The updated macro is now required. You can get it from the link provided in the OP.

When I try to run the new macro I get the following error: "Error: A valid Geocaching User Id is required. This service is only offered to active LonelyCache users."

I've made sure to sign in to Lonelycache.com. Maybe I need to go find some caches to become active?

The macro retrieves your Geocaching ID from a SQLite DB table, so perhaps yours isn't set up or is different than what you logged into LonelyCache with. The DB is the gsak.db3 database in the GSAK app folder. The table is UserInfo and the row has the uKey column set to UserId. I'm not sure how that's set in GSAK, but perhaps through the Tools -> Options... menu, then set, "Method for matching owned and found caches" to OwnerID with yours. To get your Geocaching MemberID go to https://www.geocaching.com/account/settings/membership. Let me know if that works.

I switched the method for matching owned and found caches from "Exact Match" to "Owner ID#". That didn't seem to do anything. However, I tried clicking the option to "Update User Information..." under Geocaching.com access and now the macro is working. I changed the method for matching owned and found caches back to "Exact Match" and the macro is still working. I assume the "Update User Information..." option is the fix.

Thanks Russell!

Alright, glad that's resolved. Now that I know, It makes sense how to get that table populated. Thanks for the info.

I have updated the macro, and had logged in successfully last week in order to run it, but now the site seems stuck on the sign in with Geocaching page and won't let me sign in normally. Nothing seems to happen either clicking the button or the sign in link, and the macro says it has been too long.

I seem to be having a similar problem. No matter what I do I can't get past the geocaching.com page where I agree to share data with LonelyCache. So I can't log in to LonelyCache at this point.

I noticed an issue a couple days ago on my testbed that there was an issue but didn't realize it extended to production. There's some handshaking going on between LonelyCache and Geocaching.com and Geocaching.com started returning an error code, "Bad Request." At this time, I don't know what changed and as far as I know, nothing on the LonelyCache side. Basically, when the error occurs, LonelyCache throws you back to the log in page. So you get in a sort of endless loop, attempting to log in.

Corfman Clan wrote:I noticed an issue a couple days ago on my testbed that there was an issue but didn't realize it extended to production. There's some handshaking going on between LonelyCache and Geocaching.com and Geocaching.com started returning an error code, "Bad Request." At this time, I don't know what changed and as far as I know, nothing on the LonelyCache side. Basically, when the error occurs, LonelyCache throws you back to the log in page. So you get in a sort of endless loop, attempting to log in.

This issue is now fixed and there should be no issues signing into LonelyCache. Please let me know if that is not the case.