Am Mo, 27.02.2017, 11:14 schrieb Christoph Hormann:
>
> I am not sure about the relevance of your question here.
You're right, this isn't an ODbL mailing list. I'm sorry.
___
legal-talk mailing list
legal-talk@openstreetmap.org
Am Sa, 21.01.2017, 16:04 schrieb Simon Poole:
> I've pointed this our before. but anyway: we don't really care that much
> about the imagery licence as such as long as we are allowed to display
> it in the usual OSM tools. The real question are the rights in digitized
> vector data from that
Am Di, 6.09.2016, 20:14 schrieb Michael Steffen:
>
> We have hundreds of customers hosting their own private data on our secure
> infrastructure. Many customers are also hosting private data that they
> license from 3rd parties. Give me a holler if you want to talk. Good post
> about private maps
Am Di, 6.09.2016, 18:34 schrieb Jeffrey Johnson:
> Tobias, note there are a few options for serving your own MVT pbf
> tiles outside of the mapbox ecosystem. Check projects like
> https://github.com/pka/t-rex and https://github.com/terranodo/tegola
Thanks! I'll play around on my machine with
Am Di, 6.09.2016, 17:33 schrieb Michael Steffen:
>
> This should be totally fine. Feel free to reach out directly if you
> want to talk in more detail.
Yeah, I might contact you in the next days. A problem could be that I
have to upload the non-free data to Mapbox. This might violate the data's
Am Di, 6.09.2016, 17:08 schrieb Rory McCann:
>
> Not really. Vector tiles (*.mvt) are protobuf files, not sqlite files
> (you might be thinking of mbtiles). It doesn't really matter for your
> example, since you could filter a mvt file to split out the different
> layers.
Yeah, I messed this up -
Hi there.
Mapbox allows it to upload own data under a properitary license and
deliver vector tiles and raster tiles.
Let's say, I want to overlay OpenStreetMap data with my own, non-free
data. Just overlay, no other interaction.
Does ODbL allow it, it combine both datasets in one vector data
Am Do, 30.06.2016, 13:15 schrieb Christoph Hormann:
>
> It would also be extremely unfair towards the normal individual mappers
> because their attribution (which is currently the main one
> behind 'OpenStreetMap Contributors') would be buried among tons of
> others.
Tons of others? There aren't
Am Do, 30.06.2016, 12:31 schrieb Martin Koppenhoefer:
> E2
> v1 import 1 node, amenity=place_of_worship, name=Foo
> v2 move the node significantly (e.g. 30 km)
Don't import faulty data, SCNR :)
> Do you always have to attribute once something got imported, even if there
> a no (visual) traces of
Am Mi, 29.06.2016, 23:46 schrieb Martin Koppenhoefer:
> Is there still need to attribute the original creator?
In my opinion that's what CC-BY is all about. You're allowed to change
it, but you still need to tell the name of the licensee.
It's common GIS practice:
When you've got data from
Am Mi, 29.06.2016, 22:58 schrieb Martin Koppenhoefer:
>
> just that this list becomes very long, see
> http://wiki.openstreetmap.org/wiki/Contributors
You wouldn't see "data.gov.au" in a German map extract of course.
I just wasn't creative enough to add data from one spatial area :)
"(C)
Am Di, 28.06.2016, 12:51 schrieb Simon Poole:
> We cannot restrict how our data is used outside of the
> ODbL terms. While we might not be adding personal information,
> downstream that may well happen.
Let's change ODbL and allow different BY-attributes. That would solve
much of problems.
Am Fr, 10.06.2016, 17:22 schrieb Simon Poole:
>
>> Would this make "my" data trigger share-alike?
> The specific term simply says that when there is no references between
> the datasets it is a Collective Database, or in other words that the
> trivial case when there is no interaction is OK too.
Am Do, 9.06.2016, 13:43 schrieb Simon Poole:
> http://wiki.openstreetmap.org/wiki/Collective_Database_Guideline
A question to "the non-OSM and OSM datasets do not reference each other":
Let's say, I've added municipal road identification numbers to the OSM
database (not in my extract, but the
Am Do, 17.03.2016, 23:47 schrieb Tom Lee:
> Tobias, the best option for ensuring the data is usable by OSM is an
> explicit statement of permission for the OpenStreetMap project to
> incorporate and use the data under the project's terms. This is generally
> considered preferable to a dataset that
Am Do, 17.03.2016, 23:47 schrieb Tom Lee:
> Tobias, the best option for ensuring the data is usable by OSM is an
> explicit statement of permission for the OpenStreetMap project to
> incorporate and use the data under the project's terms. This is generally
> considered preferable to a dataset that
Dear list,
could you please recommend me licenses for releasing data to ODbL?
From my point of view, compatible licenses are CC-license without
"SA" and "BY" and (only if possible) CC0 and PD or finally special
license, like the following one:
Some crporations like "Deutsche Bahn" (the biggest
Am So, 13.03.2016, 16:49 schrieb Simon Poole:
>
> I wrote the opposite.
Is my English that bad? Perhaps you can read German, perhaps anyone
else can. That's what my brain has translated from your writing:
"Es behandelt genau den Fall, dass du deine Fremddaten zur Generierung
eines OSM-Ausschnitt
Am So, 13.03.2016, 16:06 schrieb Simon Poole:
> It does (care about a change to the OSM layer). It addresses exactly the
> case that you could use your 3rd party data to generate an OSM extract
> that doesn't contain your data, generating a complement to your data
> allowing you to improve your
Am So, 13.03.2016, 14:06 schrieb Simon Poole:
>
> I specifically limited my point to the case in which there was no
> changes to the OSM layer due to the 3rd party layer and vice versa.
Yeah, I've understood this point, but the guideline doesn't care
about a change to the OSM layer! The layer
Am So, 13.03.2016, 13:50 schrieb Simon Poole:
>
> Am 13.03.2016 um 13:35 schrieb Tobias Wendorff:
>> but of course it interacts with the features.
> How?
That's exactly written in here:
http://wiki.osmfoundation.org/wiki/License/Community_Guidelines/Horizontal_Map_Lay
Am So, 13.03.2016, 13:24 schrieb Martin Koppenhoefer:
>
> what other things besides maps can be produced from our db? Not many (yes,
> you. could make "lists", but they're DBs as well). In the end, something
> like a carpet or a tshirt or a bag are just objects to apply a map on.
> FWIW, our
Am So, 13.03.2016, 13:18 schrieb Simon Poole:
>
> http://wiki.osmfoundation.org/wiki/License/Community_Guidelines/Produced_Work_-_Guideline
>
> Which covers what Christoph has already pointed out, I'm not sure why we
> would want to differentiate between maps and other produced works as you
>
Am So, 13.03.2016, 13:27 schrieb Martin Koppenhoefer:
>
> yes, you won't have to release your data if you remove similar data from
> OSM before rendering though.
So this means: layers with data under a properity license including features,
which already appear partially on a the official
Am So, 13.03.2016, 13:23 schrieb Simon Poole:
>
> IMHO if you don't undertake any efforts to suppress duplicate objects
> (which would include purely visual operations too) you already have
> completely separate datasets and are already clearly in, potentially
> ugly though, Collective Database
Hi there,
according the the Community Guidelines for Horizontal Map Layers,
feature overlays have to be released unter ODbL, if they're completing
content on an online map.
Quote from
http://wiki.osmfoundation.org/wiki/License/Community_Guidelines/Horizontal_Map_Layers_-_Guideline
"For example,
Am So, 13.03.2016, 12:39 schrieb Martin Koppenhoefer:
>
> I believe it has always been clear that the information stored in a map
> was a kind of database by arrangement and selection, e.g. you can't take a
> OSM based printed map that was released under cc0 and derive the contained
> information
Hi Christoph,
Am So, 13.03.2016, 12:18 schrieb Christoph Hormann:
> On Sunday 13 March 2016, Tobias Wendorff wrote:
>
> I don't think there has ever been any serious doubt that printed maps
> can be databases.
What? There has been a lot of discussions about this in the last years.
Hi there,
I don't know, if this thematic has already been discussed on this list,
but European Court of Justice (ECJ) has confirmed the classification
as a database for (printed) topographic maps (see EuZW 2015, 955).
Yet the commentaries can't foresee the consequences, but publishers
are happy
Am So, 7.02.2016, 08:37 schrieb Paul Norman:
>
> It sounds like you have two databases, one the landuse data, the other
> the roads data, together which form a collective database. This might be
> in one file, or more than one file. Because both databases are derived
> from OSM data, by design you
First of all: sorry, my mail client had problems while parsing the mail.
That's what the message-id got lost. I hope that won't happen again :(
> The relevant question here is if during this process you generate a
> derivative database containing both OSM and proprietary data. If you
> do you'd
Am So, 7.02.2016, 00:53 schrieb Rob Myers:
> In general the idea of share-alike is to make sure that downstream users
> of data have the same ability to work with the data as upstream users.
>
> So it's about the users continuing to be able to use the data rather
> than improving it, although that
Desr members of Legal-Talk!
I'm working on a project, which mixes feature classes of different
sources: buildings, landuse and other data from a local mapping
agency and streets streets from OpenStreetMap
Since the produced work will be published, share-alike needs to be discussed.
At lower
Hi there,
I've got a question concerning credits to give when using
OpenStreetMap tiles or data.
A qoute from English Legal FAQ [1]:
1. (c) OpenStreetMap (and) contributors, CC-BY-SA (tiles)
2. Map data (c) OpenStreetMap (and) contributors, CC-BY-SA (data)
The German FAQ translates the first
34 matches
Mail list logo
