You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMHO an important aspect of online service requests is to eliminate duplicates, as citizens can see existing service requests, before they enter a new one.
Unfortunately the app currently doesn't show the existing requests on the map (in general and geolocate view), which might result in unnecessary requests, if different citizens enter multiple requests to solve a single problem.
It would be pretty cool, if the map could visualize all requests and let the user explore the content.
The text was updated successfully, but these errors were encountered:
I totally agree and this is on our wishlist indeed!
The biggest reason for not implementing this yet is that at the City of
Eindhoven, the app will be used primarily for civil disturbance. With
regards to privacy, these reports are not allowed to be shown on a public
map, so our first priority is cooking a recipe for hiding them. Sending a
deviceid to our back end is the first step as you may have noticed in the
source code. With the deviceid, users should be able to see their own
reports. The requests.json should then be anonimized and coordinates
randomized +/-500m for these particular requests.
IMHO an important aspect of online service requests is to eliminate duplicates, as citizens can see existing service requests, before they enter a new one.
Unfortunately the app currently doesn't show the existing requests on the map (in general and geolocate view), which might result in unnecessary requests, if different citizens enter multiple requests to solve a single problem.
It would be pretty cool, if the map could visualize all requests and let the user explore the content.
The text was updated successfully, but these errors were encountered: