The Chainlink

Hi folks,

A lot of us are all over the City of Chicago and see potholes and other infrastructure defects that should be reported to 311.

I'm going to a meeting next week to see a preview of the coming web-based 311 reporting tools that city is working on through a civic development group called Code for America. I'm active in the Open Government movement here in Chicago.

What they are building is not only a better web front-end to report things like potholes and darkend streetlights, but reporting tools that shows the progress of the City at addressing and fixing these reported issues. Something that is very opaque at the moment.

I'll report back here my notes from the meeting.

Meanwhile, you can go to http://potholes.311servic.es/ to see where all of the current reported potholes are located in Chicago that are waiting for repair. Below the map, there is a link to the pothole reporting form on the City's web site. Filling in this form as just like calling 311.

Views: 278

Reply to This

Replies to This Discussion

Sounds like we'll have more of an incentive to inappropriately close reports than we do with the current system.

why?

h' said:

Sounds like we'll have more of an incentive to inappropriately close reports than we do with the current system.

Excellent!  Since I regularly use 311 (especially online) to report problems, I'll be glad to see a better web interface.  I would *love* to see the web interface give a TRACKING # after a report is submitted.  An earlier version did this via the email response, but they lost it in the most recent revision.

Since some of us may submit more than one 311 request on a day, it would be great if the system either returned a tracking # on screen or gave the location of the request along with the tracking # in email.  In the previous version, if I submitted 3 or 4 requests, unless I kept a record of the order of the requests, I didn't know which tracking # corresponded to which request when I went back to the emails.

Another request - will the next version actually sync with Google Maps to allow accurate reporting of off-street locations (such as Major Taylor Trail, Burnham Greenway, etc.) without jumping through a lot of hoops?  These locations are identifiable on Google Maps, and the more intelligent 311 operators get it.  If you get a dense one, good luck! 

Could they also make location requirements CONSISTENT for different types of requests?  Could all types of requests rely on approx. street address, nearest intersection for location OR grid coordinates on trail?  Right now forestry requires the actual street address of the nearest building, which makes it impossible to get requests for off-street locations like stand-alone trails entered into the system.  Potholes, street lights out, graffiti, fly dumping, dead animals, etc. ALL go by approx. street address or nearest intersection now.  Why does forestry have to be different?

Just my $0.02.... Yes, I've spent WAY too much time on 311 requests over the last several years.  Can you tell?  ;)

Anne,

From what I can gather, the new web input and reporting interfaces will be MUCH better than it is at the moment. Again, instead of stirring the rumor mill, I'll report on what I see at the meeting/demo this week. The meeting is Thursday evening.

Thanks.  I'll look forward to your recap after the meeting.

Tom Kompare said:

Anne,

From what I can gather, the new web input and reporting interfaces will be MUCH better than it is at the moment. Again, instead of stirring the rumor mill, I'll report on what I see at the meeting/demo this week. The meeting is Thursday evening.

Okay. Here is the progress on the new Chicago 311 web input and reporting.

1. The city is opening up the 311 system to web developers (like me). But really anyone. This means people who have the skills will be able to write their own 311 input and reporting straight to/from the 311 system.

2. The City application is going to concentrate (for now) on reporting out the back end. The reporting the city is going to roll out is very detailed. Anyone will be able to track requests at every step, and as requests get closed and opened into new tickets for different departments; to be completed.. or passed like a hot potato or a game of pong. the reporting will be completely open to the public.

A previous poster said "Sounds like we'll have more of an incentive to inappropriately close reports than we do with the current system." Actually, no. Do this, and the public and anyone else paying attention will be there to watch you do that. Good luck with that strategy.

 

Also, on the 311 request input, I'm going to be doing some testing of a smartphone app a group of persons are developing for the new 311 system. When that gets closer to fruition, I'll make another report.

 

The timeline for all of this is within the next few months.

 

So, maybe in the end, your bike's new favorite pothole may not be filled faster. At least, you'll know where in the patch pipeline it is. And watch when city departments are playing "pong" with your request, and you can complain to your alderman about it. Maybe someone with some madd statistical skillz will be able to roughly predict how long it might take!

 

Cheers, everyone.

RSS

© 2008-2016   The Chainlink Community, L.L.C.   Powered by

Disclaimer  |  Report an Issue  |  Terms of Service