Mitcham's Corner Development Framework SPD

Search representations

Results for CAMCYCLE (Cambridge Cycling Campaign) search

New search New search

Object

Mitcham's Corner Development Framework SPD

Figure 27: Movement proposals for Mitcham's Corner

Representation ID: 31320

Received: 09/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

I think the plan is insufficiently bold.
As such its has most of the draw back associated with change (cost, disruption, etc) without actually achieving a great benefit for the area.
I think the most appropriate solution would be the demolition of some of the houses on Chesterton Road between Milton Road and Victoria Avenue. This would allow a simple, efficient (especially in space) cross-roads to be created, and free up a massive amount of new space.

Object

Mitcham's Corner Development Framework SPD

Figures 31 to 33: Transport examples

Representation ID: 31321

Received: 09/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

The examples given have no provision for bikes, and reply on cars to behave well, rather than giving pedestrians explicit priority.

Support

Mitcham's Corner Development Framework SPD

Figures 34 to 43: Examples of public space

Representation ID: 31322

Received: 09/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

This would be great step forward for the area. It is not currently an area where anyone stays for longer than is necessary.

Support

Mitcham's Corner Development Framework SPD

4.2.10

Representation ID: 31323

Received: 09/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

I fully agree. In fact I would go further and require new buildings to meet the PassiveHouse standards for energy efficiency and sustainability.

Object

Mitcham's Corner Development Framework SPD

3.5.1

Representation ID: 31324

Received: 09/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

I think this is missing a key design principle
Provide Dedicated space for cycling (cycle tracks) separated from pedestrians and cars.
This should be direct and wide, with simple routes through the space.
Some of the new cycle tracks in London (along the embankment for example) have good examples of this type of design. It should be included here.

Support

Mitcham's Corner Development Framework SPD

3.5.4

Representation ID: 31325

Received: 09/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

Agreed.
This should be treated as a place first, and highway later

Support

Mitcham's Corner Development Framework SPD

4.2.20

Representation ID: 31326

Received: 09/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

The area needs more well thought out cycle parking as part of making it a destination rather than area to passed through.
For example the Boathouse and Portlands arms have the combined total of 0 bike parking spaces at the moment!
Hard to think of a business that is less suited to arriving by car.

Support

Mitcham's Corner Development Framework SPD

Figure 5: Vision and strategic objectives

Representation ID: 31472

Received: 17/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

We welcome the SPD, and feel the document correctly identifies the key issues of the Mitcham's Corner Area. We look forward to the possibility of positive changes being brought about to improve the attractiveness, liveability and safety of the area.

As the SPD identifies, the key problem facing the area is that currently the area is designed with a sole focus on maximizing the throughput of vehicle traffic.

Object

Mitcham's Corner Development Framework SPD

Figure 27: Movement proposals for Mitcham's Corner

Representation ID: 31473

Received: 17/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

We welcome the proposal for removing the gyratory, and returning many of the roads to two-way operation. However we have strong concerns about the solution identified.

The new layout being proposed is a double roundel. This would be similar to the double roundel at Lensfield Road and Trumpington Road. That junction is currently the most dangerous in the city for cyclists. We do not believe that creating another similar junction is the best way forward for the area. Ironically, the County Council is coming forward with proposals to remove the existing double roundel at Trumpington Road.

We believe that the best long-term solution for the area would be to purchase and demolish at least some of 133-155 Chesterton Road. This would allow the creation of a straightforward crossroads or roundabout joining Milton Road, Chesterton Road and Victoria Avenue, and a large new public space over part of the existing gyratory. We note that both student groups studying the junction a few years ago independently came to the same conclusion.
Shared Space

Object

Mitcham's Corner Development Framework SPD

Figures 31 to 33: Transport examples

Representation ID: 31474

Received: 17/10/2016

Respondent: CAMCYCLE (Cambridge Cycling Campaign)

Representation Summary:

The SPD points towards several recent schemes that have used so-called shared space principles to improve an area including Poynton in Cheshire and Frideswide Square in Oxford, but we believe that shared space is not appropriate for the through routes of Mitcham's Corner. Camcycle welcomes alterations that reduce traffic speeds, and improve the look and feel of the area. However we believe it is vital that these spaces include dedicated space for cycle tracks, pavements, and clear indications of pedestrian and cycle priority and crossing points.

We believe that true shared space only works when the number of people walking or cycling is equal to or higher than that of the cars. This will likely never be true for Mitcham's Corner, which is a through route in several directions, including for several bus routes.

For instructions on how to use the system and make comments, please see our help guide.