Suunto Ambit exercise without GPS-data not created correctly in FB

[GoogleCodeExporter]

- What steps will reproduce the problem?
1. Import the attached xml-file into sporttracks.
2. In sportstrack confirm that the exercise has HRM-data but lacks a map.
3. Export the exercise to funbeat with st2funbeat.

- What is the expected output? What do you see instead?
Expected a recorded exercise with pulse-diagram without a route.
No pulse-diagram, no map but a warning (about missing data-points?)

- What version of the product are you using? On what operating system?
0.8.85

- Please provide any additional information below.
xml-file is raw data straight from the data-folder for Moveslink2-SW recorded 
with a Suunto Ambit.

Original issue reported on code.google.com by fredr...@gmail.com on 7 Oct 2012 at 7:41

Attachments:

• log-67F8984623000B00-2012-09-11T18_27_39-0.xml

[GoogleCodeExporter]

Original comment by staffan....@gmail.com on 10 Oct 2012 at 8:22

• Changed title: Suunto Ambit exercise without GPS-data not created correctly in FB

[GoogleCodeExporter]

Will have a look!

Original comment by staffan....@gmail.com on 10 Oct 2012 at 8:22

[GoogleCodeExporter]

Det är alltid bra med fler exempel när man felsöker så man vet att det är 
konsekvent. Här är kvällens spinning-pass. Reggat likadant som förra 
gången med Suunto Ambit i Indoor-mode, dvs med pulsband men utan aktiv GPS. 
Vid export till funbeat får man en karta med en varning "Kartan saknar 
punkter" och inget puls-diagram. 

Original comment by fredr...@gmail.com on 11 Oct 2012 at 8:13

Attachments:

• log-67F8984623000B00-2012-09-25T17_33_22-0.xml

[GoogleCodeExporter]

It has been identified that the ST importer for Suunto Ambit creates an empty 
GPS track in the case of these workouts (when GPS was switched off). This is 
different behaviour from what has been seen with imports from other devices 
like Garmin. ST works ok with an empty GPS track, but funbeat doesn't respond 
well.

I will create a workaround to ignore the GPS track if it is empty.

Original comment by staffan....@gmail.com on 13 Oct 2012 at 1:06

• Changed state: Accepted

[GoogleCodeExporter]

Please try version 0.8.87, which includes a workaround that should solve the 
problem. Please report back here whether it works or not!

Original comment by staffan....@gmail.com on 13 Oct 2012 at 1:21

• Changed state: Fixed

[GoogleCodeExporter]

Works beautifully now with the new version, thanks!

Original comment by fredr...@gmail.com on 13 Oct 2012 at 1:50