Hi, I've been experimenting with switching from WMS (tiled=true) to WMTS and I was surprised to find out that WMTS uses metatiling just like WMS. I'm ultimately trying to eliminate metatiling for performance reasons (locking seems to be my bottleneck, I'm okay hitting my postgis database more, I'd prefer lower per-tile latency than average latency across multiple tiles).
However, it seems like my WMTS requests are plagued by the classic labelling issues that WMS is affected by, unless metatiling is enabled. Philosophically, I understand why WMS is affected by the labelling issue but I guess I'm surprised that WMTS would also be affected by this since the concept of tiling is built-in to the protocol. With a single WMTS request, couldn't the backend understand that a single tile is just a small subset of a larger grid of tiles (knowledge that is missing from the WMS protocol), and therefore it can label accordingly, without metatiling? In essence, couldn't it consider the entire tile matrix as a "metatile" for styling purposes? Is this a deficiency with the current implementation or am I missing something? Thanks, Mitchell -- Mitchell Bösecke Partner and Senior Software Developer Forcorp Solutions Inc. (d) 780.733.0494 (c) 780.993.4746 (o) 780.452.5878
_______________________________________________ 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
