> > it could also do something similar by reading and stacking on each other > different layer tiles.
Will it not mess up the labels? Cheers, Eugene сб, 19 янв. 2019 г. в 14:23, Andrea Aime <andrea.a...@geo-solutions.it>: > On Sat, Jan 19, 2019 at 12:00 PM Eugene Podshivalov <yauge...@gmail.com> > wrote: > >> A possible alternative is to actually put a tile cache behind the >>> requests, you can still use WMS request as long as "direct integration" is >>> on in the "caching defaults" and your >>> WMS request align to the tiles. This allows bigger tiles too. That's >>> what we normally do, so that we can use cached tiles for the common case, >>> but switch to on the fly generation when >>> the requested projection is not supported, or there are parameters >>> changing the >> >> There are a lot of criteria imposed on the direct integration to work and >> unfortunately referencing a single layer is one of them which does not let >> me unilize this approach. >> > > I see... well, a different approach could be to have GWC merge tiles on > the fly then. It already has a WMS mode where it merges nearby tiles to > answer a large WMS request, > it could also do something similar by reading and stacking on each other > different layer tiles. I see that as more useful than large metatiling, but > maybe it's just me. > > 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
