LAT coord out, GPX ver 1.1 & SportTracks2

[GoogleCodeExporter]

What steps will reproduce the problem?
Using build 109
1. When importing tracks my lat coordinate is really weird. 
2. Am I able to modify the text tmeplate to get it into GPX1.1?
3. What program are you using to manage your data? Any chance you could 
look into an import into SportTracks2?

What is the expected output? What do you see instead?

1. I seem to be getting a really wierd lat coord.

<trk> 
<trkseg> 
<trkpt lat="4261.236229" lon="150.996382"> 
<ele>123</ele> 
<speed>10.57</speed> 
<time>2008-02-08T20:08:21Z</time> 
<extensions> 
<gpxdata:hr>92</gpxdata:hr> 
</extensions> 
</trkpt> 
....
.... 

It should be 33°43'51.88"S (what ever that is converted to the format 
above)rather than 4261.236229. Any ideas on what I'm doing wrong or what 
settings I need to change.

2. Am I able to modify the text tmeplate to get it into GPX1.1?
I think it is pretty much just the header that needs modify.

3. I am trying to import into SportTracks2.  (I have started a thread at 
http://sporttracks.zonefivesoftware.com/Discussion/viewtopic.php?
p=12612#12612) Ver 1 use to except xml.  ver 2 doesn't any chance of have 
your exporting software atuomatically give it the gpx extension?  Even 
better apparently its possible to import directly to sporttrack if you 
have the brains.  Unfortunatley I'm not a programmer, just a copy and 
paste guy.  If your not using SportTracks what are you using.  I'm trying 
to use the what for two things, 1. Exersise/Fitness training and 2. 
Geocaching (www.geocaching.com - it would be great to be able to import 
multiple waypoints for this automatically giving set symbols).

What version of the product are you using? On what operating system?
Win Vista Home Prem

Please provide any additional information below.
SportTracks 2 - 
http://sporttracks.zonefivesoftware.com/Discussion/viewtopic.php?
p=12612#12612

Geocaching - www.geocaching.com

Original issue reported on code.google.com by jmcelve...@gmail.com on 11 Feb 2008 at 7:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Alternatively (better option):

Open the Globalsat Application, import a error-prone Track and then use the 
"File-
>Save" Option to save a .ghd File. Upload that .ghd File here.

Thanks.

Original comment by spei...@gmail.com on 23 Mar 2008 at 4:26

[GoogleCodeExporter]

Original comment by spei...@gmail.com on 23 Mar 2008 at 4:46

• Changed state: Accepted

[GoogleCodeExporter]

After upgrading the new firmware I lost all my tracks.  So I'm just back after 
about 
a 800m jog around the block.
Here is the file throught the gh615_console you wrote selecting (b)=export a 
single 
track.  I choose the fitlog format and no to merge all tracks.

I used the GlobalSat program to download the run by selecting DeviceRecord > 
Download Trackpoints from Device.  I then selected save.  This is the second 
file. 

I fininshed the run about 10:30 Australian EST with dalight savings (Sydney).
The when selecting view in google earth from the Global sat program it works 
ok. 
That is the track is at the correct coordinates.

Original comment by jmcelve...@gmail.com on 23 Mar 2008 at 11:56

Attachments:

• 2008-03-24_10-31-15.fitlog
• 2008-03-24.ghd

[GoogleCodeExporter]

Here is the .kmz file from google earth (sent from the Gloabl sat prog) with 
the 
correct track coordinates.

Original comment by jmcelve...@gmail.com on 24 Mar 2008 at 12:08

Attachments:

• 2008-3-24_10_31_15

[GoogleCodeExporter]

thanks, this has been resolved in the latest revision

Original comment by spei...@gmail.com on 24 Mar 2008 at 8:09

• Changed state: Fixed

[GoogleCodeExporter]

I have been using build 109.  Isn't this the latest version?

Original comment by jmcelve...@gmail.com on 25 Mar 2008 at 10:59

[GoogleCodeExporter]

I download build_104 (just in case this was the latest version,
-Ran the option (b)=export a single track
-Selected the track,
-Selected the fitlog format,
-Selected n to merge,
The file was exported with the sdame error in co-ordinates.

The file is attached.

Original comment by jmcelve...@gmail.com on 25 Mar 2008 at 11:11

Attachments:

• export2008-03-24_10-31-15.fitlog