Hello everyone, We are developing an app for bar, hotel and restaurant reviews, called Revuie. With all the changes that have happened with hospitality recently, we need to be able to give our users a quick and easy way to edit or add venues. Hopefully, we can add back by contributing those edits. But we’re wary of the risk of bad edits. One initial idea was to just make the edits in our local data, and then publish a change file that could be used as a source for the community. But the problem we can’t get our heads around is how to de-dupe those changes on future imports of OSM data. Another alternative is to use the API to make the changes, identifying them as coming from a user tied to our app - and maybe setting them as needing review? Whatever approach we take, we can create guides for users so that they can get a feel for how and when to make edits - and as the change functionality is implemented in the app it can be buttoned down. We’d love to be a part of the community, and to contribute it back, so it would be great to get any advice and feedback people have on this, please. Another puzzle we're facing is how to enable users to tag venues, and keep that tag list in line with existing OSM tags, as the tags could come from various sources. For example, we'd definitely want to include cuisine. Some pubs have sport tags (like pool) which could be useful. Across food, drink and accommodation, there must be lots of tags that we haven't considered. Any advice on this would be great too. Ultimately, we want to encourage tagging of venues in the app to enhance user search, and it would be great to contribute this back too. Many thanks, John

Hello everyone, We are developing an app for bar, hotel and restaurant reviews, called Revuie. With all the changes that have happened with hospitality recently, we need to be able to give our users a quick and easy way to edit or add venues. Hopefully, we can add back by contributing those edits. But we’re wary of the risk of bad edits. One initial idea was to just make the edits in our local data, and then publish a change file that could be used as a source for the community. But the problem we can’t get our heads around is how to de-dupe those changes on future imports of OSM data. Another alternative is to use the API to make the changes, identifying them as coming from a user tied to our app - and maybe setting them as needing review? Whatever approach we take, we can create guides for users so that they can get a feel for how and when to make edits - and as the change functionality is implemented in the app it can be buttoned down. We’d love to be a part of the community, and to contribute it back, so it would be great to get any advice and feedback people have on this, please. Many thanks, John