request
time (shape file method was around 200ms).
From: Kirk, Victor
Sent: 10 August 2015 07:23
To: geoserver-users@lists.sourceforge.net
Subject: RE: [Geoserver-users] Performance issue with large polygon
Thanks for the comments, a few things for me to
nd Regards, Vic
From: andrea.a...@gmail.com [andrea.a...@gmail.com] on behalf of Andrea Aime
[andrea.a...@geo-solutions.it]
Sent: 09 August 2015 20:25
To: Martin Davis
Cc: Kirk, Victor; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Performance i
On Sun, Aug 9, 2015 at 5:19 PM, Martin Davis wrote:
> AFAIK there is no way to cache a layer in memory. This would be a useful
> feature to add to GeoServer.
>
> Perhaps you could cache the geometry as a shapefile - which should provide
> fastest performance off disk? It would be interesting to
AFAIK there is no way to cache a layer in memory. This would be a useful
feature to add to GeoServer.
Perhaps you could cache the geometry as a shapefile - which should provide
fastest performance off disk? It would be interesting to see what the
performance boost is at any rate. I also wonder
On Fri, Aug 7, 2015 at 10:28 AM, Kirk, Victor wrote:
> Hi,
>
> We have a polygon layer used as a backdrop for a WMS based layer group.
> The layer contains the outlines of the UK, one of which is the mainland and
> is obviously quite large. I have generalised versions of the geometries to
> use
Hi,
We have a polygon layer used as a backdrop for a WMS based layer group. The
layer contains the outlines of the UK, one of which is the mainland and is
obviously quite large. I have generalised versions of the geometries to use
when zoomed out, however when zoomed in, encoding the whole ma
