In such cases, wouldn't be enough to add a source=NASA or source=ASTER tag?<br>
<br>
[]<br><br><div class="gmail_quote">2009/7/2 Tyler <span dir="ltr"><<a href="mailto:tyler.ritchie@gmail.com">tyler.ritchie@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote">Ævar, Thanks for trying to get clarification. Despite my disagreeing that there is any real restriction on the data that affects its use in OSM, clarification and explicit permission is always a good thing.<br>
<br>This should have been cross-posted to legal, probably. And let me preface it all with IANAL... Yet.<br><div><div><br></div><div>Martin: </div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
What about derived data? SRTM is used to generate hillshades and <span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">contour lines for example. ASTER data would be good for that too. Do they have some less strict terms about distributing such derived data (like requiring only attribution), or is their policy for it the same?</span></blockquote>
</div></div><div><br></div><div>I take it to mean that you can re-distribute derived data, that would be the "<span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">project of intended use" part. They have that in there so that they can mitigate the number of sources of the ASTER, so that there's not a bunch of different ASTER Jun 2009 datasets all saying they're the same thing on a bunch of different University servers free to the public.</span></div>
<div><br></div><div>Jeff:</div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>That clause seems very similar to the BSD advertising clause (and is problematic for the same reasons)</div>
</blockquote><div><br></div></div><div>I assume you mean "<span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">When presenting or publishing ASTER GDEM data, I agree to include</span></div>
<span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">'ASTER GDEM is a product of METI and NASA.'" That's pretty standard attribution stuff. Which we should want to encourage. Being able to find the source is probably sufficient (so on a printed map you could say "for a list of all the sources see <a href="http://www.ReallyAwesomeVolcanoMap.com/sources" target="_blank">www.ReallyAwesomeVolcanoMap.com/sources</a>"), but also doesn't appear to be a required agreement (it doesn't have the "required", which leads me to believe it is optional). </span></div>
<div class="gmail_quote"><font face="arial, sans-serif"><span style="border-collapse: collapse;"><br></span></font></div><div class="gmail_quote"><span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">If there were a more standard way to get attribution data on the slippymap (a link: view all attributed sources in this extent) then OSM would probably be fine, and 3rd parties attributing data correctly is the 3rd party's responsibility. Immutable historical attribution would also be cool so that once all the roads from TIGER are correct and totally different there is still historical attribution data. The attribution mess has been what's stopped me from using a lot of available State data. Which has no restrictions as long as there is attribution. And attribution is such a cluster with OSM data right now that I just don't really want to deal with it, there's lots to do elsewhere.</span></div>
<div class="gmail_quote"><font face="arial, sans-serif"><span style="border-collapse: collapse;"><br></span></font></div><div class="gmail_quote"><font face="arial, sans-serif"><span style="border-collapse: collapse;">The BSD argument was that there would be a spiraling out of control "This product was derived from this product was derived from this product was derived from..." a better restriction would have been. "When presenting or publishing ASTER GDEM data, I agree to provide attribution to METI and NASA." Which would allow for more options on how to give the attribution. But like I said, that seems optional to me.</span></font></div>
<div class="gmail_quote"><font face="arial, sans-serif"><span style="border-collapse: collapse;"><br></span></font></div><div class="gmail_quote"><font face="arial, sans-serif"><span style="border-collapse: collapse;">Finally, if someone is planning on doing any sort of stuff with the ASTER GDEMs in the US, there's higher resolution data available from USGS, 3m in some cases, so use that instead.</span></font></div>
<div class="gmail_quote"><font face="arial, sans-serif"><span style="border-collapse: collapse;"><br></span></font></div><font color="#888888"><div class="gmail_quote"><font face="arial, sans-serif"><span style="border-collapse: collapse;">-Tyler</span></font></div>
</font><br>_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Arlindo Saraiva Pereira Jr.<br><br>Bacharelando em Sistemas de Informação - UNIRIO - <a href="http://uniriotec.br">uniriotec.br</a><br>Consultor de Software Livre da Uniriotec Consultoria - <a href="http://uniriotec.com">uniriotec.com</a><br>
<br>Acadêmico: <a href="mailto:arlindo.pereira@uniriotec.br">arlindo.pereira@uniriotec.br</a><br>Profissional: <a href="mailto:arlindo.pereira@uniriotec.com">arlindo.pereira@uniriotec.com</a><br>Geral: <a href="mailto:contato@arlindopereira.com">contato@arlindopereira.com</a><br>
Tel.: +5521 92504072<br>Jabber/Google Talk: <a href="mailto:nighto@nighto.net">nighto@nighto.net</a><br>Skype: nighto_sumomo<br>Chave pública: BD065DEC<br>