uReport

City of Bloomington, Indiana

Search

Fields to display

Search Results: (10193)

closed #163324

Potholes, Other Street Repair

506 1/2 S High ST

Case Date:
2/26/2018

Pot holes on High Street

closed #163325

Potholes, Other Street Repair

2499 East 3rd Street

Case Date:
2/26/2018

Pot holes at 3rd St. and Hillsdale

closed #163326

Potholes, Other Street Repair

503 W Dodds ST

Case Date:
2/26/2018

Pot holes on Dodds before Rogers St.

closed #163327

Potholes, Other Street Repair

1130-1198 East 1st Street

Case Date:
2/26/2018

Pot Holes

closed #163328

Potholes, Other Street Repair

400 E 1st ST

Case Date:
2/26/2018

Pot Holes

closed #163329

Potholes, Other Street Repair

414-498 West Dodds Street

Case Date:
2/26/2018

Pot Holes

closed #163330

Potholes, Other Street Repair

901A South Rogers Street

Case Date:
2/26/2018

pot holes

closed #163332

Traffic Related Complaints

900 S High ST

Case Date:
2/26/2018

I was damn near killed today by a car that didn't stop at the corner of High Street and Maxwell Lane. The car was coming south on High Street while I was coming west on Maxwell. There is no crosswalk at the intersection, but there is a stop sign for traffic. The stop sign is not stopping traffic.

closed #163333

Potholes, Other Street Repair

Case Date:
2/26/2018

Right hand southbound lane of South Walnut Street just north or North Dr (near Herald Times entrance)

closed #163334

Website & Web Services Feedback

Case Date:
2/26/2018

Trying to use the online bill pay service for water, but it repeatedly is erroring out on me. Here is the error (stack trace), better error handling would be great, as this is not human readable in terms of actions to take.. Server Error in '/eSuite.Utilities' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>