Ciao Simone,
Option 1 works like a charm. I'll be keeping option 2 in mind when upgrading!
Cheers, Gianni
On 6/20/12, Simone Giannecchini wrote:
> Ciao Gianni,
> this was a side effect of using memory caching in the single mosaics
> of the pyramid.
> I see two options:
>
> -1- iterate over the
Ciao Gianni,
this was a side effect of using memory caching in the single mosaics
of the pyramid.
I see two options:
-1- iterate over the various mosaic properties files and add
Caching=false to them, then force a reload of the config from the UI.
This disable index caching
-2- Switch to GeoServer
Hi Simone,
First, GeoServer is fast enough after the first request is done and
paths to all files have been resolved for a certain resolution. I just
wonder why the first request takes such a long time (see GeoServer log
in this mail).
In reply to your questions:
1) GeoServer v2.1.1
2) I've creat
Ciao Gianni,
starting with a few questions:
-1- which version of the GeoServer are you using?
-2- did you properly preprocessed your geotiff files retiling them and
adding overviews?
-3- can you paste here the output of the gdalinfo on one of your images?
Btw, check the recipes here:
http://demo.
Hi,
you can make your GeoTiffs tiled and also add overviews using GDAL
command line utilities. If still not good enough for you then I
suggest caching the layer with Geowebcache. Further I assume you are
running geoserver with Native JAI support.
regards,
Imran
On Wed, Jun 20, 2012 at 12:49 AM,
Hi all,
Recently I configured a datastore and layer with aerial photos to be served
by geoserver. I've got about 3000 GeoTIFF's with a size up to 150 MB.
During configuration the ImageMosaic plugin iterates the files to create an
index in form of a shape file.
Next day, when the aerial layer is r
