Hash collision achievement

Hash Collision Icon

Template:Hash collision

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 at www.opencaching.de: The geocache OCF495 in Berlin/Germany.

Winners

• 2009-03-05 49 -123 (Vancouver, BC, Canada): Four people discovered the GC1HTNJ geocache ten to twenty metres from the hashpoint.
• 2009-08-22 52 13 (Berlin, Germany): davidc, relet and Trurl discover the geocache GC15NT8 262 metres from the hashpoint but within line of sight across the field. Proof: one two.
• 2010-10-02 52 0 (Cambridge, UK): Benjw discovered the GC2AB3N geocache 10.9 metres from the hashpoint.
• 2010-10-25 34 -84 (Roswell, Georgia): ElSupreme discovered the GC1YRE4 geocache about 5 meters from the hashpoint.
• 2010-10-26 55 13 Fasanen found GCYK9V with 160 m clear line of sight to the hashpoint.
• 2011-06-26 27 -81 (Sebring, FL): Rhonda discovered the GCPBGY geocache about 5 meters from the hashpoint.
• 2011-08-16 48 9 (Stuttgart, Germany): Steingesicht discovered the GC2W77J geocache about 11 meters from the hashpoint.
• 2012-01-24 55 13 (Eslöv, Skåne, Sweden): Llavids discovered the GC29X1A geocache just above 16 meters from the hashpoint.
• 2013-08-07 32 -117 (San Diego, California): Mathgeek discovered the GC48BZK geocache just about 173 ft. from the hashpoint.
• 2013-10-09 51 5 (Eindhoven, Netherlands): Eupeodes found the GC4FR3f geocache at 270 meters from the hash with a clear line of sight from hash to cache

Honorable Mention

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

• 2008-11-26 48 8 (Pforzheim, Germany): Ekorren and Danatar discovered the GC14WEH geocache 0.85 km from the hashpoint.

• 2009-01-01 36 -75 (Virginia Beach, Virginia): NCBears discovered the GCGF7E geocache 298 meters from the hashpoint.

• 2009-03-28 39 -86 (Bloomington, Indiana): Erik and Kira discovered the GCQ4ZP geocache 740 meters from the hashpoint.

• 2009-08-02 39 -84 (Cincinnati, Ohio): Scottkuma & family discovered the GCX7AD geocache 414 meters from the hashpoint.

• And, on the very same day... 2009-08-02 39 -84 (Cincinnati, Ohio): Scottkuma & family discovered the GCX7AE geocache 433 meters from the hashpoint.

• 2009-08-13 52 13 (Berlin, Germany): Four find the GCY864 geocache 116 metres from the hashpoint but unfortunately not in line of sight.

• 2010-10-08 56 13 (Hässleholm, Sweden): Llavids found the GC1K3MW geocache 234 metres from the hashpoint, not in line of sight.

• 2010-10-10 -31 115 (Perth, Australia): Phi-loci-raptor and Pyroteknik are thrwarted by dense bush despite locating GC1YYV4 143m from the hashpoint.

• 2010-11-21 49 8 (Mannheim, Germany): Mampfred and QuarterCacher climbing a tree to find the GC14VHJ geocache about 130 meters from the hash.

• 2010-12-28 55 13 (Malmö, Sweden): Llavids and OlofL found the GC1P8ZK geocache 162 metres from the hashpoint and also a opencaching mystery cache OS00C6 final solution within clear line of sight.

• 2011-04-30 55 13 (Malmö, Sweden): Llavids found the GC1XV8Z geocache 146 metres from the hashpoint probably within clear line of sight.

• 2011-07-04 66 25 (Rovaniemi, Finland): Isopekka found the GCVWW9 geocache 596 metres from the hashpoint, not in line of sight.

• 2011-08-06 42 -88 (Schaumburg, Illinois): RocketMac found the GC1JTJN geocache 176 meters from the hashpoint, not in line of sight.

• 2011-09-15 55 13 (Malmö, Sweden): Llavids found the GC1JQA0 geocache 119 meters from the hashpoint, not in line of sight.

• 2011-12-11 42 -87 (Kenosha, Wisconsin): RocketMac found the GC349X9 geocache 696 feet from the hashpoint, in line of sight.

• 2012-03-30 52 5 (Utrecht, Netherlands): Mennoowh found the GC1QR79 geocache 150 meters from the hashpoint, not in line of sight.

• 2012-04-05 38 -90 (St. Louis, Missouri): RocketMac discovered the GC2EVR1 geocache 461 feet and within line of sight from the hashpoint.

• 2012-06-29 51 5 (Eindhoven, Netherlands): Eupeodes found the GC1WXFZ geocache 90 meters from the hashpoint, not in line of sight.

• 2012-07-02 52 4 (Amsterdam, Netherlands): Eupeodes found the GC2ZKBY geocache 140 meters from the hashpoint, not in line of sight.

• 2013-04-07 52 6 (Enschede, Netherlands): Eupeodes found the GC2VP48 geocache 470 meters from the hashpoint, not in line of sight.

• 2013-05-19 52 5 (Utrecht, Netherlands): Eupeodes found the GC11CZR geocache 840 meters from the hash point, not in line of sight.

• 2013-05-30 52 4 (Amsterdam, Netherlands): Palmpje found the GC3E2E0 geocache 345 meters from the hashpoint, just to get this ribbon.

• 2013-10-25 49 8 (Mannheim, Germany): Q-Owl found the GC36MH4 geocache 900 meters from the hashpoint, but in line of sight.

• 2014-03-06 48 2 (Paris, France): Dunaril found the GC2FGPZ geocache 500 meters from the hashpoint.

• 2014-04-20 49 8 (Mannheim, Germany): Q-Owl found the GC2RRTR geocache 150 meters from the hashpoint, not in line of sight.

• 2014-05-02 51 9 (Kassel, Germany): GeorgDerReisende found the GC3J4A9 geocache 647 meters from the hashpoint, not in line of sight.

• 2014-05-21 51 9 (Kassel, Germany): GeorgDerReisende found the GC4H3GG geocache 971 meters from the hashpoint, not in line of sight.

• 2014-05-31 50 10 (Schweinfurt, Germany): GeorgDerReisende found the GC38X55 geocache 473 meters from the hashpoint and within line of sight from the hashpoint.

• 2014-06-02 51 9 (Kassel, Germany): GeorgDerReisende found the GCWH77 geocache 734 meters from the hashpoint, not in line of sight.

• 2014-06-05 51 10 (Nordhausen, Germany): GeorgDerReisende found the GC3EAQ9 geocache 739 meters from the hashpoint, not in line of sight.

• 2014-06-20 52 9 (Hannover, Germany): GeorgDerReisende found the GC3XHX2 geocache 695 meters from the hashpoint, not in line of sight.

• 2014-10-12 51 13 (Dresden, Germany): Oisín found the GC501DY geocache 319 meters from the hashpoint, not in line of sight.

• 2015-02-25 52 9 (Hannover, Germany): Fippe found the GC3758F geocache about 500 meters from the hashpoint, not in line of sight.

• 2015-04-17 51 9, (Kassel, Germany): GeorgDerReisende found the GC3795W geocache 327 meters from the hashpoint, and within line of sight from the hashpoint.

• 2015-05-23 66 25 (Rovaniemi, Finland): Isopekka found the GCMRV9 geocache 281 metres from the hashpoint, not in line of sight.

• 2015-09-27 37 -122 (Cupertino, California: Erik_r and meta-alt found the GC2THTB geocache about 500 meters from the hashpoint.