On Sat, Jan 19, 2019 at 11:33 AM Eugene Podshivalov <[email protected]> wrote:
> Hi Andrea, >> >> are you talking about cached tiles or just on the fly meta-tiling done on >> wms requests with tiled=true? > > I'm talking about the latter. I'm using OpenLayers to request tiles from > Geoserver wms. When meta-tiling is disabled (tile=true is not defined) it > is possible to request tiles of greater size and dpi (e.g. 320x320 px size > and 113 dpi) to improve image quality. Then I decided to switch to > meta-tiling to resolve the issues with duplicated labels but it is limited > to 256x256 tile size which impacted the map image quality. > Right... I guess it could be done, it's a matter of someone coding it, and probably adding a parameter to control the tile size (within reason, on the fly meta-tiling keeps tiles in memory for a handful of seconds, there is no caching). 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 > PS: Thanks for the link. I've seen it already, and that is why I started > the process from descussing the request on the mailing list. Is there some > issue tracking system to post this request into? > Yes, here: https://osgeo-org.atlassian.net/projects/GEOS/summary 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
