Thanks to everybody for helping me with clarifying the license.
To answer some of the questions that came up, we would be masking water
bodies at the end of our processing chain, once we had already derived
rates for all of the pixels. There are also a few other masking steps that
would be run
Rory - I don't think you can, because the negative area is area with both
no ground elevation/displacement and no water body. There would be no way
to tell whether the negative area was water body data or simply no
displacement.
On Thu, Jun 7, 2018 at 4:41 AM Rory McCann wrote:
> On 07/06/18
On 07/06/18 00:44, Kathleen Lu wrote:
The way I understand the use, the OSM data is used to identify areas
that are to be discarded. Data in those areas are discarded. Thus, the
OSM data is not kept either, and no OSM data in the final dataset. Thus,
there is no derivative database containing
On 2018-06-07 12:19 AM, Christoph Hormann wrote:
The idea that you can produce a data set using both OSM and non-OSM data
in a meaningful way without there being either a collective or a
derivative database seems fundamentally at odds with the basic concept
of the ODbL. The only way this could
On Thursday 07 June 2018, althio wrote:
>
> I would then interpret the requirements as:
> Use: Attribution is required.
> Horizontal layers / Collective Database: Share Alike is not required.
This is what i mentioned in my first reply with
"If what you do is just masking the water areas in
I feel the most relevant guideline in the case of Andrew would be:
https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines/Horizontal_Map_Layers_-_Guideline
What they do:
- using some OSM data of 1 Feature Type [large water bodies]
- and producing data of another Feature Type [ground
On Thursday 07 June 2018, Kathleen Lu wrote:
> The way I understand the use, the OSM data is used to identify areas
> that are to be discarded. Data in those areas are discarded. Thus,
> the OSM data is not kept either, and no OSM data in the final
> dataset. Thus, there is no derivative database
