Dear Kathleen,
thanks for your response.
> Even assuming the polygons are from a Derivative Database, I don't see a
> reason for the data to be released under
> https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines/Trivial_Transformations_-_Guideline
The process doesn't seem to be tr
Hi there,
https://www.wohnlagenkarte.de/ displays location quality of residential areas.
Those residential areas haven been produced using OSM data; the polygon area
results from at least three surrounding paths and streets.
Since the polygons are derived from OSM data and released in public, I
Please stop constructing such cases. This case clearly would have the intention of reproducing the OSM database.
My intention is the trivial use of OpenStreetMap. A normal process in the GIS world.
Gesendet: Freitag, 13. Dezember 2019 um 10:44 Uhr
Von: "Mateusz Konieczny"
An: "Licensing an
ar.
I don't see how roads and houses (do you mean building footprints?) would be "mixture on the same layer" or why the layer matters since they're different data types...
On Mon, Oct 14, 2019 at 8:33 AM Lars-Daniel Weber <lars-daniel.we...@gmx.de> wrote:
From: &q
From: "Kathleen Lu via legal-talk"
> Lars-Daniel already said that they are kept in separate columns and not
> de-duplicated. There is no requirement that, in order to function as a
> Collective Database, data types may not be used together to create a
> Produced Work. To the contrary, the guidanc
Hi again,
sorry for creating another topic, it's somehow related, but somehow different.
Community Guideline "Horizontal Map Layers" doesn't allow to cherry-pick
features within the same layer from a proprietary dataset to complete missing
data in OSM without triggering share-alike.
Community
required to credit OpenStreetMap as
> described in Section 4.3 of the ODbL.
Gesendet: Montag, 07. Oktober 2019 um 20:05 Uhr
Von: "Kathleen Lu"
An: "Licensing and other legal discussions."
Cc: "Lars-Daniel Weber"
Betreff: Re: [OSM-legal-talk] map drawn bas
I totally have to agree with this.
Gesendet: Donnerstag, 10. Oktober 2019 um 23:24 Uhr
Von: "Kathleen Lu via legal-talk"
An: "Licensing and other legal discussions."
Cc: "Kathleen Lu"
Betreff: Re: [OSM-legal-talk] ZIP codes from OSM in non-compatible licensed dataset
> Extracting
> Extracting than 100 elements (non repeatable) from the databse accounts for
>substantial.
That's not correct. I can extract as many as I want. It's just not allowed that
thew newly created database contains a substantial part of the OSM database.
When I create 100 databases containing 100 fea
From: "Martin Koppenhoefer"
> "substantial investment" is not the same as monetary cost. The human time
> that is
> needed to collect and arrange the data is also an investment.
Creating the items is *not* covered by the database directive. The amount of
time needed to collect them actually is
First of all, thanks for your answer. I had a long talk with a lawyer about
this topic today. He wasn't into geodata, but new about the database directive.
From: "Tom Hummel"
> First, I consider the zip code (as in addr:postcode=/feature/) a primary
> feature, although it is generally considered
From: "Kathleen Lu via legal-talk"
> However, that said, I would be doubtful that, for example, an extraction
> of all ZIPs in OSM could be insubstantial. Where the line is has not
> been conclusively established.
I've extracted 273 ZIP codes, while there are more than 8000 in Germany.
___
From: "Martin Koppenhoefer"
> As I read the collective db guideline, you cannot have both, the ZIP
> codes from your proprietary database and those from OpenStreetMap, in
> the same database matched to the same objects. It says “add or replace”
> a property (we do agree the ZIP codes are a propert
From: "Kathleen Lu via legal-talk"
> In my view, if you are keeping the two zip codes in different columns
> and not removing duplicates, then essentially what you have is one
> property that is "OSM ZIP" and one property that is "proprietary ZIP",
> and they are two different properties that are
From: "Kathleen Lu via legal-talk"
> So if what is extracted is solely what was in the database, then the
> extraction is not
> material that the tile license covered (the tile license cannot actually
> change the license of the data, which is ODbL, as that would be
> impermissible under ODbL).
From: "Simon Poole"
> I'm not ruling out the first interpretation either and potentially both
> licenses would have to apply in full (which isn't possible without
> conflict).
I would like to clarify once again that I really do want to attribute OSM. But
it's damn difficult for me to find out un
just seems to be rather unlikely.
>
> In any case you are creating a derivative of a CC BY-SA 2.0 licensed
> work which requires all derivatives to be licensed on CC BY-SA 2.0 terms
> (that are far more restrictive than the ODbL).
>
> Am 06.10.2019 um 15:05 schrieb Lars-Daniel Weber
Dear users,
I'm often intersecting geodata with a license, which is in a
non-ODbL-compatible license, with OSM data to enrich this data. Normally, I'm
doing this for internal (private) use only, but I want to publish such a
dataset now.
For example, I'm getting postal ZIP codes from OSM and ad
Dear users,
I've drawn a map based on the official OpenStreetMap tiles, which are licensed
under CC-BY-SA 2.0 using QGIS. The result is stored as a shapefile. The
shapefile should be published to students to work with it. It might be printed
and shared otherwise.
Most of the time during the dr
Frederik Ramm wrote on Donnerstag, 19. November 2015 um 13:46 Uhr:
>
> I would have a stronger opinion if it were a case where external data is
> mixed with OSM to create an "added value" product - but if someone just
> mangles the OSM data a bit, I'm tempted to view that as part of the
> rendering
Three days are gone and still no discussion about this topic.
I think, nobody is really interested in discovering license violations and
penalize the violators.
Why do we have ODbL at all, if all we do is to discuss about the license itself
or tell guys to write the correct attributation?
ODbL
ne
It's not trivial in terms of "normal" spatial algorithms, which can be found in
GEOS, Postgres etc.
Sincere regards,
Lars-Daniel Weber
___
legal-talk mailing list
legal-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/legal-talk
hink, there are some steps described
in section 9.
Sincere regards,
Lars-Daniel Weber
___
legal-talk mailing list
legal-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/legal-talk
Hi.
ODbL don't want produced works to be share-alike, but wants the underlying
database to be.
So what's the deal when I'm strictly separating ODbL licensed data from data
under another license?
In Illustrator, I could load a SVG created by qGIS with OSM data. I could only
*link* to this SVG o
24 matches
Mail list logo
