Difference between revisions of "Time-traveller achievement"

From Geohashing
imported>Benjw
(Undo revision 477251 by Mckaysalisbury (talk) It works at other latitudes; it's talking about points close to the prime meridian, not points close to the equator.)
imported>Benjw
(clarify the 'lucky' points)
Line 11: Line 11:
 
* take advantage of the autumn daylight saving clocks change.
 
* take advantage of the autumn daylight saving clocks change.
 
** Geohashers nearer the equator are at a disadvantage because they have further to travel east or west.
 
** Geohashers nearer the equator are at a disadvantage because they have further to travel east or west.
** Geohashers near longitude 0 or 180 might be lucky and not have to travel far at all.
+
** Geohashers near longitude or 180° might be lucky and not have to travel far at all.
 
* get lucky.
 
* get lucky.
** If, at the equator, the longitude is less than +/- 0.000036° you will be in the circle of uncertainty for two hashpoints simultaneously.
+
** Near the prime meridian, you might be in the circle of uncertainty for two hashpoints simultaneously.  At the equator, this happens if the longitude of the hashpoint is less than +/- 0.000036°.
** Further from the equator this longitude can be calculated from 0.000036° / cos(Latitude). The poles are singularities!
+
** Further from the equator this longitude can be calculated from 0.000036° / cos(Latitude). The poles are singularities, so if the hashpoint latitude is very close to 90°, it would be possible to be standing on 360 hashpoints at once!
 
** A similar effect applies at longitude +/- 179.999964°, but only at weekends.
 
** A similar effect applies at longitude +/- 179.999964°, but only at weekends.
** 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.
+
** 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.
  
 
Of course, as usual, you need to upload photos of yourself containing the necessary [[Achievements#Proof|proof]].  
 
Of course, as usual, you need to upload photos of yourself containing the necessary [[Achievements#Proof|proof]].  

Revision as of 14:48, 25 April 2016

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.
  • take advantage of the autumn daylight saving clocks change.
    • Geohashers nearer the equator are at a disadvantage because they have further to travel east or west.
    • Geohashers near longitude 0° or 180° might be lucky and not have to travel far at all.
  • get lucky.
    • Near the prime meridian, you might be in the circle of uncertainty for two hashpoints simultaneously. At the equator, this happens if the longitude of the hashpoint is less than +/- 0.000036°.
    • Further from the equator this longitude can be calculated from 0.000036° / cos(Latitude). The poles are singularities, so if the hashpoint latitude is very close to 90°, it would be possible to be standing on 360 hashpoints at once!
    • A similar effect applies at longitude +/- 179.999964°, but only at weekends.
    • 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.

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