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.
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.http://pierzen.dev.openstreetmap.org/swipe/UAVCompare-Colombia-Mocoa-before-after.php
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.
Pierre
De : "Stadin, Benjamin" <[email protected]>
À : Martin Koppenhoefer <[email protected]>; Rory McCann
<[email protected]>
Cc : "[email protected]" <[email protected]>;
"[email protected]" <[email protected]>
Envoyé le : samedi 22 avril 2017 18h30
Objet : Re: [OSM-dev] Legal question about attribution text on smartphone
#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 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 www.openstreetmap.org/copyright). 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. If we need to show two logos it would waste space
for navigation controls and building / floor selection UI elements. 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. Cheers Ben Von: Martin Koppenhoefer
<[email protected]>
Datum: Freitag, 21. April 2017 um 12:49
An: Rory McCann <[email protected]>
Cc: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Betreff: Re: [OSM-dev] Legal question about attribution text on smartphone
sent from a phone
On 21. Apr 2017, at 12:10, Rory McCann <[email protected]> wrote:
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.
have you seen this page? https://wiki.openstreetmap.org/wiki/Legal_FAQ
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 cheers, Martin
_______________________________________________
dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/dev
