Dear all, a follow up on this one: https://github.com/geoserver/geoserver/wiki/GSIP-177 The proposal has been updated, as suggested, to include this in 2.17-RC and in a month from now to backport to 2.16.1. The PR for 2.17.x (master) is available here, and ready to merge: https://github.com/geoserver/geoserver/pull/3732 Thank you all for the feedback! On Wed, 2019-08-14 at 20:33 -0700, Jody Garnett wrote: > On Wed, 14 Aug 2019 at 11:02, Andrea Aime > it> wrote: > > On Wed, Aug 14, 2019 at 7:49 PM Jody Garnett > > m> wrote: > > > This proposal is targeted towards 2.16? We are days away from the > > > RC deadline ... > > > > Andrea did you have any feedback on this? I would expect hold off > until after freeze, wait a month and back port? > > > Same goes for the existing TIME and ELEVATION support for vectors, > > they could be done via CQL_FILTER. But CQL_FILTER cannot be > > discovered by a generic OGC WMS client, custom dimensions are > > instead part of the WMS standard. > > > That makes perfect sense, a real gap in the standards not having a > good overview of available values for attributes. > > > > - Do you have an example of WMS 1.1 and WMS 1.3 snippet > > > advertising custom dimensions, an identical approach as for time > > > > > It's really the same as the exiting support for raster custom > > dimensions (WMS does not tell you if a particular layer is vector > > or raster). > > Here is an example taken from a GeoServer serving a raster data set > > with dimensions time, elevation and REFERENCE_TIME: > > > Thanks. > > > > > - there is a risk of conflict between dimension parameters > > > (population=100 in the demo) and other keys, perhaps something > > > similar to vendor options should be considered? Imagine if I had > > > a dimension named format, angle or env? > > > > > The WMS specification handle this by asking the client to add a > > "DIM_" prefix in the request, so if the dimension is called > > "REFERENCE_TIME" the client will add a parameter > > &DIM_REFERENCE_TIME=value in the KVP request. > > > Okay there is a small mistake in the proposal where &poluation=10000 > was used. > > I am +1 on the proposal, +0 on including it in the 2.16-RC > timeframe... > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Regards, Nuno Oliveira == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. ==
Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
