• Excellent, thanks.

    Fuck me YACF can be hard work some times. Reminds me why I sacked it off last year, only to be suckered back in by this very topic. #whywhywhy

    The big one for me is whether he can increase riding time whilst also reducing stopped time (not necessarily 1:1 ratio but it needs to be close). He needs to ride for longer (since he's not shown he can ride faster) but he can't risk sacrificing much more sleep time as that won't be sustainable. If there's a way of logging/charting the daily elapsed time too that would be fantastic (I know Strava has it but it's a ballache to get from Strava).

  • I think that jo is pulling out the GPX tracks from Strava (which requires a premium account that I don't have, and have no intention of getting), which would allow him to do something like that. His charting is stunning, but I quite understand why he's going to cut down on it.

    Steve had also started letting the garmin run on whilst he slept if he had crossed midnight, which I suspect would mess up the elapsed time details and calculations, but I've not looked. I might do if I ever get a few hours with nothing to do.

    I'm still quietly quite chuffed with mine, and impressed with what you can do with simply inputting 2 numbers per rider per day.

  • I think that jo is pulling out the GPX tracks from Strava (which requires a premium account that I don't have, and have no intention of getting)

    You don't need a Premium account to get the data from Strava, it's just not in GPX format directly. The data is displayed on the analysis page of any activity (not a Premium feature) so it must be inside the javascript somewhere, so I took a look.

    Using Firebug there are 3 queries the javascript performs, all of which return json. One contains a series of lat/lon points, the other two queries do things like time, distance, altitude, heartrate, smoothed speed, etc. There's a bit of duplication between the last two queries, and it may be possible to combine it all into one query.

    The two sets of data should have the same number of points and so it's a case of grabbing and combining the two/three datasets and then making each of the points into a GPX trackpoint.

    Busy this weekend but I'll see what I can come up with over the next few days.

About

Avatar for MrDrem @MrDrem started