OSM Licensing - is this a derivative use case?

General talk
1

Hi there!

I’m building an app that allows users to create collections of places from OSM in order to share them with others, publicly. The places themselves are OSM data which I think brings them under the derivative clause, but as I’m not adding any additional data other than creating these collections, does that still make it a derivative database?

If so, that’s no problem at all - I’m happy to make the collections available under the same license. Are there any guidelines on what’s required to do this? A regularly updated export of the database? How often? What format?

Thanks!
George

1 Like
2

If so, that’s no problem at all - I’m happy to make the collections available under the same license. Are there any guidelines on what’s required to do this? A regularly updated export of the database? How often? What format?

AFAIK you don’t have to provide these on a regular basis (you can do it if you think it’s useful for someone, but it is not an obligation from the license), you must provide them when asked for it.

1 Like
3

Ah that makes sense, thanks so much for clarifying! :slight_smile: