<div dir="ltr"><div dir="ltr">What you describe is pretty much the approach we take. If you are using geotiffs ensure that they are internally tiles (-co TILED=YES) and the you are creating a shptree index on the tile index as noted in the docs. At some point you may want to consider creating a lower resolution mosaics of coverages and using GROUPS and MIN/MAXSCALEDENOM to load the layers at different scales. Make sure to declare the layer's extent as well <div><br></div><div>Something like:</div><div><br></div><div><div> LAYER</div><div> NAME "full_res_10cm_tiles_withovr"</div><div> EXTENT 607500.000000 4824000.000000 654000.000000 4859500.000000</div><div> TYPE RASTER</div><div> PROCESSING "RESAMPLE=AVERAGE"</div><div> TILEINDEX /maps/tindex.shp</div><div> TILEITEM location</div><div> GROUP "my_photo"</div><div> MAXSCALEDENOM 10000</div><div> OFFSITE 0 0 0</div><div> METADATA</div><div> "wms_extent" "607500.000000 4824000.000000 654000.000000 4859500.000000"</div><div> END</div><div> PROJECTION</div><div> "init=epsg:2958"</div><div> END</div><div> END</div><div> LAYER</div><div> NAME "resampled_2m_tiled_bigtif_withovr"</div><div> EXTENT 607500.000000 4824000.000000 654000.000000 4859500.000000</div><div> TYPE RASTER</div><div> PROCESSING "RESAMPLE=AVERAGE"</div><div> DATA /maps/2m_overall.tif</div><div> GROUP "my_photo"</div><div> MINSCALEDENOM 10000</div><div> MAXSCALEDENOM 65000</div><div> OFFSITE 0 0 0</div><div> METADATA</div><div> "wms_extent" "607500.000000 4824000.000000 654000.000000 4859500.000000"</div><div> END</div><div> PROJECTION</div><div> "init=epsg:2958"</div><div> END</div><div> END</div></div><div><br></div><div><br><div><br></div><div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, 6 Nov 2018 at 13:39, Ziegler Stefan <<a href="mailto:Stefan.Ziegler@bd.so.ch">Stefan.Ziegler@bd.so.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
We are using MapServer for vector data stored in a PostgreSQL/PostGIS database. For a new project we are planning to provide a WMS based on raster layers and therefore in need of some performance hints or your experiences.<br>
<br>
The raw data will be a lot of single GeoTIFF (aerials, hillshading, slopes, etc.) files, like 5'000 - 10'000 from different organizations. Since the originate from different organizations it's possible that they can have different resolutions. Conceptionally for aerials it would look like this:<br>
<br>
Aerial group<br>
|_ aerial from organization one (1000 single tiffs, resolution 10cm, approx 10k x 10k pixels)<br>
|_ aerial from organization two (600 single tiffs, resolution, 12.5 cm, approx 10k x 10k pixels)<br>
|_ aerial from organization three (3000 single tiffs, resolution, 10 cm, approx 10k x 10k pixels)<br>
<br>
For some hundred single GeoTIFFs we have good experience with the Tileindex approach and an handmade external overview that kicks in at smaller scale.<br>
<br>
Will this approach still work with a massive amount of single tiffs? Or are the better ones? What about the compression (quality vs. decompression speed vs. disk space?) Or would you expect a much better performance with - let's say - a BigTIFF for each organisation?<br>
<br>
Thanks for any hints.<br>
<br>
Best regards<br>
Stefan<br>
<br>
Freundliche Grüsse<br>
<br>
Stefan Ziegler <br>
Kantonsgeometer / Leiter Amt für Geoinformation<br>
<br>
Amt für Geoinformation<br>
Rötistrasse 4 <br>
4500 Solothurn <br>
<br>
Telefon +41 32 627 75 96<br>
<a href="mailto:stefan.ziegler@bd.so.ch" target="_blank">stefan.ziegler@bd.so.ch</a><br>
<a href="http://www.so.ch" rel="noreferrer" target="_blank">http://www.so.ch</a> <br>
<br>
<br>
_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-users</a></blockquote></div>