On Bicycles, and.... what else is there?

The New York Times recently did a wonderful story about how European cities are not only directing resources towards improving access for cyclists and pedestrians, but are actively trying to retard the flow of motor vehicle traffic in order to promote cycling, walking, and public transit (which is often rail or priority-access bus lines). The text of the article was quite positive: streets for people, not for cars (which contain people, but are typically around 95% car, only 5% human), although the title was arguably directed at a motor-centric audience... a later opinion piece referred to this as "the windshield view". In any case, what Europe realizes is a priority on infrastructure for individual-passenger motor vehicle and infrastructure for cyclists and pedestrians is to a large degree mutually exclusive. I have experienced this first hand since I began working in Mountain View, CA, from my previous job in Palo Alto just to the north. There's a striking transi...

SB910, the proposed 3-foot space requirement for motor vehicles passing cyclists, has now been amended . Now it's looking to me really good. The earliest version of the bill was full of flaws, for example a requirement cars pass cyclists to he left (how does that work on Page in San Francisco, where the bike lane is on the left side of a one-way road?). Until the latest revision, there was an exemption allowed if the vehicle was no faster than 15 mph faster than the bike. The implication was speed differential matters. Speed is what matters, not differential. A major problem with the speed differential is it would have taken the teeth from the bill. All you'd need to say to defend yourself against evidence you'd passed to closely to a cyclist whom you'd hit is that your speed was only 15 mph greater. It would have been very hard to prove this was not the case. Thus we'd be back to the status quo that it would need to be established the pass was unsafe. ...

This morning a head-to-head competition.... I had 8 minutes to catch Caltrain 206. Plenty of time, but no time to waste. I got my bike in the garage, turned on the Garmin, left the garage, shut the automatic door, then pulled my Android phone from my pocket, brought up the Strava app, and hit new ride. Ten precious seconds later GPS signal was acquired and I quickly hit go. I clipped in and was off to the station. Twice per block I checked the status of the Garmin. As I've noted, this is a GPS-challenged environment, and the Garmin doesn't like it. For the first three blocks the progress bar moved steadily to the right. Then it retreated a bit. Then it regained some of its previous progress... where it stalled. I was doing well. Traffic was extremely light at 6:05 am, so my quest for scientific fairness wasn't placing too great a burden on my survival chances. The train station is just south of 4th Street. When I reached 7th Street I missed the light. I ...

Recently I've been testing the new Android Strava app . My preferred method of recording ride or run GPS data has been the Garmin Edge 500. On the bike, I use the usual mount which I attach to my stem. For running I got a Forerunner wrist strap which works great: the Edge 500 and the Forerunner share the same strap. But when the Strava app for Android app was released I was pretty excited. I'd read and heard hints and rumors of real-time features, perhaps for example instant notification of KOM rankings results while on the bike. But, alas, nothing so spectacular. The app reports speed, distance, and time of exercise, then allows the user to upload the ride to Strava. Once uploaded, a limited resolution map of the activity can be viewed along with rankings on matched segments (once the servers have had adequate time to process the data, less than a minute). So it seemed as if I'd have little use for it. But I decided to give it a try anyway. And I was pleasan...

I felt confident going into the Zombie Runner Half-Marathon last Saturday. Under advice from a friend I'd pre-run the course the Sunday before, and I was immediately really glad I had. Navigation was far from trivial, and having worked these potential snafu hotspots out already, I could focus my attention on running and less on orienteering. The only question was speed. I'd done very little approximating "speed work" this year, and with my run-specific training consisting of an average one run per week, I wasn't sure how I'd handle the increased pace that race day invariably inspires. Conditions were essentially perfect at the start line adjacent to Crissy Field as Wendell gave the starting line instructions. The course was simple, he said: just stay on Coastal Trail. But I realized from last week's preview run it wasn't that simple. One point of clarification: I asked whether we were going through the low-headroom tunnel at the top of the s...

The second worst offender in the little investigation I did last post was the "INTEGRATE Performance Fitness OLH Climb". Integrate is a fitness studio in Mountain View so I suspect they did a time trial there to test client fitness. But while the West Alpine climb which resulted in the 48 second error is a bit tricker to debug, this one is fairly clear. Old La Honda starts with a bridge crossing and finishes 5.2 km later at a stop sign immediately before a ridge road which contains high speed car and motorcycle traffic. While a full stop honestly isn't critical here, at least some attention past the sign is necessary. And it's common for riders to stop past the sign on the dirt shoulder. With manual timing, you start your climb at the bridge (I use the trailing edge) and finish when your front tire crosses the perpendicular line passing through the stop sign. It's all very precise. But nothing about commercial GPS is "very precise". As I...

DC Rainmaker recently did an interesting study of the accuracy of GPS units. He mounted eight different GPS computers on the handle of surveyer's measurement wheel then walked, ran, or rode various courses, comparing the measured results ( Part 1 , Part 2 ). The GPS units tended to disagree on how far he'd gone, although usually the results were consistent with the claimed positional accuracy of the units. I suggested he use the data to test Strava reproducibility in segment timing. No luck there, but I did find that a friend of mine has been in the habit of riding with a Garmin Edge 500 mounted alongside a Garmin Edge 800 on his rides. We have a mutual friend who works for Garmin, so he's doing this to compare the two. I asked him for data from three of his rides. I then created two new accounts on Strava and uploaded the data from his Edge 500 into one, and from the Edge 800 into the other. The new accounts are necessary because Strava rejects what appear to b...