Wednesday, July 1, 2009

Outside.in aggregating SeeClickFix data


Thanks to a recommendation from Fred Wilson Outside.In is now aggregating SeeClickFix data on their site. Outside.In is a tool that brings the full power of hyperlocal to neighborhood websites and audiences.

Check out an example: http://outside.in/New_Haven_CT

Tuesday, June 30, 2009

Connecting with DC 311 Automatically via API

New features here at SeeClickFix and interesting demo site for you to play with.

The City of DC has published an open method for reporting non-emergency 311 issues directly into DC's citizen request system. And now, SeeClickFix connects with their systems directly. As part of DC's Apps For Democracy contest, we've submitted a demo version of the website at http://dc.seeclickfix.com/. (Detailed write-up in PDF.]

When web visitors use the specialized DC subdomain of the SeeClickFix website, they have the option to report issues directly into the DC 311 system. The system automatically pulls the categories of issues from the DC API. If the user picks a category supported by DC311, the user is presented with the additional required questions. The system also uses DC's GIS to guide the user in selecting a known address. And issues reported to DC via other methods besides SeeClickFix are also displayed on dc.seeclickfix.com

Remember, this is a demo site and not live until DC takes their system integration live on their side.

We have been working in this area for a while without a partner city who was ready to implement a programmatic API. We are grateful for the opportunity to work with DC. And we look forward to working with other cities.

Thursday, June 25, 2009

SeeClickFix and Respect to FixMyStreet

I have gotten a few questions recently about FixMyStreet and how it compares with SeeClickFix. Good question.

SeeClickFix is a (mostly) free mobile phone and web tool that allows citizens to report and document non-emergency issues to communicate them to those accountable for the public space. Issues that are reported through the website are recorded on a map for everyone to see and interact with. Anyone can receive email alerts on the issues based on a filter by geographical area and keyword.

We actually looked at FixMyStreet and talked to Tom when we started and think its an awesome tool. I've got a lot of respect for what MySociety has accomplished. After thinking about it and talking amongst our group we decided we wanted to take things in a different direction. For example:
  • Easy to Implement Globally. We wanted to build something that communities could pick-up and implement without a software developer. A citizen, a local neighborhood watch or one city council person can choose to use SeeClickFix in their community. Just set up a watch area to get alerts on a geographical area and you're off and running.
  • Multiple Parties. Governments play a large role in resolving local non-emergency issues. But City Hall is far from the only entity involved. Our model allows anyone to play a role in resolving issues: from your neighbor, to the business improvement district, to the local newspaper, and even to the state department of transportation. Anyone can get alerts not just the official government channels.
  • More Maps. We have built the system on top of Google Maps so that it works globally with map UI. When we started, FixMyStreet only had maps for the UK.
  • Open Data and API. It should be easy to get data out of the system and we've implemented a bunch of methods. We are committed to Open Data and provide this data under a Creative Commons Attribution-Noncommercial-Share Alike license.
    • Web browsing (each issue has it's own web page)
    • XML issue feed (geographically and keyword focused)
    • JSON
    • KML
    • GeoRSS
    • Excel (feature of paid version SeeClickFix Pro)
    • CSV (feature of paid version SeeClickFix Pro)
    • Printable Issue List (feature of paid version SeeClickFix Pro)
    • Open 311 API
    • Embedable widget (available to be placed on other websites with keyword and geographical focus)

  • Community Features. The community should drive what gets noticed, documented and prioritized. For example:
    • Commenting engine on each issue
    • Image gallery to browse by photo
    • I want this fixed too! voting system
    • Share on Facebook features
    • Youtube video integration
    • Send issue to a friend
    • Flag as inappropriate crowd sourced moderation
    • Twitter issue reporting

So, if you're not a software developer and wanted to get started right away, create a watch areas for your
community at http://www.seeclickfix.com/fixers and or embed the map in your websites at http://www.seeclickfix.com/widget. If you are a software developer, we'd love to have you work with our open data to pull info out or help to create the Open 311 API we've proposed.

Friday, June 19, 2009

Open 311 API – An Early Draft

Last week we blogged on the growing need for an open API for 311 and local issues/service requests. There has been a lot of attention paid to getting data OUT OF government. Gov 2.0 types have been all a-Twitter about Data.gov and the feeds being created at a rapid pace. That’s wonderful.

There also should be ways to send important and actionable data INTO governments and other civic organizations. It’s time for an open API for sending service requests or identifying issues that have a specific geographical component. For example, reporting a storm drain that is clogged or a streetlight that is out. Imagine if your smart-phone, your local blog, and websites like SeeClickFix could talk back and forth with local governments automatically.

We got a great response to the blog post (thanks!) and now it is time to move the conversation to the next level. And considering that there is a session at ChangeCamp Canada this weekend on discuss such a topic, Kam and I thought it best to publish an early draft.

As we mentioned in the last post, we want this to a community-supported standard. We’re not sure where it should live on the web (here or here?) or how it should be owned, licensed, etc. Should one vendor or local government drive the conversation or should an independent third-party carry the banner? Andrew Greenhill suggested perhaps the National League of Cities or the Conference of Mayors would be a US institutions interested in such an effort.

Regardless, we wanted to get our thoughts out there and get the party started.

Open311 API
Draft Specification

2009-06
v0.1


Please read through it and let us know your thoughts. Look forward to hearing from you.

Tuesday, June 16, 2009

To Our SideClicks:

We sent this email out to our SideClicks today:
If you want to compete, feel free to follow the simple rules below.

SeeClickFix has grown a lot in the last few months and we thought we'd have another SideClick of the month contest.

Here's the Game Plan:

1) You create a watch area claiming your turf. (private or public...it's up to you)

2) You email us and let us know you have created the watch area.

3) You and your community report lots of Clickets in your hood before July 1.

4) The SideClick with the most Clickets in their watch area is announced as SideClick of the month on our blog, twitter and any place else that people listen to us.
We will also announce any additional information about your group that you would like us to publicize.

BONUS PRIZES: -Best Photo on a Clicket, -Best Video on a Clicket

Chris in Bozeman, MT holds the current belt... go out there and Click it away from him if you can.

P.S. there are now about 100 of you and you have grown to be an International community so you'll have to have your game face on.

The Goodspeed Update

After I posted about John Geraci's Four Pillars I was made aware of this post:

http://goodspeedupdate.com/2009/2625

From the article,

"There seems to be something intrinsic about Internet technology that makes it particularly well suited for local initiatives, perhaps due to some of the factors I discuss here. Second, it raises the issue of to what extent government should attempt to create new technology. There actually already is a website that does more or less what the Harvard folks describe that I’ve been meaning to write about — SeeClickFix. In fact, here’s some potholes, broken streetlights, and other problems already reported on this private website:

Some have argued the government should focus on data sources nearly exclusively, but I’m more of a moderate on the issue. After all, the private sector may not develop technology that suits the unique characteristics of government. Lastly, this local suggestion implies the subtle ways the Obama Administration’s innovation in transparency, participation, and online engagement could trickle down to state and local government."



From SeeClickFix's perspective the system that everyone ultimately ends up to interact with their government and others about the public space should be both citizen and government friendly. SeeClickFix is working with cities like Houston to make sure that the tool is useful to governments as well as citizens.

One thing we have started to notice is that when government officials start to use the tools themselves they are really looking for a simple data entry platform that is similar to what the citizen needs to be encouraged to participate.

We've also noticed that exposing issues to the public minimizes duplication of service requests as well as creates a good way for governments to weigh the public demand for the fix.

If you're a gov. official what would make it easier for you to resolve citizen complaints?

Monday, June 15, 2009

John Geraci: 4 Pillars an Open Civic System

Great blog post from John Geraci on O'Reilly:
http://radar.oreilly.com/2009/06/the-four-pillars-of-an-open-ci.html

John mentions C2C,C2G,C2C and G2G where C= Citizen and G=Gov. Substitute the variables and John is talking about a community organism that communicates without the barriers of concealed data or complicated front-ends for accessing that data.

We built SeeClickFix on these principles and are excited that someone finally put it so eloquently.