Sorry, this was a typo. Of course I mean houses in both cases:
Let's say you're creating a map of Western, taking houses from OSM in Germany and houses from proprietary data from all other countries, since OSM is incomplete here. Isn't this a mixture on the same layer?
Also, when
Recall that under the geocoding guidelines, it is not considered a
substantial extra if "only names, addresses, and/or latitude/longitude
information are included in the Geocoding Results," "the collection is not
a systematic attempt to aggregate all or substantially all Primary Features
of a
I don't think the analogy is quite right.
The Geocoding Guidelines say:
Geocoding Results can be latitude/longitude pairs (as typical in forward
Geocoding Results), and/or full or partial addresses and/or point of
interest names (as typical in reverse Geocoding Results).
Latitude/longitude pairs
The additional guidelines are OSM-specific:
https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines
On Mon, Oct 14, 2019 at 4:58 PM Lars-Daniel Weber
wrote:
> Sorry, this was a typo. Of course I mean houses in both cases:
>
> Let's say you're creating a map of Western, taking houses
> 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
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
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
According to community guideline for "Geocoding", I'm not using original OSM data in my new map at all. Since I've drawn lines from paper drawn on an Produced Work of OSM data, I don't have any of the original OSM elements in my final dataset, which are in the OSM dataset.
So, I just need to
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
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
The reference to countries come from the Regional Cuts Guideline (and then
the later Collective Database Guideline), in case that was not clear.
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
11 matches
Mail list logo
