├── CONTRIBUTING.md ├── Facebook ├── Facebook.md ├── Facebook_application_hidden_partial_attribution_2019-09-29.png ├── Facebook_application_map_with_hidden_partial_attrribution_2019-09-29.png ├── Facebook_local_application_displayed_partial_attribution_2020-01-01.png └── Facebook_local_application_hidden_partial_attribution_2020-01-01.png ├── LICENCE.md ├── MAPS.ME ├── MAPS.ME.md ├── MAPS.ME_application_missing_attribution_misleading_one_present_screenshot_2019-09-09-17-44-05.png ├── attribution_flash_2020_later_it_got_even_worse.gif ├── attribution_flash_2020_later_it_got_even_worse.mp4 ├── attribution_flash_2021.gif ├── attribution_flash_2021.mp4 ├── attribution_flash_2021.png └── what_maps_me_shows_as_an_attribution_inline.png ├── Mapbox ├── Mapbox.md ├── Mapbox_attributes_itself_2019-12-30.png ├── Mapbox_attributes_itself_inline_example_2020-01-30.jpg └── missing_attribution_mapbox_attributed_itself.png ├── Moovit ├── Moovit application misssing proper attribution 2019-11-17, confirmation of OSM use.png ├── Moovit.md ├── Moovit_application_fixed_attribution_2020-11-07.png └── Moovit_application_misssing_proper_attribution_2019-11-17.png ├── PKP ├── mejl.txt └── openstreetmap_mapa_pkp_bez_źródła.jpg ├── README.md ├── Snapchat ├── OSM_data_without_proper_attribution_Android_app_2019-12-23.png ├── OSM_data_without_proper_attribution_website_2019-12-23.png ├── Snapchat.md ├── mail_to_Snapchat.md ├── report_to_Mapbox.md └── report_to_mapbox_2021.md ├── decostyl.pl ├── IMG_20190905_120736.jpg ├── IMG_20190905_120759.jpg ├── IMG_20190905_121103.jpg ├── IMG_20190905_121110.jpg ├── IMG_20190905_121119.jpg └── IMG_20190905_121131.jpg ├── report_templates ├── polish_text_to_artist.txt └── wiki_mail_template.md └── windy.com ├── android_missing_required_attribution-2020-01-25.mp4 └── android_missing_required_attribution-2020-01-25.png /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | Contributions adding examples of major violations are welcome! 2 | 3 | Note that here only uses by major entities will be listed - big organizations, large enough that they definitely have enough resources to fix the problem. 4 | 5 | 6 | Every page should have 7 | 8 | - clear statement that what given entity is doing is illegal 9 | - images documenting usage of OpenStreetMap data in violation of its licence (usually it is a missing attribution) 10 | - list of attempts done to fix this 11 | 12 | Pull requests can be opened early, but I will merge ones with delay if recent attempt to contact is really rece, to give them time to fix (at least 7 days). 13 | 14 | # Embedding videos 15 | 16 | Sometimes video is much better at demonstrating something. In such case include bpth original screen capture and gif for linking/embedding. 17 | 18 | For generating gif files from mp4 - see 19 | 20 | ``` 21 | ffmpeg \ 22 | -i input.mp4 \ 23 | -r 15 \ 24 | -vf "scale=512:-1,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse" \ 25 | -ss 00:00:20 -to 00:00:30 \ 26 | output.gif 27 | ``` 28 | 29 | note that `00:00:03 -to 00:00:06` is for converting between this timestamps. 30 | 31 | Code by "[Ciro Santilli 新疆再教育营六四事件法轮功郝海东](https://askubuntu.com/a/837574/349903)". 32 | -------------------------------------------------------------------------------- /Facebook/Facebook.md: -------------------------------------------------------------------------------- 1 | Note that [https://m.facebook.com/maps/attribution_terms/ 2 | ](https://m.facebook.com/maps/attribution_terms/ 3 | ), even with its own page is still failing to properly credit OSM. 4 | 5 | It is not mentioned clearly that OSM is the source of data (except some rare exceptions), OSM licence is still not clearly presented. -------------------------------------------------------------------------------- /Facebook/Facebook_application_hidden_partial_attribution_2019-09-29.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Facebook/Facebook_application_hidden_partial_attribution_2019-09-29.png -------------------------------------------------------------------------------- /Facebook/Facebook_application_map_with_hidden_partial_attrribution_2019-09-29.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Facebook/Facebook_application_map_with_hidden_partial_attrribution_2019-09-29.png -------------------------------------------------------------------------------- /Facebook/Facebook_local_application_displayed_partial_attribution_2020-01-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Facebook/Facebook_local_application_displayed_partial_attribution_2020-01-01.png -------------------------------------------------------------------------------- /Facebook/Facebook_local_application_hidden_partial_attribution_2020-01-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Facebook/Facebook_local_application_hidden_partial_attribution_2020-01-01.png -------------------------------------------------------------------------------- /LICENCE.md: -------------------------------------------------------------------------------- 1 | All map data, unless specified otherwise is from OpenStreetMap and available on the ODBL licence. 2 | 3 | Artworks, styles, icons, interface elements used to make maps depicted in this repositiry may be copyrighted. All of them are used under fair use to document illegal actions of entities described here. 4 | 5 | Text published here is licenced under CC0 licence (unless specified otherwise), feel free to copy and reuse it. -------------------------------------------------------------------------------- /MAPS.ME/MAPS.ME.md: -------------------------------------------------------------------------------- 1 | # Mapsme is using OpenStreetMap data illegally 2 | 3 | This company is using OpenStreetMap data. It is a good news, but unfortunately this company failed to credit authors of this data. 4 | 5 | Note that OpenStreetMap data is available for free and there are very limited requirements. And they still failed to follow them, [what is not OK](../README.md). Note that it is also illegal, as ODBL licence used by OpenStreetMap requires proper attribution, and requires it to be properly displayed. Hiding one in place where noone will see it is both against the common sense [and the licence](../README.md). 6 | 7 | ![what_maps_me_shows_as_an_attribution_inline.png](what_maps_me_shows_as_an_attribution_inline.png) 8 | 9 | ## Fixing 10 | Can be easily fixed by replacing misleading attribution "MAPS.ME" in the bottom right corner by `© OpenStreetMap, © Booking.com for misplaced hotels` or `map data except hotel ads © OpenStreetMap` or `map data © OpenStreetMap, © Booking.com for misplaced hotels, style © MAPS.ME` or something similar. 11 | 12 | Missing attribution may be also partially remediated by adding something like "Powered by OpenStreetMap data" at the startup screen. 13 | 14 | There is a deeply hidden and insufficient attribution. It is not in a place ever visited by a typical user. 15 | 16 | Attribution text will appear on the map, immediately after opening the app but only for [2 seconds and half-hidden](attribution_flash_2021.gif). If you cannot spot it then maybe [this image will help you find it](attribution_flash_2021.png). 17 | 18 | 19 | 20 | ## Reported 21 | 22 | - [https://github.com/mapsme/omim/issues/11203](https://github.com/mapsme/omim/issues/11203) - 2019 VII 23 | - [https://github.com/mapsme/omim/issues/11845](https://github.com/mapsme/omim/issues/11845) - 2019 X 24 | 25 | ## Reaction of the company 26 | 27 | As of 2021-06-20 MAPS.ME attribution text remains pernamently visible while OpenStreetMap attribution is barely visible, in violation of the OpenStreetMap data license. 28 | 29 | On 2019-07-18 they [posted](https://github.com/mapsme/omim/issues/11203#issuecomment-512743377) "Hi, we will add info to the loading screen in one of the upcoming releases. That is a good idea. Thanks!" 30 | 31 | This claim turned out to be untrue. Instead, in of updates released in 2021 attribution shown for just two seconds become futher obscured. 32 | 33 | 34 | ## Problem reproduction 35 | 36 | 1. Install MAPS.ME on an Android phone, run it. 37 | 2. Try to find a required attribution. 38 | 39 | ## Typical MAPS.ME interface using OpenStreetMap data 40 | 41 | Note that OpenStreetMap is not presented as a source. Instead there is a misleading "MAPS.ME" attribution in bottom right corner. MAPS.ME is allowed to use OpenStreetMap data for free (like everybody else) but is required to include a clearly visible attribution (like everybody else). 42 | 43 | ![MAPS.ME_application_missing_attribution_misleading_one_present_screenshot_2019-09-09-17-44-05.png](MAPS.ME_application_missing_attribution_misleading_one_present_screenshot_2019-09-09-17-44-05.png) 44 | -------------------------------------------------------------------------------- /MAPS.ME/MAPS.ME_application_missing_attribution_misleading_one_present_screenshot_2019-09-09-17-44-05.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/MAPS.ME/MAPS.ME_application_missing_attribution_misleading_one_present_screenshot_2019-09-09-17-44-05.png -------------------------------------------------------------------------------- /MAPS.ME/attribution_flash_2020_later_it_got_even_worse.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/MAPS.ME/attribution_flash_2020_later_it_got_even_worse.gif -------------------------------------------------------------------------------- /MAPS.ME/attribution_flash_2020_later_it_got_even_worse.mp4: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/MAPS.ME/attribution_flash_2020_later_it_got_even_worse.mp4 -------------------------------------------------------------------------------- /MAPS.ME/attribution_flash_2021.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/MAPS.ME/attribution_flash_2021.gif -------------------------------------------------------------------------------- /MAPS.ME/attribution_flash_2021.mp4: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/MAPS.ME/attribution_flash_2021.mp4 -------------------------------------------------------------------------------- /MAPS.ME/attribution_flash_2021.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/MAPS.ME/attribution_flash_2021.png -------------------------------------------------------------------------------- /MAPS.ME/what_maps_me_shows_as_an_attribution_inline.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/MAPS.ME/what_maps_me_shows_as_an_attribution_inline.png -------------------------------------------------------------------------------- /Mapbox/Mapbox.md: -------------------------------------------------------------------------------- 1 | # Mapbox is using OpenStreetMap data illegally 2 | 3 | Mapbox is using OSM data. It is a good news that such service as hosting OSM data is available. But unfortunately this company failed to properly credit OpenStreetMap mappers. 4 | 5 | ![Mapbox_attributes_itself_inline_example_2020-01-30.jpg](Mapbox_attributes_itself_inline_example_2020-01-30.jpg) 6 | 7 | Mapbox is not source of data used to display this map. They are obligated to make this clear, but failing to fullfil their obligation. 8 | 9 | This specific image is from [one of their example pages](https://api.mapbox.com/styles/v1/mapbox/streets-v9.html?title=true&access_token=pk.eyJ1IjoibWFwYm94IiwiYSI6ImNpejY4M29iazA2Z2gycXA4N2pmbDZmangifQ.-g_vE53SD2WrJ6tFX7QHmA#1.07/-1.4/4.7). It has no real attribution when opened on a mobile or when browser window is resized to a smaller one. 10 | 11 | Note that there is space for displaying info. There is a big Mapbox logo, the company name is mentined twice. But they decided to hide mentioning who actually collected this data. 12 | 13 | Note also that small attribution apearing on a larger screen is not sufficient. It is not making clear that data used to make this map is from OpenStreetMap (except terrain shading). 14 | 15 | Current presentation misleads users in thinking that Mapbox is using here some data controlled by this company. 16 | 17 | Mapbox here hosts OpenStreetMap data and applied map style to it. 18 | 19 | Mapbox contributed to growth of OpenStreetMap but it does not entitle them to start hiding attribution. 20 | ## Fixing 21 | 22 | This page may be easily fixed by replacing "mapbox" on the bottom line by "Data from OpenStreetMap, available on the [ODBL licence](https://www.openstreetmap.org/copyright)". 23 | 24 | Or by any other form of actually noticeable attribution. 25 | 26 | ## Legal status 27 | 28 | As reminder section 4.3 of the [Open Database License](https://www.opendatacommons.org/licenses/odbl/1.0/) used by OpenStreetMap: 29 | 30 | > "include 31 | > a notice associated with the Produced Work reasonably calculated to 32 | > make any Person that uses, views, accesses, interacts with, or is 33 | > otherwise exposed to the Produced Work aware that Content was 34 | > obtained from the Database, Derivative Database, or the Database as 35 | > part of a Collective Database, and that it is available under this 36 | > License." 37 | 38 | For case where OSM data is directly used to make a map, viewed by user it can be shortened and simplified to 39 | 40 | > include a notice associated with the map reasonably calculated to 41 | > make any Person that views the map aware that Content was 42 | > obtained from the Database and that it is available under the 43 | > ODBL License." 44 | 45 | Attribution used by Mapbox is presenting Mapbox as source of the map data. Mention of the real source of map data is hidden by default on mobile devices. 46 | 47 | It means that design used by Mapbox is failing to be a proper attribution. 48 | 49 | As result Mapbox is using OSM data in violation of the licence. 50 | 51 | Note that this is only one of multiple cases of Mapbox illegally using OSM data. 52 | 53 | 54 | ## Reported 55 | 56 | Mapbox was notified on 2019-01-09 about violating OpenStreetMap copyright on their own website, as there was no proper attribution. 57 | 58 | Mapbox report using [missing attribution form](https://support.mapbox.com/hc/en-us/requests/new?ticket_form_id=360000308212) was send on 29th December and assigned id 77176 as indicated by an automatic reply. 59 | 60 | - 2019-01-09 via email to a support 61 | - 2019-12-29 via [missing attribution form](https://support.mapbox.com/hc/en-us/requests/new?ticket_form_id=360000308212) 62 | - 2020-01-23 response to their email received two days earlier further explaining why their attribution is not sufficient to fullfil ODBL. 63 | 64 | ## Reaction of the company 65 | 66 | Mapbox failed to fix the problem as of 2021-06-20. Mapbox also failed admit that it is violating OSM licence. 67 | 68 | On 2020-01-21 I received an email claiming that Mapbox is following an ODBL licence. Email was written by a human and responding to my email. I send a reply pointing out their arguments that I consider to be a clear misintepretation of ODBL. 69 | 70 | I received no reply to that email. 71 | 72 | ## Map without a proper attribution 73 | 74 | ![Mapbox_attributes_itself_2019-12-30.png](Mapbox_attributes_itself_2019-12-30.png) 75 | -------------------------------------------------------------------------------- /Mapbox/Mapbox_attributes_itself_2019-12-30.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Mapbox/Mapbox_attributes_itself_2019-12-30.png -------------------------------------------------------------------------------- /Mapbox/Mapbox_attributes_itself_inline_example_2020-01-30.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Mapbox/Mapbox_attributes_itself_inline_example_2020-01-30.jpg -------------------------------------------------------------------------------- /Mapbox/missing_attribution_mapbox_attributed_itself.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Mapbox/missing_attribution_mapbox_attributed_itself.png -------------------------------------------------------------------------------- /Moovit/Moovit application misssing proper attribution 2019-11-17, confirmation of OSM use.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Moovit/Moovit application misssing proper attribution 2019-11-17, confirmation of OSM use.png -------------------------------------------------------------------------------- /Moovit/Moovit.md: -------------------------------------------------------------------------------- 1 | # Moovit is no longer hiding true source of map data :) 2 | 3 | This company is using OpenStreetMap data for their Android Application. It is a good news, especially as this company now credits authors of this data. 4 | 5 | # Previous situation 6 | 7 | There was only a deeply hidden and insufficient attribution. It was in a place never visited by a typical user. 8 | 9 | Rncountering it required 10 | 11 | - enabling sidebar 12 | - scrolling down sidebar 13 | - selecting "Partners" entry 14 | - as bonus, it shows CC-BY-SA as a licence and it is not clear what is credited to OpenStreetMap 15 | 16 | ## Reported 17 | 18 | Reported on the 13th September 2019 (moovitapp.zendesk.com assigned id 343713). 19 | 20 | Moovit was reminded about this issue by emailing them on 21 | 22 | - 11th November 2019 23 | - 27th November 2019 24 | - 6th January 2020 25 | 26 | On the 2019-12-07 it was reported to OSMF Legal Working Group, report was assigned id 2019120710000072. 27 | 28 | On the 2020-03-12 the problem was discussed during OSMF Legal Working Group meeting. The LWG will send a fax message. Hopefully it will be taken more seriously than my emails. 29 | 30 | It was fixed in September 2020, within year from the initial report. 31 | 32 | ## Reaction of the company 33 | 34 | Moovit failed to fix issue, failed to specify when it will be fixed. The company also failed to admit that there is actually something to be fixed. 35 | 36 | Their Android application continues to use OSM data illegally two months later (checked on 2020-01-23). 37 | 38 | On the 3th October Moovit representative replied claiming that they are consulting with their legal team. 39 | 40 | On the 12th November they claimed that it will be fixed "soon", what turned out to be untrue. As of 2020-01-23 it was their last activity. 41 | 42 | Note that Moovit is using OSM data also for their website and they are attributing OSM there, so they do not appear to be malicious/evil. 43 | 44 | It was fixed in September 2020, within year from the initial report. 45 | 46 | ## Typical Mooovit interface using OpenStreetMap data 47 | 48 | This screenshot ilustrates former state, now it is fixed. 49 | 50 | Applies to Android phones, iPhone app is using alternative data provider with a very low data quality. 51 | 52 | ![Moovit application misssing proper attribution 2019-11-17.png](Moovit_application_misssing_proper_attribution_2019-11-17.png) 53 | -------------------------------------------------------------------------------- /Moovit/Moovit_application_fixed_attribution_2020-11-07.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Moovit/Moovit_application_fixed_attribution_2020-11-07.png -------------------------------------------------------------------------------- /Moovit/Moovit_application_misssing_proper_attribution_2019-11-17.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Moovit/Moovit_application_misssing_proper_attribution_2019-11-17.png -------------------------------------------------------------------------------- /PKP/mejl.txt: -------------------------------------------------------------------------------- 1 | Dzień dobry! 2 | 3 | Wysyłam tego mejla zgodnie z rozmową wykonaną 15 minut temu 4 | na numer biura prasowego. 5 | 6 | Bardzo mi miło że znaleźliście przydatny sposób na użycie danych 7 | OpenStreetMap. Cieszę się że wyniki pracy mapujących są 8 | wykorzystywane poprzez wyświetlanie ich w pociągach PKP Intercity, 9 | na monitorach pokazujących lokalizację pociągu. 10 | 11 | Dane te są ogólnie dostępne i można je legalnie wykorzystać przy 12 | zachowaniu naprawdę małych wymagań. Jednym z wymogów, który i tak jest 13 | standardem przy wykorzystywaniu cudzej pracy jest podanie źródła 14 | danych. Wystarczy prosto podać źródło danych - np. 15 | "© OpenStreetMap contributors (ODBL)" 16 | lub 17 | "© edytujący OpenStreetMap (ODBL)" 18 | wyraźnie widocznym tekstem powinno wystarczyć. 19 | 20 | Niestety na waszych mapach wykorzystujące te dane z OpenStreetMap 21 | tego brak. 22 | 23 | Prosiłbym o poprawę tego błędu i podanie wymaganych licencją źródeł 24 | danych w swoich dziełach wykorzystujące dane z OpenStreetMap. 25 | 26 | Zapraszam do przejrzenia informacji o stanie prawnym danych 27 | OpenStreetMap na https://www.openstreetmap.org/copyright 28 | 29 | W załączniku jest zdjęcie jednej z tych map. 30 | 31 | Z poważaniem, 32 | Mateusz Konieczny -------------------------------------------------------------------------------- /PKP/openstreetmap_mapa_pkp_bez_źródła.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/PKP/openstreetmap_mapa_pkp_bez_źródła.jpg -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # OpenStreetMap 2 | 3 | OpenStreetMap is a project of mappers who together create map of the world. Created dataset can be used by anyone, for free, for any purpose. There are minimal requirements. Proper attribution is a fundamental one and very easy to fulfill - just mention who provided data that you use. 4 | 5 | OpenStreetMap data is used for many purposes, by individuals, in hobby projects, by scientists, governments and megacorporations. 6 | 7 | This data was collected by thousands of people with intention of being used and OpenStreetMap mappers are happy to see that it is happening. 8 | 9 | # Large scale plagiarism 10 | 11 | Unfortunately in many cases users of this great dataset are not attributing OpenStreetMap at all. They are using OpenStreetMap data illegally, despite that mentioning source of data is not hard. Hiding real source of data is both unethical and illegal. 12 | 13 | This project documents companies involved in this kind of plagiarism. The use OpenStreetMap data on a large scale and try to hide this. Smaller entities especially blatant in their plagiarism also may be listed. 14 | 15 | Currently following large scale plagiarisms are documented: 16 | 17 | - [MAPS.ME](MAPS.ME/MAPS.ME.md) that is using OpenStreetMap data and attributing it to MAPS.ME. It was reported to this company at 2019-07-10 18 | - [Mapbox](Mapbox/Mapbox.md) is not attributing OpenStreetMap on their website. They are informed about this problem since at least 2019-01-09 19 | - [Snapchat](Snapchat/Snapchat.md) failed to attribute OpenStreetMap in their app. They are informed about this problem since at least 2019-12-23 20 | 21 | Goal of this project is to document such persistent copyright violation. It is also documenting that it is not accident. This entities are aware about this and continue with this unethical and illegal practice. 22 | 23 | # Wait, there is a hidden attribution 24 | 25 | Some behave like hiding attribution in places where no one will see it and behave like it would be acceptable. It is not. 26 | 27 | Fortunately, this is also illegal. Note section 4.3 of the [Open Database License](https://www.opendatacommons.org/licenses/odbl/1.0/) used by OpenStreetMap: 28 | 29 | > "include 30 | > a notice associated with the Produced Work reasonably calculated to 31 | > make any Person that uses, views, accesses, interacts with, or is 32 | > otherwise exposed to the Produced Work aware that Content was 33 | > obtained from the Database, Derivative Database, or the Database as 34 | > part of a Collective Database, and that it is available under this 35 | > License." 36 | 37 | For case where OSM data is directly used to make a map, viewed by user it can be shortened and simplified to 38 | 39 | > include a notice associated with the map reasonably calculated to 40 | > make any Person that views the map aware that Content was 41 | > obtained from the Database and that it is available under the 42 | > ODBL License." 43 | 44 | Hiding attribution in settings, at the bottom, in "[About MAPS.ME](MAPS.ME/MAPS.ME.md)" entry is not 45 | 46 | > reasonably calculated to make any Person 47 | 48 | Similarly, attribution hidden by default behind a button is not reasonably calculated to make all people aware of what is the source of data. 49 | 50 | # How can I help? 51 | 52 | Any misleading claims, outdated information or typos? Please, [report them](https://github.com/matkoniecz/illegal-use-of-OpenStreetMap/issues)! 53 | 54 | Pull requests are even more welcome! Note that by making pull request you agree to licence your work under [CC0](https://creativecommons.org/publicdomain/zero/1.0/). See [licence file](LICENCE.md) for more info. 55 | 56 | # Similar projects 57 | 58 | [Lacking proper attribution](https://wiki.openstreetmap.org/wiki/Lacking_proper_attribution) page at the OSM Wiki has a very similar purpose. 59 | 60 | Main difference is that this project focuses on documenting cases of especially eggregious, persistent and large scale copyright violations. 61 | 62 | In addition, this project is intended to be self-contained and understandable by people unfamiliar with OSM, ODBL or licences. 63 | -------------------------------------------------------------------------------- /Snapchat/OSM_data_without_proper_attribution_Android_app_2019-12-23.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Snapchat/OSM_data_without_proper_attribution_Android_app_2019-12-23.png -------------------------------------------------------------------------------- /Snapchat/OSM_data_without_proper_attribution_website_2019-12-23.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/Snapchat/OSM_data_without_proper_attribution_website_2019-12-23.png -------------------------------------------------------------------------------- /Snapchat/Snapchat.md: -------------------------------------------------------------------------------- 1 | # Snapchat is using OpenStreetMap data illegally 2 | 3 | Snapchat is using OSM data, their map is really pretty and nice. It is cool that apparently OpenStreetMap was the best source. But unfortunately this company failed to properly credit OpenStreetMap mappers. 4 | 5 | Snapchat is not source of data used to display this map. They are obligated to make this clear, but failing to fullfil their obligation. 6 | 7 | ![OSM_data_without_proper_attribution_Android_app_2019-12-23.png](OSM_data_without_proper_attribution_Android_app_2019-12-23.png) 8 | 9 | ## Reported 10 | 11 | I send an [email to Snapchat](mail_to_Snapchat.md) to remind them about licencing obligation and that they are currently commiting a large scale copyright violation. Email was send on 2019-12-23. 12 | 13 | [Mapbox report](report_to_Mapbox.md) was send on 2019-12-23 and assigned id 77032 as indicated by an automatic reply. 14 | 15 | There is [special form for reporting copyright infringement](https://support.snapchat.com/article/infringement-reporting-about) but it would need to be filled by an official OSMF representative. 16 | 17 | On 2020-01-24 I asked also about what kind of date was given as a deadline for Snapchat. 18 | 19 | On 2021-02-22 I [reminded](report_to_mapbox_2021.md) Mapbox that they claimed to be doing something about this problem. 20 | 21 | ## Reaction of the company 22 | 23 | Snapchat failed to react, as of 2021-06-20 they continue to use OpenStreetMap data without required atttribution. 24 | 25 | Mapbox replied on 2020-01-13 that Mapbox reminded Snapchat about attribution requirements and that they gave Snapchat deadline. Email contained no specific info about the deadline. -------------------------------------------------------------------------------- /Snapchat/mail_to_Snapchat.md: -------------------------------------------------------------------------------- 1 | original mail send to Snapchat mail can be seen at https://github.com/matkoniecz/illegal-use-of-OpenStreetMap/blob/09ca6b5ef9aead85bf6298f83fe8b84ddcfa4ca0/Snapchat/report_to_Mapbox.md , this is a fixed version (ready for resending) 2 | 3 | Why Snapchat is using OpenStreetMap data illegally, without a proper 4 | attribution? 5 | 6 | Snapchat has Snapchat maps at for example https://map.snapchat.com with 7 | a ghost icon linking to a similar map within app, also without a proper attribution. 8 | 9 | This maps are using OpenStreetMap data. 10 | 11 | Using OpenStreetMap data for such purposes requires following odbl licence, 12 | see [https://www.openstreetmap.org/copyright](https://www.openstreetmap.org/copyright) for details. 13 | 14 | Odbl licence requires (among other requirements) a proper attribution. 15 | 16 | See [https://www.opendatacommons.org/licenses/odbl/1.0/index.html](https://www.opendatacommons.org/licenses/odbl/1.0/index.html) 17 | 18 | Note that attribution must be clearly visible to anyone using this map. 19 | 20 | "4.3 Notice for using output (Contents). Creating and Using a Produced 21 | Work does not require the notice in Section 4.2. However, if you 22 | Publicly Use a Produced Work, You must include a notice associated with 23 | the Produced Work reasonably calculated to make any Person that uses, 24 | views, accesses, interacts with, or is otherwise exposed to the Produced 25 | Work aware that Content was obtained from the Database, Derivative 26 | Database, or the Database as part of a Collective Database, and that it 27 | is available under this License." 28 | 29 | Note also "How to credit OpenStreetMap 30 | We require that you use the credit “© OpenStreetMap contributors”. 31 | 32 | You must also make it clear that the data is available under the Open 33 | Database Licence, and if using our map tiles, that the cartography is 34 | licenced as CC BY-SA. You may do this by linking to this copyright page." 35 | at [https://www.openstreetmap.org/copyright](https://www.openstreetmap.org/copyright). 36 | 37 | I am awaiting your response that such include information what you will do to stop this copyright infringement, when first effects will be visible and when problem will fully fixed. 38 | 39 | I attached screenshots providing evidence that Snapchat is using 40 | OpenStreetMap data in violation of its licence. 41 | 42 | -- Mateusz Konieczny 43 | 44 | ![Screenshot_20191223-191823.png](Screenshot_20191223-191823.png) 45 | ![Screenshot_20191223-194329.png](Screenshot_20191223-194329.png) 46 | -------------------------------------------------------------------------------- /Snapchat/report_to_Mapbox.md: -------------------------------------------------------------------------------- 1 | reported at [https://support.mapbox.com/hc/en-us/requests/new?ticket_form_id=360000308212](https://support.mapbox.com/hc/en-us/requests/new?ticket_form_id=360000308212) 2 | 3 | 4 | [https://map.snapchat.com/@41.335703,-95.590514,2.00z](https://map.snapchat.com/@41.335703,-95.590514,2.00z) page is missing proper 5 | attribution - it is not made clear that data is from OpenStreetMap and on 6 | the odbl licence. 7 | 8 | The same problem applies to the app, linked by ghost icon at the bottom. 9 | 10 | Note that OSM attribution according to the odbl licence must be clearly 11 | visible to users, hidden one is not sufficient. 12 | 13 | See "reasonably calculated to make any Person that uses, 14 | views, accesses, interacts with, or is otherwise exposed to the Produced 15 | Work aware that Content was obtained from the Database, Derivative 16 | Database, or the Database as part of a Collective Database, and that it 17 | is available under this License" in the licence 18 | -------------------------------------------------------------------------------- /Snapchat/report_to_mapbox_2021.md: -------------------------------------------------------------------------------- 1 | https://support.mapbox.com/hc/en-us/requests/new?ticket_form_id=360000308212 2 | 3 | Subject: Snapchat continues to illegally use OSM data 4 | 5 | url: https://play.google.com/store/apps/details?id=com.snapchat.android&hl=en_US&gl=US 6 | 7 | Map within app is missing a clearly visible attribution of OpenStreetMap data. 8 | 9 | Note that OSM attribution according to the odbl licence must be clearly visible to users, hidden one is not sufficient. 10 | 11 | See "reasonably calculated to make any Person that uses, views, accesses, interacts with, or is otherwise exposed to the Produced Work aware that Content was obtained from the Database, Derivative Database, or the Database as part of a Collective Database, and that it is available under this License" in the ODBL licence. 12 | 13 | This was reported to Snapchat and Mapbox in 2019 (id 77032) - see https://github.com/matkoniecz/illegal-use-of-OpenStreetMap/blob/master/Snapchat/Snapchat.md 14 | 15 | Mapbox replied on 2020-01-13 that Mapbox reminded Snapchat about attribution requirements and that they gave Snapchat deadline. Email contained no specific info about the deadline. 16 | 17 | Is Mapbox planning to take some actual action? -------------------------------------------------------------------------------- /decostyl.pl/IMG_20190905_120736.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/decostyl.pl/IMG_20190905_120736.jpg -------------------------------------------------------------------------------- /decostyl.pl/IMG_20190905_120759.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/decostyl.pl/IMG_20190905_120759.jpg -------------------------------------------------------------------------------- /decostyl.pl/IMG_20190905_121103.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/decostyl.pl/IMG_20190905_121103.jpg -------------------------------------------------------------------------------- /decostyl.pl/IMG_20190905_121110.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/decostyl.pl/IMG_20190905_121110.jpg -------------------------------------------------------------------------------- /decostyl.pl/IMG_20190905_121119.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/decostyl.pl/IMG_20190905_121119.jpg -------------------------------------------------------------------------------- /decostyl.pl/IMG_20190905_121131.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/decostyl.pl/IMG_20190905_121131.jpg -------------------------------------------------------------------------------- /report_templates/polish_text_to_artist.txt: -------------------------------------------------------------------------------- 1 | Dzień dobry! 2 | 3 | Bardzo mi miło że znaleźliście ciekawy i atrakcyjny sposób na użycie danych 4 | OpenStreetMap. Cieszę się że wyniki pracy mojej i innych mapujących są 5 | wykorzystywane w ciekawy sposób. 6 | 7 | Dane te są ogólnie dostępne i można je legalnie wykorzystać przy 8 | zachowaniu naprawdę małych wymagań. Jednym z wymogów, który i tak jest 9 | standardem przy wykorzystywaniu cudzej pracy jest podanie źródła 10 | danych. Wystarczy prosto podać źródło danych - np. 11 | "© OpenStreetMap contributors (ODBL)" 12 | lub 13 | "© edytujący OpenStreetMap (ODBL)" 14 | powinno wystarczyć. 15 | 16 | Niestety na waszych mapach wykorzystujące dla dróg dane z OpenStreetMap 17 | tego brak. 18 | 19 | Prosiłbym o poprawę tego błędu i podanie wymaganych licencją źródeł 20 | danych w swoich dziełach wykorzystujące dane z OpenStreetMap. 21 | 22 | Zapraszam do przejrzenia informacji o stanie prawnym danych 23 | OpenStreetMap na https://www.openstreetmap.org/copyright 24 | 25 | Z poważaniem, 26 | 27 | -------------------------------------------------------------------------------- /report_templates/wiki_mail_template.md: -------------------------------------------------------------------------------- 1 | [OSM Wiki has a mail template of a possible mail asking to add an attribution](https://wiki.openstreetmap.org/wiki/Lacking_proper_attribution/Example_email) 2 | -------------------------------------------------------------------------------- /windy.com/android_missing_required_attribution-2020-01-25.mp4: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/windy.com/android_missing_required_attribution-2020-01-25.mp4 -------------------------------------------------------------------------------- /windy.com/android_missing_required_attribution-2020-01-25.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/matkoniecz/illegal-use-of-OpenStreetMap/9349ade7e06f46129a6f9991d64fb5a09c2d4cb1/windy.com/android_missing_required_attribution-2020-01-25.png --------------------------------------------------------------------------------