|
|
ccancellieri created an issue |
|
WMS multipleValues attribute to dimension looks missing into GetCapabilities |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.18.0 |
|
Assignee: |
Unassigned |
|
Created: |
27/Jul/21 7:51 PM |
|
Environment: |
linux ubuntu 20 |
|
Priority: |
|
|
Reporter: |
Medium|
looking at the standard definitions page (page 52) Table C.1 — Contents of a dimension element I see multipleValues=0|1 available as OPTIONAL attribute to the dimension. Now I also see that geoserver is using all the other parameters but not this one. We are working on a frontend and we would like to recognize (without having to specify over the frontend configuration) if the layer supports the multiple dimension values or not, not supposing that but checking the real backend capabilities so also checking for that attribute. MapServer is implementing that so I was wondering IF there’s a way to obtain the same attribute also from geoserver (already implemented). I know geoserver supports multiple values but from the url we can’t understand if it’s a geoserver and personally I would not add logic to frontend if the indication of that ‘may’ come from the backend. Example: When you have a custom dimension (but also works over time and elevation) you can have a list of values to select in the request. Let me make an example: What we are missing apparently is ‘multipleValue’ as attribute in the getCapabilities letting the clients know that the server is capable of returning tiles resulting from multiple values of the same dimension. It’s still unclear to me if this also apply to dimensions with interval or duration (my usecase at the moment is related only to lists of custom dimensions) |
|
|
|
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100170-sha1:ea3e94d) |
|
|
|
