<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div style="16px">Note that in this I focus specifically on Mapbox, but they are not<br></div><div style="16px">unique in repeatedly "forgetting" to properly attribute OSM while<br></div><div style="16px">prominently featuring their own logo.<br></div><div style="16px"><br></div><div style="16px">For start I would be thankful for fact check - are facts that I listed<br></div><div style="16px">below actually facts or are hilarious misrepresentation of a legal<br></div><div style="16px">situation?<br></div><div style="16px"><br></div><div style="16px">tl;dr: Mapbox in at least some situations hides OSM attribution while<br></div><div style="16px">displaying their own logo and recommends to others to do the same.<br></div><div style="16px">Mapbox failed to fix problem that I reported to them in December 2018.<br></div><div style="16px"><br></div><div style="16px">---------<br></div><div style="16px"><br></div><div style="16px">For long time I hoped that it will be done by somebody else but it<br></div><div style="16px">appears less and less likely.<br></div><div style="16px"><br></div><div style="16px">I am irritated that despite attribution requirement almost all people<br></div><div style="16px">using OSM data have no chance to learn that they are doing this.<br></div><div style="16px"><br></div><div style="16px">It is caused by data consumers routinely ignoring attribution<br></div><div style="16px">requirements, in many case presenting OSM data like it was collected by<br></div><div style="16px">their company.<br></div><div style="16px"><br></div><div style="16px">---------<br></div><div style="16px"><br></div><div style="16px">Most things will have notes how sure I am about them as I may be making<br></div><div style="16px">hilarious misinterpretations. In such cases I would be thankful for an<br></div><div style="16px">explanation how I am mistaken.<br></div><div style="16px"><br></div><div style="16px"><br></div><div style="16px">1)<br></div><div style="16px">OSM data is ODBL licensed (100% sure)<br></div><div style="16px"><br></div><div style="16px">as specified at <a href="https://www.openstreetmap.org/copyright">https://www.openstreetmap.org/copyright</a><br></div><div style="16px"><br></div><div style="16px">2)<br></div><div style="16px">text of ODBL license is at<br></div><div style="16px"><a href="https://opendatacommons.org/licenses/odbl/1.0/index.html">https://opendatacommons.org/licenses/odbl/1.0/index.html</a> (100% sure)<br></div><div style="16px"><br></div><div style="16px">as specified at <a href="https://www.openstreetmap.org/copyright">https://www.openstreetmap.org/copyright</a><br></div><div style="16px"><br></div><div style="16px">3)<br></div><div style="16px">ODBL requires attribution (100% sure)<br></div><div style="16px"><br></div><div style="16px">4)<br></div><div style="16px">ODBL gives some minimal limits that attribution must fulfill (99% sure)<br></div><div style="16px"><br></div><div style="16px">"You must include a notice associated with<br></div><div style="16px">the Produced Work reasonably calculated to make any Person that uses,<br></div><div style="16px">views, accesses, interacts with, or is otherwise exposed to the Produced<br></div><div style="16px">Work aware that Content was obtained from the Database, Derivative<br></div><div style="16px">Database, or the Database as part of a Collective Database, and that it<br></div><div style="16px">is available under this License."<br></div><div style="16px"><br></div><div style="16px">5)<br></div><div style="16px">ODBL minimal limits are not fulfilled by attribution not<br></div><div style="16px">displayed when map is displayed full screen at a modern smartphone<br></div><div style="16px">(95% sure)<br></div><div style="16px"><br></div><div style="16px">For reference: I tested it on Xiaomi Redmi 4<br></div><div style="16px">- 5.0 inches, 68.9 cm2<br></div><div style="16px">- 1080 x 1920 pixels<br></div><div style="16px"><a href="https://www.gsmarena.com/xiaomi_redmi_4_prime-8263.php">https://www.gsmarena.com/xiaomi_redmi_4_prime-8263.php</a><br></div><div style="16px"><br></div><div style="16px">6)<br></div><div style="16px">Individual mappers have no legal standing against entities using OSM<br></div><div style="16px">data without attribution (filing DMCA notices, suing etc) (75% sure)<br></div><div style="16px"><br></div><div style="16px">7)<br></div><div style="16px">OSMF has legal standing against entities<br></div><div style="16px">using OSM data without attribution (99% sure)<br></div><div style="16px"><br></div><div style="16px">8)<br></div><div style="16px">I am not a Mapbox hater<br></div><div style="16px">(100% sure)<br></div><div style="16px"><br></div><div style="16px">I am focusing on Mapbox here. It does not mean that that others are<br></div><div style="16px">much better. It only means that I started digging in attribution<br></div><div style="16px">situation after encountering map hosted by them that was missing<br></div><div style="16px">attribution and I want to fix before proceeding to the next copyright<br></div><div style="16px">violation.<br></div><div style="16px"><br></div><div style="16px"><br></div><div style="16px">9)<br></div><div style="16px">Mapbox is in some situations using OSM data without giving a proper<br></div><div style="16px">attribution (95% sure)<br></div><div style="16px"><br></div><div style="16px">For example see <a href="https://www.mapbox.com/maps/">https://www.mapbox.com/maps/</a> - only one map is<br></div><div style="16px">attributed to OSM (though it is still in a way suggesting that part of<br></div><div style="16px">data is copyrighted by Mapbox - "© Mapbox © OpenStreetMap")<br></div><div style="16px"><br></div><div style="16px">Or see "view live map" from <a href="https://www.mapbox.com/maps/streets/">https://www.mapbox.com/maps/streets/</a><br></div><div style="16px">leading to<br></div><div style="16px"><a href="https://api.mapbox.com/styles/v1/mapbox/streets-v9.html?title=true&access_token=pk.eyJ1IjoibWFwYm94IiwiYSI6ImNpejY4M29iazA2Z2gycXA4N2pmbDZmangifQ.-g_vE53SD2WrJ6tFX7QHmA#1.07/-1.4/4.7">https://api.mapbox.com/styles/v1/mapbox/streets-v9.html?title=true&access_token=pk.eyJ1IjoibWFwYm94IiwiYSI6ImNpejY4M29iazA2Z2gycXA4N2pmbDZmangifQ.-g_vE53SD2WrJ6tFX7QHmA#1.07/-1.4/4.7</a><br></div><div style="16px"><br></div><div style="16px">on my Xiaomi Redmi 4 with following screen<br></div><div style="16px"><br></div><div style="16px">- 5.0 inches, 68.9 cm2<br></div><div style="16px">- 1080 x 1920 pixels<br></div><div style="16px"><br></div><div style="16px">it is hiding OSM attribution while displaying Mapbox attribution.<br></div><div style="16px"><br></div><div style="16px">See screenshot at<br></div><div style="16px"><a href="https://user-images.githubusercontent.com/899988/51281667-67210a80-19e3-11e9-807a-480de4fa8eea.png">https://user-images.githubusercontent.com/899988/51281667-67210a80-19e3-11e9-807a-480de4fa8eea.png</a><br></div><div style="16px"><br></div><div style="16px"><a href="https://docs.mapbox.com/help/tutorials/first-steps-android-sdk/">https://docs.mapbox.com/help/tutorials/first-steps-android-sdk/</a><br></div><div style="16px"><br></div><div style="16px">The very first image recommends to hide OSM attribution - but not<br></div><div style="16px">Mapbox logo<br></div><div style="16px"><br></div><div style="16px"><a href="https://docs.mapbox.com/help/img/android/android-first-steps-intro.png">https://docs.mapbox.com/help/img/android/android-first-steps-intro.png</a><br></div><div style="16px"><br></div><div style="16px">Their main site at <a href="https://www.mapbox.com/">https://www.mapbox.com/</a> is showing some maps, none<br></div><div style="16px">is attributing OSM (and I am suspecting that they are using OSM data<br></div><div style="16px">also there).<br></div><div style="16px"><br></div><div style="16px">10)<br></div><div style="16px">Mapbox is therefore in some situations illegally using OSM data<br></div><div style="16px">(95% sure)<br></div><div style="16px"><br></div><div style="16px">11)<br></div><div style="16px">Mapbox ignored my attempts to notify them about this issue<br></div><div style="16px">(100% sure)<br></div><div style="16px"><br></div><div style="16px">I contacted them via <a href="http://mapbox.com/contact/support/#attribution">mapbox.com/contact/support/#attribution</a> on<br></div><div style="16px">December 2018 and January 2019.<br></div><div style="16px"><br></div><div style="16px">Contact in the first case stopped after I asked them<br></div><div style="16px"><br></div><div style="16px">> So in opinion of Mapbox "click to view" attribution hiding is enough<br></div><div style="16px">> to cover "reasonably calculated to make any Person (...)"?<br></div><div style="16px"><br></div><div style="16px">In the second case they refused to answer at all.<br></div><div style="16px"><br></div><div style="16px">I also made a bit desperate attempt to contact them at<br></div><div style="16px"><a href="https://www.openstreetmap.org/user/lxbarth/diary/21847">https://www.openstreetmap.org/user/lxbarth/diary/21847</a> (this user is no<br></div><div style="16px">longer active - last edit 6 months ago, last diary entry in 2015 about<br></div><div style="16px">his desire to be on OpenStreetMap US board of directors).<br></div><div style="16px"><br></div><div style="16px">Title of this thread is also attempt to get problem noticed by someone<br></div><div style="16px">at Mapbox who can fix the mentioned problems (or provide explanation<br></div><div style="16px">why it is not a problem).<br></div><div style="16px"><br></div><div style="16px">12)<br></div><div style="16px">This is likely to not be a deliberate attempt to misrepresent OSM data<br></div><div style="16px">as something owned by Mapbox.<br></div><div style="16px"><a href="https://www.openstreetmap.org/user/lxbarth/diary/21847">https://www.openstreetmap.org/user/lxbarth/diary/21847</a> indicates that<br></div><div style="16px">at least in 2014 they were improving<br></div><div style="16px"><br></div><div style="16px">It is possible that it is just treated as one of unimportant issues on<br></div><div style="16px">giant pile of bugs that will be never fixed - any serious software<br></div><div style="16px">project has hundreds or thousands of those. (status: pure guessing)<br></div><div style="16px"><br></div><div style="16px">13 and final)<br></div><div style="16px">I am not sure how to proceed and how to convince Mapbox that missing<br></div><div style="16px">attributing is a serious problem that needs to be fixed (and not put on<br></div><div style="16px">pile of "low priority bug, will be never fixed") and that following OSM<br></div><div style="16px">license is not optional.<br></div><div style="16px"><br></div><div style="16px">For start I would be thankful for fact check - are facts that I listed<br></div><div style="16px">actually facts or are hilarious misrepresentation of a legal situation?<br></div> </body>
</html>