tracked by: https://osgeo-org.atlassian.net/browse/GEOS-10169
Il giorno mar 27 lug 2021 alle ore 19:39 carlo cancellieri < geo.ccancelli...@gmail.com> ha scritto: > Hi Andrea, > thanks I'll start firing an issue to keep track of this. > > Hugo thanks for your questions, well actually geoserver is already > providing such functionality it's just not declaring that into the > GetCapabilities. > > 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: > Having a dimension called 'x' with values a,b,c you may want to query the > server with: > &DIM_x=a > or (if the server is supporting that) > &DIM_x=a,b > which may return granules from you both values of that dimension. > > 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) > > Best, > C. > > Il giorno mar 27 lug 2021 alle ore 16:47 Hugo Herrador Carrasco < > hugo.herra...@gmail.com> ha scritto: > >> I don't know if multipleValues attribute for dimension tag is natively in >> GeoServer or if you need a customization of your capability document. >> >> you mean having a layer with two different time dimension, for example, >> one with periocity of month and another with peridicity of days? >> would that mean having two time dimension declaration in the capability >> document or that possibility implies just one time name dimension >> declaration? >> >> If is the second case maybe next paragraph doesn't sound good (: >> >> A layer may provide a dimension declaration that has the same name >> attribute (case-insensitive matching) as a >> declaration in another layer. However, the dimension shall not be >> re-declared using the same name with >> conflicting units or unitSymbol attributes. Extent values, and the >> attributes default, nearestValue and >> multipleValues, may be different for each layer. >> >> Greetings, >> >> El lun, 19 jul 2021 a las 17:50, carlo cancellieri (< >> geo.ccancelli...@gmail.com>) escribió: >> >>> Dear List, >>> I've a question over the getCapabilities 1.3.0 related the WMS >>> dimensions. >>> I'm over geoserver 2.18.0 >>> >>> Into the standard definitions page (page 52) Table C.1 — Contents of a >>> dimension element >>> available here: >>> >>> https://portal.ogc.org/files/?artifact_id=14416 >>> >>> 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. >>> >>> What do you think? Should we add that or there are specific thoughts >>> over that attribute that I'm not aware of? >>> >>> Thanks. Regards. >>> C. >>> >>> -- >>> Mr. Carlo Cancellieri >>> *skype*: ccancellieri >>> *Twitter*: @cancellieric >>> *LinkedIn*: http://it.linkedin.com/in/ccancellieri/ >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >> >> >> -- >> Hugo Herrador Carrasco >> SP (+34) 659 26 84 11 >> hugo.herra...@gmail.com >> >> > > -- > Mr. Carlo Cancellieri > *skype*: ccancellieri > *Twitter*: @cancellieric > *LinkedIn*: http://it.linkedin.com/in/ccancellieri/ > -- Mr. Carlo Cancellieri *skype*: ccancellieri *Twitter*: @cancellieric *LinkedIn*: http://it.linkedin.com/in/ccancellieri/
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
