On 12.07.2014 00:46, Martin Koppenhoefer wrote:
Generally what I think about when reading "geocoding": you'd take a list of
addresses and use the database to localize (translate) them in geo coordinates. This
seems to fit perfectly to the derivative db description:
“Derivative Database” – Means a database based upon the Database, and includes
any translation, adaptation, arrangement, modification, or any other alteration
of the Database or of a Substantial part of the Contents. This includes, but is
not limited to, Extracting or Re-utilising the whole or a Substantial part of
the Contents in a new Database. - See more at:
http://opendatacommons.org/licenses/odbl/1.0/#sthash.l1YXFGoW.dpuf
So based on this interpretation you could do geocoding without any
requirements (in terms of attribution or share-alike) as long as it is
insubstantial.
As a single geocode run returns only one, maybe a hand full of locations
it's certainly insubstantial. So can be freely used.
Only when you start to use the process to systematically recreate a
database from the process the ODbL kicks in.
Refer:
6.2 This License does not affect any rights of lawful users to Extract
and Re-utilise insubstantial parts of the Contents, evaluated
quantitatively or qualitatively, for any purposes whatsoever, including
creating a Derivative Database (subject to other rights over the
Contents, see Section 2.4). The repeated and systematic Extraction or
Re-utilisation of insubstantial parts of the Contents may however amount
to the Extraction or Re-utilisation of a Substantial part of the Contents.
- See more at:
http://opendatacommons.org/licenses/odbl/1-0/#sthash.zN2GeAfp.ZYQaM1VQ.dpuf
Stephan
_______________________________________________
legal-talk mailing list
legal-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/legal-talk
