Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-13 Thread Christoph Hormann
On Saturday 13 January 2018, Paul Norman wrote: > > Has anyone requested the derivative database their produced work is > based on? It'd give us their interpretation. As said i have contacted the author (primarily regarding attribution - which he promised to improve - and has partly already

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-13 Thread Paul Norman
On 1/11/2018 7:30 AM, Christoph Hormann wrote: My interpretation of the ODbL here is that this is a share-alike case that would require the combined data sources to be made available. But you could probably also look at it differently. I would like to hear opinions on this. In particular if

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-13 Thread Christoph Hormann
On Saturday 13 January 2018, Kathleen Lu wrote: > Your example doesn't work. Even if you could render > "distance-to-water" > > this way, you wouldn't get a set proprietary data based lakes + OSM > lakes, you would get a visualization of one massive complicated body > of water that included all

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-12 Thread Kathleen Lu
> > My argument is about the geometry information. The friction map > combines road geometries from OSM and Google road geometry information. > I see no way it can be argued that this combination of road geometry > data which is rendered into the friction map is a collective database. > None of

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-12 Thread Christoph Hormann
On Friday 12 January 2018, Kathleen Lu wrote: > Your analysis does not follow. > > The researcher's description says: "These datasets were each > allocated a speed or speeds of travel in terms of time to cross each > pixel of that type. The datasets were then combined to produce a > 'friction

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-12 Thread Kathleen Lu
They are using OSM road data and Google road data to generate what they > call a "friction surface" which is essentially a raster map indicating > how fast you can move at every point of the map - faster on roads, > slower elsewhere depending on relief and landcover. This friction map > you can

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-12 Thread Christoph Hormann
On Friday 12 January 2018, Rory McCann wrote: > As near as I can see, the only data they are distributing (publicly) > is the 2 GeoTIFF files in the "map.ox.ac.uk" page. The question is: > Is a GeoTIFF file created like this from OSM data which has been > mixed with other data, a Produced Work, or

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-12 Thread Rory McCann
As near as I can see, the only data they are distributing (publicly) is the 2 GeoTIFF files in the "map.ox.ac.uk" page. The question is: Is a GeoTIFF file created like this from OSM data which has been mixed with other data, a Produced Work, or a Derived Database? In support of "Produced Work",

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-11 Thread Christoph Hormann
On Thursday 11 January 2018, Kathleen Lu wrote: > > I don't have access to the locked Nature article, but the description > from the first link suggests that they are using a derivative > statistic calculated from the Google road network instead of the > network itself: "The game-changing

Re: [OSM-legal-talk] Interesting use case of combining OSM with proprietary data

2018-01-11 Thread Kathleen Lu
Hi Christoph, What is done here is combining road information (and some other data) > from OSM and proprietary data sources (Google) into a raster map (made > available as 'friction surface' under the first link above) and doing > further processing, analysis and map rendering based on that and >