Hello Andrea, You're right, I will see on the client library side what it is possible.
I only find it surprising that GeoServer is capable of generating the GetLegend element in the WMS case and not in the WMTS case. Regards Alexandre Le sam. 21 mai 2022 à 19:08, Andrea Aime <andrea.a...@geosolutionsgroup.com> a écrit : > On Fri, May 20, 2022 at 1:28 PM Alexandre Gacon <alexandre.ga...@gmail.com> > wrote: > >> Hi, >> >> I have a layer group I would like to access with WMTS with some JS >> library (ol-ext) using the WMTS GetCapability request. >> >> The library expects that the capability document contains a LegendURL in >> the style of a given layer to work. >> > > XML schema says: > > element ref="wmts:LegendURL" *minOccurs="0"* maxOccurs="unbounded"> > <annotation> > <documentation>Description of an image that represents the legend of the > map</documentation> > </annotation> > </element> > > A client should not assume it's there. > > >> If such LegendURL exists for classic layers, it is not present for a >> layer group with only the default style. >> How could I have this item in the LegendURL document? >> > > By generating the link in the capabilities-writing code. A change is > needed in this method: > > > https://github.com/geoserver/geoserver/blob/fd7aa31105849dad95c0b443f68e838e29117bf8/src/gwc/src/main/java/org/geoserver/gwc/layer/GeoServerTileLayer.java#L1385 > > It should also consider that groups can have multiple styles in 2.21.x > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 333 8128928 > > https://www.geosolutionsgroup.com/ > > 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 > -- Alexandre Gacon
_______________________________________________ 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
