Difference between revisions of "Hash collision achievement"

From Geohashing
imported>Fippe
(Goslar)
m (successful cache collision)
 
(11 intermediate revisions by 6 users not shown)
Line 15: Line 15:
  
 
==Reverse collision==
 
==Reverse collision==
There is now a geocache listing, [http://coord.info/GC4JCB6 GC4JCB6], which reverses the challenge. In order for a geocacher to complete the challenge (akin to earning the ribbon) and be able to log the cache as found, the geocacher must find a geocache that is within 1km of a geohash location. It follows that any geohasher that has already earned the Collision Achievement has already completed this geocaching challenge. But rather than introduce geocaching to the geohashing community, this cache serves to introduce geocachers to the concepts of geohashing. Of course, to claim this geocache as found, one would also need to physically visit the geocache, which is located in Southern New Mexico, and it is unlikely that a herd of Geohashers will descend on the state to do so. There are other geocache listings that introduce the concepts of geohashing as well.
+
There is now a geocache listing, [http://coord.info/GC4JCB6 GC4JCB6], which reverses the challenge. In order for a geocacher to complete the challenge (akin to earning the ribbon) and be able to log the cache as found, the geocacher must find a geocache that is within 1km of a geohash location. It follows that any geohasher that has already earned the Collision Achievement has already completed this geocaching challenge. But rather than introduce geocaching to the geohashing community, this cache serves to introduce geocachers to the concepts of geohashing. Of course, to claim this geocache as found, one would also need to physically visit the geocache, which is located in Southern [[New Mexico]], and it is unlikely that a herd of Geohashers will descend on the state to do so. There are other geocache listings that introduce the concepts of geohashing as well.
  
You will find another reversed challenge at [http://www.opencaching.de www.opencaching.de]: The geocache [http://www.opencaching.de/viewcache.php?wp=OCF495 OCF495] in Berlin/Germany.  
+
You will find another reversed challenge (Safari Cache) at [http://www.opencaching.de www.opencaching.de]: The geocache [http://www.opencaching.de/viewcache.php?wp=OCF495 OCF495] in Berlin/Germany. This cache can be loged as son as you visit your first geohash. There is no need to travel to Berlin.
  
 
==Winners==
 
==Winners==
Line 35: Line 35:
 
*[[2018-09-28 52 9]] ([[Hannover, Germany]]): [[User:Fippe|Fippe]] found the [https://coord.info/GC4EHDT GC4EHDT] Geocache 265 meters near the Geohash, in line of sight.
 
*[[2018-09-28 52 9]] ([[Hannover, Germany]]): [[User:Fippe|Fippe]] found the [https://coord.info/GC4EHDT GC4EHDT] Geocache 265 meters near the Geohash, in line of sight.
 
*[[2018-11-23 54 13]] ([[Stralsund, Germany]]): [[User:SastRe.O|SastRe.O]] visited the [https://coord.info/GC7HJR8 GC7HJR8] geocache, 27 meters from the Geohash.
 
*[[2018-11-23 54 13]] ([[Stralsund, Germany]]): [[User:SastRe.O|SastRe.O]] visited the [https://coord.info/GC7HJR8 GC7HJR8] geocache, 27 meters from the Geohash.
 +
*[[2023-08-08 47 8]] ([[Zürich, Switzerland]]): [[User:globescorer|globescorer]] found the [https://coord.info/GC5492F GC5492F] Geocache 393.28 meters near the Geohash, but in line of sight.
 +
*[[2023-10-29 -34 138]] ([[Adelaide North, Australia|Adelaide, Australia]]): [[User:XXOs|XXOs]] found the [https://coord.info/GC2CJWA GC2CJWA] Geocache 90 metres near the Geohash.
  
 
==Honorable Mention==
 
==Honorable Mention==
Line 74: Line 76:
 
* [[2015-05-23 66 25]] ([[Rovaniemi, Finland]]): [[User:Isopekka|Isopekka]] found the [http://coord.info/GCMRV9 GCMRV9] geocache 281 metres from the hashpoint, not in line of sight.
 
* [[2015-05-23 66 25]] ([[Rovaniemi, Finland]]): [[User:Isopekka|Isopekka]] found the [http://coord.info/GCMRV9 GCMRV9] geocache 281 metres from the hashpoint, not in line of sight.
 
* [[2015-09-27 37 -122]] ([[San Francisco|Los Altos Hills, California]]): [[User:Erik_r|Erik_r]] and [[User:meta-alt|meta-alt]] found the [http://coord.info/GC2THTB GC2THTB] geocache about 500 meters from the hashpoint.
 
* [[2015-09-27 37 -122]] ([[San Francisco|Los Altos Hills, California]]): [[User:Erik_r|Erik_r]] and [[User:meta-alt|meta-alt]] found the [http://coord.info/GC2THTB GC2THTB] geocache about 500 meters from the hashpoint.
*[[2018-08-05 53 9]] ([[Hamburg, Germany]]): [[User:Fippe|Fippe]] found the [https://coord.info/GCDCBE GCDCBE] Geocache 380 meters near the Geohash, not in line of sight.
+
*[[2018-08-05 53 9]] ([[Hamburg (West), Germany]]): [[User:Fippe|Fippe]] found the [https://coord.info/GCDCBE GCDCBE] Geocache 380 meters near the Geohash, not in line of sight.
 +
* [[2021-02-09 45 4]] ([[Lyon, France]]): [[User:Baarde|Baarde]] found the [http://coord.info/GC8C9VX GC8C9VX] geocache 777 meters from the hashpoint, not in line of sight.
 +
* [[2021-02-19 32 -96]] ([[Dallas, Texas]]): [[User:Luke|Luke]] and [[User:Gabe|Gabe]] found the [http://coord.info/GC7TFWN GC7TFWN] geocache 455 meters from the hashpoint, not in line of sight.
 +
* [[2023-01-25 47 8]] ([[Zürich, Switzerland]]): [[User:globescorer|globescorer]] found the [https://www.geocaching.com/seek/log.aspx?LUID=6ee8795e-ed81-4ffe-9012-895818219fae GC9NC74] geocache 800 meters from the hashpoint, not in line of sight.
 +
* [[2023-02-15 47 8]] ([[Zürich, Switzerland]]): [[User:globescorer|globescorer]] found the [https://www.geocaching.com/geocache/GC8KW6M GC8KW6M] geocache 200 meters from the hashpoint, not in line of sight.
  
 
[[Category:Geocaching]]
 
[[Category:Geocaching]]

Latest revision as of 06:49, 29 October 2023

Hash Collision Icon

Template:Hash collision

Hashcollision.png
This user earned the Hash collision achievement
by discovering a geocache near the ({{{latitude}}}, {{{longitude}}}) geohash on [[{{{date}}} {{{latitude}}} {{{longitude}}}|{{{date}}}]].

Anyone accomplishing this achievement can add this template to their user and/or expedition page.

Visit a geohash and, either through prior knowledge or pure chance, find a geocache on site of the hash. To count as being at the geohash site, the geocache must lie within sight of the circle of uncertainty of your GPS around the geohash coordinates. Placing a cache yourself does not count, unless you placed it before the coordinates of the geohash were announced, but you can place one that helps other geohashers later in the day win this award.

Proof

For proof, the contents of the cache should be photographed, particularly if it has a logbook; feel free to sign it. A link to a geocache site advertising that location would also be good.

Reverse collision

There is now a geocache listing, GC4JCB6, which reverses the challenge. In order for a geocacher to complete the challenge (akin to earning the ribbon) and be able to log the cache as found, the geocacher must find a geocache that is within 1km of a geohash location. It follows that any geohasher that has already earned the Collision Achievement has already completed this geocaching challenge. But rather than introduce geocaching to the geohashing community, this cache serves to introduce geocachers to the concepts of geohashing. Of course, to claim this geocache as found, one would also need to physically visit the geocache, which is located in Southern New Mexico, and it is unlikely that a herd of Geohashers will descend on the state to do so. There are other geocache listings that introduce the concepts of geohashing as well.

You will find another reversed challenge (Safari Cache) at www.opencaching.de: The geocache OCF495 in Berlin/Germany. This cache can be loged as son as you visit your first geohash. There is no need to travel to Berlin.

Winners

Honorable Mention

A geocache discovered within one kilometer of the geohash wins you the honorable mention.