[OSM-legal-talk] License question, user clicking on map

Alex Barth alex at mapbox.com
Fri Feb 22 01:55:05 GMT 2013


I think all of these use cases should be ok and we should adjust the
community guide lines to clarify that ODbL's share alike clause shouldn't
kick in here.


On Thu, Feb 21, 2013 at 6:16 PM, Olov McKie <olov at mckie.se> wrote:

> Hello all!
>
> I have a few usecases for OSM where I do not know if I can use it or not.
>
> I work for a library where we are building a new version of an application
> to handle all sort of collections, for example books, letters, images,
> music sheets, etc. The application will store metadata and digitalized
> versions of the works. To know where an item was created, a letter sent
> from / to, etc we need to store places and information about them. The
> information we normally store about a place is name, alternative names,
> names translated to different languages, etc. A place might be a historic
> one that no longer exists.
>
> In the current system, metadata about a place is constructed by giving it
> a name, known variations of the name, which country it is in (problematic
> as it might change over the time) and translation of the name.
> As an OSM user and contributor my first reaction was, we can make the
> places more precise and avoid the changing countries problem by using
> coordinates for places, and also present them in a better way.
>
> As the applications data should be readable for a long time (forever),
> will we be storing all metadata together with the digitalized objects. We
> will over the lifetime of the application construct several thousand
> places. We will not be able to share the complete db under the ODbL as the
> works have all kinds of licenses that are incompatible with the ODbL. The
> resulting system will be accessible for anyone from the Internet,
> subsections might have restricted access.
>
> 1. If we present an OSM map to the user let them click on the map and use
> the coordinates they clicked on as part of the metadata for a place in our
> application, will the resulting database be considered a derived database?
>  To clarify, we would not extract any information from the map, beside the
> coordinates that the user clicked on, they would by themselves navigate the
> map to for example London and then click somewhere in London.
>
> 2. If we use the overpass API to find possible matches for a placename
> entered by a user, present the possible matches with markers on a map and
> let the user click on the map and use the coordinates the user clicks on,
> will the resulting database be considered a derived database?  Again, we
> would not extract any information from the map, beside the coordinates that
> the user clicked on. Presenting the markers would of course help the user
> find a place, such as London.
>
> 3. If we use the overpass API to find possible matches for a placename
> entered by a user, present the possible matches with markers on a map and
> if we have more then one result ask the user to fill in more details about
> the place such as, country, region, close to major city, local name, etc
> until overpass only returns on result, would the user entered data be
> considered a derived database? To clarify, in this case would we not
> extract the coordinates or any other data from the map.
>
> 4. If we present several places (all data about the place including
> coordinates originates from other sources than OSM) on an OSM map to help
> find duplicates, and then lets the user click on two places marked on the
> map, to merge them into one, would the resulting database be considered a
> derived database?
>
>
> I would love for us to use OSM in our application, but I have been unable
> to find out if we can use it for the four usecases presented above.
>
> with hope of a speedy answer
>
> /Olov
>
> _______________________________________________
> legal-talk mailing list
> legal-talk at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/legal-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/legal-talk/attachments/20130221/15029efd/attachment.html>


More information about the legal-talk mailing list