uReport

City of Bloomington, Indiana

Search

Fields to display

Search Results: (116)

open #185011

Website & Web Services Feedback

219 1/2 E 8th ST

Case Date:
8/12/2023

Each time I enter 219 E. 8th St. to find the trash/recycle day, that address is not recognized!

closed #180907

Website & Web Services Feedback

Case Date:
8/5/2022

I live at 2114 E. Rock Creek Drive, During Fiber installation between the street and sidewalk, the machinary that was used lifted my concrete pad making an uneven unsafe surface. This has not been repaired by the installers of the Fiber. Thanks for your attention to this matter and your response.

closed #176308

Website & Web Services Feedback

Case Date:
6/22/2021

the abominable condition of the large homeless camp has been made even more disasterous by flooding. Debris and probably syringes are now plastered onto trees for a great distance

open #181883

Website & Web Services Feedback

715 S Park AVE

Case Date:
10/22/2022

I'm not sure uReport is working correctly. I've reported a few Bird scooters blocking sidewalks and the process seems to hang at the 4th step, saying that the request is being processing. I did create one earlier today and it progressed to the point where it showed my the ticket that was created. The next one I created did not and appeared to hang at step 4 again.

closed #182104

Website & Web Services Feedback

Case Date:
11/18/2022

Our apartment seems to have been entered twice this week. I know because an item was left; in addition, an item was taken. These thefts are unacceptable.

closed #182829

Website & Web Services Feedback

215 S Westplex AVE

Case Date:
2/14/2023

Wheeler mission throwing everything away with no notice because you are showing up and they are trying to impress you.

closed #173871

Website & Web Services Feedback

3151 N Kingsley DR

Case Date:
10/4/2020

Bush at the corner of the property near the intersection needs to be trimmed back to make traffic more visible. The bush makes it hard to see oncoming traffic coming over the hill toward the intersection.

closed #186624

Website & Web Services Feedback

Case Date:
12/28/2023

If you haven't yet finalized the text and layout for the 2024 Sanitation Collection Schedule, there is one improvement: Please print any solid waste pickup date exceptions in a readable font size as part of the Solid Waste & Recycling Checklist. The very fine print listed vertically on the 2023 magnet has obviously been overlooked by residents scheduled for Thursday route pickup. It would also help to have pickup exceptions listed on the website. Thank you.

closed #182718

Website & Web Services Feedback

Bloomington City Hall, 401 N Morton St, Bloomington, IN 47401, USA

Case Date:
2/3/2023

Hello, I would like to inquire about the domain name blue ridge.bloomington.in.us as I believe that the city owns this and currently redirects this to Lingo Technology where we host our Blue Ridge web site. We have recently created a new Google Sites web page and would now like to change the CName to this new web site at https://sites.google.com/view/brnabloomington/home If you can assist with this that would be great, I can be reached at 4088399811 to discuss further, Thanks Wes Scholl Blue Ridge Neighborhood Association Vice President

closed #174607

Website & Web Services Feedback

Case Date:
1/30/2021

The B Clear Open Data portal should follow the best practice of referencing source URLs over the HTTPS protocol. For example on this page: https://data.bloomington.in.gov/dataset/bloomington-city-council-districts-gis-data/resource/9b0438ae-fdba-44f3-a14a-b39fd63912d0 The link to the actual resource is not secured. It is served over plaintext `http`: http://bloomington.in.gov/geoserver/publicgis/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=publicgis:CityCouncilDistricts&outputFormat=shape-zip This has practical implications for data users. Esri's ArcGIS Online product only supports loading URLS over 'https', so the current URLs don't work directly with Esri. A test confirmed that the URLs are valid if "http" is simply replaced with "https" in the returned URLs. Hopefully this means that this fix amounts to small configuration change to start referencing the secure versions of the resource URLs. Thanks.