> Hello, Hi Lucas
> We have a set of ECW files (LUFO2002), about 3015 files in total. > > All these files have to be served as one layer. > > In Geoserver 2.4.0 we have created a datastore 'ImageMosiac' but the > performance is not that good. > > What is the best approach on serving so many ECW files? Do we need to make > GeoTIFF / ImagePyramid of this set? I am not certain if GeoServer might not have some way to improve your setup programmatically (ie. via setup), but as an old data man myself, I would recommend doing something to the root of your problem: - Having ECWs that need to be decompressed for each request - Having a large (tiled) set of data that need to be parsed/handled for each request. I would suggest that you use GDAL to: 1) Make a single VRT of your lib full of ECWs (see http://www.gdal.org/gdalbuildvrt.html) 2) Add overviews to said VRT, for instance 2 4 8 16 32 64 (depending on your usual zooms you might even go as far as 128 or 156) (see http://www.gdal.org/gdaladdo.html) 3) Load said VRT instead of using an imagemosaic That way the ECWs will only be decompressed when people want to look at near real resolutions (better than 1/2 resolution). Best, Greg -- Hans Gregers Petersen Partner, Senior Consultant www.septima.dk ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
