great :)

@m-mohr FYI this branch allow correctly stream from a local titiler, but not able to show any collection footprint served by eoAPI pgstac compose (removing stac-browser). Footprint is shown only for Items.

@luipir Your problem should be fixed.

Generally, I've tried to better document above what known issues exist, all other functionality should be back and working. You can start tests now.

@p1d1d1 No, not at all. Please check #548 though.

Hi @m-mohr is it intentional that item submenu now will open on the right of the ol-map? In main it will open just where the item BBOX is visualised (or where collection is visualised, I do not remember correctly). Could it be considered a regression?

p.s. rendering on Firefox anonymous windows with version 134.0.1 on Ubuntu if this could help

Another observation that I realised only now that COG preview is working correctly:
Item preview in a collection view DO NOT use buildTileUrlTemplate to render it, but just direct COG read.
In the screenshot on the left the collection view with inner items rendered directly without using buildTileUrlTemplate and on the right the item view that yes it uses the buildTileUrlTemplate.

In my case is a light problem because API follow a different authorization pattern.
Is there a reason why collection view do not use TileLayer to show it's item?

is it intentional that item submenu now will open on the right of the ol-map

No. I'll check whether the old behaviour is possible with OpenLayers. Due to WebGL rendering, it might be difficult though.

Item preview in a collection view DO NOT use buildTileUrlTemplate to render it, but just direct COG read. In the screenshot on the left the collection view with inner items rendered directly without using buildTileUrlTemplate and on the right the item view that yes it uses the buildTileUrlTemplate. [...] In my case is a light problem because API follow a different authorization pattern. Is there a reason why collection view do not use TileLayer to show it's item?

I'm not sure I fully understand what you are saying.
As a general note: Tile servers have been disabled by default in STAC Browser as the client-side rendering is better than before. If needed, tile server rendering can be enforced in custom deployments through the options buildTileUrlTemplate (set to a function) and useTileLayerAsFallback (set to false).

I'm not sure I fully understand what you are saying. As a general note: Tile servers have been disabled by default in STAC Browser as the client-side rendering is better than before. If needed, tile server rendering can be enforced in custom deployments through the options buildTileUrlTemplate (set to a function) and useTileLayerAsFallback (set to false).

not sure if it is a better rephrase of my question as been posted here where you already answered.

is it intentional that item submenu now will open on the right of the ol-map

This has been fixed, it shows now where the mouse click happened. It can't directly attach to the feature anymore as we support selecting multiple features now. Beforehand you could only select the topmost is multiple features were stacked over each other.

Once the next ol-stac release is released, STAC Browser will also highlight the selected features in red again and have a bit of a hit tolerance to click smaller geometries easier.

Thanks for the report @luipir .

This has been fixed, it shows now where the mouse click happened. It can't directly attach to the feature anymore as we support selecting multiple features now. Beforehand you could only select the topmost is multiple features were stacked over each other.

confirmed that it works now :)

Once the next ol-stac release is released, STAC Browser will also highlight the selected features in red again and have a bit of a hit tolerance to click smaller geometries easier.

:)

Thanks for the report @luipir .

thank you for the bug fix and new features :)