20 March 2015

The uncertainty principle

My last post was about how problematic uncertainty is in cycle infrastructure.  It's since occurred to me that the problem isn't uncertainty itself, but uncertainty for the more vulnerable.

Good cycle infra, as seen in Holland, Denmark, etc reduces uncertainty - cyclists have their own safe spaces, as do pedestrians and cars.  But even the Dutch have some spaces where uncertainty is permitted - such as the bike streets that identify cars as visitors, and make it clear that the space is intended for cyclists and pedestrians.  Likewise, streets with no centre line and bike lanes on either side - a UK can be seen here and a study by TfL here .   But crucially here, the uncertainty is on the part of the car drivers, as the least vulnerable users. 

Edinburgh is trialling this system on a road on the outskirts of the city.  It's not perfect - the road speed is too high, and the bike lanes are not going to be colored. But it does introduce uncertainty for the car driver, rather than the cyclist. 

By contrast, the paths leading to North Meadow Walk have given the uncertainty to the pedestrians, as discussed in my last blogpost, and as @fountainbridge shows in this mockup:  
https://www.flickr.com/photos/130059894@N04/16865206971/
Cyclists have lots of signs telling them what to do and how to behave, but pedestrians have nothing.  Anyone who knows about Scottish law will know that pedestrians have full rights to use both the paths marked in green and in pink, but the signals being sent to them say differently.  So uncertainty is created.  

This is the exact opposite of the basic principles discussed above -- the heavier, more dangerous form of transport should be made to feel like a 'guest', not the most vulnerable. 

Until we put this principle at the heart of our infrastructure, we're getting it wrong.  We'll continue to foster resentment and hostility between cyclists and pedestrians, and discourage the take-up of active travel that our policies claim to promote. 

14 March 2015

What's the point of 'infrastructure'?

I'd like to think that the point of infrastructure was to decrease conflict and increase safety of all road users, but especially the most vulnerable.  So, roads should be designed to enable pedestrians to cross safely and easily.  Too often this isn't the case and unnecessary barriers are put in their way  (as shown here and here).  

Sadly, this is too often the effect of cycle infrastructure too.  And this is frustrating because pedestrians' subjective safety matters too.  The two most common examples  are chicanes  and shared use pavements.  But Edinburgh seems to have invented some new and particularly baffling versions.  

'Normal' shared use has a pavement with some blue signs in the air, that most people don't see or understand.  But since shared use should only be used on wide pavements with relatively low footfall, its rarely a huge cause of problems (except misunderstandings, of which there are many). 

But the video above is from North Meadow Walk in Edinburgh - a much used commuter, jogging, dog-walking and leisure route. This is an intensively used path, where markings have been painted in such a way to suggest to pedestrians coming from the east that cyclists should be on the right hand side of the path and to pedestrians coming from the west that they should be on the left. Maybe.  It's not clear.  

Similar paint is used on the short cut-through path on the other side of the toucan crossing.  It's been raised many times as confusing. But instead of improving it, the Council has seen fit to replicate it.  On an even shorter length of path. 

What's the point to putting in 'infrastructure' (if we can call paint that), when it confuses users and creates conflict?