|
Jun 2013
11:23am, 7 Jun 2013
3,406 posts
|
HermanBloom
Uploaded my latest runs this morning. Will do the parkrun one tomorrow though.
|
|
Jun 2013
11:26am, 7 Jun 2013
18 posts
|
Rob-H
I've not been able to import for a month, I've give up trying and my detailed training blog has died after four years. Can't be bothered to input manually anymore.
|
|
Jun 2013
11:31am, 7 Jun 2013
12,931 posts
|
fetcheveryone
Herman - thanks 
Rob - I'm sorry to hear that, but I'm here trying to address the problem right now, with a new version of the importer. As far as I know, I've not received any feedback from you to report a problem, so it's difficult to see how I might attempt to fix it
|
|
Jun 2013
11:37am, 7 Jun 2013
3,407 posts
|
HermanBloom
Fwiw, I did a reset of my Garmin a week back and since then the current import method has been working like a dream. Not much help I know to those having problems, but hopefully you won't give up on it Rob-H.
|
|
Jun 2013
12:25pm, 7 Jun 2013
162 posts
|
Podkin
The new uploader is great, it's much faster - so fast that I wasn't sure it had done everything OK but all the information is there
|
|
Jun 2013
12:37pm, 7 Jun 2013
12,933 posts
|
fetcheveryone
Excellent Any other folks tried it yet?
|
|
Jun 2013
12:44pm, 7 Jun 2013
4,647 posts
|
rf_fozzy
Didn't find it much quicker with my 205. But it worked ok. It didn't differentiate older sessions that I've already uploaded from the newer ones like the old import function used to do.
Also don't quite like the way it changes the splits recorded by the Garmin.
It might stupid, but I record everything in km, but like having my split times as miles, so that I can see both sets of information easily. My Garmin is set to record mile splits.
|
|
Jun 2013
12:46pm, 7 Jun 2013
4,648 posts
|
rf_fozzy
I.e. it used to record splits as, for example:
Split Summary
====
1) - 1.61km - 12:06(7:31/km) - 122cal
2) - 1.61km - 9:58(6:12/km) - 129cal
3) - 1.22km - 6:18(5:09/km) - 97cal
and now it does this:
Imported from file
Split Summary
===
1) 1km - 9:59(9:59/km)
2) 1km - 6:26(6:26/km)
3) 1km - 4:17(4:17/km)
4) 1km - 8:05(8:05/km)
5) 1km - 8:05(8:05/km)
6) 1km - 4:14(4:14/km)
7) 1km - 4:58(4:58/km)
|
|
Jun 2013
12:47pm, 7 Jun 2013
4,649 posts
|
rf_fozzy
In fact, it's also missed off the last split, as that second run was 7.87km, so there's a 0.87km split missing.
|
|
Jun 2013
1:04pm, 7 Jun 2013
12,934 posts
|
fetcheveryone
Thanks fozzy.
It won't grab the raw data from the watch any quicker, because that's all encapsulated within the Garmin API - but whereas before I'd do a lot of analysis in Javascript on your browser, now it just transfers the data to the server, where it's fed through a bit of code that also services GPX/TCX files etc. And if I can get the performance bugs onto the server, as opposed to on user browsers, then that makes it easier for me to make it more stable.
Regarding the data, showing the 'runs since last import' is possible to reinstate - although I'm keen to illustrate to users that sometimes when the import is slow, it's because they have a lot of data. It helps me to diagnose and fix.
Regarding the splits, the server-based code reverts to the raw data on your watch, so repeated [lat lon time] data essentially. I'm intending to make it pick up the partial km you did at the end, and I can even finally tackle the 'pause' issue that some users struggle with - but I'm not sure that there's an easy approach to appealing to your miles and km in the same place, without getting a bit messy
|
