Magic Spot Flowing

One of my favorite things about not having a car is that it reminds me to think of my journeys as part of the fun of my trips. Journeys take more of my time than they do of most people’s, so if I don’t enjoy them and look for ways to spice them up, I’d be much more annoyed by their duration, and I might as well just give up and buy a car.

This weekend I had several long-journey adventures.

First, I decided that instead of taking the Capital Corridor train all the way from San Jose to Davis, I would shorten (and save money on) the journey by taking BART to Richmond. (It’s not really shorter, but the weekend afternoon CC and Caltrain schedules don’t mesh very well.) There are two options: Caltrain to Millbrae to Richmond, and bike to Fremont to Richmond.

Fremont beckoned. In the three years that I’ve lived in the Bay Area (I moved here on the second weekend of November in 2005, so this was my anniversary weekend), I’ve never been to Fremont, only through it on CA-84 and I-880. And I’ve never biked over the Dumbarton Bridge (CA-84) which is one of the four bridges in the Bay Area you can bike over, and the only one that’s within my normal bike area that I have never biked over (since I crossed the Golden Gate for the first time during Waves to Wine).

I mapped out a route using Fremont’s bike map, aiming for roads with bike lanes because I’m not familiar enough with Fremont’s roads to know which non-laned roads would be comfortable for riding. The route I chose was scenic, but not short:

Willow > CA-84 Bike/Ped sidepath/sidewalk > Marshlands Rd > Thornton Road > Paseo Padre Parkway > Mowry Ave > Civic Center Pl > BART Way

The total distance was 17.8 miles, so my roundabouting added about six extra miles (Fremont is about 12 miles as the crow flies). Luckily, I planned for the extra time, leaving around 1pm for a 2:30 BART train. I got to the train just in time to board without being in a desperate hurry, but not without being worried. Thank goodness for having a tailwind most of the way, and for my leftover W2W fitness.

The route, despite involving bike lanes for nearly the entire way, was not entirely what I would call pleasant riding. To go about it backwards, Paseo Padre is a bit like Central Expressway (something I suspected from its Parkway appellation) only the bike lanes are even more poorly lined at intersections even though they are official bike lanes and not shoulders. The intersections were poorly designed overall, with bad pavement and short lights, and the intersection of Thornton with CA-84 and surrounds (yes, you get off 84 and then have to cross it again) was seriously the most terribly-designed intersection of a bike-laned road with a major highway I’ve ever seen. And I’ve seen lots. Fremont? Not a terribly bike-friendly town, based on what I saw.

Before you get on Thornton, Marshlands Road is a two-lane road with “bike lanes”. The lack of real bike lanes rather than gravelly, terribly-paved, nearly unpainted imitations isn’t a serious problem because there’s almost no traffic, but the paving in general is very poor, although the scenery is quite nice: marshy areas, with hills arising out of them.

The bridge bike-ped path, and the path leading up to it (it starts at Bayfront Expwy, where the road gets wide and the speed limit high) was for most of its length fine except for having a lot of debris, which is basically par for the course for sidepaths. However, it also had two inset plates which were so inset that had I hit them unawares, I could easily have lost control of my bike. Note to self: find out who is responsible for that crap, and get it fixed. And then there was the flooded road. Yes, really. The road up to the bridge, itself, of course, was not flooded. Can’t have that. Cars must get through. But the sidepath/road to the recreation area (which you’re supposed to use until you reach the sidepath for the bridge itself) was under several inches of water.

No thanks. So I rode a short distance on the shoulder of the bridge approach, then carefully took my bike down a small embankment and over to the bridge path proper.

Riding over the bridge was pretty awesome though. The temperature was in the upper 70s and it was as clear as a bell. I watched the blueish water of the bay, and seagulls flying along below me, as I took in a view of the contrasting pinkish-tan East Bay hills ahead. It’s a longish climb but shallow, and an equally nice descent.

I enjoyed my BART ride too: conversation with a fellow bike enthusiast, reading and people-watching, and an unexpected view of the city and the bay when the train came up out of the Oakland subway portions. Transfer at Richmond was fairly painless (this was also the first time I’ve ever been north of Berkeley or south of Bay Fair on BART — now I’ve been to all the line termini in the inner Bay Area!), and the views began again. The Capitol Corridor runs along the edge of the North Bay there and I’ve never seen it in full daylight before, so it was a treat.

As we approached Davis, the sky pinked and the sun slanted prettily over the green fields. I rode around downtown Davis for a while as it got dark (sporting my new MiNewt light so I could actually see — amazing). It’s a pretty town, lots of trees and big houses, perfect for just tooling around going nowhere and enjoying it.

Today Mike and I went on another long-journey adventure: a ride over to Winters for lunch. It’s a 28-mile roundtrip, so neither long nor short by ride standards (mine anyway), but certainly longer than you would usually take just to have lunch. But the ride was part of the point, which is my point: when you ride, the journey is fun too.

It’s an interesting area to ride in, very different from the Bay Area. Out in the farmlands, you wouldn’t know you’re in California except that when you look west, you see mountains — that, and the fact that it’s in the 70s in November! But the farmland is amazingly like every other farm landscape I’ve ever seen, except flatter than some. Green, brown, and tan fields, distant lines of trees and small buildings.

It’s very, very flat, and so windy that it’s almost like having hills, though today was not as windy as the last time we went riding. Also, no tomatoes to avoid, but plenty of cracks in the asphalt. Does anyone know why asphalt cracks horizontally in that weirdly regular way? Or why fruit trees are painted white in the middle of their trunks, but not at the thicker lower part? Such are the mysteries that arise while enjoying the journey.

The radio was on this morning in the shuttle, playing various things, including a traffic report. It was almost like it was calculated: 101-S is a complete mess in two different places, as is 237. Aren’t you glad you’ve been on the train?

But of course, on any given day, you might rather be on the road if there’s a Caltrain snafu. Still, just thinking of all the nightmarish traffic I regularly miss was a reminder of why I prefer a cycling/transit commute.

On the other hand, I find Caltrain just mind-boggling sometimes. Recently, they decided to change the shuttle schedule for the shuttle I take. I discovered the shuttle back some months ago and was thrilled to find that I could not bike and still take the fast trains. It used to connect to the limited train in the mornings and I would arrive at work around either 8:30 or 9:30, which was great because the bullet trains + bike got me to work at either 8:00 or 9:00, and the local train + walking around 9:15, so I could pretty much arrive at any time I chose, with intervals of 15-30 minutes. That’s about all I expect or need as far as tolerances. There was even a late shuttle run that would get me to work around 10 on the unusual occasion I can’t get in any earlier. In the evenings, it picked up at 5:15 or 6:15 and connected to the bullet and limited trains that got me home around 6 or 7 (usually the latter). Perfect.

Well, nothing is perfect for everyone (the bullet people used to wait quite a while for the shuttle to leave, for example), but the change was just stunningly bad. Suddenly the shuttle only connected to the morning (crowded, slow) local train, despite the fact that the bullet comes in only a few minutes later. (Which, additionally, would push more people onto the bullets’ crowded bike cars, since they no longer had the shuttle option.) In the evenings, the convenient pickup times had changed to inconvenient 5:45 and 6:45, the latter completely killing the time advantage for the last shuttle in the evening, and only connected to local trains also.

They’ve now retooled the schedule again — to their credit, they have fixed the morning and it makes complete sense now. It meets the local and bullet trains, albeit not the limited, and most people who take it get to work around 9. Cool. This is awesome. (Why not do this in the first place?!)

But the afternoon schedule is still bizarre and, to my view, stupid. The pickup times have moved ten minutes earlier so that allegedly the shuttle meets the limited trains, at least. However, the leeway is one minute. You need at least five minutes of leeway in case the shuttle is late, and/or to cross the platform, buy or validate a ticket, etc. Plus, they are now claiming to meet the bullet trains, even though they really are not doing so, because you would have to wait almost an hour for a northbound bullet. (Most people who take these shuttles are going northbound in the evenings, in my experience. It looks like the schedule does serve the southbound trains a bit better, but considering a southbound bullet saves you a ten minutes, compared to a northbound one which saves you about twice that, and serves fewer people, I can’t see that this is a huge benefit.)

One of the biggest things that bothers me about how this has occurred, which is completely typical for Caltrain, is that they don’t seem to have actually thought the changes through from the perspective of the users, or communicated to the users aside from announcing the new schedule, or asked for feedback, or anything. (I think a lot of people have called or written them to complain, though. I certainly did.) The complete illogic isn’t necessarily typical, but the fact that they’ve now gone through three schedules (one proposed, which I guess was so bad they just abandoned it and delayed the change by a week, and two actual) and the schedule still seems somewhat stupid, doesn’t really give me a lot of confidence that they thought about it, not just from a user perspective, but honestly, at all. It’s been so bad that even the drivers noticed it and started surveying people and collecting comments. I mean, really. Good for them, but what went wrong here that this was, and is, so messed up?

My experiences with transit and cycling in Toronto were almost uniformly overwhelmingly positive. If only it wasn’t so cold there, I’d totally want to live there.

When I first arrived, I got a GO bus and then the TTC subway into downtown Toronto. This had two complications. One, GO and TTC are different systems, so I had to pay for both. But the total was only about CDN$8, so it was still astoundingly cheap for an airport-to-downtown option. Two, the GO bus that I got on went to a station on the other side of the U-shaped line (Yonge/University/Spadina) than the part of the U I wanted to be on, but that was simply fixed by briefly transferring to the Bloor-Danforth line to cut off the bottom of the U. (On the way back I did what I should have done in the first place: take the Bloor-Danforth line to Kipling and the 192 Airport Rocket to Pearson, which costs only CDN$2.75 and is a TTC-only journey. The Airport Rocket has 10-minute frequency during the afternoons — pretty great.)

The TTC is kind of expensive on a per-journey basis, CDN$2.75 per journey, but if you’re taking a long journey it’s quite reasonable, and you can buy at a discount if you get a lot of tokens at once. Transfers between lines are allowed, though you have to remember to pick one up if you get on the subway, and they’re rather finicky about where you can use them — you can’t use them at the station where you got them, and you can’t use them at a station that isn’t a direct transfer between one line and another (though it wasn’t evident to me how closely this was enforced). The one time I forgot to pick one up at my origin, I remembered to get it at my first subway transfer, so that was okay.

It’s relatively quick and pleasant, although crowded (it sometimes required a lot of “excuse me, I need to get out”s). The subway has a minimum frequency of 4-5 minutes between trains, so you’re never waiting long, and I had good experiences with my attempts to find buses and streetcars and get help from their drivers. They could use better signs at stops about routes and timing, but many stops do have the necessary information.

I did quite a lot of walking as well, and found that a nice way to get around, even going into downtown, though it did take longer than the subway. But most of my time not spent on TTC transit was spent cycling around. It was an adventure for me because I was equipped only with a minimal map of the downtown area, and didn’t have a Toronto bike map (allegedly you can pick them up at various places but I didn’t try very hard and didn’t see anything obvious) so I was mostly going on faith and some helpful directions from the owner of my borrowed bike, Crazy Biker Chick. The downtown streets are narrow and often have marginal pavement quality. There are some bike lanes, but not a lot, and some designated routes, but from what I could tell people rode their bikes almost everywhere anyway. Streetcar tracks were frequent and nerve-wracking, and in several cases I put my box-turn practice to good use in order to avoid bad left turns over streetcar tracks.

The most impressive thing was that there were bike racks absolutely everywhere, every 10-30 feet on pretty much every downtown street. Mostly they were just a post with a circle through it that could hold two bikes, about as simple as you can get but very functional. I saw tons of utility/city/hybrid-type bikes, and very few road bikes, while I was there, showing that people are choosing practical options for their environment. I enjoyed riding a very upright bike (a Raleigh Twenty that looks much like the picture at the link — evidently a classic and much-loved folding bike). Most were equipped with a rack or basket of some kind.

I found that the majority of cars were quite polite. A few people passed too close, but by and large I felt that my head was safer unhelmeted in Toronto (I didn’t bring my helmet or any other protective gear) than helmeted here. There were a few cases in which construction and other adverse circumstances made me uncomfortable enough to temporarily decamp to the sidewalk. Shock horror! I think time in Toronto has largely cured me of my default sidewalk anger (one of my 101 goals!), though I still am annoyed by people who ride recklessly on the sidewalk or ride on it where conditions are not very good (too narrow — the sidewalks in downtown Toronto are very wide). I particularly enjoyed my ride on Toronto Island. I took the ferry to Ward’s Island, and rode around and back, enjoying myself in the park and taking pictures, and on my last day there, I was able to see many more things in one day than I could have managed without a bike, so it was not only fun but extremely useful.

One of the things I did on my last day was visit Urbane Cyclist, a wonderful bike shop focused on commuting cycles at 180 John Street, just north of Queen, in downtown. The shop was full of fascinating things. There were urban, folding, and recumbent, and cargo bicycles — including a bakfiets!!! Unlike most shops, rows of shiny new identical high-end road bikes were not the featured item. Instead, the rest of the shop was filled with racks, panniers, mirrors, gloves, jackets, and other useful items. There was a parts section in the back. I picked up a set of road bike bar-end mirrors and a copy of Momentum as well. What a great shop.

Hang on for part 2, about what I actually did between all my subway and bike rides…

I have quite a bit to say about Canada, but just as a quick followup to my last post, gas was indeed very expensive. I was lucky enough to be able to borrow a car from my relatives, but my side trip of 194 km (120 mi) one way (so 240 miles total) cost CDN$73.30 in gas (51.077 L @ CDN$1.435/L), plus the CDN$60.06 (40.445 L at $1.485/L) of gas that I put into the tank to leave it more or less full for my relatives (the tank didn’t start out full, so I had to fill up twice).
[My bank indicates I was charged US$72.71 for the CDN$73.30. The other I paid in cash.]

Interestingly, Google Maps is completely convinced that the way I went — Hwy 401 to CR-73 (Elgin Road) — isn’t the best way, but my relatives all insisted that it was the best way. The distance and time given are identical for the route Google suggests and the route that was recommended to me (though the one I actually took, which was given as a slightly simpler alternative, is 2 miles and 3 minutes longer), and doesn’t involve going through downtown Toronto just after the rush hour (something that is indeed the nightmare you might imagine, as I discovered the next day on bike, but on bike it’s not a big deal because you can’t be going that fast anyway). It seems like a no-brainer to me.

That was the only time I was in a car for the entire trip, except for a brief drive with my aunt and uncle to dinner (I took buses to and from the airport). I’m pretty sure we could have gotten to the place we wanted to go faster on the TTC subway than driving at that time, too. I was very impressed by the TTC, but I’ll leave that discourse for another entry, along with my joy at visiting Urbane Cyclist.

I sometimes don’t understand 511. Or rather, I understand, but I just disagree.

There are three trips that I looked at for getting where I was going tonight. The one I actually wanted was the third one. The other two are marginally shorter (by 2-3 minutes) and in one case quite a bit more complicated, involving more than one transfer. The other one is probably about the same but it involves dealing with a station and bus that I’m not as familiar with and which are a bit more sketchy. I know 511 doesn’t know that I’m less familiar, but I still think the trip I picked (Caltrain to 4th and King, N-Judah to Duboce & Church) is the easiest one, and the least sketchy. The fact that it’s three minutes longer really matters not at all to me. Similarly, the return trip tried a multi-transfer trip first before giving me the N option.

In my opinion, transfers should definitely be weighted more heavily as a negative. If there’s something I hate about transit, it’s transferring when the connections aren’t well-defined and familiar, and all the attendant worry it brings. Give me the simple option that takes two minutes longer, please.

Oh, and did I forget to mention that it said that the 6:37 Caltrain is the last one of the day, and then promptly displayed a schedule showing many more? Yeah, I really don’t know what that’s about.

Courtesy the brilliant minds on the SVBC listserv and especially Margaret Okuzumi, ED of the Bay Rail Alliance and a very nice and friendly person:

Caltrain Bike Tips

Caltrain will tell you the bike rules, but those of us who use it every day will tell you how to do better than the rules and be a courteous bike commuter when using the train as part of your commute.

One thing we missed: don’t obstruct pedestrians getting on or off the train. Caltrain says pedestrians have the right to board and exit first. Try not to get in the way of a pedestrian or contact one with your bike — it could end in reprimand, anger, or injury. Sometimes simultaneous bike/ped boarding and deboarding is permitted by the conductors. If the stairs are divided unevenly, it’s bikes through the wide side unless you’re experienced and have a skinny bike, but if the wide side is on the south (pedestrian) side of the car, the pedestrians get to go first.

I enjoyed MetroRiderLA’s series of posts on transit in the Bay Area.

My most-used system: Caltrain

Best line:

The January 17 journey on Train 362 was very fast.
Then again, this trip didn’t cover anything south of Millbrae. Had
there been more time, this 10-part miniseries would have been a Greek
epic, with the transit odyssey including entries on the Santa Clara
Valley Transportation Authority’s bus and barren light rail and the
ruins of the once vast samTrans duchy. Any transit agency rebellious
enough to begin its name without capitalization is worth a write-up.

The system I hate to love: BART

This is a really excellent analysis of the pros and cons of BART. A few excerpts:

BART focuses its primary trunk service on San Francisco, with it
forming the head of a squid. The four endpoints on the east side of
the Tube form its tentacles, with a secondary trunk formed through
Oakland….

In the East Bay, this squid service also took on the characteristics
of a gorilla. It was very burdensome to maintain both San Francisco-
like train and bus service. BART had something that AC Transit
didn’t: funding primacy.

When counties buy in to BART by joining the district, they take on
the responsibilities of funding both their construction and and
operations within their jurisdictions. This solved the problem of
the who’s-subsidizing-whom issue, but there was always a threat of a
county chiseling its obligation. So the BART service obligations were
the first to be paid. It sounded like a fiscally upright arrangement.

The burden would then fall on bus riders. Since BART only had to
be concerned with its trains and would get first dibs on money, it
didn’t have to worry about local bus service. AC Transit bore the
brunt of service cuts, even though there was very heavy demand for
local East Bay bus service….

The Bay Area’s biggest loser has to be samTrans. San Mateo County bet
it all on a massive BART extension and watched it backfire bad. San
Mateo opted out of being a charter member of the BART district, but
it still got service as far as Daly City, on the northern edge of the
county line, and then Colma, the city where the dead outnumber the
living. The line kept creeping southward, going in as far as Millbrae
and San Francisco International Airport. The county paid for these
extensions by pawning samTrans service. The massive service expansion
southward proved to be a colossal failure. Airport ridership had been
abysmal, plus BART was largely duplicating the service of the more
culturally ingrained Caltrain commuter rail service. The saddest part
of all: samTrans lost more bus riders than BART gained rail riders.

Now the squid-gorilla is coming after Santa Clara County, with a
long-term vision of forming a ring around the Bay. The Valley
Transportation Authority is grappling with paying for an excessively
expensive BART extension, all while being infamous for having an
extensive but unproductive light rail network. It also already has
service along both sides of the bay by the more antiquated technology
known as conventional rail. BART would be astronomically expensive,
redundant and if light rail has been any indication … Santa Clara
County should know what the First Rule of Holes is.

Just yesterday I was reading an editorial that used San Mateo County BART as a success story. <game show eeeeennnnnnnt>

I haven’t read the whole series but I suspect it’s worth reading.

In the meantime, tonight I’m off to Sunnyvale City Hall to tell the City Council that that all road users deserve safe accommodation.

More later: I’m planning a letter to the Menlo Park City Council telling them I think they have their heads in the sand (or somewhere else, perhaps) if they really think opposing high-speed rail on the Peninsula is a good plan.

This is super cool.

Type in “{City} Caltrain” in Google Maps where X is a city name with a Caltrain station and you get a map with a pic of the station, indications of the time of next 6 trains, their type (Bullet, Limited, Local), and their final destination (SF, SJ, Tamien, or Gilroy). Pretty goshdarn awesome in a world that needs more awesomeness.

Some of the non-city names work too, like 22nd St or San Antonio, but others don’t, like California Ave and Tamien, which do bring up the station location and snapshot but only bring up bus and light rail info, respectively. Still awesome!