ol-stac migration #531

[m-mohr]

Implements/Fixes

• ol-stac migration #531
• WMS hidden by thumbnails #503 - dev example
• When web-map-links are rendered on map half opacity fill of bbox feature partially covers data #345
• Browser showing smeared thumbnails #369 - example
• Inversion of image outside of BBOX in STAC Browser #407
• add support for decent GeoTIFF compression algorithms: LERC_ZSTD, WEBP, etc. #538

Open issues:

• When navigating between pages, the map sometimes shows unexpected results
• Label extension support - good example missing
• WMS basemaps from USGS don't show up (i.e. are white) and no previews - dev example 1 2
• ItemCollection example doesn't show all items correctly m-mohr/ol-stac#22 (not released in ol-stac yet)
• Communication between assets ("Show on map" / "shown" badge) and the map needs to be implemented - see also Refactor communication between map and assets #314
• GeoJSON visualization support
• Show popovers directly next to the footprint, if possible.
• Potentially check event.layer.setStyle is not a function error for POINT geometries #554

Potential features to be considered:

• Show thumbnail if map is empty #383
• User-selectable options, e.g. number of previews on map #411 (comment)
• Better display of multispectral / surface reflectance data #309 - example
• Authentication support Support Auth (custom headers & query parameters) m-mohr/ol-stac#5
• stac-js migration Fully embrace stac-js in the codebase #546
• WMS web map link support (potentially only needs to be tested)
• Switching between baselayers of different projections
• "Reset" button to get back to the default view
• Panel to customize GeoTiff rendering (min, max, band combinations, etc)
• More advanced basemaps (e.g. swisstopo's WMTS or VestorTiles with EPSG:2056)
• buildTileUrlTemplate in config.js as an async function buildTileUrlTemplate in config.js as an async function #373

Breaking changes:

• Removed maxPreviewsOnMap
• buildTileUrlTemplate default to null now. The function has a different signature now, an Asset object (see stac-js) is passed as only argument. No other parameters are passen. To get the absolute url for the URL constuction, use asset.getAbsoluteUrl()
• basemaps.config.js has a new format. Multiple basemaps per planet can be provided. The default behaviour of configureBasemap has changed, including a removal of the map parameter.

[luipir]

great :)

[luipir]

@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.

[m-mohr]

@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.

[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 :)

[luipir]

FYI, not clear to me if this is a regression or the issue was there before but I can't draw BBOX to set up spatial extent to prepare a spatial query to the catalog.
There is a trigger of many errors and no way to draw a polygon. BTW the extent of the current show map is used to setup the spatial query

[m-mohr]

@luipir You should be able to create a bbox regardless of the error. Please be aware that it was not a "drawing" mechanism (click & drag) to create the initial bbox, instead it was a single click and then you can adjust from there. I just implemented shift click & drag as well to create a bounding box.

Nevertheless, the error has also been fixed. Thanks.

[luipir]

FYI some other glitches that are not present in main.

1. The error appear ONLY after the spatial query is executed
2. there is not a zoom to the BBOX of the union of bboxes of the query results and the main map is shown at whole earth level.

• IMHO a good feature in the search box map is to fit to the catalog bbox as starting point. BTW it is a feature not a bug.
  

p.s. sorry if I can't help in fixing directly the code, I'm not so expert in vue framework to be more effective helping you :/

[m-mohr]

@luipir I think both issues should be fixed/implemented now.

[luipir]

@luipir I think both issues should be fixed/implemented now.

right has been fixed, but still having select item issue.

[luipir]

FYI is it already an main issue that after dig into an item selected via search gui , than "back" start from a brand new query without remind what was the previous search setup?

[m-mohr]

@luipir I can't reproduce the selection issue, unfortunately. Are your dependencies up to date? Can you link me to an example?

It's indeed a bit cumbersome that the Search doesn't remember the search query, but that's a different issue and tracked via #393. It's major effort to improve this. I recommend opening items in a new tab for now.

[luipir]

It's indeed a bit cumbersome that the Search doesn't remember the search query, but that's a different issue and tracked via #393. It's major effort to improve this. I recommend opening items in a new tab for now.

ok, no problem

[luipir]

@luipir I can't reproduce the selection issue, unfortunately. Are your dependencies up to date?

checking with a clean install

Can you link me to an example?

I already shared times privately a set of json and link to real images.

[m-mohr]

I already shared times privately a set of json and link to real images.

Yes, but only static files. Search doesn't work on static files and it takes too much time to set up a whole new fastapi instance just to test this, sorry.