Fix Baltimore endpoint

[bensheldon]

Looks like ~10 months ago the Baltimore 311 endpoint changed. Requests stopped altogether on Open311 and images are broken. https://status.open311.org/cities/baltimore

If you check their portal: https://balt311.baltimorecity.gov/citizen/requests then you'll see actual requests filtering in.

API Docs:  https://dev.socrata.com/foundry/data.baltimorecity.gov/9agw-sxsr

[Mr0grog]

Don’t know if this helps, but I took a quick look and:

• The API docs at dev.socrata.com/foundry/data.baltimorecity.gov/9agw-sxsr appear to be a frozen data set that hasn’t been updated since April (maybe when the API changed?)
• The portal now uses the endpoint at: https://baltimore311.herokuapp.com/311/v3/services.json
  • It’s labeled v3 but a real rough check looks like it adheres to the Open311 v2 API.
  • /311/v2/services.json doesn’t exist (and I assume nothing else at /311/v2/*). (Updated to fix typo in this line.)

…so I think you might be able to just change the YAML to point at the new Heroku URL above: https://github.com/codeforamerica/open311status/blob/607b13034346d559fbcbef3e634ff978a764fd67/config/cities.yml#L13-L17

On a very poor connection while traveling, so can’t really dig in to confirm fully.

[bensheldon]

Thanks @Mr0grog. It looks like it requires me to register to get a working api_key that will allow me to fetch requests 😞 ... and supporting that will require code changes.