mustakorppi

Thanks. I assumed the actual cartridges aren't checked, but I also assumed that rules about virtual stages would apply to Wherigos too. And that if they apply, they would be checked in review. So they'd need to be listed as waypoints on the cache page. And at that point why not enforce maintenance rules too.

There's a Wherigo that was published around the same time as, ahem, not-arisoft's long distance multis, where you need to go to the deepest spot in Finnish territorial waters to unlock the next stage. I wonder who the local guardian for that spot is, and what their expected tasks are.

I would like to report two regressions: ”Hey wait!” is back Links like https://adventurelab.page.link/6RBX show the warning even though these links are generated by the Adventure Lab app itself, and the links lead to a geocaching.com sub-domain (or open the Adventure Lab app on mobile devices).

Mine is on greasyfork, listed under the catchy name "geocaching.com external url warning remover".

My script should still be working, with the caveat that I never got around to adding support for discontinued page elements and links in comments. If you’re using my script, could you please link the cache where it doesn’t work? HQ, is http://adventurelab.page.link a supported way to create ”readable” links to adventure labs? That causes the pop-up to show... Also, why is ”Hey wait!” back in the pop up?

Starting from step 6 you'd need to have found specific caches in the UK so the checker isn't much fun for everyone else.

I have to think the extra maintenance work isn't great for the CO to begin with, and the feedback from finders who get halfway thru a multi before DNFing a physical waypoint can be pretty salty. And I can imagine it must be extra demotivating to have finders trade coordinates and go directly to the final container on a physical multi. Whichalso turns into a negative feedback loop as it's misleading to everyone trying to do the multi properly. It has taken me way too long to realize that no one who's logged a find in recent years has actually found the waypoint I've been searching for in vain...

Due to covid-related restrictions for public events, the GIFF 2021 souvenir came from logging this trackable with a code from the GIFF video. Similar to how the rover trackable worked. Trackable logs themselves aren’t currently allowed criteria I think, but souvenirs are.

The first challenge could be ”have 1 souvenir”. The souvenir from GIFF 2021 was obtainable without a find. Or the Mars rover one…

The professional cyclist Filippo Ganna was the first ever to maintain an average speed of over 35mph (35.289mph to be exact) in his new 1 hour world record, on October 8th 2022. This was riding a prototype bike specially build for that purpose by the best in the business, wearing a custom skinsuit, on an indoor velodrome with carefully maintained temperature to get the lowest air resistance without quite overheating in exactly 60 minutes of maximal effort, and of course with a support team to figure all of this out.

I don’t usually bother checking as it’s mostly noobs who don’t even care about stats. But after a recent found it log that just said ”easy”, I went to check it and deleted every other online-only find from the past year too.

You intend to ride a motorized vehicle capable of going 100kph on a trail intended for bicycles and pedestrians? And that's legal in your jurisdiction? Maybe there's something I'm missing but for now I'm just glad there's an ocean between us.

I… that’s a quick fix and it might be all you ever need to do, but I would still suggest actually validating your XML output as a part of the process.

This is a tough one. The last streak challenge I'm trying to complete is Sparkyfry's Challenge of the Millennium (1000 day streak, only physical caches count), which will be done next week. Not necessarily going to stop the streak immediately after, but it would be hard to stay motivated through the winter, especially since I'll no longer have any excuse to go caching by car. If the summer is nice, I hope I can squeeze in a couple of bikepacking trips to get finds in counties I'm still missing (and more importantly, visit counties I've never actually been to.) Not sure how much effort, if any, I'll put to any other geocaching stats. Right now Veloviewer Tile Hunting seems more interesting to me. Probably go to the mega in Helsinki because why not. There are a few cache ideas I've been mulling over, but they seem too difficult to be worthwhile. We'll see. So I guess it's mostly going to be casual caching and a marked drop in my finds per year.

The problem with Garmin MapSource is that it tries to validate the file before loading it. And that's a problem because the new pocket query doesn't follow the schema it claims it should be validated against, i.e. http://www.topografix.com/GPX/1/0/gpx.xsd Quoting the relevant bit of the schema here, the <xsd:sequence> indicates that the following elements should appear in the given order: name, desc, author... <xsd:element name="gpx"> <xsd:complexType> <xsd:sequence> <xsd:element name="name" type="xsd:string" minOccurs="0"/> <!-- GPX file name --> <xsd:element name="desc" type="xsd:string" minOccurs="0"/> <!-- GPX file description --> <xsd:element name="author" type="xsd:string" minOccurs="0"/> <!-- GPX file author --> But see how in new Pocket Queries the <author> element is out of order: <gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.Groundspeak.com/cache/1/0/1 http://www.Groundspeak.com/cache/1/0/1/cache.xsd" creator="Groundspeak Pocket Query" xmlns="http://www.topografix.com/GPX/1/0"> <author>Groundspeak</author> <name>Belgia</name> <desc>Geocache file generated by Groundspeak</desc> While waiting for HQ to fix this, you can open the gpx file in any text editor and cut the line <author>Groundspeak</author> and paste it after the line <desc>Geocache file generated by Groundspeak</desc> Save, and if you didn't make mistakes the file should open in MapSource.

I of course don’t have API access myself, but the change was discussed on another API partner’s forum back in 2019 (as the Groundspeak HQ —> Geocaching HQ name change broke their functionality). We are talking about this API, right? https://api.Groundspeak.com/documentation#geocache-types

I’m confused, didn’t these name changes (and Geocaching HQ Block Party) happen in June 2019? Is something in the API going to change again? Asking because a certain other API partner is probably still using cache type names where they really should use the corresponding id…

Never once saw a can like that in my 1 year mandatory service. The 12.7mm machinegun had ammo cans you opened with a giant can opener, but I don't carry one when caching so this type of cans are like a field puzzle to me.

I’m still on my streak, so I can’t be too picky. I try to remember to check my stats to see if I’m missing a cache type for the calendar day (I have 3 full rounds of find date calendar, but not for any single cache type). When I’m travelling, I try to find railway station and church caches, at least one cache per county and multiple cache types per county if possible. Oldest per county and island caches per county are usually logistically too difficult for me, so those challenges I ignore. There are local cache type challenges for earthcaches, virtuals and wherigos (and some attribute based as well) that require obscene amount of finds so I’m basically just ignoring them. Especially since I don’t enjoy these cache types much either. I also have an ongoing FTF per month streak that I’m conscious of, but I guess I wouldn’t care too much if that broke.

The stat exclusion isn’t reflected in the API. I don’t know how HQ handles it internally, but API partners would basically have to look at the bookmark list that lists these caches. I’m guessing Project-GC doesn’t.

That cache (and all other known antipode caches) have been marked for exclusion from statistics. Also mystery caches must now be located within 2 miles of the bogus coordinates.

Can't this be solved as a multiple choice too, if that's easier than decrypting the URL? The cartridge must be hosted on Wherigo.com.

I don't always follow my own principle, but to me location is the main point and the cache and container are secondary. So surely FPs should also be given based on location, even if the container isn't great. But the cache page and container represent the COs effort more directly, so it feels bad to not give a FP for a gadget cache, even if the location is uninteresting.

I'm not one of the test group it seems. I'm somewhat curious why this test wasn't conducted with the existing Experimental features function, where everyone with an interest could test it, and provide feedback. Raw FP count is probably the right choice for the app. FP score is a fairly good indicator of accessibility of the cache, and that's worthwhile information when using the app. There's a place for multi-hour caching experiences, but doing those is not a choice I'd make when spontaneously looking at the app. When travelling, I want to find nice caches that I can do as a side activity, not caches that would take over my entire trip. And of course the flagged caches change as I filter out everything I've already found, so even if the high FP% aren't in the first set, they will be flagged sooner or later.

Lamp posts are generally round around here, yes. The ”problem” is that they generally don’t contain caches. But search a random fir tree and chances are you’ll find a preform tube.