> > existing OSMF community guidelines suggest spatial operations like > ST_Difference() and ST_Intersection() yield Derivative Databases that > are subject to share-alike.
Let's take the Collective Database Guideline, you've mentioned: https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines/Collective_Database_Guideline_Guideline "Technically a reference between non-OSM and OSM data can be by a database key or any other method of identifying a specific OSM or non-OSM element that may be used with a database join." So actually, I just need to create a collective database, put the non-free data in one table and OSM data in another. For table joining, I'm using ST_Intersects() and I'm fine? Confusing. _______________________________________________ legal-talk mailing list legal-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/legal-talk