Currently the only way to get heart-rate into sporttracks is to export to csv and import in Sporttracks.
Works perfect, even without modifying any column-headers as described below. Just export and import.
BUT
The speed of import is incredible low.
A GPX file from same workout needs 1 sec. CSV needs almost 30 sec. to be loaded into Sporttracks.
A similar GPX-File which includes the heartrate-data (from 3rd-party sw) also needs only 1 or 2 sec.
So what is the reason for that?
Anybody an idea, or anybody having same experience ?
from the csv file I received from NoPlayBack, I'am pretty sure there is a bug on the csv export part of RunGPS.
I believe the heartRate is not corretly outputed. So you should contact RunGPS admin for that bug, so they can solve it in the next release.
your page is not public so I can't send message to you.
could you send me a new message with YOUR EMAIL address, I will then be able to contact you on that address.
I just tried with an old csv file I had around. I imported it into Sporttracks 3.0 and no issue.
you can maybe send me your csv file, so I can look and see what is wrong for you.
normally it doesn't matter the type of belt you are using, ultimately it is the content of the csv file which mattres.
15.03.2011 13:22:06 UTCgeändert am 15.03.2011 13:46:50 UTC
Did a test with csv export-import to Sporttracks. Unfortunately the heartrate information was not transferred correctly. I am using Polar Bluetooth Belt. So currently for me there is no way to export data from run.gps and import to Sporttracks...
There are spikes in the Sporttracks display... and these are also as raw-data in the csv-file. Seems to be generated from Run.GPS. The rest of the data (non-spikes-area) is also not correct, it shows values below 2000, but definitly not heart-rate-values...