[OSM-legal-talk] Collective databases (was: Using OSM data, to generate game worlds.)

Frederik Ramm frederik at remote.org
Thu Feb 11 19:25:28 UTC 2021


Hi,

about adding LIDAR heights to OSM buildings:

On 2/11/21 19:04, Christoph Hormann wrote:
> If you generate a new database (one of 3d models of buildings) from OSM
> building footprint data and LIDAR point cloud data that is quite
> evidently not a collective database but a derivative database.

> A collective database would
> require the OSM sourced components and the data from other sources to
> be independent from each other.

This is a very interesting question and I am not sure what my own
opinion on it is.

Your reasoning seems to be that, because the LIDAR dataset only says "a
height of 123m has been observed at lon=x, lat=y", you can only match it
to OSM by merging it with the OSM geometry, and therefore the two data
sets are not sufficiently independent. Is that correct?

A frequent example for a collective database is taking a list of
restaurants and their locations from OSM, and then from a different
source adding reviews for these restaurants. Would you agree that this
is a collective database?
https://wiki.openstreetmap.org/wiki/Collective_Database_Guideline does
the same with phone numbers as an example.

In the restaurant example, the review source will likely identify the
restaurants by name or address, and you will have to look at OSM's name
and address in order to create the link that makes the two data sets
into a collection.

Is there a fundamental difference between using a name from OSM to match
it with the review data I am taking from a different source, or using a
geography from OSM to match it with LIDAR data from a different source?

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"



More information about the legal-talk mailing list