The grey area (particularly since you are doing this at the end of the
processing chain) is really if the end result is a produced work or not
(the third kind of derivative you can have in the ODBL), because if it
is, then 4.5 b. kicks in
/b. Using this Database, a Derivative Database, or this Da
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 aro
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 0
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 O
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 f
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 visual
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 elev
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 c
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 OSM data.
On Wed, Jun 6, 2018 at 3:36 PM C
On Wednesday 06 June 2018, Andrew Pon wrote:
> [...]
>
> Given that we are using open street maps to just remove pixels at an
> early stage of processing, would we be able to just put a statement
> in our written reports saying that open street maps was used in this
> masking process, or would we h
Hi Andy,
In my opinion, your suggested attribution is sufficient. (Others are free
to weigh in.)
Best,
Kathleen
On Wed, Jun 6, 2018 at 10:46 AM Andrew Pon wrote:
> Hello,
> I am an employee with 3vGeomatics and we are interested in using open
> street maps to help process our data, but were uns
Hello,
I am an employee with 3vGeomatics and we are interested in using open
street maps to help process our data, but were unsure of how to interpret
the license restrictions.
What we do is take satellite radar data and process it through a rather
length chain in order to figure out where the gro
Nathan Vander Wilt wrote:
> For example,
> if a photographer geotags a picture using OSM, what are the chances of
> a local surveyor (or any other contributor) wanting to decide how that
> copy of the photograph must then be licensed?
Zero.
(I am not a lawyer, this is not legal advice.)
-
On Dec 19, 2008, at 11:41 PM, Jukka Rahkonen wrote:
> Ævar Arnfjörð Bjarmason writes:
>> There's a license FAQ [1] which I think should answer your question.
>> whether your POI data is derived work would depend on whether you use
>> OSM data to place those POIs. I presume you have them already in
Hi everybody,
I've been thinking about the situation and I currently still have some
questions:
- The POI _Metadata_ (which is shown in a "Popup") is definitely not
licensed under the CC-By-SA, right?
- Concerning the new license: [1]
> Geocoding
>
> If I run my database of 1000 customers
Hi Peter,
> With the new licence I believe this will also be a possible however I
> have not been able to see any recent drafts of the licence so can't
> give any more reassurance.. See the proposed Use Cases for the new
> licence which I see as the 'requirements' document for the new licence
> and
Hello,
thanks for your responses!
>> There's a license FAQ [1] which I think should answer your question.
>> whether your POI data is derived work would depend on whether you use
>> OSM data to place those POIs. I presume you have them already in some
>> database however and just wish to use OSM
Ævar Arnfjörð Bjarmason writes:
>
> There's a license FAQ [1] which I think should answer your question.
> whether your POI data is derived work would depend on whether you use
> OSM data to place those POIs. I presume you have them already in some
> database however and just wish to use OSM as
Hello everybody,
I am working for a small startup company which wants to provide
geographical information for tourism areas. We intend to produce an
online map-widget like you have at your website, and want to add a
custom overlay of touristically relevant POIs (Hotels, Guest houses,
Resta
19 matches
Mail list logo
