> > Yes, by memory the scale range in the caps should report visibility: you > have a chance of seeing something in that range, outside of it, no chance > at all. > So, while I did not review the code, range union should be the way to go. > By extension, if you have a rule in any associated style that shows > features at all scales, then the range would disappear from the > capabilities (the layer has at least one > style where part of the features are always visible).
Very good, we'll play with this to improve our understanding over here. One other notion I've had is that GetFeatureInfo "should" return only features that are within the scale range of the request implied by bbox/width/height. Does that sound wacky to you? Thanks Peter On Thu, Oct 20, 2022 at 12:06 PM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > On Thu, Oct 20, 2022 at 5:14 PM Peter Rushforth <peter.rushfo...@gmail.com> > wrote: > >> It also lists quite a few styles for that layer. Among the styles listed >> for rail, there are a few rules, which have a different min/max scale >> specified >> (example) >> <https://github.com/OrdnanceSurvey/OS-Open-Zoomstack-Stylesheets/blob/master/GeoPackage/Styled%20Layer%20Descriptors%20(SLD)/Light%20style/rail%20-%20Light.sld>, >> but it seems perhaps the scale ranges among the different SLD docs and >> rules may be unioned and reported in the capabilities document as the >> single range above. >> > > Yes, by memory the scale range in the caps should report visibility: you > have a chance of seeing something in that range, outside of it, no chance > at all. > So, while I did not review the code, range union should be the way to go. > By extension, if you have a rule in any associated style that shows > features at all scales, then the range would disappear from the > capabilities (the layer has at least one > style where part of the features are always visible). > > >> I am wondering if the version of GeoServer would make any difference here >> - I am currently working with 2.20.4. >> > > Not that I can remember of, that code has been around for ages. > > 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 339 8844549 > > 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 >
_______________________________________________ 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
