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.

And in case it wasn't obvious, I love riding.  ;)  I haven't done anything seriously active for the past 7 years (I quit swimming in January 2000), and I didn't realize how much I'd missed it.  Riding's nice, because you get fairly constant scenery changes (unlike the bottom of a pool), dynamic exertion from hills and such, and it's just so much fun work your way up a big hill and get to scream down the other side.

Second, I resorted the ride listing so that by default the most recent ride is at the top.  That's what I'd intended from the beginning, but it didn't work, and I hadn't taken the time to figure out why until now.  Turns out that my reference maintenance code reorders stuff when new data is pulled in and it does the state substitution on existing entities.  It uses a couple Dictionary objects as lookups for the substitutions, and they don't maintain insertion ordering (and why should they?), and I didn't consider the ramifications.  But that's fixed now, and also means that the bike selector when adding a new ride will work "correctly" in that it'll automatically select the bike you've ridden most recently, rather than the one your rode first.

The route maps stuff is nothing more than  URL field that causes rendering of a 'view' link that loads the URL in a new window.  As such, you can use whatever you want for your maps.  Now that Google Maps has custom rerouting, that's pretty hard to beat for ease of use.  But you can use whatever you want as long as it lives at a public URL.

Now that that's working right, multiuser is next on the list, and I'll probably throw a "route link" field in there as well so you can link to a map of your route if you have one.

There's a couple "weird" characteristics to the UI, but they have sound backing.  First, the entire UI is modal-free excepting the login form.  I didn't want to be stuck editing something and realize that I hadn't created some related entity and have to cancel out to create it.  I also wanted to be able to view the listings while adding/editing entities, so all the forms show up in tabs along with the listings so you can easily switch back and forth.

Second, the whole UI is publicly available.  I didn't want to build a separate admin area, so the editing UI doubles as the detail view UI.  The "Save" buttons are disabled unless you're logged in, and that's backed up on the server-side, of course.

Last, while not easily apparent, is the security of the authentication without using SSL.  Part of the AS3 Core Lib is MD5 hashing capabilities, so when the password is entered client-side, it gets hashed before sending to the server.  This provided a nice solution to password transmission that didn't require an outward facing self-signed SSL certificate (which isn't very friendly) but also doesn't compromise passwords.

Once I get stuff a little cleaner, I'll post source.  I'm also thinking of making it multi-user, but there are some weird issues (like handling public browsing) that would need to be dealt with.  Time will tell what becomes of it.

I also added contextual ride history to the single-entry pages on my blog.  I'd added it to the listing pages a while ago, but realized that a large percentage of my audience reads my blog via the XML feeds, so they never see the listing pages.  So rides within 24 hours of a given entry will now show up on the single-entry pages.

My dad graciously donated his old touring bike to the cause, and boy and I out of shape. I've never been a particularly strong person, but I've always been able to exert to my limits and sustain it. Not anymore. Covering the 10 miles is no big deal, but the number of times I have to remind myself to take it easy is annoying. But that'll come down as I get back into it. Fortunately it's cooled down for the past couple weeks after. We'll see how it goes when it gets hot again.

So far, no real muscle aches or anything, which is nice. Definitely can tell I've been working, but I'm still able to bound up the stairs without issue. Sitting at my desk all day has led to some stiffness, but it's not too bad. Need to start doing a better job of stretching and such after riding to help the muscles "clean up".

Most exciting news of all is that I'm getting a new bike next week. Dad's is a solid bike, but after riding it a while, I wanted to change a few things to suit me better. After talking to the guy at the bike shop, it wasn't going to be significantly more to just get a new one compared with upgrading. And while newer isn't always better, getting a fresh set of everything will certainly reduce the amount of maintenance and upkeep required for a while.

With me an my penchant for info porn, I've been logging all kinds of relevant data about rides. Expect to see pretty visual displays of that data with the next "whenever I feel like it" or so. Might even have to break out CFCHART with the public consumption requirement, rather than my usual SVG charts.