Friday, July 31, 2009

This doesn't bode well...

...for justice in Asheville. An (unnamed) judge reduced Charles Diez' bail from $500,000 to $200,000 so he could get out of jail. Still no word on if he's still being paid. I have some problems with a culture that looks the other way and allows people to render mayhem with guns on the public at large just because they are "public servants". As alleged, this is a serious crime, and (according to news accounts at least) the facts of the matter do not seem to be much at issue.

Throw the book at this guy. He's proved that he's a menace.

Tuesday, July 28, 2009

Words can't express...

...the outrageousness of this story.

Charles Diez, an Asheville, NC fireman shot a bicycle rider on a Sunday morning because he was upset that the victim was bike riding with his child on a heavily traveled roadway.

The good news is that the fireman has been arrested, charged with attempted first degree murder, and has had bond set at $500,000. The bad news (well I should say more bad news) is that the fireman has been placed on paid investigative leave pending the outcome of an investigation.

The weird but great news is that the intended victim was hit in his bicycle helmet, according to police.They said the bullet penetrated the outer lining of the helmet but did not actually hit the victim's head.

Based on not a lot of data, let me do some rampant speculation of my own by making some observations and questions:
  • No doubt there were words exchanged. If it were me and a stranger came up in a car and accused me of endangering my child by carrying him on my bike, I'd no doubt call him (I think accurately enough) an "asshole".
  • The only child endangerment going on is being perpetrated by the guy with the gun.
  • Domestic terrorists? Bike-shooting gunmen? What the heck is going on in North Carolina? I've visited Raleigh on a couple of business trips and found it pretty pleasant, even a little hip for a Southern city. Obviously, I was missing something.
  • Traffic on a Sunday morning on any street in a town of 75,000 can't be that heavy.
  • There are inevitable perceived parallels to the Cambridge police / Gates story as it relates to potential abuse of power by public servants. (I wonder what race the bike rider, who is not identified, was?)
  • This is a great example of a great reason for background checks not only to purchase a firearm, but also background checks to renew a license to own and use a firearm. (In other words, the owner, not the hardware, should be registered and should periodically have to prove that he is not a menace for owning the weapon.)
  • Paid leave? Come on! What's to investigate? Chief, read the police report and cut your losses!
  • I want a helmet like the one the bicyclist had!
It's worth going to the story link above to read the 14 or so pages of comments. They are very telling. (The fireman actually has some defenders.)

I have to ask the question, how can this happen in a city named the "most vegetarian-friendly small city in America" by the PETA?

Saturday, July 25, 2009

Creepy

Is it just me who finds the new Toyota Prius ads creepy? Apparently.



Yes, I know that the Prius is the most fuel-efficient car out there. Yes, I know the Munchkin-like seething mass of humanity is mostly computer-augmented, just like the Coliseum crowd effects that won the Oscar for the movie Gladiator. But it still creeps me out.

Part of what I know about the Prius is this: It's a car. (well, duh.) And that means it's big and heavy (relative to my scrawny transporation system, that is.) Think about it this way: A Prius hauling a single person (most of them do) is getting (let's say) 50 person-miles per gallon of gas, (which contains 31,548 kcal), or 31,548 / 50 = 630 kcal per mile. On a bike, I can cover roughly 15 miles per hour burning 700 kcal, which works out to 700 / 15 = 46.7 kcal per mile. So my system (for a single passenger) is 13.5 times as efficient as a Prius. So if a Prius gets 50 mpg, I get "675 mpg". (I know that's a bit of a red herring.)

In honor of this ratio, I'vc created a graphic. You can download the high-rez version here, if you want to put it on a t-shirt or something.

But the latest data point about hybrids is a truly unexpected one: according to insurance statistics, hybrid drivers drive more, get more tickets, and have more accidents than non-hybrid drivers. (Perhaps they are distracted by their hypermiling techniques?) According to the study cited here, the decreased guilt associated with improved fuel-efficiency increases the number of discretionary trips by up to 25%, largely offsetting any petroleum savings.

It is, after all, just a car.

Sunday, July 19, 2009

Hardware, Software, Wetware

My twin brother Willie (who runs teams of engineers that design highly-sophisticated silicon chips) used to say that there were three kinds of computer "ware": hardware, software, and wetware. Hardware and software (and their distant cousin, firmware) you already know about, if you're using the Web to read this. Wetware is, of course, the user of the computer, and ultimately where the rubber meets the road, so to speak.

It seems to me that when one thinks about bicycle-commuting systems, the same three levels impose themselves. Let's consider them in reverse order:

There's the "wetware" crowd, the people who get out there and "just do it". Sometimes referred to as "vehicular cyclists", they insist that all that they need is the road and the rules for it, which exist everywhere. They tend to be skeptical of structured solutions. The most radical among them can be rather vocal in their beliefs that structure is bad, and will give the powers that be the ability to segregate cyclists to a second-class status. (I count myself in this crowd, although to be sure not one of the radical ones.)

Then there's the "software" crowd, the ones who think that to be safe, cyclists need the protection of bike lanes and striping -- clear demarcations that differentiate cyclist territory from motorist domain. Sometimes referred to as "infrastructuralists", they don't commute as much as vehicular cyclists, simply because bicycling infrastructure isn't so widespread as it could be. Those among this group who do commute regularly therefore are geographically distinct -- they tend to be located out West, in Oregon, Colorado, and parts of California and Washington. Sort of like rare birds with a distinct habitat.

Finally, there's the "hardware" group -- those who think that to be safe, bicyclists need their own separate and independent bikeways. These can be bike paths (typically engineered for about 8 mph, and leading to recreational destinations, not so great for commuting, really) or fully separate bike lanes (preferably with curbs to physically separate them from cars). The Achilles' heel of these approaches is usually the place where they have to come back to the "standard" roadway system. Rejoining the regular transportation system is the most critical aspect of any separated system, and often times it is under-engineered (the "engineering" consisting of a wheelchair ramp at the curb.)

I have a 3/8 mile stretch of bike path paralleling a busy road that I use on my daily commute, and I have learned that rejoining the traffic from that path is by far the most treacherous part of my daily ride.

Recently, a couple of designers have gone quite a bit further and proposed systems that totally separate bikes from the quotidian automobile infrastructure. (Maybe I should categorize these as "super-hardware" people.) Personally, I find them amusingly naïve and impractical. Naïve, because these people are convinced that public financing can be found for these schemes when it's hard enough to find money and will to do simple striping. Impractical, because I don't see where these structures provide the motiviation to ride. If one is motivated, he or she tends toward the "wetware", and all these other things just become (in their absence) excuses not to ride.

I'm not trying to be mean here, it's just my belief that since the advent of the first commercial "safety bicycle", the bike has evolved into a pretty efficient system which works pretty well quite on its own, thank you very much. When I see a new idea to improve the system, I'll be the first to doff my helmet. but it's not so easy to get excited about ideas that just tinker around the edges.

Anyway, let's take a look at a couple of these visionary pretexts for not riding.

Vel0-City is a system of elevated enclosed tubes proposed for Toronto. To its credit, it seems to have the macro-planning thought out in that it appears to be integrated into the mass transit system as a whole. To be fair to the envisioners of this project, I think that protection from the elements in the winter in Toronto is a winner of an idea, but I wonder if the good taxpayers of Toronto will support yet another mode of mass transit, in addition to its existing bus, tram, and metro lines. Like any of those other mass transitways, I suspect, graffiti would pose an ongoing problem.

Remarkably, Velo-City promises a perpetual tailwind, with one-way tubes somehow creating a "dynamic air circulation loop." I could use some of that, but I wonder about the physics!

The Shweeb (no, I don't know where the name comes from -- it seems vaguely German in its tendency to clear the throat) is a pedal powered monorail that exists as an amusement park ride in Roterua, New Zealand. Two pedal-powered capsules swing around a 200M monorail racetrack. Frankly, this looks like quite a bit of fun. The fun rumor is that someone in the London Development Agency has latched on to this idea as a means of mass transit in London. (Don't you just love the "science-fiction pulp magazine cover" look of the rendering at right?) I think this idea works much better as an amusement park race than as a mass-transit system. I'd hate to get stuck behind the little old lady who's doing some urban sight-seeing when I'm in a hurry to get to work. And as much maintenance as Velo-City would require in removing graffiti, Shweeb would require in spades. Believe me, you don't want the capsule that's just been given up by the vomiting drunk!

As a postscript, here's a different take on bikes-as-infrastructure: Hybrid-squared. This system proposes a public bike system (think Vélib) whose bikes have a combination of dynamos and regenerative braking to charge ultracapacitors that then dump their stored energy back into the grid when you return the bike to its station. It's a neat gedankenexperiment, and envisions a credit system where bike-commuting pays for mass transit use, which is a clever scheme. But I wonder if the net energy would amount to a hill of beans, enough to ever pay back the investment in infrastructure. (Is anybody running the numbers on these flights of fancy?)

Thursday, July 16, 2009

Practical Cycling Defined

I define practical cycling most succinctly as "cycling miles that displace motor vehicle miles."

A group of six (only six?) high-school counselors has done a significant bit of practical cycling by touring college campuses (in my stomping ground, in Maryland, Pennsylvania, and Delaware) to check them out for their student counselees. Twelve days, more than a dozen colleges. 400 miles. (Now that I think about it, although that's only 33 miles a day, it still would take some selling to convince most people not doing serious cycling already that they could handle that.) This is significant. Yes, it's billed as "combining a serious tour with their love of bicycling," but this is ordinary people doing a sustained tour at 1/4 to 1/3 the rate of the Tour de France.

The story in the New York Times is here.

I'm impressed, and I hope their numbers grow next year.

Friday, July 10, 2009

Tripping the Lights Fantastic

Trip it as you go On the light fantastic toe -- Milton, L'Allegro

If you do much urban riding, you've probably encountered one of the practical cyclist's banes: embedded loop sensor activated traffic signals. Which is to say, loop sensors that ignore (or rather, fail to detect) bicycles.

There's one on my daily commute home. If I'm a little late on the way home and motor-vehicle traffic is diminished, I can wait through a couple of cycles. Nothing is more frustrating.

Apparently, this is a widespread problem for cyclists. There have been some gadgeteer approaches to this problem involving gluing very strong magnets or large metal plates to the bottom of your cycling shoes. Hm. I carry a laptop in my left pannier, and I'm reluctant to expose it to strong magnets.

So what to do? I've done some research, and have some information to share. I've come to the conclusion that this is a three-stage process; Keep advancing until you find a satisfactory solution for you.

1. Optimize your placement. First and foremost, know where to put your bike on the loop. (This is where I was going wrong.) The green zones in the diagram at right are optimal. (I was using a "Dipole" position on a "Quadrupole" loop. If you are seeing a "Diagonal Quadrupole" loop, you probably live in Davis CA, Boulder CO, or Portland OR.)

2. Know when you can "Cheat". If you use optimal position as noted above, yet you pass through an entire cycle and the traffic signal fails to let you through, then the signal can be considered "defective". Most jurisdictions allow running the light in such a situation. If you do this, be doubly careful! Watch most carefully for traffic that doesn't see you!

3. Contact your local Traffic Engineers. The good news about inductive traffic loops is, they're easy to adjust. The bad news is, you may get ignored by your local traffic engineers. When I emailed my county engineers about the light I'd been having trouble with, their advice was to dismount, walk as a pedestrian across 3 traffic lanes, and actuate a pedestrian call button. I hope you have better luck when and if you have to call them.

Here are some more avenues for research, if you want to dig deeply into the physics of embedded loops:

Goodridge article, "Detection of Bicycles by Quadrupole Loops at Demand-Actuated Traffic Signals"

Tracy-Williams article, "Traffic Signals"

John Allen article, "Traffic Signal Actuators: Am I paranoid?"

Friday, July 3, 2009

Online Bike repair guides

In the old days, when there weren't so many bike shops and the Internet was a green-screen geeks-only paradise that offered only email, FTP, and Usenet discussion groups, getting information on how to fix your bike was difficult. Bicycle repair was a matter of lore, and virtually all serious riders were competent mechanics (at least to a degree.) For the first 20 years of the Tour de France (1903 - 1923), a rider was in fact required to do his own repairs. (Thanks Chairman Bill.) Perhaps this custom that riders be self-sufficient is why John Forrester's seminal book Effective Cycling has so many of its pages dedicated to bike maintenance and repair.

Now, of course, if you don't want to get your hands dirty, it's a quick trip down to the local bike shop to get that drivetrain fixed or those brakes adjusted, or maybe even a trip down there to get diagnosed what is wrong in the first place. This is fine if you have the money, or lack a mechanical aptitude gene. (It also keeps the local bike shop in business, which isn't a bad thing either.) So you, dear reader, have choices, and an excellent choice is an on-line bicycle repair website. The web is full of them, some good, some very good, and some quite generic (the "generic" ones are the ones that list "bike repair" up alongside "gutter repair" and "13 uses for baking soda".) I've surveyed several of the bike-specific sites here and hope you find the overview useful:

Park Tools Repair Site:
This ia an encyclopedic, professional bike repair web site. Not surprising when you consider the source -- Park tools have a deservedly excellent reputation and there's no better way to sell and support tools than to show people the proper way to use them. The Park website has a nifty interactive Flash-based "bicycle map" that hightlights the parts of the bike that may need repair and navigates you to the "chapter" of the website where you can see the specific topics on that part.

Bikewebsite.com:
This website is very old-school. It has a chaotic layout, with ads sprinked about. Topics are hit-or-miss. The illustrations are both sparse and of marginal quality, looking like they were created with a DOS-based paint program on a VGA screen. There are a few interesting sections, though, including a section that deals with diagnosing what's wrong with your bike based on how often you hear noises.

Bicycletutor.com:
This is easily the most "social web" oriented of the repair sites. Most if not all instructions include downloadable videos. Note the "tags" below the image-map of the bike at right. All instructions allow comments by users. This site has some general topics, such as "how to shift gears" and "how to tune up your bike", as well as the specific highly-categorized topics.

Utah Mountain Biking:
This site has a large selection of topics; each topic is well-illustrated with lots of well-cropped photos. I like that the graphic bike-parts index includes "Chad". Definitely a focus on mountain bike and downhill stuff here -- this is the place to go to get info on disk brakes and shocks.

Jim Langley's Bicycling Site:

This is definitely an "old-school" site with a pleasing personality. Lots of old-bicycle-poster eye candy, lots of mini-articles about bikes, with a focus on antique bikes. He does have a page calling out bike terminology, but unlike the other sites, he doesn't use this as a clickable index. This won't suit everyone, but the information given, although you may have to hunt around a bit to find it, is good. He has a number of topics on bicycle fit and adjustment.

Sheldon Brown's Fixit Pages:
The late, great Sheldon Brown of Massachusetts' Harris Cyclery had a collection of pages on the Harris website. The range of topics is by no means encyclopedic, in fact it's hit-and-miss, but if Sheldon Brown covers a topic, it's worth taking a look, because the depth of his topics is extreme (including things about the history of each component, going back to the English/ French/ Italian standards of the 1950s). Each topic is more like a brief "white-paper" style treatise on that kind of bike component or situation. For the experienced cyclist, this will be elucidating and enjoyable, but it's not for beginners who are looking for a "step-by-step" approach.

Wheelpro Wheel Building Guide:

I'm going to wrap this up with a single-topic website, or rather, a reference to an excellent book on perhaps the most important maintenance / repair topic, and that is wheels and wheelbuilding. Roger Musson, a British bicycle wheelbuilder and mechanic, has written the final word on building bike wheels.

It's not free, but neither is it expensive, and it comes with a money-back guarantee. It's packed with useful information and guarantees you that if you follow the instructions, you can build a wheel that will be straight and true for its lifetime (i.e., until the rims wear out.) If you like riding on round, true wheels and want to build wheels that are better than those you can buy, this is the reference for you.

Summary Chart:
For those of you who have made it this far, here's a chart summarizing the topics covered in all the sites listed. Click the image for a high-resolution, printable version.

Saturday, June 27, 2009

Bike Comics

Bike comic strips and comic books, that is. No stand-up here. Let's visit a couple of modern-day heroes, and one very special superhero from the 70's.

Frazz by Jef Mallet

Frazz, aka Edwin Frazier, is a man for our times. Obviously educated, he is nonetheless underemployed (intentionally, for his backstory is, he's a songwriter who has made it big but can't give up the interactions of his "day job" as a middle-school janitor.) His interests? Education, philosophy, music, the impertinence of youth, and (to no small degree) physical activity, which includes a good deal of bicycling. To his credit, when Frazz is on a bike, he always wears a helmet. If you're lucky enough to have a daily newspaper that carries Frazz, don't pass him by.

I really like Mallet's graphic style. While it is very disciplined, it looks loose and sketchy, almost at times like Bill Watterson. His characterizations (both visual and dialogue-based) are great. I especially like Ms. Olson, who (no doubt unfairly) reminds me of countless teachers of my youth.

Yehuda Moon and the Kickstand Cyclery by Rick Smith

Yehuda Moon, like Frazz, is full of attitude (what practical cyclist isn't?) Yehuda is in the trenches, however. He works in a bike shop (the Kickstand Cyclery) and is a year-round commuter. He lives to ride, and will use any excuse to get on his bike to "run an errand". He seems to lack Frazz's lofty philosophical point of view, though, and the day-to-day of the world gets to him quite a bit more than Frazz. Sometimes the 'tude manifests itself as antipathy to heedless drivers (as in the example above) and sometimes it's just pure stubbornness, as in Yehuda's refusal to wear a bike helmet.

Yehuda Moon is an online-only strip and is subscription supported. Judging from the amount of comments on a strip on any given day, he has a strong readership (and I hope that is reflected in the subscription ranks.) There are a lot of cyclist "insider" jokes in this strip, and casual recreational cyclists might not get all of them. But you know, I've known guys (especially in Austin, Texas, where I used to live) who worked in bike shops who were just like Yehuda Moon.

Sprocketman by Louis Saekow

Sprocketman is a superhero with a single purpose, to see that people are safe on their bikes. He originally appeared in the mid-t0-late 1970's in a comic book that was published and distributed as a joint project of the (California) Department of Public Safety and a nonprofit organization called the Urban Bikeway Design Collaborative. The comic book was drawn by a pre-med student at Stanford named Louis Saekow. It turned out to be a bit of a game-changer for Saekow, as he had so much fun drawing the comic book (his first) that he changed his major from medicine to graphic design!

In late 2002, Stanford University Transportation Services commissioned Saekow to do some more Sprocketman promotions. I'm not sure if they ever intended to do a complete comic book, but if it happened, I haven't been able to locate it. I think I may still have some original Sprockeman comics out in the garage — I used it in a bike commuting class that I taught 'way back in 1979. If you want to see the original Sprocketman comic book, you can download a PDF of it here.

Sprocketman also puts in an appearance in a very quirky website called "Pisser," which stands for "Public Information & Safety Superhero Education Rangers".

Wednesday, June 24, 2009

Times Square

I asked my younger daughter (who lives in New York City) what she thought about the new Times Square makeover (where Broadway has been blocked from automobile traffic in a couple of places) and she seemed dismissive. (She might have called it a "gimmick".) I think that she, as an adoptive New Yorker, wants to keep away from touristy areas, and Times Square certainly qualifies.

It's weird to think about cheap folding lawn chairs in the left-over spaces where Broadway used to cross 7th Avenue (which remains open, by the way.) Supposedly, the city takes up the chairs every night and redistributes them every morning. Is this any way to run a national urban landmark?

But there's something important about the New Times Square makeover by the Planning Department of New York City. If nothing else, it's the first U.S. project (ad hoc though it be) in my memory whose momentum is decidedly anti-car. Nicholai Ouroussoff reviews the "design" in this article. Nick O (as I will dare to call him) is right on the money about the unplanned nature of the action (as he says, "this is not the Piazza San Marco in Venice or even Trafalgar Square", but I think it is so important to expose people (even if they are unwitting tourists!) to the idea that the U.S. can have a "public realm" that isn't driven (sorry!) by traffic engineering.

Over at the very interesting blog, World Streets (newly on my blogroll), there is a very interesting article (which promises to be a series) by Paul Barter, a professor in public policy at the National University of Singapore, about "The Battle for Street Space" that is really worth a read (as is much of the other stuff over there.) I see many people from all over the world on that blog talking about 30 kph (yes, kph) speed limits everywhere except on highways. My first reaction is to lecture these people about how this will never fly in the U.S.; the auto is forever king here. But maybe not -- Times Square is a very interesting precedent. It will be fascinating to see where it goes.

Sunday, June 21, 2009

Apple and bikes

Continuing on in the "what if XX made a bike" series, let's take a deep breath and go after the big one: Apple.

Prologue: Today's state of bicycle "captial D" design to my mind is so-so at best. The fact that opportunity still exists for Apple to come in to the market (should they decide they want to) means that design is still lagging, despite all the effort put towards it. At right is a "design" put forth by Puma, a design-conscious fashion clothing manufacturer, for their fourth-generation bike. They appear to be making some kind of statement about color, except they can't quite get even that right (ahem, guys, get a white handlebar, stem, and front rim, and powder-coat the front brake calipers! If you're going to make it about color, DO IT!)

If Apple made a bike, what would it look like? Knowing what I know about Apple (I've been a Mac user since 1984 and have worked for 10 years for Nemetschek North America, makers of Vectorworks, the best-selling CAD product on the Mac), and particularly considering its recent successes with industrial design since the iPod, here is what I could reasonably predict about any Apple product:
  • It would be iconic; recognizable as the thing that it is (that is, it would be a realization of a classic design rather than a revolutionary design.)
  • It would feature obsessive attention to detail.
  • It would focus on the user experience.
  • It would definitively fix problems with the product category that users didn't realize they had.
  • It would be visually beautiful and a tactile delight.
  • It would co-promote other products made by Apple as part of a lifestyle.
  • It would be expensive, a stretch for the pocketbook; something that conveys status, but stops short of aloofness.
  • It would be value-engineered, so Apple could make a decent profit.
  • It would be sold only through the Apple store. (duh.)
  • There would be tremendous opportunity to create a third-party "add-on" ecosystem.
So, how would these "branding requirements" translate into a specific bicycle design? What are the "unrealized problems" waiting to be solved in bicycle design that could be fixed with an obsessive amount of user-centric problem solving and delivered through industrial design? I think the major problems to be solved (the "user requirements") are these:
  • Looks: The bike should have a minimalist look, as much like a fixie as possible. The explosive popularity of fixies is all about that sexy, iconic bike look.
  • Shifting: Bikes need to be easier to use (i.e. shift) so that users don't wear themselves out getting from point A to point B. (Fixies look great, but aren't practical unless you're an athlete.)
  • Security: There needs to be a convenient, highly effective anti-theft solution.
  • Comfort: The places where your body touches the bike, the controls, the seat and the pedals, need improvement. This is after all the "user interface" of the bike. Ideally, other than for a helmet (and maybe some sporty-looking gloves) you wouldn't need any special clothing to use this bike.
  • Maintenance: The thing needs to set new standards of minimalism in maintenance.
Specking out this bike (at a high level) would be fun—more fun, I daresay, than the sweat-work of designing and testing it. (So, let's do it!) I would think we'd see the following kind of "functional specification" from Apple in trying to fulfill these requirements:
  • Frame: Probably hydr0formed aluminum, welded, with smooth-dressed joints. The finish would be anodized ("nanochromatic" colors to match the iPod nano?) and clear-coated. All cables would be internally routed. The frame would be set up so that a minimum number of sizes (maybe just two: small and large) would accommodate all riders. This presumes a maximally adjustable seatpost and stem arrangement.
  • Drivetrain: Internally-geared rear hub, probably 8 speed, with an automatic shifter working off cadence and speed scnsors integrated in the frame. Belt drive. Gear range for city hills.
  • Brakes: Internal hub brakes front and rear. (Yes, the hubs will be big, but it'll be a clean look and low maintenance. Speaking of which...).
  • Maintenance: Carbon or aramid drive belt good for 10,000 miles. Sealed bearings everywhere. Aramid-belted tires (possibly tubeless) with interior goo to stop slow leaks. All cables Teflon-coated. An absolute minimum of hardware exposed to the elements. Here's where that famous Apple attention to detail will pay off.
  • Controls: Brake handles with fully-concealed cabling. The cyclocomputer would be your iPhone or iPod touch running a "free" app from the App Store. The app would integrate GPS, speed, odometer, traffic and weather reports, and (naturally) music. There would be special valve-stem caps that could sense low pressure in your tires and transmit warnings to the control unit via Bluetooth. Oh, and the app would enable customization of your shift points on the transmission. The front hub would be a dyno-hub to keep the lights and the iPhone charged up.
  • User Interface (pedals, seat, handlebars): I think Apple could come up with some clever platform pedals that would work with street shoes but still have some restraint to allow pedaling efficiency. And the handlebars should be "fixie" style, perhaps with cell-foam padding so they could be used without gloves. The saddle is the real problem, because it needs to fulfill two conflicting requirements (1) be an iconic bike saddle; and (2) be comfortable. I think they'd have to do something like provide a "basic" saddle that has a proven comfort record like the Terry Liberator, and a "premium" saddle that is a Brooks classic leather saddle that comes fully broken in. (That will be an expensive extra cost option!)
  • Accessories: I think fenders, yes; but rack, no. (Fenders are sexy, racks aren't.) Instead of selling racks and panniers, Apple could sell coordinated backpacks (they could re-brand this ergonomic German one). Lights front and rear, for sure, integrated into the frame. The really tough challenge is the security issue. You could easily design security to work for Mudville, but not so easy for Manhattan. And effective locks are so big and heavy. I think Apple might try a two-pronged approach: first, a frame design that integrated a solid locking bar that would allow you to use a small high-security lock rather than a U-bar lock, and secondly, something (again an extra cost option) that worked with the iPhone to transmit a "help" signal if the bike were being tampered with.
Whew. Quite a bike, huh? What should it sell for? I would say that it ought to sell slightly above the price range for Apple laptops, say $1900 to $3500 depending on the options. I daresay that Apple has enough economies of scale, manufacturing wise, to be able to pull this off, and to value-engineer it to make a profit. (That auto-shifter will be tricky to engineer for sure, but Apple's just the company to do it.)

An industrial designer who is really ready to take on the challenge of the Apple bike is the Swedish designer Erik Nohlin from Gothenburg. He entered his delightfully minimalist, well thought out "MuskOx" design in the Bicycle Design (blog) "Ultimate Commuter Bike" design contest. (He should have won in my opinion.) If Apple wanted to get into bikes, they should just hire this guy, give him the list of requirements, and fund him.

But, first things first, Apple. Before you can proceed on this project, you have to wrestle the "iBike" trademark (#3096850) away from Velocomp LLP, makers of the "iBike" cyclocomputers.

Thursday, June 18, 2009

Web Skills for Practical Cyclists I

It's 7:15 am, and for the last 90 minutes, my part of Maryland has been under a downpour. Nonetheless, I'll be riding into work today, because by 8 am, the rain will be gone. How do I know this? Accuweather radar.

The Accuweather web site has made finding the "holes in the weather" (if they exist) possible. Real time radar is such a great piece of information. It's not hard to learn how to gauge clear spots, and to leave work a half-an-hour early if that's going to get you home dry. You can look at the radar and see if the storms are concentrated "cells" or widely dispersed, slow or fast moving, and figure out if (mostly) dry riding is possible.

Modify the following URL and paste it into your browser to see the real-time weather radar in your area, right now:

http://www.accuweather.com/radar-local.asp?partner=accuweather&zipcode="YOUR ZIPCODE HERE, NO QUOTES"&level=local&anim=1

One of these days, I'll evolve into a real practical cyclist, one who doesn't care what the weather is doing, because I'll be properly equipped and will have the right attitude. Until then, I've got Accuweather.

Sunday, June 14, 2009

Disc Brakes

... or is it Disk Brakes? Anyway, I've never understood the use of disc brakes on anything other than a mud-eating mountain, downhill, or (maybe) cyclocross bike. The brake-choking mud or dirt seems to me to be a requisite to justify it.

Why is this? The reason is simple, if you have an interest in amateur physics (and I do): Braking Torque. Think of it this way: if the braking is occurring at the hub (as it is with a disk brake), then all the braking force has to be transmitted from the hub, through the spokes, to the rim (where after all, the "rubber meets the road.")

This means that the spokes (which are the weakest link of the wheel) do at least twice as much work on a bike equipped with disk brakes. I haven't seen statistics for this, but I'd be willing to bet that spoke breakage is higher on bicycles equipped with disk brakes. I also wonder if there is a higher rate of failure of the seat stays (which absorb braking force), since the force applied by the disk brake is several times higher than a rim-caliper brake. (see illustration)

On a rim-brake setup, you can think of the entire wheel as the "disk". Braking force is less, but more importantly, the braking force is being applied near the rim, and the only loads that are carried by the spokes are for driving force (which are inevitable) and structural (keeping the wheel true and round).

As long as the wheel is in fact true, and you can properly keep adjusted your rim-caliper brakes (of whatever type), They are a physically and structurally superior solution. It does require that you keep your wheels true, but I'm sorry, if you have wobbly wheels, your riding quality is going to be pretty poor no matter what. I will grant that using the rim for braking means that the rim is eventually going to wear out and you'll have to replace the rim (rebuild the wheel), but we're talking tens of thousands of miles here.

Of course, bike manufacturers are loading up their offerings with disc brakes, even for bikes that will never see off-road use (and of course many so-called "mountain bikes" will always be on a paved trail.) Here's an offering from Raleigh, here's one from Trek, here's a Civia, and even REI has one. These are all touted as premium bikes in their categories. But bear in mind that the disk brakes, while superior in an automotive setting, don't convey that much superiority in a bike that won't be used on unpaved trails.

Give me old-school cantilevers any time. They require some hand strength, but they never fade, and boy are they reliable.

Update: The excellent "Cozy Beehive" blog has a report on a disc brake induced failure here.