Thanks for raising the issue. We at tried to follow the license: 
basically we are combining the OSM data without certain nodes (see the list of 
ids at ) and a 
proprietary data set for hotels. Since we do not use any OSM information, like 
names or coordinates, for these hotels, I assumed the result could be 
considered a collective database.

Now, the matching process does indeed compare coordinates of hotels in both 
datasets, and filters out nodes in the OSM data. The list of nodes is 
published, so anyone can reproduce the open part of the data from a planet 
dump. Again, the proprietary data is in no way affected by the OSM data (it is 
added in its entirety, not a single object is omitted or altered using OSM 
data). So the last item in the guidelines ("all hotels not found in the 
OpenStreetMap data layers") does not apply.

If the LWG decides we are violating the license (and explains how, maybe 
producing another guidelines), we will remove all OSM hotels from our data. But 
for now I don't see how it's different from removing just some of the hotels.


Andrew Harvey wrote:
> According to [1] if someone combines non-horizontal layers together,
> the results must be shared under the ODBL.
>> From my investigation it appears that the MAPS.ME app [2] is combining
> OSM hotels with non-OSM hotels.
> is a screenshot from the
> app. Hotel A appears in the app,
> but as far as I can tell was never in OSM but rather one of the hotels
> they've added to their app from Hotel B is from OSM.
> This is the area
> There are other examples of this too like this hotel
> which in the app shows up
> next to their supplemented data like this
> Am I correct that in order to be complaint with the license MAPS.ME
> either need to make this data available under the ODBL or remove all
> OSM hotels from their app?
> [1] 
> [2] version 6.2.2-Google Data version: 160621

legal-talk mailing list

Reply via email to