Hi.
ODbL don't want produced works to be share-alike, but wants the underlying
database to be.
So what's the deal when I'm strictly separating ODbL licensed data from data
under another license?
In Illustrator, I could load a SVG created by qGIS with OSM data. I could only
*link* to this SVG
On 29/03/15 16:43, Lars-Daniel Weber wrote:
Sure, I have to release the SVG file or the workflow under share-alike, that's fine so
far. But when I press export to PDF, will this be an intermidiate database,
which also has to be share-alike? This simply wouldn't be possible pecause of the use
Hi,
On 03/29/2015 05:43 PM, Lars-Daniel Weber wrote:
In Illustrator, I could load a SVG created by qGIS with OSM data. I could
only *link* to this SVG only without embedding it. So it's in a complete
seperate file / XML DB, which can't or doesn't have to be edited. Now I could
add other
