Collection names are duplicated

[drnextgis]

I'm running stac-browser v3 locally and pointing it at a private test stac catalog:

$ npm start -- --open --catalogUrl="https://stac-api.local

The catalog has 2 collections but stac-browser shows them two times:

As you can see names of collections are the same but its URLs a bit different:

• http://localhost:8080/collections/my-collection
• http://localhost:8080/http:/stac-api.local/collections/my-collection

[m-mohr]

Thanks for the report. Could you make the JSON available so that I can test against it?

[drnextgis]

Please tell me which stac endpoint I should call to make a json you need?

[m-mohr]

I guess from your report that it would be the JSON responses from both:

• http://stac-api.local (root catalog)
• http://stac-api.local/collections (collection list)

You can send it to the e-mail in my profile, if you don't want it to be publicly posted.

[drnextgis]

responses.zip

[m-mohr]

Thanks. The issue here is that you list catalogs as childs in the root catalogs with the same name as the collections in the collection endpoint. They get merged and thus they are there shown twice.

[drnextgis]

I use stac_fastapi-based stac catalog and can see in the code where it is happening. Do you think stac-browser should handle this case to filter out collections with same names?

[m-mohr]

Hmm, I'm not sure. I could probably try to detect duplicates based on the URL, but that may not always work perfectly if URLs differ slightly or collections have no self link etc.
I'd rather see this as an implementation issue or a best practice that should evolve in the API spec as I'm not sure why you'd want to list the collection twice (it also doesn't scale very well). I remember that we have discussed this issue before, but I guess nothing has been written / specified so far, at least I see related issues that are still open: radiantearth/stac-api-spec#137 and radiantearth/stac-api-spec#159 (comment)

[m-mohr]

@drnextgis This has been fixed, but may get another change once the issues above have been tackled in the API spec.

[drnextgis]

Thanks!