Datahub: fix some issues in query URL generation form #1106
Conversation
|
Affected libs:
|
|
📷 Screenshots are here! |
jahow
force-pushed
the
fix-ogc-api-url-generation
branch
2 times, most recently
from
37290df to
9172df7
Compare
If multiple collections are available in an endpoint then use the name in the online resource instead of the first collection
jahow
force-pushed
the
fix-ogc-api-url-generation
branch
from
9172df7 to
d6933a5
Compare
There was a problem hiding this comment.
@jahow thank you for implementing the fix!
When I tested the feature I was wondering if the changes in the url were only applied to the WFS endpoint. In the OGC API form I still see the old format:
Is that how it is supposed to be?
|
Thanks for the review! This change should be applied to all endpoints, whichever the protocol. Let me take a look |
|
@Angi-Kinas so I think it's behaving as expected. If you look at: https://data.lillemetropole.fr/data/ogcapi/collections/environnement_energie:jour_collecte?f=json The download link for the mimeType
|
* feat(ui): use mimeTypes in API form query url generation * feat(ui): use OGCAPI collection name if available If multiple collections are available in an endpoint then use the name in the online resource instead of the first collection
Description
This PR fixes #1067 to use the correct mime-type when generating an URL in the API form.
This also supports specifying a collection name alongside an OGC API link instead of having the URL already point to a specific collection.
Architectural changes
none
Screenshots
Quality Assurance Checklist
breaking changelabelbackport <release branch>label