Time-traveller achievement

From Geohashing
(Redirected from Time-Traveller Geohash)
TimeTravel.PNG

Template:Time-traveller

TimeTravel.PNG
This user earned the Time-traveller achievement
by reaching both the ({{{latitude}}}, {{{longitude}}}) and ({{{latitude2}}}, {{{longitude2}}}) geohashes at exactly {{{time}}} on {{{date}}}.

The achievement can be claimed if you venture to two or more geohashing locations on the same day and the same local time.

If you don't own a time-machine, you could ...

  • cross a time-zone border, and go fast.
    • In most cases, time zone borders are separated by an hour which gives you one hour to travel the 69 miles (times the cosine of the latitude) necessary, which can be difficult.
      • This gives geohashers further from the equator a slightly easier task, as the distance between graticules is smaller at higher latitudes.
    • Across the international date line is a time zone border of usually around 24 hours. This should give substantial time to cross to the next graticule, but most of these are on water.
    • There are places where the time zone borders are more than an hour apart. While this is makes it much easier, there are usually (but not always, e.g. Russia, Australia) international boundaries to travel through, which can also take additional time.
    • Note that border crossings sometimes give or take away an hour due to different countries observing Daylight Savings Time (summer time).
  • take advantage of the autumn daylight saving clocks change, and go fast.
    • Just like the time zone borders, higher latitudes make the journey shorter.
  • be in a mirror graticule (one with latitude or longitude 0 or -0) and get extremely lucky.
    • Because graticules that touch across the equator or the prime meridian or the 180° meridian mirror each other, there is a very small chance, if you're standing on the border between them, that you could be in the circle of uncertainty for two hashpoints simultaneously.
      • For those graticules that touch across the equator, this happens if the latitude of the hashpoint is less than 0.000036°.
      • For those that touch across the prime or 180° meridian, the required longitude of the hashpoint can be calculated from the expression 0.000036° / cos(latitude).
      • Note that across the 180° Meridian, the points only mirror each other on the weekend, because of the 30°W rule.
  • Go near the poles and be lucky.
    • At latitudes 89°N or 89°S, because graticules get narrower east-west the further north they are, hashpoints at all longitudes are closer to each other. When the latitude of the hashpoint is greater than 89.9984° the circles of uncertainty for two hashpoints will overlap. See South Pole.
  • Get very very extremely lucky because of the 30°W rule.
    • On weekdays hashpoints east and west of longitude 30°W are calculated separately, so may both be close to 30°W or 180°E/W. However, pretty much all of these points will be in an ocean.
  • A Globalhash-Geohash Colocation
    • A Globalhash and a Geohash can have the same coordinates on the same day. However, this has not happened yet.

It is possible to combine some of the above phenomena to achieve 3, or possibly more, hashes at the same local time. For instance, you could start near the western border of South Australia, on the day when day light saving ends (2am on Sunday, some time in April). Get to the first hash at, say, 2:05am. Get to the second hash an hour later, at 3:05 original time (2:05 local time). Now head west into Western Australia (1.5 hours timezone difference) and get to the third hash at 4:35 original time (2:05 local time).

Of course, as usual, you need to upload photos of yourself containing the necessary proof.

Winners

Woodveil was at the 2009-03-08 33 -84 and 2009-03-08 33 -85 hashes at 12:39 local time.
B2c and Patrizius were at the 2013-10-27 47 13 and 2013-10-27 47 12 hashes at 02:09 local time. It was a DST time travel.
Micsnare and B2c were at the 2014-10-26 47 14 and 2014-10-26 47 13 hashes at 02:01 local time. It was a DST time travel. Again ;)

See also

Multihash -- reach multiple geohashes on one day