<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Sprechblasentext Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.E-MailFormatvorlage19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.SprechblasentextZchn
{mso-style-name:"Sprechblasentext Zchn";
mso-style-priority:99;
mso-style-link:Sprechblasentext;
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="blue" vlink="purple" style="word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space">
<div class="Section1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">you still pointed to the right answer, strategies like overviews and tiling are IMHO not scale-dependent. They depend on the pixel-dimension
of the image and you have - let’s say - a not so small one ;-)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">So converting to GeoTIFF with internal „Tiling“ could be the right strategy for you (<a href="http://www.gdal.org/frmt_gtiff.html">http://www.gdal.org/frmt_gtiff.html</a>;
use “BigTIFF” if files are expected to be larger than 4GB) </span><span lang="EN-US" style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">à</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"> hint:
gdal_translate with “BIGTIFF=YES” and “TILED=YES” … and of course Overviews (gdaladdo; also possible with BigTIFF-option).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Compression for original and overviews, could be lossless “LZW” or lossy „JPEG-YCBCR” for example, this would also substantially squeeze down
the size an d depends on your needs…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I have a lot of aerial images with up to 250.000*150.000px (GSD up to 6cm) in that manner and they are serving really, really fast via mapserver.
Not every GIS-software is able to read those tiled and compressed BigTiffs directly (due to the lack of support for this file-format), but ArcGIS and QGIS do well (both use GDAL) and all others could still use the WMS served from mapserver!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Regards<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D">Ben</span></b><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D">
<br>
</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D"><br>
Luftbild und Geoinformationssysteme<br>
schepers@rvr-online.de<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D"><img border="0" width="132" height="107" id="_x0000_i1025" src="cid:image001.jpg@01D167C6.4912F620"></span><span style="font-size:10.0pt;
font-family:"Arial","sans-serif";color:#1F497D"><br>
</span><b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";
color:#1F497D"><br>
</span></b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";
color:#1F497D">Kronprinzenstraße 35<br>
45128 Essen<br>
Germany<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial","sans-serif";
color:#1F497D">www.metropoleruhr.de<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> mapserver-users [mailto:mapserver-users-bounces@lists.osgeo.org]
<b>Im Auftrag von </b>Avi Blackmore<br>
<b>Gesendet:</b> Freitag, 12. Februar 2016 23:28<br>
<b>An:</b> mapserver-users@lists.osgeo.org<br>
<b>Betreff:</b> [mapserver-users] Very poor WMS tiling performance with small area, ultra-high resolution image<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-tab-span"> </span>We've been using Mapserver as, among other things, a WMS server for some time with satellite and aerial imagery, without problems. We've been able to serve imagery of resolutions down to
.25 meters without any significant performance hit.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-tab-span"> </span>Today, we got a sample image from a new source, which has a resolution of 0.06 meters. The image is 317 megabytes in size, and has dimensions of 17538 x 19035 pixels. The file size is smaller
than many of the Landsat or other images that we have displayed in the past. However, we're finding that rendering this image is extremely expensive. In particular, with tiled access, a la Google Maps, the WMS requests bog down our server to the point where
all of its memory is consumed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-tab-span"> </span>I know that overviews, tiling, and such, are good strategies for reducing the render time on a large area, reasonably high resolution image. But what would be good strategies for improving
rendering time on this smaller, ultra-high resolution image?<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size:13.5pt;
font-family:"Helvetica","sans-serif";color:black">--</span></span><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black"><br>
<span class="apple-style-span">Avi Blackmore</span><br>
<span class="apple-style-span">Head Programmer/System Administrator</span><br>
<span class="apple-style-span">Satshot Inc.</span></span> <o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>