Come on Alex.
If you accidentally publicly use a produced work or a derivative
database that is linked somehow with sensitive data and if somebody
actually asks you for the underlying data and if for legal (privacy) or
business reasons you can't hand out the non-OSM data part (lots of ifs),
you
Randy,
On 09/23/2015 07:18 PM, Randy Meech wrote:
> 3. The database you have created is partly derived from OSM (as far as
> "this address is at location lon=x, lat=y" is concerned).
>
> Actually I mis-spoke a bit (sorry, it was several years ago). The
> lat/lngs are actually from state
sent from a phone
> Am 24.09.2015 um 11:23 schrieb Frederik Ramm :
>
>
> I would hesitate to apply this rule for making a selection that can not
> be repeated ("select reverse geocoding results for this non-public list
> of coordinates and store them in my non-public
My understanding of the trivial transformation guideline is that the
data in the nominatim instance would fall under it (so you are not
obliged to supply somebody that asks with a dump of your nominatim
database or your osm2pgsql rendering database etc etc, you can simply
point to the original
Hi,
On 09/24/2015 10:17 AM, Martin Koppenhoefer wrote:
>> and another with exactly these coordinates and their
>> OSM reverse geocoding result, and that you join them when displaying,
>> and make the OSM result database available under ODbL on request
>
> Does he even have to? Isn't this covered
Hi,
On 09/24/2015 06:52 PM, Stephan Knauss wrote:
> If a printed map is a database
A printed map is not a database for us; the German court opinion you
quote has been mentioned in the run-up to the license change but it
didn't convince us.
A database has to consist of things "arranged in a
Frederik Ramm writes:
geocoding results seem like
a produced work to me. I believe that I am decorating other open data
with the results of a geocoder that contains sufficient art to make it
not derived, but produced.
Our usual definition of produced work doesn't look at how much art there