<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>[Cancelled] GC9YY43 - 161km Challenge Cache</title>
        <description> Hi checker experts,

I would need a checker for the following challenge (GC9YY43):
Find 10 caches of different types (excluding locationless and lab caches) that have a distance of 161km to each other.

In fact 161m would be a no-brainer as this is the minimum required distance, but 161km might be a bit more challenging. At least it took me some travels to complete as you can see in the following flops map: https://t1p.de/fpaj1 (shortened URL).
Providing evidence using a map like this is simple, but coding a checker to proof this challenge might be challenging as well. But I am quite sure you have seen more complicated requests and will manage. :-)

Kind regards and good luck,
Thomas aka topax_xx</description>
        <link>/forum/read.php?10,64682,64682#msg-64682</link>
        <lastBuildDate>Tue, 17 Mar 2026 05:51:50 +0000</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>/forum/read.php?10,64682,65419#msg-65419</guid>
            <title>Re: GC9YY43 - 161km Challenge Cache</title>
            <link>/forum/read.php?10,64682,65419#msg-65419</link>
            <description><![CDATA[ The feedback from my reviewer took some time as he &#039;challenged&#039; also other reviewers. Conclusion is that he does not agree to the argument that this challenge violates the &quot;guideline 10&quot; <b>but</b> there have been discussions with geocaching HQ in the past that these kind of challenges are &quot;not wanted&quot; as they seem to be &quot;not simple and easy to explain, follow and document&quot; - and presumably not that easy to write a checker for that is now a requirement.<br />
There have been similar caches considering distances between single caches, even from moderators of this forum (e.g. GC7K4KC) or the one bmuzzin mentioned in the previous post, but it&#039;s not worth the effort to fight for this one as I have many other cache ideas in stock, so I reject the request and discard this challenge idea.<br />
This forum thread can be closed.]]></description>
            <dc:creator>topax_xx</dc:creator>
            <category>ARCHIVE Checker requests (impossible)</category>
            <pubDate>Tue, 20 Sep 2022 04:15:43 +0000</pubDate>
        </item>
        <item>
            <guid>/forum/read.php?10,64682,65409#msg-65409</guid>
            <title>Re: GC9YY43 - 161km Challenge Cache</title>
            <link>/forum/read.php?10,64682,65409#msg-65409</link>
            <description><![CDATA[ I&#039;ve recently created a script where you need two finds, with the &#039;boat&#039; attribute that are 6000km apart. It required a custom script, as there was no existing script that could be tagged to calculate it. It was accepted by my reviewer without question, and your request seems somewhat similar in terms of criteria.<br />
<br />
However, I think doing the actual calculation is going to prove exceedingly difficult. Finding the two most distant points in a set is a &quot;known problem&quot; that can be solved in O(N x log(N)) time, thus finding a pair of caches some distance apart is not difficult, and can be achieved in the 60 seconds checkers have to run. However, finding 10 points that are all a large distance apart seems like it wouldn&#039;t be able to be calculated within that time frame, especially for users with a large number of finds of many types.]]></description>
            <dc:creator>bmuzzin</dc:creator>
            <category>ARCHIVE Checker requests (impossible)</category>
            <pubDate>Tue, 20 Sep 2022 01:50:05 +0000</pubDate>
        </item>
        <item>
            <guid>/forum/read.php?10,64682,64700#msg-64700</guid>
            <title>Re: GC9YY43 - 161km Challenge Cache</title>
            <link>/forum/read.php?10,64682,64700#msg-64700</link>
            <description><![CDATA[ Thank you. I will contact the reviewer and come back to you.]]></description>
            <dc:creator>topax_xx</dc:creator>
            <category>ARCHIVE Checker requests (impossible)</category>
            <pubDate>Fri, 26 Aug 2022 06:06:56 +0000</pubDate>
        </item>
        <item>
            <guid>/forum/read.php?10,64682,64699#msg-64699</guid>
            <title>Re: GC9YY43 - 161km Challenge Cache</title>
            <link>/forum/read.php?10,64682,64699#msg-64699</link>
            <description><![CDATA[ The final arbitrators of what is and is not allowed are the reviewers. We only provide guidance based on our understanding of the guidelines and advice we have previously received from reviewers.<br />
<br />
I am aware of other challenges being rejected due to use of distances between caches being used in the criteria, citing this guideline. If you wish to ask your reviewer and get back to us, go ahead.]]></description>
            <dc:creator>sumbloke</dc:creator>
            <category>ARCHIVE Checker requests (impossible)</category>
            <pubDate>Fri, 26 Aug 2022 06:04:02 +0000</pubDate>
        </item>
        <item>
            <guid>/forum/read.php?10,64682,64698#msg-64698</guid>
            <title>Re: GC9YY43 - 161km Challenge Cache</title>
            <link>/forum/read.php?10,64682,64698#msg-64698</link>
            <description><![CDATA[ I read the guidance carefully before I raised this checker request and disagree to the violation of guidance 10!<br />
This challenge is not referring to a geographic area, but can be completed everywhere, well at least everywhere the corresponding cache types are available. It neither defines a region where the caches have to be located nor any other geographical constraints besides the distance to each other.<br />
I assume guideline 10 was defined to enable the challenge can be fulfilled by anyone and does not enforce geocachers to travel to distinct places (before finding the cache container). This is not needed for this challenge at all. There is also no relation to the home coordinates of the geocacher or any other local or global reference coordinate.<br />
<br />
Is there eventually a second opinion from another moderator? :-)]]></description>
            <dc:creator>topax_xx</dc:creator>
            <category>ARCHIVE Checker requests (impossible)</category>
            <pubDate>Fri, 26 Aug 2022 05:56:44 +0000</pubDate>
        </item>
        <item>
            <guid>/forum/read.php?10,64682,64697#msg-64697</guid>
            <title>Re: GC9YY43 - 161km Challenge Cache</title>
            <link>/forum/read.php?10,64682,64697#msg-64697</link>
            <description><![CDATA[ Sorry, this sort of challenge is no longer allowed under <a href="https://www.geocaching.com/help/index.php?pg=kb.chapter&amp;id=127&amp;pgid=206#criteria"  rel="nofollow">guideline 10</a>:<br />
<blockquote class="bbcode"><div><small>Quote<br /></small><strong>Not acceptable</strong><br />
Challenges based on geographic areas other than countries, states/provinces, counties (or their local equivalent). Examples: user-defined mapping polygons, latitude/longitude, radius, etc.</div></blockquote>]]></description>
            <dc:creator>sumbloke</dc:creator>
            <category>ARCHIVE Checker requests (impossible)</category>
            <pubDate>Fri, 26 Aug 2022 04:20:12 +0000</pubDate>
        </item>
        <item>
            <guid>/forum/read.php?10,64682,64682#msg-64682</guid>
            <title>[Cancelled] GC9YY43 - 161km Challenge Cache</title>
            <link>/forum/read.php?10,64682,64682#msg-64682</link>
            <description><![CDATA[ Hi checker experts,<br />
<br />
I would need a checker for the following challenge (GC9YY43):<br />
Find 10 caches of different types (excluding locationless and lab caches) that have a distance of 161km to each other.<br />
<br />
In fact 161m would be a no-brainer as this is the minimum required distance, but 161km might be a bit more challenging. At least it took me some travels to complete as you can see in the following flops map: <a href="https://t1p.de/fpaj1"  rel="nofollow">https://t1p.de/fpaj1</a> (shortened URL).<br />
Providing evidence using a map like this is simple, but coding a checker to proof this challenge might be challenging as well. But I am quite sure you have seen more complicated requests and will manage. :-)<br />
<br />
Kind regards and good luck,<br />
Thomas aka topax_xx]]></description>
            <dc:creator>topax_xx</dc:creator>
            <category>ARCHIVE Checker requests (impossible)</category>
            <pubDate>Wed, 24 Aug 2022 05:49:58 +0000</pubDate>
        </item>
    </channel>
</rss>
