Thanks for the hints, Andrea.
If we provide fixed values for time and spatial extent when creating the
layer - would that avoid the execssive data base queries?
Am 20.02.2013 16:26, schrieb Andrea Aime:
On Wed, Feb 20, 2013 at 3:46 PM, Matthias Müller
matthias_muel...@tu-dresden.de
On Thu, Feb 21, 2013 at 1:19 PM, Matthias Müller
matthias_muel...@tu-dresden.de wrote:
Thanks for the hints, Andrea.
If we provide fixed values for time and spatial extent when creating the
layer - would that avoid the execssive data base queries?
The spatial extent used is the one already
So we'll try to implement some logic calulates the WMS layer time based
on the preconfigured interval / resolution. I haven't yet hacked in the
geoserver project. Can you point me to a particular module, package or
class that requires tweaking?
Thanks,
Matthias
Am 21.02.2013 14:12, schrieb
Hello list,
are there any best practices on offering a large number of WMS layers
with geoserver? We are operating a geoserver instance that has about 600
time-enabled vector layers (loaded from a postgres database) which
causes two problems:
1) The capabilities take a very long time (5
On Wed, Feb 20, 2013 at 3:46 PM, Matthias Müller
matthias_muel...@tu-dresden.de wrote:
Hello list,
are there any best practices on offering a large number of WMS layers with
geoserver? We are operating a geoserver instance that has about 600
time-enabled vector layers (loaded from a
