You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem primarily occurs when navigating to the "Search" tab, where we can only select the ecosystem-characteristics-alpha2 collection, even though there are many more collections available. In our local deployment of the browser, we are using the SB_apiCatalogPriority = "childs" environment property to prevent any duplicate entries from appearing in the "Browse" tab. However, this does not seem to impact the Search tab.
This behavior is somewhat strange, and it is unclear why this is happening. We would greatly appreciate more insights into whether this behavior is expected and any guidance on how to resolve this situation.
The text was updated successfully, but these errors were encountered:
The self link in each collection in the /collections endpoint all point to https://catalogue.weed.apex.esa.int/collections, which confuses the database as it uses the URL as the primary key for identification. You'll have to fix the self links then it should work. If this doesn't help, please let me know and I'll reopen the issue.
We are seeking support regarding an issue with one of our STAC catalogs and its visualization in the browser. The example can be found at: https://radiantearth.github.io/stac-browser/#/external/catalogue.weed.apex.esa.int/.
The problem primarily occurs when navigating to the "Search" tab, where we can only select the
ecosystem-characteristics-alpha2
collection, even though there are many more collections available. In our local deployment of the browser, we are using theSB_apiCatalogPriority = "childs"
environment property to prevent any duplicate entries from appearing in the "Browse" tab. However, this does not seem to impact the Search tab.This behavior is somewhat strange, and it is unclear why this is happening. We would greatly appreciate more insights into whether this behavior is expected and any guidance on how to resolve this situation.
The text was updated successfully, but these errors were encountered: