<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1492658770755_264419">When you present many layers of inforation, it is a challenge to avoid to encomber the map with too many information while providing attribution to all.</div><div id="yui_3_16_0_ym19_1_1492658770755_264910"><br></div><div id="yui_3_16_0_ym19_1_1492658770755_264909">This UAVCompare map analyzes the situation in Mocoa, Colombia, following the mudslide at the beginning of april 2017. This map reflects the response of the Columbia OSM community in collaboration with some international OSM community members.</div><div id="yui_3_16_0_ym19_1_1492658770755_264421" dir="ltr"><a href="http://pierzen.dev.openstreetmap.org/swipe/UAVCompare-Colombia-Mocoa-before-after.php" id="yui_3_16_0_ym19_1_1492658770755_264435" class="">http://pierzen.dev.openstreetmap.org/swipe/UAVCompare-Colombia-Mocoa-before-after.php</a><br> </div><div id="yui_3_16_0_ym19_1_1492658770755_264443"><br></div><div id="yui_3_16_0_ym19_1_1492658770755_264508" dir="ltr">Adding / Selecting various layers from various providers, it is not easy to have both a good design and provide attribution to all. My choice was to have a dynamic attribution line at the bottom of the image that list the various image providers. Plus the Layer selection panel credit each image provider. Detailed information with url is accessible via the Credits url link at the bottom of the screen. <br></div><div id="yui_3_16_0_ym19_1_1492658770755_264493"><br></div><div id="yui_3_16_0_ym19_1_1492658770755_264333"><span></span></div><div id="yui_3_16_0_ym19_1_1492658770755_264348"> </div><div class="signature" id="yui_3_16_0_ym19_1_1492658770755_264377"><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;"> <br><font face="garamond, new york, times, serif">Pierre </font><br></span></div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1492658770755_264423"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1492658770755_264428" style="display: block;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 13px;" id="yui_3_16_0_ym19_1_1492658770755_264427"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, linéale; font-size: 16px;" id="yui_3_16_0_ym19_1_1492658770755_264426"> <div dir="ltr" id="yui_3_16_0_ym19_1_1492658770755_264425"> <font id="yui_3_16_0_ym19_1_1492658770755_264424" size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">De :</span></b> "Stadin, Benjamin" <Benjamin.Stadin@heidelberg-mobil.com><br> <b><span style="font-weight: bold;">À :</span></b> Martin Koppenhoefer <dieterdreist@gmail.com>; Rory McCann <rory@technomancy.org> <br><b><span style="font-weight: bold;">Cc :</span></b> "dev@openstreetmap.org" <dev@openstreetmap.org>; "legal-talk@openstreetmap.org" <legal-talk@openstreetmap.org><br> <b><span style="font-weight: bold;">Envoyé le :</span></b> samedi 22 avril 2017 18h30<br> <b><span style="font-weight: bold;">Objet :</span></b> Re: [OSM-dev] Legal question about attribution text on smartphone<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1492658770755_265095"><br><div id="yiv6907453065"><style>#yiv6907453065 #yiv6907453065 --
_filtered #yiv6907453065 {panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered #yiv6907453065 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
#yiv6907453065
#yiv6907453065 p.yiv6907453065MsoNormal, #yiv6907453065 li.yiv6907453065MsoNormal, #yiv6907453065 div.yiv6907453065MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv6907453065 a:link, #yiv6907453065 span.yiv6907453065MsoHyperlink
{color:blue;text-decoration:underline;}
#yiv6907453065 a:visited, #yiv6907453065 span.yiv6907453065MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
#yiv6907453065 span.yiv6907453065E-Mail-Formatvorlage17
{font-family:Calibri;color:windowtext;}
#yiv6907453065 span.yiv6907453065msoIns
{text-decoration:underline;color:teal;}
#yiv6907453065 .yiv6907453065MsoChpDefault
{font-size:10.0pt;}
_filtered #yiv6907453065 {margin:70.85pt 70.85pt 2.0cm 70.85pt;}
#yiv6907453065 div.yiv6907453065WordSection1
{}
#yiv6907453065 </style><div id="yui_3_16_0_ym19_1_1492658770755_265094">
<div class="yiv6907453065WordSection1" id="yui_3_16_0_ym19_1_1492658770755_265093">
<div class="yiv6907453065MsoNormal" id="yui_3_16_0_ym19_1_1492658770755_265092"><span style="font-size:11.0pt;font-family:Calibri;" id="yui_3_16_0_ym19_1_1492658770755_265091" lang="EN-US">It’s not our app, but this is an (indoor) map SDK which can be integrated into other native iOS and Android apps. A list (UIActionSheet on iOS) appears
when our logo is tapped, showing multiple links (including a link to <a rel="nofollow" shape="rect" target="_blank" href="http://www.openstreetmap.org/copyright" id="yui_3_16_0_ym19_1_1492658770755_265144">
www.openstreetmap.org/copyright</a>). Having our logo visible is a legal requirement also, and it wouldn’t be convenient to place the list with multiple legal links not associated to OSM behind the OSM attribution logo or text.
</span></div>
<div class="yiv6907453065MsoNormal" id="yui_3_16_0_ym19_1_1492658770755_265113"><span style="font-size:11.0pt;font-family:Calibri;" lang="EN-US"> </span></div>
<div class="yiv6907453065MsoNormal" id="yui_3_16_0_ym19_1_1492658770755_265115"><span style="font-size:11.0pt;font-family:Calibri;" id="yui_3_16_0_ym19_1_1492658770755_265117" lang="EN-US">If we need to show two logos it would waste space for navigation controls and building / floor selection UI elements.
</span></div>
<div class="yiv6907453065MsoNormal" id="yui_3_16_0_ym19_1_1492658770755_265119"><span style="font-size:11.0pt;font-family:Calibri;" lang="EN-US"> </span></div>
<div class="yiv6907453065MsoNormal" id="yui_3_16_0_ym19_1_1492658770755_265122"><span style="font-size:11.0pt;font-family:Calibri;" id="yui_3_16_0_ym19_1_1492658770755_265121" lang="EN-US">Since the map view will be used in other apps, we cannot control what is shown on the splash screen. We can place it there for our own apps, and
ask customers of our SDK to place it there. But from experience this is often forgotten, and I’d rather prefer a permanent solution and give credit to OSM one way or another on the map view.</span></div>
<div class="yiv6907453065MsoNormal" id="yui_3_16_0_ym19_1_1492658770755_265140"><span style="font-size:11.0pt;font-family:Calibri;" lang="EN-US"> </span></div>
<div class="yiv6907453065MsoNormal" id="yui_3_16_0_ym19_1_1492658770755_265142"><span style="font-size:11.0pt;font-family:Calibri;" lang="EN-US">Cheers</span></div>
<div class="yiv6907453065MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;" lang="EN-US">Ben</span></div>
<div class="yiv6907453065MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;" lang="EN-US"> </span></div>
<div class="yiv6907453065MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;" lang="EN-US"> </span></div>
<div class="yiv6907453065yqt3361240352" id="yiv6907453065yqt73210"><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm;">
<div class="yiv6907453065MsoNormal"><b><span style="font-family:Calibri;color:black;">Von: </span>
</b><span style="font-family:Calibri;color:black;">Martin Koppenhoefer <dieterdreist@gmail.com><br clear="none">
<b>Datum: </b>Freitag, 21. April 2017 um 12:49<br clear="none">
<b>An: </b>Rory McCann <rory@technomancy.org><br clear="none">
<b>Cc: </b>"dev@openstreetmap.org" <dev@openstreetmap.org>, "legal-talk@openstreetmap.org" <legal-talk@openstreetmap.org><br clear="none">
<b>Betreff: </b>Re: [OSM-dev] Legal question about attribution text on smartphone</span></div>
</div>
<div>
<div class="yiv6907453065MsoNormal"> </div>
</div>
<div>
<div class="yiv6907453065MsoNormal"><br clear="none">
<br clear="none">
sent from a phone</div>
</div>
<div>
<div class="yiv6907453065MsoNormal" style="margin-bottom:12.0pt;"><br clear="none">
On 21. Apr 2017, at 12:10, Rory McCann <<a rel="nofollow" shape="rect" ymailto="mailto:rory@technomancy.org" target="_blank" href="mailto:rory@technomancy.org">rory@technomancy.org</a>> wrote:</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;">
<div>
<div class="yiv6907453065MsoNormal">So I dunno? Maybe? There could be ways around it if you don't want to include it on every map page. Does your app have a loading/spash screen? Including an attribution there, which is shown every time the app is started might meet the requirements.</div>
</div>
</blockquote>
<div class="yiv6907453065MsoNormal"> </div>
<div>
<div class="yiv6907453065MsoNormal"> </div>
</div>
<div>
<div class="yiv6907453065MsoNormal">have you seen this page?</div>
</div>
<div>
<div class="yiv6907453065MsoNormal"><a rel="nofollow" shape="rect" target="_blank" href="https://wiki.openstreetmap.org/wiki/Legal_FAQ">https://wiki.openstreetmap.org/wiki/Legal_FAQ</a></div>
</div>
<div>
<div class="yiv6907453065MsoNormal"> </div>
</div>
<div>
<div class="yiv6907453065MsoNormal">generally, if there is enough space for your logo, there should also be for osm (on pages showing maps). If there's space for just one attribution, why not use it to attribute osm? The user will more likely be aware who you are (as he's
using your app) than he will be that your map data comes from osm, so prioritizing OSM attribution seems to make sense </div>
</div>
<div>
<div class="yiv6907453065MsoNormal"> </div>
</div>
<div>
<div class="yiv6907453065MsoNormal"> </div>
</div>
<div>
<div class="yiv6907453065MsoNormal">cheers,</div>
</div>
<div>
<div class="yiv6907453065MsoNormal">Martin </div>
</div></div>
</div>
</div></div><div class="yqt3361240352" id="yqt03672">_______________________________________________<br clear="none">dev mailing list<br clear="none"><a shape="rect" ymailto="mailto:dev@openstreetmap.org" href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br clear="none"><a shape="rect" href="https://lists.openstreetmap.org/listinfo/dev" target="_blank">https://lists.openstreetmap.org/listinfo/dev</a><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>