Wednesday, 3 June 2015

Safe cycle priority road crossings

I've covered several types of road crossing for cyclists in the past. Those with traffic lights, where cyclists have to wait for motorists but can stop in the middle of the road, those where there is equal priority between cyclists and motorists. Sometimes it's possible to give cyclist priority over roads when cycle-paths and roads cross but this can only be safely achieved if certain conditions are met. It is not enough simply to put up a give-way (yield) sign and expect that drivers will obey it.


Driver behaviour is more effectively controlled by road layout than by signs or speed limits. In order for it to be safe to give cyclists priority at a crossing, the speed of cars on the road needs to be controlled and traffic volumes need to be low. The junction needs to be designed such that it gives obvious visual priority to cyclists, and sight lines need to be good enough that drivers and cyclists can see each other and respond accordingly. This is not the same concept as "making eye contact". If people driving and cycling are surprised by the other party because they cannot see them in time then they are less likely to be able to respond safely.

First example in the video. Cycle priority crossing of a minor road. 30 km/h speed limit on the road, raised table starts 20 m and 14 m away from the crossing. Bend in road naturally slows cars. The cycle-path is three metres wide and runs at a distance of six metres from the parallel road.
Second example. This road has a 30 km/h speed limit, but it is a much busier road than the other two, providing a route by car to local shops and other facilities. Raised table starts 5 m and 12.6 m from the cycle crossing. Bend in road naturally slows cars. Cycle-path is 3.5 m wide and runs perpendicular to the road.

Third example. The raised table almost doesn't exist in this case and there is no bend in the road so drivers pass over this crossing at far higher speeds than the other two. Note how drivers may not be able to see cyclists coming from North or South until they are close to the crossing due to being obscured by buildings and vegetation and then there is a chance that a driver will misinterpret the intentions of a cyclist so not slow down for them. Note also how the curves on cycle-paths, especially North of the crossing, are far less helpful for cyclists than the other two examples. Cycle-path is 3 m wide and at the point of the turn it's just 3 m from the parallel road.
While the third example is the one which I believe is least satisfactory (see the video for why), collisions between cars and bikes are only recorded as having happened at the second example. There is a rational explanation for this. The second example is located adjacent to the local facilities of a suburb (shops / doctor / health / church) and this results in considerably more cycle and car traffic than the other two which located within residential streets. Three collisions with cyclists occurred over the 2007-2012 period at the second example, one of which caused an injury.

Curve radii and approach visibility
The recommendation of the CROW Design Manual for Bicycle Traffic for curve radii is particularly relevant to cycle priority crossings. The manual says that on curves with below 5 m radius, "cycling speed drops below 12 km/h and the cyclist has to work hard to remain upright" and suggests appropriate curve radii as follows:

  1. cycle connections that form part of the basic network should have a radius of greater than 10 m, geared to a design speed of 20 km/h;
  2. cycle routes and main cycle routes should have a radius of greater than 20 m, geared to a design speed of 30 km/h
Note that this refers to cycle-paths having a design speed of 30 km/h. Cycle facilities should not be designed to slow cyclists, but to enable efficient cycling. The first two examples above conform to this recommendation, while the third, especially when approached from the east, does not. This causes a problem for cyclists and motorists.
CROW recommended visibility at crossings by road width (crossing distance) and speed.
The requirement for approach visibility should also be noted. Take into account that these speeds are 85th percentile speeds in actual use, not merely the posted speed limit, and that the required sight lines more than double in length for any crossing of a 50 km/h road vs. a 30 km/h road. Also note that wide roads require more visibility than narrow roads because crossing times are longer.

All the roads shown in the above examples are under 7 m in width and in all those cases there is a 30 km/h speed limit so sight lines of about 50 m in length are required. All three examples include additional measures to control speed. In the first example, the posted speed limit and additional measures are adequate for a 50 m sight line. In the second example they are marginal (though helped enormously by the curve in the cycle-path which places cyclists in a more visible position and the curve in the road which slows drivers). The third example does not meet the requirements because the speed of cars is excessive and the sight-lines are not long enough.

Related: Note that it has been understood for many years in the Netherlands that posting a lower speed limit is not enough to ensure lower speeds.

Difficult to retrofit
It is very difficult to successfully retrofit crossings of this type because existing streets are often too straight, existing paths often not visible enough. While cycle priority crossings are fairly unusual in the Netherlands, retro-fitted cycle priority crossings are even more rare. All the examples of priority junctions in Assen were designed as integral parts of the road design. Those used as examples in the video and images above date from when those parts of Assen were designed and built in the late 1970s through to the 1980s.

Cycle priority is not the same as pedestrian priority
People sometimes ask why cyclists are not given permission to cross with priority on all pedestrian priority (zebra) crossings. There are good reasons why this should not be so. In many locations, it would be difficult for a cyclist to be The risk of a cyclist emerging quickly from behind a building or because there are inadequate sight lines. Cyclists are much faster than pedestrians and they require space in order to make a turn.

This crossing of a busy road gives priority for pedestrians over both cyclists and drivers. but there is no place within this layout to provide a safe priority cycle crossing. In any case, any cycle crossing would be better slightly further North on desire lines.

This location has a parallel cycle and pedestrian crossing. Pedestrians have priority while cyclists do not. This is a relatively busy through route for cars with a 50 km/h speed limit. As a result a cyclist emerging at speed from the side roads may appear in front of a driver before the driver has had an adequate chance to response and therefore there is too high a chance that a driver won't stop in time. But they have much more time to react to a pedestrian due to the slower speed of pedestrians.

In this location cyclists have priority over side road crossings which are parallel with the main road. These roads have 30 km/h speed limits and speeds are further reduced by the junction, the small corner radii and the raised tables. However only pedestrians have been priority over the 50 km/h main road.


At a very large busy junction, this example joining the 70 km/h ring road to a 50 km/h main route out of the city, neither cyclists nor pedestrians are given priority over motor traffic in any direction. On a road like this with many lanes of traffic, higher speeds and much to look out for it would be dangerous to give priority to cyclists or pedestrians. This junction is too large and busy to be a "protected intersection". While it could have seen implementation of a simultaneous green junction, instead there is a more conventional traffic light junction here next to which cycle path green lights are synchronized with motor vehicle red lights where conflicts would otherwise occur. Priority can be given for cyclists and pedestrians by other means. In other locations in Assen this is done by use of tunnels and very quick reacting light controlled crossings. Two cyclists were injured here. One due to a single sided collision with street furniture, the other due to ignoring a red light.

Hook turns
A possible solution which people sometimes think of to the problem of turning across traffic is the hook turn. We have precisely one example of this in Assen. It's a relic from the past which has somehow survived on a quiet residential street and it's shown in the photo below. Note that the hook starts with a cycle-path in the top right hand corner of the image and continues more than 60 metres to the junction which it serves in order that it could provide a gradual enough transition for cyclists. The crossing is then assisted by a large raised table. Despite all of this, it's actually quite awkward to use. It perhaps made a little more sense decades ago when this was a busier route, but it certainly doesn't help in this situation now. I don't recommend this type of infrastructure.
A generously proportioned 60 metre long hook turn assisted by a raised table. But it's still awkward to use.
"Visual priority" The Alternative Department of Transport blog recently coined the phrase "visual priority" to refer to where priority at a crossing is indicated by the design of the street and not merely by signs. The red surfacing continuing through each of the junctions shown in the video at the top of this blog post is a good example. I like this term, it's concise and obvious, so I have used it too. Most examples of crossings in the Netherlands benefit from good visual priority. Of course, good visual priority is only one factor. In itself it is no guarantee of success. As you will see from the video, the third example of a junction with a short raised table which coincides only with the crossing itself is not successful at slowing cars even though the visual priority is good. Junctions must also encourage safe behaviour by other means, such as use of bends on roads and level changes using a raised tables to slow drivers, bends on cycle-paths to improve sight lines, and we must of course realise that there is no one-size-fits-all solution. The majority of junctions are not suitable for a cycle priority treatment for reasons of sight-line or traffic speeds and volumes.

Real examples in real-life usage
It's not possible to completely understand infrastructure like this from reading blog posts and watching youtube videos. On our study tours we demonstrate real life examples.

1 comment:

  1. I came up with a pair of blog posts that describe my proposal for a high quality cycle route from one school nearby to me to another school and using a near completely unraveled route from motor vehicles, though I include 4 priority crossings in the design, using the technique of raised table, visual priority, fairly sharp S curves in the road on some crossings and full bends on the other, all crossings taking place in a 30 km/h road. I think they are fairly good examples of how certain retrofits are possible. http://cyclinginedmontonfromtheeyesofateen.blogspot.ca/2016/02/a-complete-cycle-route-proposal-part-1.html and http://cyclinginedmontonfromtheeyesofateen.blogspot.ca/2016/02/a-complete-cycle-route-proposal-part-2.html. I also designed the rest of the route to correspond to Sustainable Safety, including separation of pedestrians and cyclists which much of the world misses.

    ReplyDelete