Difference between revisions of "Talk:Antimeridian"

From Geohashing
(Created page with "IIRC, technically, the graticules on different sides of the Antimeridian follow different versions of the 30W rule, so in a theoretical zero offset on e...")
 
(Antimeridian != Dateline problem)
Line 1: Line 1:
 
IIRC, technically, the graticules on different sides of the Antimeridian follow different versions of [[30W Time Zone Rule|the 30W rule]], so in a theoretical zero offset on either side, only 180 hashes would fall here (unless ''both'' offsets are zero, which is ''doubly'' unlikely).
 
IIRC, technically, the graticules on different sides of the Antimeridian follow different versions of [[30W Time Zone Rule|the 30W rule]], so in a theoretical zero offset on either side, only 180 hashes would fall here (unless ''both'' offsets are zero, which is ''doubly'' unlikely).
  
Yes, this also means that any theoretical (e.g.) Samoan geohashers would get their hashes sometime early morning of next day. But the alternative was allowing graticules like [[Matavai, Samoa]] to have ''two'' valid hashes on the same day.
+
Yes, this also means that any theoretical (e.g.) Samoan geohashers would get their hashes sometime early morning of next day. But the alternative was allowing graticules like [[Matavai, Samoa]] to have ''two'' valid hashes on the same day. --[[User:January First-of-May|January First-of-May]]
 +
 
 +
:You are right, I did not consider this. Ironically, [[Talk:Main Page#Graticules without weekday geohashes|I raised this issue]] in a different context a few years ago. Currently, all implementations that I know about use the Antimeridian as the date line, which of course is not true.
 +
:It would be fair to Geohashers east of the Antimeridian but west of the date line if they would also be protected by the W30 rule. They should be considered east of W30, not west of W30. Of course that would lead to two geohashes in the same graticule on the same day in graticules where the date line cuts through, so a date-lat-lon combination would not be unambiguous, which of course is unacceptable.
 +
:One way to tackle this would be to assign a value to all graticules if they should be considered east or west of the date line. That way there is only one valid geohash each day. Your example, [[Matavai, Samoa]], should be considered west of the date line, since all of it's land is west of the date line. On the other hand, [[Wales, Alaska]], should be considered east of the date line since most of it's land is east of the date line, even though a tiny sliver of land is west of the date line.
 +
:Of course, this would be a nightmare to go through all graticules, implement it into a program, and nobody I know has done this so far. I know it is lazy, but it is probably not worth worrying about this problem since there aren't any geohashers in these areas anyway, at least currently.
 +
:I'll change the text on the page to say that it's 180 locations, since that is the interpretation that the implementations currently follow. --[[User:Fippe|Fippe]] ([[User talk:Fippe|talk]]) 16:59, 1 August 2020 (UTC)

Revision as of 17:00, 1 August 2020

IIRC, technically, the graticules on different sides of the Antimeridian follow different versions of the 30W rule, so in a theoretical zero offset on either side, only 180 hashes would fall here (unless both offsets are zero, which is doubly unlikely).

Yes, this also means that any theoretical (e.g.) Samoan geohashers would get their hashes sometime early morning of next day. But the alternative was allowing graticules like Matavai, Samoa to have two valid hashes on the same day. --January First-of-May

You are right, I did not consider this. Ironically, I raised this issue in a different context a few years ago. Currently, all implementations that I know about use the Antimeridian as the date line, which of course is not true.
It would be fair to Geohashers east of the Antimeridian but west of the date line if they would also be protected by the W30 rule. They should be considered east of W30, not west of W30. Of course that would lead to two geohashes in the same graticule on the same day in graticules where the date line cuts through, so a date-lat-lon combination would not be unambiguous, which of course is unacceptable.
One way to tackle this would be to assign a value to all graticules if they should be considered east or west of the date line. That way there is only one valid geohash each day. Your example, Matavai, Samoa, should be considered west of the date line, since all of it's land is west of the date line. On the other hand, Wales, Alaska, should be considered east of the date line since most of it's land is east of the date line, even though a tiny sliver of land is west of the date line.
Of course, this would be a nightmare to go through all graticules, implement it into a program, and nobody I know has done this so far. I know it is lazy, but it is probably not worth worrying about this problem since there aren't any geohashers in these areas anyway, at least currently.
I'll change the text on the page to say that it's 180 locations, since that is the interpretation that the implementations currently follow. --Fippe (talk) 16:59, 1 August 2020 (UTC)