joelmap / geohashdroid

Automatically exported from code.google.com/p/geohashdroid
0 stars 0 forks source link

..is not 30W compliant for earlier dates #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. lookup a 30W geohash prior to 2008-05-27 
e.g. 2009-05-20 52 13 yields 52.24047842, 13.12366119
(another issue: trying the same with 68,-29 results in a black screen, the
message "trying to determine your location" and a frozen application)

What is the expected output? What do you see instead?
http://wiki.xkcd.com/geohashing/30W_Time_Zone_Rule#Testing_for_30W_compliance
and 2009-05-20 52 13 should yield 52.630990585392, 13.618945982091

Original issue reported on code.google.com by thomas.h...@gmail.com on 2 Jan 2010 at 2:58

GoogleCodeExporter commented 9 years ago
I have marked the application as "PARTIALLY" 30W-compliant in the wiki for now.

Original comment by thomas.h...@gmail.com on 2 Jan 2010 at 2:59

GoogleCodeExporter commented 9 years ago
Ah, I see.  I completely forgot the 30W rule only applies after they came up 
with it.
 This shouldn't be too hard.  I'll get right on it.

Original comment by captains...@gmail.com on 2 Jan 2010 at 6:03

GoogleCodeExporter commented 9 years ago
There.  As per r293, Info.makeAdjustedCalendar has been updated to account for 
dates
on or before May 26, 2008, which should bring it up to compliance.  I tested it 
with
the dates given in the wiki, and it appears to work properly.  Assuming this 
works
right, this will go into 0.7.1 once the wiki features are finished.

Of course, if you tested it before r293, you would want to clear the stock 
cache in
the Settings screen before testing it again.

Original comment by captains...@gmail.com on 2 Jan 2010 at 6:43