Donate using PayPal

Gallery: Busy shared-use paths

Some photos of shared use paths in S Cambridge busy with friends and families on a Sunday Afternoon

This gallery was created on Sunday, 7th June 2015

NCN11 With a 2m shared-use path both pedestrians and riders need to single out. Easy when you meet, not easy when you overtake

NCN11 2m wide shared-use. Parents (tandem) with small child. Not wide enough to meet others in safety

Link to Long Road from CGB path 2.75m wide path pedestrians naturally walk to one side, but riders singled

3m wide (kerb to kerb) underpass beneath Long Road. Pedestrians single out for rider who rang bell. Poor visibility an issue

CGB shared use path. 3m on a bend. Needs more width where visibility limited

CGB shared-use path. Regular use by people towing child trailers requires more than 3m especially where visibility is limited (Long Road underpass)

New Bit. Shared-use 1.6m path. When social walking there is little room for safe cycling

NCN 11 on 'New Bit' Shared-use 2.5 m. enough to ride two-a-breast if no others around

NCN11 shared-use 2.5m just enough room for two-abreast walking when you can see the oncoming rider

Shared-use NCN11 2.5m Caution needed if approaching walkers from the rear (they'd 'just' moved across as they thought they were spoiling my photo, and hadn't seen or heard the bikes)

Coe Fen. Shared-use 2.25m Family Group with mother 'protecting' youngest. What if they met another?

Coe Fen Shared-use 2.25m Family group meets walkers whilst passing others

Coe Fen NCN11 Shared-use. At 1.6m there is no room for cycles

Coe Fen NCN11 Shared-use. 1.6m You need to look behind you just to walk next to your child

Coe Fen. Shared-use 2.25m widening to 3.0m Cycles needed to single out

Coe Fen Shared-use 2.25m. need to single out not sociable. Can't even chat to child in rear seat

Coe Fen. Shared-use. 3.0m Still tight when two bikes pass and there is also a pedestrian

New Bit. NCN11 Shared-use. Family groups need space especially with young riders

We welcome your feedback, especially to report bugs or give us route feedback.

My comments relate to: *

Your comments: *
URL of page: *
How did you find out about CycleStreets?:
Your name:
Our ref: Please leave blank - anti-spam measure

* Items marked with an asterisk [*] are required fields and must be fully completed.