Draft: WCS Coverage for multidimensional layers #332
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
tests/expectedoutputs/TestWCS/test_WCSDescribeCoverage_Multidimdata.xml
Outdated
Show resolved
Hide resolved
added 2 commits
January 31, 2024 12:34
adagucserverEC/CXMLGen.cpp
Outdated
| // Dims | ||
| for (size_t d = 0; d < layer->dimList.size(); d++) { | ||
| WMSLayer::Dim *dim = layer->dimList[d]; | ||
| if (dim->name.indexOf("time") != -1) { |
There was a problem hiding this comment.
Would it be possible to show for time the min/max and resolution?
When I do describecoverage on a KNMI Radar file there is no time dimension in the describecoverage. I think we have to accomodate for a webclient, for a webclient it would be useful to have this information to generate a UI.
There was a problem hiding this comment.
The resolution in the same way that we show in the getCapabilities description?
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.
As I wrote in the chat last month: Just some thoughts on the DescribeCoverage problem when it comes to including multidimensional layers. I thought maybe adding multiple AxisDescriptions would be the way to go, based on something I found in the documentation:
The optional and repeatable axisDescription/AxisDescription element (...) describes an additional parameter (that is, an independent variable besides space and time), and the valid values of this parameter, which GetCoverage requests can use to select subsets of a coverage offering. However, there is some info about the layer dimensions that it not straightforward to get (for example, min and max for a given dimension), so I am a bit stuck there. Or maybe I could make a different request to provide the metadata that we do have, independently of this standard. Another thing I've observed is that one AxisDescription for the bands of a raster is hardcoded everywhere. Typing this here so I don't forget, we can discuss later.