I could use more clarification, I really do not understand this answer and I'm not sure if it's falling upon a nuance I don't see. The OSM Legal FAQ says in 3d, "However, if the two datasets are matched 'trivially' by, for example, automated matching using a simple criterion such as name/locality, this is not 'substantial' and remains a Collective Database." (http://wiki.openstreetmap.org/wiki/Legal_FAQ#3c._If_I_make_something_with_OSM_data.2C_do_I_now_have_to_apply_your_license_to_my_whole_work.3F)

If you are placing pins on an OSM map (from your own tile server) and those pins are being placed based on a latitude and longitude you already know (generated from your own app), that surely remains a Collective Database and thus does not require releasing your customer information. (Surely lat/long is far more trivial than name/locality.)

If you are placing pins on an OSM map and those pins are being placed based on street address you already know (from customers giving it to you), isn't that too a trivial match and thus a Collective Database and does not require releasing your customer information? (Address is less trivial than name/locality, but still seems very trivial.) I'm struggling to understand the Legal FAQ any other way.

Thanks.

asked 25 Feb '15, 17:23

ben9898's gravatar image

ben9898
61123
accept rate: 0%

edited 07 Mar '15, 13:09

aseerel4c26's gravatar image

aseerel4c26 ♦
31.9k16237548


This is the wrong place to start a legal discussion.

For discussions please usr the legal-talk mailing list, if you have specific question to the licensor (the OSMF) please see http://osmfoundation.org/wiki/License or contact the LWG at legal-questions@osmfoundation.org

permanent link

answered 25 Feb '15, 17:58

SimonPoole's gravatar image

SimonPoole ♦
38.0k13284605
accept rate: 19%

If you display anything on top of an OSM map then the two data sets are completely separate and nothing happens, license-wise.

If you use OSM data to derive the location of a point (either by letting your user click on the OSM map to place the point, or by using OSM street names, house numbers, and boundary information to match an address to a coordinate pair) then you're in murky waters. Some people will say it's trivial, others will say you are deriving information from OSM. There's also a distinction to be made between doing this just once or on the fly, or doing this often and saving the results in a new database. The jury is still out on this one and you can see different possible interpretations in the work-in-progress geocoding guideline.

permanent link

answered 06 Mar '15, 17:30

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
69.3k806291083
accept rate: 24%

edited 06 Mar '15, 17:31

-1

If you are placing pins on an OSM map (from your own tile server) and those pins are being placed based on a latitude and longitude you already know (generated from your own app), that surely remains a Collective Database and thus does not require releasing your customer information. (Surely lat/long is far more trivial than name/locality.)

Correct.

If you are placing pins on an OSM map and those pins are being placed based on street address you already know (from customers giving it to you), isn't that too a trivial match and thus a Collective Database and does not require releasing your customer information?

Correct.

permanent link

answered 06 Mar '15, 16:45

lxbarth's gravatar image

lxbarth
252
accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×80
×29
×4

question asked: 25 Feb '15, 17:23

question was seen: 3,025 times

last updated: 07 Mar '15, 13:09

powered by OSQA