Potential Waypoint Issue

[Jason Blauert]

So I am not sure if there is an issue or not, but the more I look ...
it seems like a problem.

I have a cache that has 5 children waypoints. They have West coords
of:
W 110 55.242
W 110 55.238
W 110 55.260
W 110 55.230
W 110 55.244

But when I look at the Additional Waypoints coords in Geohunter they
are in degree decimal and all are:
-110.921
And on the map they make a straight N-S line.

This seems like too few decimal points for degrees and I do not know
if it just shows only 3 and there are more in the database or not.

A little math shows that we would round to the same -110.921 for
coords between W 110 55.230 and W 110 55.285 which is a potential 283
foot error!!!! That is pretty bad.

Also, if I choose to edit the waypoint from the details view, it
displays in decimal minutes, but they all have the same longitude
(55.260) and actually there appears to be some precision errors in the
latitude.

In the GPX file it looks like the waypoints are in decimal degrees
with 6 decimal places. Does geohunter round these off when they are
added to the database?

I will upload the cache in question in file "zoo.gpx"

[Jason Blauert]

BTW, I am using a Droid with 2.2 and just deleted and reimported all
my caches into the 1.9.3 preview.

[John Drake]

I was able to reproduce the problem with the zoo.gpx file -- thanks for providing this. Fortunately, Geohunter does not round the values when adding them to the database. Rather, the problem arises when reading the values back from the DB: apparently an unnecessary Double -> String -> Double conversion takes place, which rounds to three decimal places.

The attached patch, I believe, solves the problem. (At least for waypoints: I did not check if this problem also occurs for the main cache.)

Cheers

[Theodore K. Milbaugh]

That problem will not happen with the cache coordinates