+1
Issue created: https://osgeo-org.atlassian.net/browse/GEOS-8228
On 07/19/2017 02:51 PM, Andrea Aime wrote:
Agreed. Can anyone open a bug report?
Cheers
Andrea
Il 19 lug 2017 3:48 PM, "Jason Newmoyer" mailto:ja...@newmoyergeospatial.com>> ha scritto:
I think we should consider this a b
Agreed. Can anyone open a bug report?
Cheers
Andrea
Il 19 lug 2017 3:48 PM, "Jason Newmoyer" ha
scritto:
I think we should consider this a bug. If metatiling doesn't apply to
Vector Tiles under any circumstances then it shouldn't effect it.
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606
I think we should consider this a bug. If metatiling doesn't apply to
Vector Tiles under any circumstances then it shouldn't effect it.
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
ja...@newmoyergeospatial.com
On Tue, Jul 18, 2017 at 10:08 PM, Ben Jerrim
wrote:
> Thanks guys...
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. Met
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 (on
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
lea
Ah, i see two very different things on your request string. You're using the
WMTS service and addressing GWC directly. I was using WMS for my vector tile
requests and expecting the geoserver integration with geowebcache to handle
the cache lookup.
I've updated my requests to use the WMTS and dire
Hi,
I just made a test with trunk GeoServer, I basically perform this request
several times:
http://localhost:8075/geoserver/gwc/service/wmts?REQUEST=GetTile&SERVICE=WMTS&VERSION=1.0.0&LAYER=sf:AggregateGeoFeature&STYLE=&TILEMATRIX=EPSG:4326:6&TILEMATRIXSET=EPSG:4326&FORMAT=application/x-protob
Hey Nuno, if i seed the layer for png8 and request these tiles, i get a 100%
HIT on the cache for the requests. If i seed the same layer for the
mapbox-vector format I get about a 10% HIT on the cache. Apart from the
format value, the request query string is identical. I'm using the default
'line'
Hi,
The type of used data store (vector tiles in this case) per se should not have
any impact
on the GWC number of hits / misses.
GWC will request from the data store the needed tiles, store them and try to
map them
with future requests. If a request doesn't match any existing tiles then GWC
12 matches
Mail list logo
