I understand, but I don't like arbitrarily chopping off significant figures at the beginning of a process when I don't know the reason for it.

I fixed the issue by the way by changing the format to "%.6f".


Ross Dillon
roscoe.dillon@gmail.com

On May 3, 2010, at 10:23 PM, Robert Lipe wrote:

Somewhere around 5/6 decimal digits, the lat/lon of consumer grade GPS turns into fiction.  I keep seeing people reporting sub centimeter "precision" on hardware with a 10meter accuracy.

From your description, I can't work out if this is GPX, Unicsv, or csv (all of which are different code to us) and since you didn't provide a test case, can't put it in a debugger to analyze.

On Mon, May 3, 2010 at 11:36 AM, Ross Dillon <roscoe.dillon@gmail.com> wrote:
OK, I'm confused.  Using the following lines in my stylesheet:

OFIELD LAT_DECIMAL, "", "%8.5f"
OFIELD LON_DECIMAL, "", "%8.5f"

I get a lat/lon output out to 5 decimal places.  When I convert the
same GPX file using UNICSV I get a lat/lon output out to 6 decimal
places (note the original GPX data file has 6 decimal places as well).

I thought, easy enough, change the output format to "%9.6f".  Except
that the additional decimal place is always a zero.

How do I get that additional significant digit back?

------------------------------------------------------------------------------
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@lists.sourceforge.net
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc