The VeloBusDriver

[ UPDATE - 2/2/2012: Apparently there are indeed holes in the wireless network that are being addressed.  Several new access points are in the permit process and due to be completed within the next couple of months.  This should fix these issues as well as several signal priority issues I have yet to blog about but encounter on a regular basis - In short, they're working on it. ]

It’s been almost 4 month since the RapidRide B-Line started operating. There have been many hiccups along the way but in general, the line is working well. I’m pleased with it as an operator and also as an occasional rider.  I rarely ever took the 253 but often take the B-Line since it provides frequent service to my favorite food court at Crossroads mall.  (Although figuring out how to schedule transfers back home is still difficult)  For the last days of this shakeup, I’ll be writing up all of the remaining loose ends I know about here and tagging them as “B Line Loose Ends” – I’ll be working the B-Line next shakeup as well and will keep all of these posts up to date with any changes.

First up are two B-Line stations that have never been fully functional.  Stop #73240 (148th Ave NE & NE 51st Street) and Stop #73108 (148th Ave NE & NE 87th Street).  Both of these southbound stops have deactivated ORCA readers that are hooded and Real-Time Information System signs that are always blank. I believe these stops are located within gaps in the wireless network that the B-Line operates on. I was told by a Twitter follower that a fix was in the works but that was months ago and I’ve heard no updates since.  If anybody has more detail on this issue feel free to comment here. Neither of these stops are terribly busy, at least during the morning rush hour when I’m driving, so I’d understand if they have been pushed down on the priority list.

I’ve been using RapidRide B, in conjunction with the 249, to travel to several locations I would normally drive to.  Each time I travel, I plan my trip using various transit planning services including Google maps, Bing, and Metro’s trip planner. So far, all services have worked well with each giving a simple trip recommendation involving a single transfer.  My 249 shows up at Bellevue Transit Center where I walk over to a waiting RapidRide B coach which usually leaves within a few minutes.  Total travel time from my front door to my favorite food court at Crossroads Shopping Center is usually about 30 minutes.

Getting home, however, has been more difficult to plan.  When using Google or Bing maps, I cannot get a trip recommendation that involves RapidRide.  All recommendations involve long walks or transfers to other numbered routes with fixed schedules and typically travel a much longer, and sometimes more complicated route.  On some trips Metro’s trip planner gives the same results but on others I can get a route recommendation with RapidRide, if I tweak the travel times a bit.

An example will illustrate.  Use your favorite transit planning service to get a trip recommendation for the following locations and times:

Start point: 2000 104th Ave SE (Add Bellevue, WA if you need to – Trip planner doesn’t need / want this)
End point: 15600 NE 8th
Time: 5:00pm

The result should be a trip on the 249 transferring to RapidRide B.  However, if you plan the reverse trip you’ll get many different route recommendations, most of which do not include RapidRide B.  On Metro’s trip planner I get a trip on the 245 transferring to the 249 in Overlake.  However, if I switch the departure time to 5:20pm I get trip on RapidRide B transferring to the same 249 recommended above but closer to my destination.

I’ve also seen this problem occur with other trips that involve a transfer at Bellevue Transit Center so I’m guessing there is something wrong with the GTFS data for RapidRide B at that point.  I’m going to stop digging here, lest I “go down the rabbit hole” as my wife likes to say.  Besides, it’s time for bed – I’ve got to get up tomorrow to actually drive RapidRide.

If you are in the know, feel free to add comments or contact me on Twitter and I can work with you to investigate further.