Thanks guys... that took a while to understand!
Hopefully this thread helps the next person.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Mapbox-vector-tile-cache-tp5327585p5328321.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
I think so - metatiling doesn't make any sense for VTs. I thought it was
automatically disabled...
Dave
On Tue, Jul 18, 2017 at 11:12 AM, Nuno Oliveira <
nuno.olive...@geo-solutions.it> wrote:
> Ah! I didn't think about that. So since meta tiling is enabled by default
> (4x4)
> this means that
Ah! I didn't think about that. So since meta tiling is enabled by default (4x4)
this means that for using vector tiles with GWC in the best conditions meta
tiling should deactivated (set to 1x1) ?
On 07/18/2017 06:13 PM, Dave Blasby wrote:
Hi, Ben,
Metatiling doesn't work with Vector Tiles.
Hi, Ben,
Metatiling doesn't work with Vector Tiles. Metatiling, basically, has the
WMS create an image 4* (in both directions) as large and then GWC breaks it
into 16 smaller images. This helps with labelling.
You cannot (easily) cut up vector tiles, so you cannot do this with vector
tiles
Had some time to pick this up again today and have found that it's the tile
seeding process that's causing me issues, or more accurately the use of
metatiling with vector tiles. Once the tiles are seeded with a metatileing
factor of 1x1 i get a 100% HIT on the cache as expected using WMTS. If i
On 18-07-17 00:53, Attila Peller wrote:
> Hi,
> On windows if Geoserver is installed as service, the port (8080) is
> configured in the registry!!
> All configuration files (wrapper.conf, jetty.xml) are ignored!
> I'm wondering why on the earth is like that and why this isn't
> documented???