Open anayeaye opened 3 weeks ago
@j08lue I think the fastest way for us to add thumbnails to our catalog is to just use the mdx thumbnails which means we will have many duplicated tiles in our browser. It also means we don't have anything as a placeholder for the landsat lakes/glaciers collections but IIRC we had thumbnails for those at one point. Do you recall where those are (maybe git history?) and do you think the duplicates will be OK?
Thumbnails from the Dashboard config are fine, @anayeaye.
I do not think we had thumbnails for the Landsat collections, so I created some. Sizes / aspect ratios are unfortunately not consistent.
Please crop and/or resample them, if need be. No worries if parts of the lakes or so get cut off.
landsat-c2l2-sr-antarctic-glaciers-thwaites
Screenshot from EO Dashboard
landsat-c2l2-sr-antarctic-glaciers-pine-island
Screenshot from EO Dashboard
landsat-c2l2-sr-lakes-vanern
Screenshot from EO Dashboard
landsat-c2l2-sr-lakes-lake-balaton
Screenshot from EO Dashboard
landsat-c2l2-sr-lakes-aral-sea
Screenshot from Planetary Computer
landsat-c2l2-sr-lakes-tonle-sap
Screenshot from Planetary Computer
landsat-c2l2-sr-lakes-lake-biwa
Screenshot from Planetary Computer
Should we generally name the thumbnails after the collection ID?
stac-spec + thumbnail attribution
We haven't yet planned how to handle attribution for the thumbnails we are using. Veda-config handles attribution in the dataset mdx file (example). veda config
media:
src: ::file ./caldor-fire--dataset-cover.jpg
alt: Hillside engulfed by a wildfire.
author:
name: Marek Piwnicki
url: https://unsplash.com/photos/WiZOyYqzUss
stac catalog In the stac-spec we have the provider object, but that feels odd to include the thumbnail producer alongside the data producers. Inside the asset object we have the description property where we could add author and the source url for the thumbnail. For reference we are adding assets to our collection metadata like this to make for a nicer stac-browser experience:
...,
"assets": {
"thumbnail": {
"title": "Thumbnail",
"description": "<???MAYBE thumb author here?>",
"href": "https://thumbnails.openveda.cloud/caldor-fire--dataset-cover.jpg",
"type": "image/jpeg",
"roles": ["thumbnail"]
}
}
I've added thumbnails to all the production collection metadata in PR #145 and published to https://test.openveda.cloud/ 🚀
What
We now have a bucket in MCP
s3://veda-thumbnails
that is publicly accessible via cloudfronthttps://thumbnails.openveda.cloud/
. Update production collection metadata to include these thumbnails as assets to improve the browser experience.Parent issues
124 #122
Notes
For a first pass at improving our browser experience we can use exactly the same thumbnails that are configured in the dashboard for our STAC collections. The thumbnails from veda-config/datasets have already been copied to the thumbnail bucket but the thumbnails in eic-config have not (there is a large amount of overlap, probably only the climdex-* thumbnails need to be copied to the thumbnail bucket.
For a collection in s3, you can identify the dataset name by searching the collection id in veda-config and using the data.mdx file to identify the appropriate thumbnail. Veda-config groups datasets so in this first pass some of our collections will have duplicate thumbnails.
Config mdx example
For the hls-events.ej.data.mdx configuration, the thumbnail
hls-events-ej--dataset-cover.png
is located in media attributes.STAC Collection metadata example
Thumbnail objects are added to the
assets
property of a collection with the keythumbnail
. If a collection does not already have an assets. See https://test.openveda.cloud/api/stac/collections/hls-l30-002-ej-reprocessed for an example of a collection with a thumbnail asset.veda-configs
AC
s3://veda-thumbnails
s3://veda-thumbnails
landsat-c2l2-sr-*
thumbnails identifieds3://veda-thumbnails