I created a hobby app where I pulled OSM data (i.e. amenity=toilets) for seeding my DB with existing restrooms. The app will be used for rating restrooms. Its only in closed testing right now so this is the time to adjust my approach to modifying any data, if needed. More info about the app can be found at restroomcritic.app, including joining closed testing… but I have a question.
Some businesses have individual restrooms mapped as separate nodes. I am looking at combining these in the app. For example, small businesses like a gas station. If I modify the data, I need to make it available back to OSM, from what I understand. But I feel these changes would degrade the map. So I do not want to push these changes.
Is my thinking accurate? I want to be sure to stick to the licensing, but not degrade the map.
The ODBL (specifically, section 4.6) only requires you to “make available” your modified database; 4.6(b) specifies that it’s sufficient to provide just the changes. Providing something such as an OSC file somewhere on your website for users to download will comply with the license, letting people view the changes and merge them back into the main OSM database if they find them useful.
Great! Thanks for that input. I was hoping it would be that simple. I was thinking I’d have to find another source of DB seed data. A download link is no prob. I just didn’t want to integrate OSM edits in to my app since it would likely cause unknowingly bad data on OSM. Most users of this kind of app wouldn’t realize they’re editing OSM.