Open Data Manchester March meeting

March’s meeting was an opportunity to help shape Manchester City Council’s forthcoming open data Hackathon. Stuart Baldwin – an ODM regular – spoke about Manchester’s plans for an event in October to coincide with the Manchester Science Festival.

The driver behind this is the recently announced Manchester Digital Strategy and a recent trip that Chief Executive of MCC, Sir Howard Bernstein made to New York. Whilst a guest of Mayor Bloomberg, Sir Howard was apparently impressed with what New York was doing with their open data initiatives such as 311 and App Challenges.

Open Data Manchester and MDDA advised MCC, that for a Hackathon to work it needed to work with the developer community to make the event relevant and developer friendly.

The conversation was mainly focussed on the types of data that developers wanted releasing and there is a list from Duncun Hull @dullhunk here

What was notable was the willingness to listen to what the community wanted and by suggestions from MCC itself, such as Contaminated Land data which has traditionally been contentious.

[vimeo http://www.vimeo.com/36540620 w=400&h=300]
Visualisation by Jonathan Fisher more details here

After the Hackathon discussion attention focussed on Road Traffic Collision data and the work that Steven Flower, Jonathan Fisher and Jonathan S. – There has been discussion about forming a sub-group around RTC data and its use. So if people want to get involved in that contact Steven Flower on the Google Group. Jonathan Fisher’s visualisations where discussed and also the variation in data quality that exists. It was noted that although data was provided to TfGM who collated the data for the Department of Transport. Different flavours of the data existed in different places. TfGM upload monthly data to DataGM which lacked detail on casualties and vehicles involved. The complete RTC data gets forwarded it to the DfT who then make it available via the DfT website and and data.gov.uk with more detail but in two different versions. We are trying to find out why DataGM only holds a less detailed version.