> > One could further simplify this by adding a new flag in the request that > allows to filter the style, picking only the labeling parts, and the non > labeling ones, that would allow to reduce the style maintenance down to one > style per layer.
I currently do it by means of env variables which filter geometric or label parts within one style. The style is more complicated than it could be with your desired solution but I guess the result is the same, isn't it? But anyway if GWC can only stack images from different layers how would it resolve label conflicts if they are in different layers? Cheers, Eugene вс, 20 янв. 2019 г. в 11:00, Andrea Aime <[email protected]>: > On Sat, Jan 19, 2019 at 11:24 PM Eugene Podshivalov <[email protected]> > wrote: > >> I currently have 7 layers (and there will be more added later on). So for >> the labeling to work proper I would have to setup 7*7=49 label layers which >> is a bit more than "a bit of setup". >> > > I believe you just need 7, a GetMap allows you to list as many layers as > you want, the label request just has to list the currently active layers, > comma separated, with > their corresponding label styles. But you'd still need 2 styles per layer, > one without labels, and with. One could further simplify this by adding a > new flag in the request > that allows to filter the style, picking only the labeling parts, and the > non labeling ones, that would allow to reduce the style maintenance down to > one style per layer. > Something I've been wanted to do for a while, but cannot find a project to > sponsor this activity in working hours. > > 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
