So, for example, an item has geometry and a collection has one or multiple bounding boxes, so it starts to show that, of course. And then it looks into the assets, whether there are anything that it can render. So, for example, if there is a Cloud Optimized Geotiff, then it starts to render that and shows it to you based on the metadata that you have.

So, if there are min and max values, for example, it tries to stretch the values accordingly for nice visualization. And then, if there are other file formats, it can actually also pass that through a tile renderer so that you can also show those on the map. Then there is a Web Map Links extension which can link to other tile services such as WMTS, WMS, and that is also passed through.

This should be an animation, but in the PDF it doesn't work, so let's look at that in the demo. So, what it tries to visualize on the map is, in the end, a thumbnail, if it's available, a Geotiff, or all these different types of map visualizations, XYZ, WMS, WMTS, or PMTiles.

If there are lists of items and collections, it tries to render all of them with the bounding boxes and the images on the map. And there are events that you can hook into so that if you're clicking one of these,

for example, it shows you or gives you information about the stack entity that you have clicked. There are other ideas that came up. For example, stack layer is the same for Leaflet. There is another library that does the same for Leaflet. But what is it, for example, about Map Libre? Yesterday there was Terradraw, for example, so there's the idea.

Maybe we can just do the same there, where you have adapters for different mapping libraries and the whole business logic is the same. So that's something that if you're interested in other mapping libraries, that's something we can discuss, of course. That would be an interesting idea, I think. And then maybe integrating something like this also as components into these view component libraries would also be an interesting idea, just saw.

Let's quickly go into the demo because the animations don't work. Let's see whether that goes according to plan. So here's some examples, right? And they show you how to use the library and what it does.

So, for example, if I just render a stack item that has a coq file, it loads a map, shows the geometry and then starts to load the Cloud Optimized Geotab. You can zoom in, as usual, and then it loads the necessary tiles via HTTP range requests and shows them on the map. It's relatively simple. That's all the JavaScript that you need. You pretty much import the

stack layer group here, do all the other things that you need for open layers. It reprojects automatically if required, if you have this here, and then you pass in the URL to the stack entity or the stack object and then pretty much just add it to the map.

And there you go, that's it. If you have multiple lists of items, that just shows this. This is based because there are no cogs in the examples. It tries to do the best with the thumbnails, for example. And if you click them, that's the events here that you see. In this case, it just shows the ID that you clicked.

But you could show pop-ups or anything. So maybe just go through the examples, have a look. WMS loaded from a service here that is in the stack entity here, so if there is a link that points to WMS, you can specify which layers to show.

And then you have it. You could add, for example, a layer chooser here as well. And then, depending on which things you have, you can change the opacity of individual layers, etc. And that's it. The website is here. If you want to use it, it's on NPM. You can just install it and use it.

As I said, there is an equivalent for leaflet as well, which is called stacklayer. You can find it on NPM and GitHub as well. But maybe we can also just abstract it away and do one of these libraries for all mapping components at some point. Thanks.