Open milovanderlinden opened 8 years ago
For a few 311 services it might make sense; however, I think for most of them what the user is choosing is not a named "Place" according to Google.
I'm thinking along the lines of potholes. We're asking the user to pinpoint where the pothole is. Designating coordinates using a map is useful.
What are the reporting services your city is wanting to offer?
We will be starting with "woonoverlast" (I do not know the exact english word for it; domestic disturbance, neighbour noise complaint and so on). The reports may contain privacy sensitive information. Any advice on how you guys handle that? I am thinking about using opennlp in the backend to anonimize names and addresses on the public API interface so we will be able to give insight to the public, but hide the details.
The PlacePicker has a getLatLng() function and will not limit you to selecting a place. It uses google maps and as far as I can see even gives you the ability to place your pin based on streetview imagery. That would even provide a more detailed way of assigning a location!
For us, the open311 apps report to our uReport server.
https://github.com/City-of-Bloomington/uReport
uReport does not expose personal information fields from the reports. However, it does display the comment text of the reports. Sometimes people put personal information in the comments, and we're not sure what to do with that. Usually, a city employee will edit the comments to remove the personal information.
Anonymizing the addresses does not make sense. Addresses are part of the location. Open311 is a location-based report system. If you have reports where you do not want to expose the addresses where the problems are, then you might need a different report system.
uReport looks great! I agree that addresses do not need to be masked. opennlp offers a mechanism to detect a common first en surnames and indeed, I need to grab them from the comments. I will keep you posted. Maybe opennlp can be used as middleware for signaling potential private content and let the employee check it. https://opennlp.apache.org/
There is a PlacePicker that will give you more then just location from the map and gives users more flexibility picking their location. https://developers.google.com/places/android-api/place-details
Would it be a good idea to replace the current LOCATION_REQUEST with the default PlacePicker?