Grant from the Polden-Puckham Charitable Foundation

We are delighted to announce that Cyclescape has been successfully awarded a grant from the Polden-Puckham Charitable Foundation for the next phase of development on Cyclescape.

The grant covers £10,000 of development work this year, and £8,000 in 2015-16.

The Polden-Puckham Charitable Foundation (PPCF) is a grant-giving trust with Quaker family roots in the United Kingdom. It aims to contribute to the development of a just society based on a commitment to nonviolence and environmental sustainability.

poldenpuckham

Key things that we want to work on, which the funding will contribute towards, are:

  • Launching the automated planning applications integration - changes when datasource finalised (see previous blog post)
  • Show Google Street View at any location automatically
  • Membership management system for delegated groups
  • Ability to invite decision-makers and others into specific discussions
  • Enhancement of the Library system, which enables key resources to be shared nationally
  • Subscription on the basis of themes (e.g. cycle parking) rather than only defined areas
  • Private messaging system
  • Much better search
  • Deadline reminders
  • Show photos in nearby area automatically
  • ... and more.

You can see many of these within the list of outstanding issues in our public bug-tracker.

We are currently looking for a developer to work on Cyclescape using the funding from this grant - which is open-source code written in Ruby on Rails. Do get in touch if you may be interested.

New development mailing list and developer resources

We've set up a new mailing list for anyone interested in helping maintain and develop the Cyclescape code. Do join if you want to get involved, want to discuss the development of Cyclescape, or have any questions or ideas.

The list is public and open, and you can subscribe to the list.

We've also created a list of key developer resources via a new 'Help with the code' page on this blog.

We hope these will help get new developers involved. We're very happy to help give advice on getting you going - just post to the new list.

Early issues on Cyclescape seeing results

It's very pleasing to see that some of the earliest issues submitted to Cyclescape, and discussed heavily on the site, are now seeing real improvements on the ground as a result.

Several big issues first lodged on the site in around 2011-12, and with hundreds of postings on Cyclescape since to advance the issue, have seen major breakthroughs since.

This blog post features three issues from Cambridge, currently the most active group on Cyclescape.

For instance, there has long been a shortage of cycle parking at Cambridge station, and a new cycle park was proposed. Members have been campaigning and discussing the cycle park, and its design. Construction is about to begin.

Another great example is the problem of cycle parking in Cambridge city centre. Since a user posted this as an issue in February 2012, members have been discussing it using Cyclescape, and this pressure resulted in a project to allocate over 600 spaces in the area.

You can see some more photographs of the results of this successful Cyclescape-backed campaigning on our sister website, CycleStreets.

cyclestreets59766-size640

Here is one more issue from Cambridge - the need for space for cycling on key roads in Cambridge. Huntingdon Road is one such location, and local campaigning, using Cyclescape to enable the group's members to discuss proposals, is about to see the scheme built.

Obviously, cycle campaigning is a mixture of campaigner pressure, as well as agreement from the authorities. We hope that Cyclescape will increasingly be seen as the solution of choice to help facilitate the first of these.

Have a browse through more of the issues in Cambridge and beyond, and get involved!

Planning applications and their effect on cycling

Over the last few years since our beta went live, the over 1,000 issues logged on Cyclescape, and being discussed by members of the site, contain a wide range of concerns. It's interesting to see the kinds of issues that act as a barrier to greater cycling around the UK.

Common things include lack of cycle parking, dangerous roads, collision-prone junctions, missing links, scrutiny of new cycleway proposals, and new residential/commercial developments that will affect cycling.

The last of these examples - planning applications, are interesting as they often represent both dangers and opportunities for cycling.

For instance, a major new housing development could result in a lot of new traffic on an already congested roads. However, there could also be an opportunity, as councils are able to negotiate "planning gain", known as Section 106 agreements (or Community Infrastructure Levy), where public infrastructure nearby is improved - such as a new cycle route, cycle parking, or traffic calming measures.

However, it is crucial that cycle campaigners know about planning applications as soon as possible, to maximise the chances of pursuading the local council to negotiate Section 106 proposals, and to give more time to look through often lengthy and complex documents for potential problems. Planning application websites are often hard to use, fail to provide a proper map view, and in general are not orientated towards monitoring of cross-cutting concerns like cycling.

Discussing a planning application relies on someone actually knowing about a planning application (that might have effects on cycling) in the first place. Of course, Cyclescape enables people to add planning applications as an issue like any other. 

However, we think there is a better way - having planning applications automatically appear on the map as a potential issue. So we've been working on a way to automate this. Using data from Openly Local, we plan to add a new tab to the overview page, so that any member of the site can 'promote' a planning application that looks like it might be of interest to an issue automatically.

Here are some screenshots of the work in progress:

Listing of planning applications in an area

Accessing any link on this page, gives a button in the corner:

Convert to an issue

This creates a new issue page, but with all the details pre-filled in, so it can be quickly reviewed/adjusted and submitted in the usual way as with any issue:

planningclone

We think that automated listings of planning applications will be a powerful new feature of the site.

The motivation for this has come from Cambridge, which is a considerable growth area, and where the local cycling campaign spends a lot of time scrutinising planning applications. The vast majority of planning applications on the Cyclescape site are indeed from Cambridge. This work for Cambridge has been gratefully funded by Cambridge Sustainable City who awarded a grant for Cambridge Cyclescape.

If you're interested to help develop the code, any contributions would be very welcome, on the 'planning' branch. We now have completed the integration and user interface code, but are awaiting availability of the data, which will come from Openly Local.

Guide for new users

Now that various groups are using Cyclescape, and adding members, we've created a new Guide for new users.

The Guide gives an overview of Cyclescape, getting you set up, and some of the features that we have available.

Over time, we hope the need for the Guide will go away as we improve some of the remaining usability improvements, as programmer time and funding becomes available.

Guide for new users

logo‚Äč

Final report to GeoVation

We've submitted our Final report to GeoVation, which describes the work we've been able to undertake with this funding.

It outlines what we've been able to achieve to get Cyclescape as a working site, what remains to be done in advance of our national launch in October, and the challenges that we've faced and overcome.

Stay tuned for news shortly on the latest updates on development. We've been making steady progress with ticking off the remainining areas needing work to finish.

We would like to thank everyone involved in GeoVation for enabling this project to go ahead. We are excited to have been able to deliver it, and are very encouraged by its potential.

A screenshot from Cyclescape, showing the interface for adding an issue

What we’re working to finish

Cyclescape has been used now for three months by Cambridge Cycling Campaign as our test group. We added them even though we knew not everything was in place, as it was important to get good feedback on real campaigning usage, even though that has meant some confusion in the short-term.

Over 180 issues (cycling infrastructure problems) have been posted, over 250 discussion threads on these, containing over 2,000 messages.

We've also had meetings with CTC, Cyclenation, and London Cycling Campaign to show the site as it currently stands and talk through what's done and what's not, to see what they most need:

   
Meetings with London Cycling Campaign and Cyclenation / CTC

A lot of the work going on now is about tidying up and finishing off pieces of functionality, reorganising things a bit, and making things more flexible. The site isn't quite ready for wider usage, but things are falling into place.

These are the main things left now, not in any particular order, to ensure that the site will be a big step up for campaigners:

1) Settings: "What do I get told about?"

A key aspect of the site is to avoid the 'e-mail list syndrome' where everyone gets absolutely everything, which puts off people who don't have enormous amounts of time. Instead, users can outline places they want to hear about things.

a) Three months' usage of the site has clarified what the various settings should now be. This is now being finalised, as top-priority work. [Done]

b) We need a clearer route through to encourage people to set their preferences.

c) The ability to subscribe automatically to discussions based on keywords (e.g. 20mph zones) rather than purely map-based areas.


Users have found that the settings don't give them quite enough flexibility yet. The key addition about to be added is auto-subscribing, rather than just being notified.

2) User interface

Much functionality is now in place, but users are having trouble finding things. So:

a) The search box will be moved to a more accessible position and cover all types of data (issues, threads, library) [Done]

b) Reorganising the various listing screens.

c) Removing scrolling past previously-read replies. We're aiming to avoid pagination (which people don't like).

d) Tags (categories) just need an auto-complete so that 'cycle parking' comes up as soon as you start typing: p.. a...

e) Getting a more natural (and 'frictionless') connection between an issue (basically the container for discussions) and threads (the actual discussions). In general, starting a discussion on a completely new issue involves a bit too much friction, which we need to address.

f) General little bits of tidying up, improving the labelling and making the site as 'warm' as possible.


This shows three of a number of ways of viewing what's going on. There are more, and we are gaining a better insight into what users need to see to help them campaign.

3) E-mail integration

From the start, it has been a core principle that people can interact with Cyclescape via e-mail as well as the web, much like a Yahoo Group for instance.

a) At present, a discussion thread can't be started by e-mail. A key question is how to ensure this gets grouped with other discussions on a topic.

b) The ability to move an existing thead into a different issue.

c) Finishing off the work on attachments so they can be attached to an incoming e-mail.

4) The Library

The Library is a place for useful resources to be 'tagged' (categorised) so that Cyclescape can automatically suggest them in discussions. For instance, if a 20mph zone is being proposed, it makes sense for the key guidance on this to be handed to people 'on a plate'.

a) Adding to the library isn't a very smooth process at the moment. We intend to enable any reply to be 'promoted' to be a library item retrospectively.

b) More types of library item will make things a bit more flexible and improve how they appear in discussions.

c) Adding the category tags needs to be made more integrated.


The core Library functionality is there - it just needs a bit more development to ensure it's a genuinely useful campaigning resource.

5) Other features

a) A key need in Cambridge, for which we have grant funding from Cambridge Sustainable City: Getting planning applications landing on the map automatically, something we're very excited about. OpenlyLocal have been making good progress with developing the new PlanningAlerts. We've done some initial work to determine how this will work, interface-wise, to avoid lots of roof extension planning applications (etc.) appearing and cluttering things up.

b) There isn't a listing of My priorities, so there's currently no incentive to set this. Currently you can set this but it's not actually then used. [Done]

Stay tuned for news as these each get ticked off!

More features in place

Work is continuing apace with Cyclescape, with more features now in place as we work up to a wider release.

There are still quite a number of unfinished areas, but we're getting there. Andrew and (most recently) Andy have been busy adding more in place for us.

  • Deadline setting
  • Collision data
  • Per-thread attachments
  • Committee-only privacy setting
  • Popular issues

Read about these below:

Deadline setting:

Deadlines (or other dates) can now be set.

Our experience of cycle campaigning is that it's often easy to miss a consultation deadline or some other date, if there's a lot going on. By then, it's too late, and the opportunity to see improvements to cycling are missed.

The set dates are now listed in 'My Cyclescape', the user's main summary area. We'll be developing this interface further.

Collision data:

Collision data is now integrated, using a new data feed from CycleStreets, and linking through to their collision reports.

This feature has been developed for the Cambridge group, pushed forward because of the large number of planning applications in that area, for which collision data can often provide a useful context.

Development of this feature, and various underlying code pre-requisites, has been possible thanks to a grant from Cambridge Sustainable City, whose support has been invaluable.

This screenshot, for instance, shows the site of collisions in Mill Road, an area subject to continuing pressures on cyclists from lorries. Several planning applications in recent years would have benefitted from this data being available.

The finalised interface for collisions isn't quite in place yet - buttons for this will be added to finish it off.

Per-thread attachments:

Attachments can now be added to individual discussion threads. Previously the only way to add an attachment was to add it to the Library, which is always public.

Currently there is a slight limitation that, if e-mailing to the discussion thread (since you can reply to things via e-mail, not just via the website), attachments do not get through. We're working on this!

Committee-only privacy setting:

There are now three privacy options for each discussion thread:

  • Public (publicly visible)
  • Group (i.e. available to all members of the group)
  • Committee (available only to current Committee members)

The latter option means that groups can discuss sensitive matters in privacy if required, e.g. pre-consultation plans from a developer.

There is a setting in the group's area which sets the default (public/group) when their members start a discussion thread.

Cyclescape has a voting system, which now results in a list of popular items, ensuring that key strategic issues can stay floated to the top.

More will be done to expose this feature in due course, as the rest of the interface is improved, but the underlying functionality is now in place.

 

The What's New? link at the end of each page on the site has a log of individual features and bugfixes as they are put in.

Bit by bit, the site's functionality and interface is falling into place!

In our next blog post we'll talk about what we're currently working on, i.e. what's missing and what's not yet finished.