The source linked, for village boundaries in India, requires printed attribution on the map or a link for online maps:
“Attribute Please use the following lines to attribute the maps if you use in your work. You could link instead of printing the URLs in case of web projects. Villages Maps Provided by Indian Village Boundaries Project [ http://projects.datameet.org/indian_village_boundaries/] by Data{Meet}. Its made available under the Open Database License (ODbL)[ http://opendatacommons.org/licenses/odbl/].” So that source of data also expects visible attribution from map makers. — Joseph Eisenberg On Thu, Apr 30, 2020 at 8:20 AM Tom Lee via talk <talk@openstreetmap.org> wrote: > At the risk of repeating others' words, I strongly encourage participants > in this conversation to review the draft attribution guideline ( > https://wiki.openstreetmap.org/wiki/Draft_Attribution_Guideline) and > previous conversations regarding attribution on this list. It would be hard > to overstate the depth of experience that the legal working group has > regarding these issues, so it has been surprising to me to see their > perspective receive so little attention. > > Because I know not everyone will dig back into those listserv archives, I > want to highlight one point that has been previously made: OpenStreetMap > itself does not meet the ODbL attribution standards that are being > presented as obvious by some parties to this conversation. This applies not > only to several ODbL data source attributions present on > https://wiki.openstreetmap.org/wiki/Contributors (but not on the map) but > also to the many ODbL data sources that can be found under > https://wiki.openstreetmap.org/wiki/Category:Data_sources (note that not > all of these sources may be in use; this part of the wiki is not > sufficiently organized to be sure). > > OpenStreetMap is by far the most significant project using ODbL, and when > geodata is published under ODbL terms (as frequently happens in France[1]) > or when it is adopted by a geodata project (such as Datameet's work on > Indian village boundaries[2] > <http://projects.datameet.org/indian_village_boundaries/>) it is > typically with the intent of making the data useful to OpenStreetMap. It > doesn't seem plausible that the volunteers working on those Indian village > boundaries expect their preferred attribution[3] to be part of the UI that > greets any OSM user. This suggests to me that volunteers' attribution > expectations are not as uniform as has been suggested in this thread. > > Reviewing the diversity of attribution policies found under > https://wiki.openstreetmap.org/wiki/Category:Data_sources might prove > more illuminating than rehashing our understanding of Google's terms and > what they might or might not do for enterprise customers. A review of the > many custom government licenses and amended CC-BY licenses that OSM > volunteers have added to those wiki pages will show a variety of approaches > to attribution, almost none of which meet the level of obtrusiveness > proposed at various times in this thread. Obviously, the ODbL is its own > beast; as others have noted, the practices of the rest of the open mapping > world and commercial mapping industry need not bind it. But I do think they > are a useful signal as we consider what "reasonable" could mean. > > [1] > https://wiki.openstreetmap.org/wiki/FR:Sources_de_donn%C3%A9es_potentielles/France > [2] http://projects.datameet.org/indian_village_boundaries/ > [3] "Villages Maps Provided by Indian Village Boundaries Project [ > http://projects.datameet.org/indian_village_boundaries/] by Data{Meet}. > Its made available under the Open Database License (ODbL)[ > http://opendatacommons.org/licenses/odbl/]"; > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
