Open gbif-portal opened 7 years ago
Let me know if you need me to change anything on the map attribution
@MortenHofft, I don't know anything about links on the map itself or the layers. The requested change refers to the text on the page https://demo.gbif.org/citation-guidelines - comms?
Hey @dschigel - cleaning up some old issues. I'm having a bit of trouble understanding exactly what is missing here?
Someone needs to cite GBIF maps specifically. How to? Perhaps a section on that can be added to citation guidelines as @MortenHofft suggests, please consult with @ahahn-gbif on earlier requests for such citations, possibly came through helpdesk.
We occasionally get requests from users who e.g. want to include the screenshot of a map like the one from a dataset page (https://www.gbif.org/dataset/292a71df-588b-48fa-9ab5-29ae868ba88c) or other contexts in a presentations or a publication, and ask how that should be cited. If possible, we should add a paragraph on "GBIF maps" to https://www.gbif.org/citation-guidelines, but I'd need to check how that should be phrased.
I often see people citing species pages for using the map or simply describing a distribution. Ideally, they should be citing the occurrences of that species, but that would require downloading the data, which they don't need, because they're not doing any further analysis.
I've shared some ideas about how to improve this here gbif/portal16#624
I like the second ' simpler "cite data without downloading" option' @dnoesgaard proposes. From a practical standpoint, could we make such a service available throughout the site, or at least on some of the key content types that we know people do try to reference?
If we could, I'd suggest that we treat the service just as we do downloads by 1) requiring a user registration and 2) storing the DOI citation in their profile.
You already know how to cite the occurrence data on the map.
The GBIF base map (world map) uses:
Actually generating the map primarily uses a workflow developed by the OpenMapTiles project, but that workflow is built upon a lot of other work (PostGIS, PostgreSQL, Mapnik, messaging systems, Docker, Linux, ...)
Showing the map on the screen uses a Javascript library, in most cases OpenLayers but some pages use Leaflet.
Some maps, I think only the ones on individual occurrence pages, use a base map made by CartoDB, but again built from OpenStreetMap and other sources, and using a whole load of tools.
I think I'd prefer to cite to the data sources (OSM, Natural Earth) and credit the tools elsewhere, like the documentation or the project code on Github.
Then there's the copyright. The design of the map is copyrightable in two ways:
The choice of what data to include at each zoom level -- like only showing big roads at level 4 rather than 5 or whatever. These choices have been made by OpenMapTiles, and it's CC-BY: https://openmaptiles.org/schema/
The choice of how to style those features, like the colour and thickness of a road. For the bi-colour GBIF maps, that's GBIF developers (let's call them CC0?). For "Streets" it's again OpenMapTiles, and CC-BY: https://github.com/openmaptiles/osm-bright-gl-style
Sounds like we should change the map to simply redirect to a page where it is all described. Currently it looks like this - I thought that was it. OSM require attribution - I don't know anything about all the rest you mention Matt.
Aren't we overdesigning this a bit? I agree that for those who really want to know, a link to a page giving all the technical components could be nice, and it would be good style to credit them. To respond to the request of a user who asks "how should I cite your map when I include a screenshot in my publication", though, this is total overkill. I don't think it requires a service, either, just a standard citation phrase that included reference to GBIF occurrence data/network attribution, the page it was taken from (or just the dataset citation if the map is on a dataset page), datetime, and maybe the context (species occurrences for..., search result for...). Simply a text snippet added to https://www.gbif.org/citation-guidelines, so that the author can include attribution of the map they use in their text. No?
Maybe I am overcomplicating things, but I feel there are two separate, but connected issues here. If strictly talking about a citation for a screenshot of a map, then I agree with @ahahn-gbif. No real need for complicating things further. Properly citing data shown on a map is not as trivial, and I will continue my mission for improving such data citations in gbif/portal16#624.
In case you use OpenMapTiles schema and/or even partly our design - our CC-BY requires an attribution with a link visible on the map. @MattBlissett Do you use our preprocessed data for the entire world from OpenMapTiles.com Downloads?
You can, of course, do that. Your map and project are amazing and we are proud to see you use our open-source maps. It is very welcome and 100% free for non-commercial and research purpose. As our project is open-source you can also generate the vector tile data yourself with our code and use it without restrictions - but visible attribution is always required unless you purchase attribution exemption rights.
Products or services using maps derived from OpenMapTiles schema need to visibly credit "OpenMapTiles.org" or reference "OpenMapTiles" with a link to http://openmaptiles.org/.
For a browsable electronic map based on OpenMapTiles and OpenStreetMap data, the credit should appear in the corner of the map. For example:
© OpenMapTiles © OpenStreetMap contributors
For printed and static maps a similar attribution should be made in a textual description near the image, in the same fashion as if you cite a photograph.
Details are at https://openmaptiles.com/terms/ and https://github.com/openmaptiles/openmaptiles/blob/master/LICENSE.md#design-license-cc-by-40
GBIF is a lovely project!
Thank you @klokan - that is useful.
Just to be sure so we do this right - it is part of your license requirements to have your name visible at all times and not 'hidden' behind a popup as is the openlayers standard?
the way openlayers do it by default
If someone provides me with a full list of the names/links that should go on top of maps, then I will add them all. If there are other special requirements for how they should be displayed (logos, sizes etc), then let me know as well please.
Add a paragraph to Citation-guidelines for GBIF map
Perhaps, the way to generate the recommended citation for maps is to extend the Species page with Leaflet | © Mapbox OpenStreetMap contributors, those links in the bottom right of the map. Just need to asnwer this question for a single case, AH says there were many before.
fbitem-57ee03dd725ec36a7faf1f69bca70ff2ef3c507e Reported by: @dschigel System: Firefox 51.0.0 / Windows 10 0.0.0 Referer: https://demo.gbif.org/citation-guidelines Window size: width 1920 - height 1077 API log&_a=(columns:!(request,response,clientip),filters:!(),index:'prod-varnish-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499%20AND%20(request:%22%2F%2Fapi.gbif.org%22)')),sort:!('@timestamp',desc))&indexPattern=uat-varnish-&type=histogram) Site log&_a=(columns:!(request,response,clientip),filters:!(),index:'prod-varnish-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E399%20AND%20(request:%22%2F%2Fdemo.gbif.org%22)')),sort:!('@timestamp',desc))&indexPattern=uat-varnish-&type=histogram)