Datahub: fix some issues in query URL generation form #1106
+77
−52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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