Wrong LAT and LON Coordinates

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start logging
2.
3.

What is the expected output? What do you see instead?
I see the right coordinates, but the Programm write wrong coordinates in
the KML, GXL output logs.
EXAMPLE: 
*The Code in the KML File*
<description><![CDATA[<table><tr><td>Longitude</td><td>8°47'11.02"E</td></tr><t
r><td>Latitude</td><td>53°05'46.47"N</td></tr></table>]]></description>
*So the Discription is ok, but the coordinates in the Code are theese*
<coordinates>8,786397,53,096244,64,0</coordinates>

and that´s are not the right points.
I where happy when you can Fix it, because i`m searching for a long time to
find this programm!

What version of the product are you using? On what operating system?
Im using the current version on my Nokia N97 with the 11th Firmware (german)

Please provide any additional information below.
I put the KML and GPX Files in the attachment.

Original issue reported on code.google.com by sidewigk@googlemail.com on 19 Nov 2009 at 12:39

Attachments:

• 20091119003541.kml
• 20091119004148.gpx

[GoogleCodeExporter]

similar problems.
I have: <coordinates> 30,532018,50,399719,104,0 </ coordinates>
Should be: <coordinates> 30.532018,50.399719,104.0 </ coordinates>

Nokia 5800 UA

Original comment by sdi...@yahoo.com on 23 Nov 2009 at 7:46

[GoogleCodeExporter]

I have the same problem on a Nokia N82 (S60 3rd ed. FP1) using the internal GPS.

<trkpt lon="9,260380" lat="45,502857">
        <time>2010-03-09T16:30:07Z</time>
        <ele>170,5</ele>
        ....
</trkpt>

Any idea?
Thank you
Sergio

Original comment by sergiode...@gmail.com on 10 Mar 2010 at 9:50

Attachments:

• 20100309173032.gpx

[GoogleCodeExporter]

Me pasa lo mismo.

Nokia 5800 Firm V31.0.101.301.04
TTGPSLogger V0.4B

Original comment by josean.a...@gmail.com on 9 Apr 2010 at 4:24

Attachments:

• 20100408004026.kml

[GoogleCodeExporter]

I solved by setting NMEA output format. next convert in kmz-kml by using one of 
available tools on the internet (gpsbabel etc etc).
It works for me.
Of course it would be better to create directly a kml file...the problem 
relates to 
comma-dot mistake during kml file creation by the ttgpslogger I think.

Original comment by leonardo...@gmail.com on 9 Apr 2010 at 6:55

[GoogleCodeExporter]

When I need capture a route, I change the languaje set to English, and the kmz 
is
correct. A restart is neccesary.
In Spanish settings, decimal separator is a comma, not a dot.

Original comment by josean.a...@gmail.com on 21 Apr 2010 at 8:14

[GoogleCodeExporter]

As for GPX files - I open these files on PC with any text editor and just 
replace 
all commas with dots. That works too since there's no commas generated by 
ttgpslogger in GPX files.

Original comment by doos...@gmail.com on 22 Apr 2010 at 11:28

[GoogleCodeExporter]

Changing Language to English works for me also...the .kml file display the 
correct 
coords.
But I still prefere to generate an NMEA file (without comma-dot issue), and 
postworks 
it...better way to filter and arrange keypoints.

Original comment by leonardo...@gmail.com on 24 Apr 2010 at 12:29

[GoogleCodeExporter]

Please fix the "coma-dot"-bug. It's annoying to open the file with text editor 
and change the comas to dots.

Thank You

Original comment by AmmokSka...@gmail.com on 29 Jun 2010 at 1:15

[GoogleCodeExporter]

The decimal sign of the output file should never be language-dependent. It 
always should be a simple dot.

You can fix the corrupted kml file with

sed 
"s/\(coordinates.[0-9]*\)\,\([0-9]*\)\,\([0-9]*\)\,\([0-9]*\)\,\([0-9]*\)\,\([0-
9]*..coordinates\)/\1\.\2\,\3\.\4\,\5\.\6/" x.kml> y.kml

Original comment by Marvo...@gmail.com on 27 Jul 2010 at 9:06

[GoogleCodeExporter]

It seems they use the default decimal separator from 
"TLocale::DecimalSeparator()const".

They use AppendFormat with format strings that includes "%f" format specifiers. 
And therfore the values are converted into TReal values, this class has a 
iPoint Member which defines the separator, and it's default is 
"TLocale::DecimalSeparator()const". I dont know the best way how to change this 
default in that case but the easiest way is to introduce a TReal member 
variable and set iPont to '.'.

Original comment by andre.tippel@googlemail.com on 8 Aug 2010 at 11:57

[GoogleCodeExporter]

I fix this error and issue 3 
(http://code.google.com/p/ttgpslogger/issues/detail?id=3) and attach the 
corresponding cpp file here, because i have no rights to check into svn 
repository.

Original comment by andre.tippel@googlemail.com on 19 Aug 2010 at 1:45

Attachments:

• TTGPSLoggerRecorderFormatGPX.cpp

[GoogleCodeExporter]

I offer a patched version of TTGPSLogger where i have patched issue 2 and issue 
3 like i have described in my previous post -> 
http://datenmuehle.kilu.de/TTGPSLogger/

Original comment by andre.tippel@googlemail.com on 5 Sep 2010 at 11:20

[GoogleCodeExporter]

Can you allso make a patched version for the Nokia E72 (FP1)? Thanks.

Original comment by deruyter...@gmail.com on 17 Sep 2010 at 9:14

[GoogleCodeExporter]

Andre, I tried your patched version on a Nokia 6760-slide (after signing), but 
it wouldn't run. (No error messages, no output at all?). Have I missed a step?

Original comment by horn...@gmail.com on 17 Sep 2010 at 12:44

[GoogleCodeExporter]

I guess that you have the same problem like me. What we need is a patch for 
Symbian S60 3rd FP1.

Original comment by deruyter...@gmail.com on 17 Sep 2010 at 1:53

[GoogleCodeExporter]

Hi,
if i try to build a 3rd FP1 binary the compiler indicates a missing file 
"TTGPSLogger.rsg". It seems to me that the SVN sources aren't complete for 3rd 
FP1 edition!? Sorry...

But i won't exclude that i make something wrong when i try build it...
I try to setup 3rd FP1 toolchain from scratch in the next days. Maybe ^1 and 
3rd FP1 toolchain can't work together on one machine??

Original comment by andre.tippel@googlemail.com on 20 Sep 2010 at 7:36

[GoogleCodeExporter]

I'm sure that you are right and will make the best of it. Unfortunately I dont 
have a clue how something like that is made. Thanks alot in advance, keep up 
the good work.

Original comment by deruyter...@gmail.com on 20 Sep 2010 at 8:52

[GoogleCodeExporter]

I use my lunchtime to compile it again for 3rd FP1 with some changes i made in 
"TTGPSLoggerS60v5x.rssi". I attach the changed file to this post. It seems it 
works. It successfully runs in the emulator but i can't test it on a real 
device. But anyway i decide to host "TTGPSLogger_S60v31_0_4_37_I2_I3.sis" on 
http://www.datenmuehle.kilu.de/TTGPSLogger.

I hope this works for you.

Original comment by andre.tippel@googlemail.com on 21 Sep 2010 at 11:16

Attachments:

• TTGPSLoggerS60v5x.rssi

[GoogleCodeExporter]

Thanks a lot for the effort. Now i can see my track (a line wich is good) but 
on my trackline are hundreds of circles...and that is weird? Do i have to 
change something in my settings or what can it be?

Original comment by deruyter...@gmail.com on 21 Sep 2010 at 5:50

[GoogleCodeExporter]

Latest TTGPSLogger_S60v31_0_4_37_I2_I3.sis runs successfully on Nokia 
6760-slide and produces gpx file with elements in the correct order. Thanks!

Original comment by horn...@gmail.com on 21 Sep 2010 at 7:53

[GoogleCodeExporter]

I used my patched 5th edition version and can't see any circles along the 
track. If i run the 3rd FP1 version in the emulator it produces a valid 
(fake-)track. I attach this (fake-)track to this post.
Can you post your gpx file here too? Maybe it's a gpx viewer problem or 
something else goes wrong.

Original comment by andre.tippel@googlemail.com on 22 Sep 2010 at 10:38

Attachments:

• 20100922092343.gpx

[GoogleCodeExporter]

Ok, includeded the GPX file from a small track that i recorded today.

Original comment by deruyter...@gmail.com on 22 Sep 2010 at 11:29

Attachments:

• 20100922074200.gpx

[GoogleCodeExporter]

I viewed your track on "http://www.gpswandern.de/gpxviewer/gpxviewer.shtml" and 
all seems to be ok, no circles at your track. It's a german website like many 
others on the internet. They use google maps to visualize gpx tracks.

The only different to my (fake-)track is that your file contains a "vdop" field 
but it seems to be irrelevant for the track viewer...

Original comment by andre.tippel@googlemail.com on 23 Sep 2010 at 6:01

[GoogleCodeExporter]

That solves the problem with me now, that vdop and hdop, i putted it of in my 
setting and now it works 100% Thanks alot for the good work!!

Original comment by deruyter...@gmail.com on 23 Sep 2010 at 4:19

[GoogleCodeExporter]

datenmuehle.kilu.de is history!

Please load patched the TTGPSLogger version from http://datenmuehle.org

Original comment by andre.tippel@googlemail.com on 19 Jun 2011 at 12:37

[GoogleCodeExporter]

I tried the patched version from datenmuehle.org but it saves wrong (comma vs 
dots problem) KML files  for me :( E52.

Original comment by baskuru...@gmail.com on 19 Jun 2011 at 7:46

[GoogleCodeExporter]

Hi, i fixed only the gpx part. If it's just easy as this i think i try to fix 
it in the near future.

Original comment by andre.tippel@googlemail.com on 21 Jun 2011 at 6:48

[GoogleCodeExporter]

Now i patched even the kml part too. It writes now always a "." instead of 
language dependant decimal separator for kml files. Furthermore i patched the 
gpx part so that the number of decimals is always 6 for lon and lat and 1 for 
alt.

See http://www.datenmuehle.org

Fixed source code attached to this post.

Original comment by andre.tippel@googlemail.com on 10 Jul 2011 at 6:49

Attachments:

• TTGPSLoggerRecorderFormatKML.cpp
• TTGPSLoggerRecorderFormatGPX.cpp