<div dir="ltr">Thank you all for your responses. I apologize for the vagueness - this is a highly confidential project. <div><br></div><div>We would like to use the Overpass API (<a href="http://wiki.openstreetmap.org/wiki/Overpass_API">http://wiki.openstreetmap.org/wiki/Overpass_API</a>) which I believe is made for read-only purposes, which is what we need. We would be well below the 10,000 calls per day, at least for the foreseeable future.</div><div><br></div><div>So, if we could find a way to credit OSM on the packaging of the product, would this be a legit use?</div><div><br></div><div>Thanks very much,</div><div>Jen</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 2, 2015 at 2:30 PM, Richard Weait <span dir="ltr"><<a href="mailto:richard@weait.com" target="_blank">richard@weait.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm pretty sure that Martijn means "does NOT allow", rather than "now". :-)<br>
<br>
So, whatever you are planning, Jennifer, hitting the editing API is<br>
probably going to get you some unwanted attention. There are other<br>
ways to access the OpenStreetMap data, and you'll want to make sure<br>
that you are using one of those approved methods that is suitable to<br>
your use case. To be clear, accessing and using OpenStreetMap data is<br>
"okay", all else being equal. Causing inappropriate stress on<br>
OpenStreetMap Foundation resources is not okay. Let's presume that you<br>
are going to use the replication data method to keep a local and<br>
current version of OpenStreetMap data, so you won't be loading the<br>
editing API.<br>
<br>
What you describe in very general terms does sound like case 3 from<br>
that wiki page, [1]. "I want to publish something based on<br>
OpenStreetMap data and my own data."<br>
<br>
So where you ask, "1) is this allowed," I would say, "yes, the<br>
license grants you permission so long as you comply with the terms of<br>
the license."<br>
<br>
and where you ask "2) If so, how would I give credit if nothing is<br>
<span class="">displayed? Or would I not have to give credit since no map or direct<br>
data is displayed?"<br>
<br>
</span>This answer is more complicated. You are obliged to give credit, that<br>
is one of the license terms. So if you fail to give credit, you<br>
haven't got a license to use and republish the data. Additionally,<br>
there is the share-alike obligation. So, if that applies, you'll have<br>
to meet that obligation as well. You've been very general about the<br>
nature of the external data you plan to consult, so I don't know if<br>
you'll have an obligation to share-alike.<br>
<br>
How would you give credit? You should do so in a manner suitable or<br>
customary to the medium. Consider the TV credit roll mentioned in the<br>
wiki. For say, cupcakes or ear rings made with OpenStreetMap data, I<br>
would expect a notation on the packaging. For a wall clock, or<br>
coasters, I would expect a label on the back.[2] For electronic<br>
hardware I'd expect credit in the firmware and the documentation. So,<br>
in short, the credit should be where a user, or consumer, or developer<br>
(or mapper) would expect it. Credit shouldn't be somewhere hidden<br>
behind a disused file cabinet. :-)<br>
<br>
Best regards and happy mapping,<br>
Richard<br>
<br>
[1] <a href="http://wiki.openstreetmap.org/wiki/License/Use_Cases#Case_3:_I_want_to_publish_something_based_on_OSM_and_my_own_data" target="_blank">http://wiki.openstreetmap.org/wiki/License/Use_Cases#Case_3:_I_want_to_publish_something_based_on_OSM_and_my_own_data</a><br>
[2] <a href="http://weait.com/coasters.png" target="_blank">http://weait.com/coasters.png</a><br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
legal-talk mailing list<br>
<a href="mailto:legal-talk@openstreetmap.org">legal-talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/legal-talk" target="_blank">https://lists.openstreetmap.org/listinfo/legal-talk</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><font face="'arial narrow', sans-serif"><p style="margin:0cm 0cm 0pt;line-height:normal">Jennifer Bauman<br></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0pt;margin-left:0cm;line-height:normal">Director, Vehicle Modeling | CrossChasm Technologies<b><span style="color:rgb(0,0,153)"></span></b></p>
<div><font><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0pt;margin-left:0cm;line-height:normal"><span>Phone: <a value="+15193427385">519.342.7385</a></span></p>
<p style="margin-top:0cm;margin-right:0cm;margin-bottom:0pt;margin-left:0cm;line-height:normal"><span>Toll-Free: <a value="+18009752434">1.800.975.2434</a></span></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0pt;margin-left:0cm;line-height:normal">
<span>Email: <a href="mailto:jbauman@crosschasm.com" target="_blank">jbauman@crosschasm.com</a></span></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0pt;margin-left:0cm;line-height:normal">
<span>Web: <a href="http://www.crosschasm.com" target="_blank">www.crosschasm.com</a></span></p></font></div></font></div></div>
</div>