😀🚲: "car supremacy is when you put a speed bump on the bikeway but not the street…" - Urbanists.Social

This appears to be a case of "best practices" that's perhaps so good it's excessive when put together. I'll try to explain as succinctly as I can.

As you can see in these two examples, having the pedestrian crosswalk to a bus stop raised where it crosses the bike lane is a standard design. The floating bus island reduces bus-bike conflict and speeds up bus time by removing the need to merge in and out of the travel lane. Meanwhile it also preserves the protected bike lane and, depending on design, gives folks waiting for the bus a nice space not immediately next to automotive traffic to sit/stand. However this design introduces potential pedestrian-bike conflict, especially in urban contexts where road space is cramped, visibility is poor, and/or people exiting the bus or moving from the sidewalk to the bus island do not have a lot of space and may unexpectedly (from the perspective of bike riders) enter the bike lane. Rushing to catch a bus that's about to depart especially can cause people to have blinders and suddenly enter into the bike lane without looking because they're too focused on the bus. For accessibility reasons it's best to have the path across the bike lane raised to sidewalk level but only for the duration of the crossing (otherwise you end up with people walking or even standing around waiting in the bike lane).

Finally there's the fragile political alignment of people on foot and people on bicycles; these two groups should be allies in the fight against car dominance but our road and even recreational systems have often pitted the two against each other: it's very common to hear pedestrians especially complain about near-misses with bicycles, particularly on shared paths ("I was walking my dog and this speeding cyclist appeared out of nowhere and almost ran us over!" "I was riding my bike and this inattentive pedestrian's dog abruptly jumped into my path and I had to swerve to avoid them both!"). Reducing conflict between these two groups of road users to keep them allied is critical for political reasons in many places, and this means slowing cycling speed near the conflict zone (via the speed bump) while also keeping the conflict zone reduced to just one or maybe two specific crossing areas (indicated by the elevated crossing).

All the above seems like overkill in the example cited above because these "best practices" were designed for cramped urban environments, such as major automotive corridors with multiple lanes through city centers that recently had a lane or two converted to bike/bus/ped infrastructure via a major "road diet" or bus enhancement project. But here there's a huge bus island, an extra wide bike lane (because it's for two-way use), great visibility, the waiting area is on the bus island rather than the sidewalk, etc. so while these best practices probably are still effective, they aren't as necessary for reducing bike-ped conflict as in other contexts. As to why there's no speed bump in the automotive lanes, the bus island itself may provide sufficient traffic calming by breaking up the monotony of the roadway, and most importantly, a speed bump would greatly reduce comfort of bus riders. Speed bumps are not meant as "punishment" to one form of transportation or another; they're a tool that's only rolled out to solve a specific issue.

I hope this helps explain why this spot is designed as it is, and why this is a poor example of "unfair" road design.