Difference between revisions of "2017-03-12 32 -110"

From Geohashing
imported>Jiml
(Indicate possible problems)
imported>FippeBot
m (Location)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
 
{{meetup graticule  
 
{{meetup graticule  
 
| lat=32
 
| lat=32
 
| lon=-110
 
| lon=-110
| date=2018-03-12
+
| date=2017-03-12
 
}}
 
}}
  
Line 15: Line 14:
 
== Participants ==
 
== Participants ==
  
* [[User:Fugads]]
+
* Team2002 (Geocacher)
 +
* [[User:Fugads|Fugads]] (possibly)
  
 
== Plans ==
 
== Plans ==
 
 
Unknown - sounds like they were going geocaching
 
Unknown - sounds like they were going geocaching
 
  
 
== Expedition ==
 
== Expedition ==
 
<!-- how it all turned out. your narrative goes here. -->
 
<!-- how it all turned out. your narrative goes here. -->
 
 
  
 
Coordinates for this date:  
 
Coordinates for this date:  
Line 31: Line 27:
  
 
This Hash was found by a geocacher, Team2002, while finding the nearby geocache GC6ZPP0.
 
This Hash was found by a geocacher, Team2002, while finding the nearby geocache GC6ZPP0.
 
Note:  The coordinates above don't seem to be correct for the given date.  I wonder if this really should be for Dec 8 (or Dec 3 European date style) when this page was created....
 
 
 
  
 
== Achievements ==
 
== Achievements ==
 
{{#vardefine:ribbonwidth|800px}}
 
{{#vardefine:ribbonwidth|800px}}
<!-- Add any achievement ribbons you earned below, or remove this section -->
+
{{land geohash|latitude=32|longitude=-110|date=2017-03-12|name=Team2002}}
 
+
{{hash collision|latitude=32|longitude=-110|date=2017-03-12|name=Team2002|id=GC6ZPP0|distance=483m|honor=yes}}
* Land Geohash??
 
 
 
<!-- =============== USEFUL CATEGORIES FOLLOW ================
 
Delete the next line ONLY if you have chosen the appropriate categories below. If you are unsure, don't worry. People will read your report and help you with the classification. -->
 
[[Category:New report]]
 
 
 
<!-- ==REQUEST FOR TWITTER BOT== Please leave either the New report or the Expedition planning category in as long as you work on it. This helps the twitter bot a lot with announcing the right outcome at the right moment. -->
 
 
 
<!-- Potential categories. Please include all the ones appropriate to your expedition -->
 
<!-- If this is a planning page:
 
[[Category:Expedition planning]]
 
-->
 
  
<!-- If all those plans are never acted upon, change [[Category:Expedition planning]] to [[Category:Not reached - Did not attempt]]. -->
 
  
<!-- An actual expedition:
 
 
[[Category:Expeditions]]
 
[[Category:Expeditions]]
-- and one or more of --
 
[[Category:Expeditions with photos]]
 
[[Category:Expeditions with videos]]
 
[[Category:Expedition without GPS]]
 
-->
 
 
<!-- if you reached your coords:
 
 
[[Category:Coordinates reached]]
 
[[Category:Coordinates reached]]
 
+
{{location|US|AZ|PM}}
 
 
--><!-- or if you failed :(
 
[[Category:Coordinates not reached]]
 
-- and a reason --
 
When there is a natural obstacle between you and the target:
 
[[Category:Not reached - Mother Nature]]
 
 
 
When there is a man-made obstacle between you and the target:
 
[[Category:Not reached - No public access]]
 
 
 
When you failed get your GPS, car, bike or such to work:
 
[[Category:Not reached - Technology]]
 
   
 
When you went to an alternate location instead of the actual geohash:
 
[[Category:Not reached - Attended alternate location]]
 
 
 
(Don't forget to delete this final close comment marker) -->
 

Latest revision as of 02:14, 16 August 2019

Sun 12 Mar 2017 in 32,-110:
32.1649559, -110.9398019
geohashing.info google osm bing/os kml crox



Location

Near Tuscon

Participants

  • Team2002 (Geocacher)
  • Fugads (possibly)

Plans

Unknown - sounds like they were going geocaching

Expedition

Coordinates for this date: 32.16495591, -110.93980192

This Hash was found by a geocacher, Team2002, while finding the nearby geocache GC6ZPP0.

Achievements

Landgeohash.png
Team2002 earned the Land geohash achievement
by reaching the (32, -110) geohash on 2017-03-12.
Hashcollision.png
Team2002 earned the Hash collision honorable mention
by discovering the geocache GC6ZPP0 483m from the (32, -110) geohash on 2017-03-12.