On Wed, Mar 4, 2020 at 10:24 AM David I <[email protected]> wrote: > This might be useful for a client, to read and construct a legend, I > imagine. >
Correct > > What seems to not be present in the json response (when the > getLegendGraphic > call is made without a scale parameter and otherwise) are the > minscaledenominator and maxscaledenominators. The rules are elsewise > returned wholly, it seems. So you get all the rules present in the SLD file > but you can't tell which rules apply to which scale levels, if dealing with > a scale-dependant style and not wishing to make the getLegendGraphic call > every time the map is zoomed. > The format mimics the raster one, if no scale is provided, all rules are depicted, if it is, only the ones active at the current scale are. Am I misunderstanding part of its purpose? > Not really, but it could be you're misunderstanding the process... the initial contribution of a functionality is based on its sponsor requirements, rounded up with some community discussion, see the proposal that introduced it, it mentions explicitly the scales: https://github.com/geoserver/geoserver/wiki/GSIP-173 If you're not happy with the current status quo, it's possible to contribute a change or sponsor one, possibly enabling the fuller reporting with a "legend_options" key: https://docs.geoserver.org/latest/en/user/services/wms/get_legend_graphic/index.html#controlling-legend-appearance-with-legend-options See also: https://docs.geoserver.org/latest/en/docguide/contributing.html > Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 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-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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
