My New Toy (and a Bug Fix)

As if I were lacking on the toy front, last night I picked up a Garmin Edge 305 bicycle computer. I'd been looking for a GPS data logger for a while, and this one is pretty much exactly what I'm looking for. In addition to the time/lat/long/elevation track points, it also has a heart rate monitor and a cadence/wheelspeed sensor which is also correlated to the track points. This yields more data than you can shake a stick at.

I haven't yet figured out exactly how I want to approach the problem of extracting, storing, and visualizing all this data, but I've got some ideas. The data is a superset of what I already track with my bike dashboard (by design), so I'll continue to use that as a base, just with the ability to drill down into more detail per ride. Wheeeee!

I also fixed a rounding error in one of the dashboard's view definitions that artificially inflated mileage (and therefore average speed) throughout the app.  I'd misaligned my CAST AS DECIMAL and ROUND calls, and ended up rounding at the wrong spot.  The raw data was uncompromised, only the view's computations based on it were affected.

9 responses to “My New Toy (and a Bug Fix)”

  1. Matt Williams

    Fun stuff. I've been thinking about the same model, but the ForeRunner version. I do some running too and would be able to go back and forth that way.

    Which makes me think I could actually use the Bicycle Dashboard to put in running data too. Just define a new bike as Nike. :)

  2. PaulH

    see http://www.motionbased.com for some ideas. a flex/AIR app like that would be sweet.

  3. PaulH

    i think you get that kind of functionality w/the paid subscription (i'm too cheap). i'm using a forerunner 205 & it's s/w (training center) does much of what i want for stats w/a spreadsheet doing the rest but i'm mainly obsessed w/single rides anyways–though these days i've been doing intervals & simply counting the speed spikes & their flatness. i haven't seen much improvement (except sprinting away from farmer's dogs) after 3 weeks. my century time's worse than before i started & last week i couldn't even finish one (came up 15km short).

  4. PaulH

    you need a sports medicine checkup for that sort of stuff (if you're *that* serious but you can guesstimate quite a bit of that). i've been trying to follow the advice here:

    http://www.cptips.com/intervl.htm
    http://www.ultracycling.com/training/training.html
    http://www.ultracycling.com/training/century.html

    we cheat a bit over here, our "centuries" are in kilometers ;-)

    btw what's your MB handle? mine's http://coldfusionpaul.motionbased.com/

  5. PaulH

    it took me a couple of years to crack 100km (mind you i'm still riding a mountain bike though i tricked it out a bit w/malvic rims & hutchison tires–the tires are nice & light but wear fast & get punctured way too easily–and i lost 6++ months when i dumped my bike into a canal & blew out my right knee). i spend 90% of my time on country/farm roads these days so i'll switch to a real road bike as soon as i can bring myself to spend that kind of money on a "hobby" (decent road bikes here are expensive & the choice is pretty limited though trek has a "starter" that looks like a good value).