Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
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
Original comment by spei...@gmail.com
on 23 Mar 2008 at 4:46
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:
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:
thanks, this has been resolved in the latest revision
Original comment by spei...@gmail.com
on 24 Mar 2008 at 8:09
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
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:
Original issue reported on code.google.com by
jmcelve...@gmail.com
on 11 Feb 2008 at 7:09