> Gesendet: Dienstag, 17. Dezember 2019 um 01:00 Uhr
> Von: "Martin Koppenhoefer"
>
> it will contain a lot of postcode information from the original OpenStreetMap
> database,
> in adapted/translated form. Whether the amount is sufficient to be considered
> substantial
> will have to be
> Gesendet: Montag, 16. Dezember 2019 um 17:03 Uhr
> Von: "Tom Lee via legal-talk"
>
> This is an admirable impulse, but it is worth emphasizing that those of
> us who participate on OSM listservs are a small and unrepresentative
> fraction of the project's 5.9 million registered users. Lists
> Von: "Nuno Caldeira"
> it's a derivated, therefore share alike. I'm glad they trusted OSM data.
So the distance calculations are derivated, of course.
But what about their points of interests? They've interacted with the roads.
___
legal-talk
Dear IANALs,
I'm sorry to ask an additional question.
A while ago, I've listened to a talk about navigation of pupils from their home
to the school - it was used to decide whether the pupil gets a free bus ticket
or not.
The distance calculation was done by a land registry office, which
Christoph.
> Gesendet: Montag, 16. Dezember 2019 um 12:03 Uhr
> Von: "Christoph Hormann"
>
> This is definitely a better approach than trying to find loopholes in
> the license with brute force and wishful thinking. Even if that is
> possible and you can present an interpretation of the wording
Simon,
> Gesendet: Montag, 16. Dezember 2019 um 13:33 Uhr
> Von: "Simon Poole"
>
> Just to be clear: you asked a question on an unmoderated, publicly
> accessible mailing list on which everybody can voice their opinions
> however unfounded they are or not, and now you are unhappy with that you
>
I don't care about the money it costs, I even would pay for OpenStreetMap. I just wanted to use OSM, since the data quality is pretty high in the area I need it.
In a future license it would be better to allow attributions like "Data: (c) Non-Free, selected using (c) OpenStreetMap under
> Von: "Christoph Hormann"
>
> The idea that your process of intersecting non-OSM data with OSM based
> admin polygons results in a collective database is not realistic. To
> me this kind of operation would be a textbook example of something
> generating a derivative database - you combine OSM
>
> existing OSMF community guidelines suggest spatial operations like
> ST_Difference() and ST_Intersection() yield Derivative Databases that
> are subject to share-alike.
Let's take the Collective Database Guideline, you've mentioned:
Hi Mateusz,
>> No, ODbL does not apply to any database that does not include OSM data.
> It is true but misleading to mention here as this database contains
> transformed OSM data.
So if I don't merge the postcodes, it's fine?
>> There is no OSM data in the secondary list so it is not a
Hi Lars-Daniel, yeah, same here.
I've read you tried to do similar work in the past. I think, you've merged postcodes with OSM data in a seperate column and didn't need to attribute it as share-alike.
What did you end up with?
Gesendet: Freitag, 13. Dezember 2019 um 19:25 Uhr
Von:
Let me get into detail is this project to proof that this case isn't constructed.
We've purchased geodata with real estate prices (houses & flats) for Germany's federal state "Northrhine Westfalia". Each row has coordinates in WGS84. The TOS of the purchhased dataset state, that it's not
> we are here to create more open data, not to feed proprietary data than is
> lock under their TOS.
I want to apologize for my misunderstanding: my final product does not contain
any OpenStreetMap data.
___
legal-talk mailing list
> From a practical point of view, boundaries in OSM rarely originate from
> surveys,
> you might be lucky to be able to identify the original source (most likely
> open data)
> which may have a more liberal license than ODbL (check the history and
> changeset
> source tags / object source
Hi,
> when you write „number of boundaries“, you intend „boundary points“?
No, for example postcodes. I want to merge some of them to new polygons.
Regards,
Matthias
___
legal-talk mailing list
legal-talk@openstreetmap.org
Hi,
> In my NAL opinion, the result will be derived from OSM data and
> therefore inherits the ODbL license. This does, however, not mean that
> you have to publish it; but *if* you publish (or "publilcy use") it,
> then it has to be available under ODbL. If you just use it internally
> then it
Dear IANALs,
I want to use polygons (district boundaries) from OSM dataset to select points
for a proprietary dataset.
The OSM dataset might be altered trivially (f.e. boundaries might be merged
where needed).
The proprietary data isn't allowed to be used freely and is incompatible with
ODBL.
17 matches
Mail list logo
