« | Home | »

Update on Open Data in Edmonton

I’m encouraged by the progress that is being made on making open data a reality here in Edmonton. I think the open data sessions at ChangeCamp had an impact, as did Councillor Iveson’s formal inquiry. There’s still a lot of work to do, however!

A few brief updates:

We’ve also started having open data chats with beer! Our next one takes place tomorrow evening:

#yegdata conversation
November 4, 2009 at 4:30pm (come whenever)
Rose & Crown Pub, 10235 101 Street

RSVP on Facebook
See the event on ShareEdmonton

Feel free to drop after work. Our last discussion was really great. One of the things we talked about was the approach we should take. In general, I think the preferred approach is something like the following:

  1. Low-hanging fruit (stuff that is already on the website, just in a closed format, etc)
  2. Data that doesn’t have FOIP implications but that isn’t already available
  3. Everything else
  4. APIs for real-time data?

We’ve got more than enough with the first two to keep everyone involved busy for quite some time.

One of the things we discussed was identifying and prioritizing the first two. What kinds of data does the community want? Which data is already up on the website in a closed format? To help facilitate that, I’ve created a UserVoice site for #yegdata, and have seeded it with 18 types of data that I’d like to see the City of Edmonton make available. Here’s where I need your help!

There are no guarantees that the data and priority identified through the UserVoice site will be what actually happens, but it’ll definitely help the City move forward. Thanks in advance!

Help us identify and prioritize open data here!




Tags: , , , ,
Categories: Uncategorized | 1 Comment »

Related Posts:

One Response to “Update on Open Data in Edmonton”

  1. Open Data comes to Edmonton at MasterMaq's Blog Says:
    January 13th, 2010 at 2:58 pm

    [...] led to the creation of the #yegdata hashtag, a UserVoice site to identify potential data sets, and a number of smaller follow-up events. It also prompted Chris Moore to open up access to the creation of his report. On November 23, 2009 [...]

Comments