search

joelmap / geohashdroid

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

Detect correct (current) location, but wrong graticule #36

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. activate "Use Closest"
2. click "Go!"

What is the expected output?  What happened instead?
My current location is Vienna/AT (48º 11'N 16º 20'E) but the geohashed 
coordinates are in 47ºN 16ºE.
When i manually set the graticule or select in from the map, everything is fine.
- 0.7.14: tested on 30.11.11 only latitude is wrong
- 0.7.13: tested on 29.11.11 both coordinates are off by one
The current location in the infobox and in logcat are fine.

What version of Geohash Droid are you using?  On what phone?
Phone: HTC Desire 
Version: 0.7.14 and 0.7.13

What version of Android is running on that phone, if you know?
2.3.7 - CM7 nightly 262

Please provide any additional information below.

Original issue reported on code.google.com by seh...@gmail.com on 30 Nov 2011 at 1:35

GoogleCodeExporter commented 9 years ago 
Are you sure that graticule's hashpoint is the closest one?  The intent of the 
"Use Closest" checkbox is to choose the closest hashpoint to wherever you are 
at that moment, not necessarily the graticule in which you currently are.  That 
is to say, if the hashpoint in the neighboring graticule is only 10km away, it 
will pick that over your current graticule, which may be 50km away.

Original comment by captains...@gmail.com on 30 Nov 2011 at 2:49

GoogleCodeExporter commented 9 years ago 
Ok, now the result makes sense.
I misinterpreted the checkbox.
I thought all the elements below the label "Graticule:" are for selecting the 
graticule in which I want so start:
- Manually by entering degrees
- Automatic (use cell/wifi/gps)
- Manually by map.

Thanks for the fast feedback.

Original comment by seh...@gmail.com on 30 Nov 2011 at 6:36

GoogleCodeExporter commented 9 years ago 
Yeah, I can understand why that may be confusing.  Unfortunately, I can't make 
it any clearer that it's the closest point, not graticule, owing to space 
limitations with that text.

But, thanks for the report anyway!

Original comment by captains...@gmail.com on 30 Nov 2011 at 7:43