armindoantunes / gh615

Automatically exported from code.google.com/p/gh615
0 stars 0 forks source link

Support for fitlog format used by sporttrack #12

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hello
I have created a fitlog exporter fitlog is used by SportTrack
http://www.zonefivesoftware.com/SportTracks

I attache it here so it can be included in your next version if you like :)

Put the supplied file in exportTemplates/
e.g exportTemplates/fitlog.txt
and add the folowing to exportTemplate/formats.ini

-------- exportTemplate/formats.ini
[fitlog]

hasMultiple = true

extension = fitlog

nicename = Fitness Work Book used by Sporttracks
-------------------------
Thanx for a great set of pyton script I manage to get it to work under
Linux with some configuration settings :)

/Zingo  (zingo a_ring zingo dottiledot org)

Original issue reported on code.google.com by ZingoAnd...@gmail.com on 5 Mar 2008 at 9:25

Attachments:

GoogleCodeExporter commented 8 years ago
I have installed your template  and give a mistake in the length, design 
someone?

Original comment by jasanch...@gmail.com on 7 Mar 2008 at 3:33

GoogleCodeExporter commented 8 years ago
Hello
I have set my units to the "standard 10 based" not imperial e.g. km and not 
miles
what setting did you have?

Do you get the problem when importing to SportTrack or when creating the file?

Original comment by ZingoAnd...@gmail.com on 9 Mar 2008 at 7:30

GoogleCodeExporter commented 8 years ago
Another thing could be that I used latest gh615 from svn and latest sportrack.

/Zingo

Original comment by ZingoAnd...@gmail.com on 10 Mar 2008 at 5:47

GoogleCodeExporter commented 8 years ago
In sporttracks 2 a mistake gives in the coordinates GPS(GLOBAL POSITIONING 
SYSTEM),
they me appear very far from the royal(real) ones, it(he,she) designs someone? 
Thank you 

Original comment by jasanch...@gmail.com on 14 Mar 2008 at 1:35

GoogleCodeExporter commented 8 years ago
Do you have a problem that when you import it to sporttrack you get one or many
points wrong compared to the map?
Have you tried looking at the generated <file>.fitlog in an onrdinary 
texteditor like
notepad or notepad2, the points are generated file should look like the example 
below
the posisione is specified as lat="57.664402" lon="12.122978" ele="86"  probably
those are wrong somehow

1. Is it one point that is wrong or all?
2. If the problem is a few points can you find them in the <file>.fitlog 
3. If possible generate a gpx file, does that work?
4. How does the problem points look in the gpx file comapred to the 
<file>.fitlog file
--------------------------------- example <file>.fitlog
<?xml version="1.0" encoding="utf-8"?>
<FitnessWorkbook version="1.0" creator="code.google.com/p/GH615"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.zonefivesoftware.com/xmlschemas/FitnessLogbook/v1">

  <AthleteLog>
      <Activity StartTime= "2008-03-02T07:38:23Z">
      <Metadata Source="GlobalSat GH615M" Created="2008-03-02T07:38:23Z"
Modified="2008-03-02T07:38:23Z" />
      <!-- topspeed=17.54 -->
      <Duration TotalSeconds="825.5" /> 
      <Distance TotalMeters="2255" /> 
      <Calories TotalCal="199" /> 
      <Track StartTime= "2008-03-02T07:38:23Z" >
              <pt tm="0.0" lat="57.664402" lon="12.122972" ele="86" hr="107"
dist="0.0" /> <!-- speed="0.0" -->
                <pt tm="0.6" lat="57.664402" lon="12.122978" ele="86" hr="107"
dist="0.0" /> <!-- speed="0.0" -->
                <pt tm="1.6" lat="57.664398" lon="12.122998" ele="84" hr="107"
dist="1.05555555556" /> <!-- speed="3.8" -->
                <pt tm="2.6" lat="57.664395" lon="12.123018" ele="83" hr="109"
dist="1.50277777778" /> <!-- speed="5.41" -->
                <pt tm="3.6" lat="57.664387" lon="12.123053" ele="82" hr="109"
dist="2.37777777778" /> <!-- speed="8.56" -->
                <pt tm="4.7" lat="57.664390" lon="12.123098" ele="80" hr="109"
dist="2.51166666667" /> <!-- speed="8.22" -->
                <pt tm="5.7" lat="57.664403" lon="12.123128" ele="79" hr="109"
dist="2.03611111111" /> <!-- speed="7.33" -->
                <pt tm="6.7" lat="57.664417" lon="12.123162" ele="78" hr="109"
dist="2.39722222222" /> <!-- speed="8.63" -->

... many line like this ...

                <pt tm="824.6" lat="57.664377" lon="12.123130" ele="78" hr="164"
dist="3.375" /> <!-- speed="12.15" -->
                <pt tm="825.5" lat="57.664377" lon="12.123130" ele="78" hr="164"
dist="3.0375" /> <!-- speed="12.15" -->
              </Track>
    </Activity>
    </AthleteLog>
</FitnessWorkbook>

Original comment by ZingoAnd...@gmail.com on 14 Mar 2008 at 5:30

GoogleCodeExporter commented 8 years ago
I have attached two files both viewable i a text editor.  The first 
temp_data.viw is 
the downloaded track in Global Sats GH615 PC Utility.  The second file is the 
file 
exported using the fitlog.  I am getting the same error even when exporting 
using 
other templates (that is the lat is way out).

Original comment by jmcelve...@gmail.com on 22 Mar 2008 at 12:06

Attachments:

GoogleCodeExporter commented 8 years ago
thanks zingo, I added your work to the svn.

Original comment by spei...@gmail.com on 23 Mar 2008 at 2:59

GoogleCodeExporter commented 8 years ago

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

GoogleCodeExporter commented 8 years ago
Hello, sorry for my english.

I have errors in the long of the GPS(GLOBAL POSITIONING SYSTEM).
Example: lat 42.143360 lon 4294.545606 when it has to say lat 42.123360N long 
-0.42169W 

The location is Huesca, Spain.

Original comment by jasanch...@gmail.com on 24 Mar 2008 at 10:55

Attachments:

GoogleCodeExporter commented 8 years ago
"I am getting the same error even when exporting using 
other templates (that is the lat is way out)."

so this is a general problem on not in the fitlog exporter? 

Original comment by ZingoAnd...@gmail.com on 31 Mar 2008 at 8:40

GoogleCodeExporter commented 8 years ago
The Fitlog Exporter works fine. It was a more general one that has been fixed.

Original comment by spei...@gmail.com on 31 Mar 2008 at 9:46