This requires a well defined area, it will work in places like Kópavogur or within its defined neighborhoods, counting POIs and types, like shops etc, cache it and count again later and track changes.
Another POI possibility would be to add a special tag to a POI, like osm_contact: some@emailexample.tld , then if the node has not been updated in a year send (bulk if many nodes with same osm_contact) a generated e-mail, listing the POI and links to them on the map and a uniquely generated link that allows them, in a simple interface, to update data.
For example:
Marking it has closed
Updating the address
Fixing opening time
The interface could then either update the database in case of simple fixes (opening time), perhaps delete node if it closed.
If it has moved then we can try and do a lookup and present a pin on a map and ask "Is this the new location?", if not and we can't find new address then we put it on a microtask list that can be looked at, or put an OSM Note on it.
This requires a well defined area, it will work in places like Kópavogur or within its defined neighborhoods, counting POIs and types, like shops etc, cache it and count again later and track changes.
Another POI possibility would be to add a special tag to a POI, like osm_contact: some@emailexample.tld , then if the node has not been updated in a year send (bulk if many nodes with same osm_contact) a generated e-mail, listing the POI and links to them on the map and a uniquely generated link that allows them, in a simple interface, to update data.
For example:
The interface could then either update the database in case of simple fixes (opening time), perhaps delete node if it closed.
If it has moved then we can try and do a lookup and present a pin on a map and ask "Is this the new location?", if not and we can't find new address then we put it on a microtask list that can be looked at, or put an OSM Note on it.