GPX export inaccuracy - Githubissues

pautimbol / open-gpstracker

Automatically exported from code.google.com/p/open-gpstracker

0 stars 0 forks source link

GPX export inaccuracy #61

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

When exporting tracks to GPX format the precision seems to be limited to 4 
precision digits and the output line imported in e.g. Google Earth becomes 
jagged. As far as I know the data is stored in real floating point format 
in the app db and from the in-app display the line is always smooth. The 
exporting thread is using a simple getString() on all numeric data, so I 
believe the 4 digits may be the default precision. Instead getting float 
values and outputting these numbers using java.util.Formatter should give 
better results.

Original issue reported on code.google.com by iscary...@gmail.com on 1 Feb 2010 at 11:03

GoogleCodeExporter commented 9 years ago

Original comment by rcgr...@gmail.com on 2 Feb 2010 at 11:16

Added labels: Milestone-Release0.9

GoogleCodeExporter commented 9 years ago

Original comment by rcgr...@gmail.com on 16 Feb 2010 at 8:55

Changed state: Accepted
Added labels: Priority-High
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

I settled to the Double.toString(double). The old versus new output on Google 
maps
seems to come to about a meter difference on some points.

Thanks for the sharp eye spotting this one!

The Google lines are not drawn with anti-aliasing or as a continues line. 
In-app the
line is drawn with a couple of pixels leeway to smooth the curves and 
anti-aliasing
is turned on. That would also add a bit of jaggedness to Google Earth.

Original comment by rcgr...@gmail.com on 17 Feb 2010 at 5:45

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Issue 81 has been merged into this issue.

Original comment by rcgr...@gmail.com on 21 Jul 2010 at 7:08