In order for an Open Data platform to have any sustainability it must have a community around it that consumes its data, be that the public or developers creating applications that people then use. This second CodeTheCity event saw that community begin to form around the MatchTheCity platform.
This is a short tale of how I took another city’s data in order to expand the information we can provide for people / apps to consume. It also acts as a warning as to some of the unexpected side effects of using automatically generated data that has not been checked by a human.
Back in May of this year I was involved in the planning for the inaugural CodeTheCity event that was to take place in Aberdeen the following month. Initially the event was going to be billed as another hackathon-type event doing stuff with Aberdeen-based open data. However, between the five of us who were putting the event together we decided to drop the reference to the hackathon term and to make it more approachable, more attractive even, to the non-developer community. As well as involving local (and further afield) developers, we also wanted to involve the community in Aberdeen to ensure they got something out of it that they actually wanted. This led to the CodeTheCity name idea. Not only was it perfect for Aberdeen but could easily be re-run in other cities around the world under the same umbrella.