Bikes and Code

And bike racing is back on the menu.

Team Escape Velocity puts on a series of races every spring, the aptly named Spring Series. The first race is a nearly flat 4 corner circuit race in Langley. Specifically, this. Last year’s race was marked by sleet and snow towards the end of it. This year, the forecast called for rain ‘in the afternoon’. I don’t want to give too much away here, but the forecast lied.

Let’s start out with a quick overview of a lap of the course: Go straight with a tailwind. Turn right onto a slightly narrower road. Enjoy a crosswind from the right for a minute or so, then turn right again onto a yet narrower road. This is also dead straight, but undulates slightly with a dip down most of the way through it. Turn right yet again onto the narrowest road in the race, which is also entertainingly the worst pavement in the race. Be bumped and jostled and lose 10m or so of elevation and turn right one final time back onto the front stretch.

I should have remembered this from last year, but the C race at least plays out in such a way that positioning is very important. With the yellow line rule in effect, there consistently is only one good place to move up significantly per lap, coming out of turn 4, onto the front stretch. Generally out of the other three corners, there is the usual acceleration out of the corner, then it slows right down again. As soon as that happens, the pack bunches up and there is no room to pass. The front stretch is a bit wider and takes closer to a kilometer before this happens, so moving up pretty much needs to happen here.

As for how much? Based on the numbers I got from the race, there were consistent accelerations nearly up to 50km/h out of the corners. This slowed down to below 35km/h on much of the rest of the course. What this actually meant was that the accordion effect was somewhat mitigated. Even at the back where you slowed down for the corners, you did not need to hit it too hard to stay on as the field slowed down significantly on a regular basis.

As for my race? The plan was to tailgun for much of it, getting a decent interval workout at the back. If I could position myself well, then try attacking on the last lap or two. I couldn’t position myself and a couple of crashes in the dying moments of the race did not inspire me to take further risks on the wet roads. Finished in the middle of the pack which did break up somewhat in the final metres.

All in all? I’m somewhat happy with it. It’s pretty much the flattest road race of the year for me, which is theoretically good for me, but not terribly exciting. Next week is the Armstrong Road course, which is dominated by a fairly serious climb every lap.

A few days ago, Translink announced that they would be releasing their bus, train and seabus route information in a standard format. A list of every bus stop, route, time, etc might not seem overly exciting to most people, but I love datasets. Admittedly, I often don’t know exactly what to do with datasets, but that’s hardly the real issue here. Anyhow, this seemed like a promising thing for me to do and I downloaded it, unzipped it and spent a couple of hours prepping a Rails project to serve as a new home for it.

Roughly 500 routes, 8700 stops, 126000 trips and 3.4 million timepoints at those stops. Not a whopping amount of data, but enough to start having some fun. My initial plan was just to be able to plot the stops for a given route onto google maps. That’s done in it’s ugly glory at my stopfinder. If you want to search for a 1 or 2 digit route, put in the leading 0’s. Sorry, haven’t done that yet.

My next steps are going to be to publish a number of primitive operations on the data with results in JSON format. Things like ‘closest stop to lat,lon’, ‘how to get from stop x to stop y’, and other similar sorts of things. The idea being that if I can build up a suitable library of common operations on the dataset, any future ideas that do come to mind should be relatively easy to implement.

That and if anyone does want to do some data mining, well, this is an option. I’ll post any updates, formats and that sort of thing on this site as I work through it. In general, the services will be pretty much simply URL based and will return raw JSON. Nothing special, but fairly easy to parse and work with. I have a relatively irrational dislike of XML which I will probably get over at some point, but it will take someone making a very good argument.

Cyclocross is my favourite type of bike racing. Due to my general lack of fitness and catastrophically (for a bike racer) low hematocrit, it’s also a type of racing that I’m pretty unsuited for. But amateur racing is for fun and not glory, so we’re not going to focus on that.

Ottawa has a great series of races each fall and while I knew it was something special, I had hopes that Vancouver would offer a similar number of races. As it turns out, there are a bunch of races, unfortunately, 4 of the 6 in the Lower Mainland are on two weekends as opposed to spread out over the season. Alas.

On the plus side, it’s easier to pretend you are a Serious Bike Racer when you have back to back races, which was kind of cool for me.

Race 1: New Brighton Park

Tough, tough race – Google Earth

Start was paved and slightly downhill into a paved hairpin. Bunny hop up a curb and into a narrow, muddy climb. No need to run up this one. Some up and down twisties then a double barrier for running. Up over some more grass and into some very tight, massively off camber corners where speeds dropped to below walking. Couple more corners, then some deep sand, more grass, two very short steep climbs, if it had been wet, both would have been run-ups, but as it was, riding was possible. Down to more sand and a giant step, then a final climb onto the pavement again.

Tough for me mainly as there was effectively no place to recover. I’m a decent technical rider, but I need to have short sections to ease up for a bit and bring the heart rate under control for a bit. Otherwise, it’s a more pure form of suffering which does not bode well for me. This was the case here. The course was, despite some short punchy climbs, was relatively flat, so there were no extended downhills to ease up a bit. To use some retarded sport dude statement, I was deep in the hurt locker the entire race.

Placed near the back of the pack. On the lead lap though.

Race 2: Vanier Park

More my style and possibly one of the most fun courses I’ve ever raced on – Google Earth

The start on this one was across a flat, hard packed and very bumpy grass field. Quick dismount to get up 6ish stairs and back on to climb up alongside the Planetarium. Winding climb up through the trees, not too steep, but in some thickish grass so it was somewhat of a power climb. Off camber hairpin at the top to drop down to the main part of the course again. Over a bridge and then continue the descent through some fast sweeping corners. Deep gravel hairpin, then some more twisty grass stuff and a couple of barriers on a steep uphill. From there, into what was called the maze. 4 back to back tight hairpins, 2 very off camber. The last part of the course was a hard packed mud out and back and a fun steep downhill into a right/left/right before the finish line.

The nice thing about this course, aside from the lack of places where running was required, was that there were places to recover. The relatively long downhill beside the Planetarium allowed for a few seconds of respite, which I need badly in a ‘cross race. It showed. I finished just behind someone who was nearly 3 minutes ahead of me at New Brighton. I was 2:30 behind the winner at Vanier and more like 6:00 behind the winner at New Brighton. Ended up 14th out of about 40, so not terrible I suppose.

What did I learn here? Not much. I don’t do well in road races that have lots of climbs as I am not terribly good at them. That said, climbing in a ‘cross race seems to be good for me. It means there will be recovery time later. Still, was well above the halfway through the field point at Vanier, so I’m taking that as a good sign.