Heading up Queen Charlotte Street from Queens Square, we first get to see a near-collision between a deliveroo rider and a small child running out from the side. It's possible to conclude the rider doesn't have a small child, or they'd have known that trying to control one is futile: asking the parent to do so even more so. "Fuck off you wanker" is the correct response here.
Then it's left onto the half-of-Baldwin Street path. A lot of people accuse Ferguson of following some anti-car, pro bicycle policy. Well, this is the main legacy of his of his reign from a cycling perspective. London also had a mayor prepared to sacrifice the country in his ambition to become PM.
The Baldwin Street path starts of as a reference example of what modern thinking on segregated cycle routes should be: not just a safe separation from cars, but a clearly delineated separation from people on foot, the bikes not having to weave between people -better for all.
It then switches to being a reference example of what you expect to see in Bristol: the bike path suddenly gives up in order to have some car parking, before ending up at some lights. Here the other tax-dodger decides not to stop for the lights, so proving that we do show such events when they happen. Its notable that actually he had less to worry about across the junction than our reporter, what with the past-the-lights taxi and the van swerving over to pick up a mate.
On to Baldwin Street, and what do we see?
- An explicitly cut out path to the lights +10
- Some lights: 0
- No clear indication of which bits of the lights your bike should go to: -10
- Lights green when the road going straight on: +10
- A central plaza where there is no indication whatsoever of where you are meant to go to cycle across to the other side; -10
- Another set of lights with no clear cues as to which side a bike should be on: -10
- The lights now red, so adding a delay of ten seconds: -5
- Roadworks in the middle so not actually proving any way to cycle further: -20
- Some pedestrian lights to wait for and use: +5
- Signs of a bike path possibly appearing by the hippodrome: +10
- The bike path not being ready to use: -5
- The need to execute (badly) a bunny-hop to get your bike up the kerb *where the road to Colston-the-Slaver-Hill used to be*-10
- Another bit of utterly undelineated bike path: -10
- The utterly undelinated bike path now abandoning you to a road where nobody expects bikes to come from: -20
This was done by someone who wants "an urban realm" design, despite the fact they've just added a new road and bus line through the heart of the area, someone who doesn't actually want bikes there and finds the idea of having a functional way to get across by bike unsightly. It is, to use a technical term, "bollocks".
the worst part is probably the approach to Colston Hill. Until recently, there was a road entrance there. All they had to add was a sign and some build out to narrow the entrance. Everything else was in place. Except they spent money on adding a new pavement and some tiles, and in doing so removed the option of a safe exit. Now all private vehicles on that road will be entering or exiting Pipe Lane: a road where the road signage has been changed so that Colston Street has lost the right of way it used to have. This is now dangerous.