Fixes the use of storage CRS code from list of supported CRS #90
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.
...instead of the CRS name.
If no match can be found for the storage CRS codes in the list of supported CRS, the first of the storage CRS codes is used.
This is done to if possible fulfill the requirement in the specification of OGC API Features Part 2, that the storage CRS shall be one of the identifiers of the supported CRS.
Since we can't determine for the storage CRS which code was initially used to specify it, we use the list of supported query CRS for deegree OAF as a way to determine the desired code, if possible. So with these changes to fulfill the requirement of the OGC spec you need to specify the desired code for the storage CRS as part of the supported query CRS.
Solves #89