Re: [mapserver-users] Very poor WMS tiling performance with small area, ultra-high resolution image

2016-02-15 Thread Avi Blackmore

On Feb 15, 2016, at 1:16 AM, Schepers, Benjamin wrote:

> Hi,
>  
> 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 ;-)
>  
> So converting to GeoTIFF with internal „Tiling“ could be the right strategy  
> for you (http://www.gdal.org/frmt_gtiff.html;  use “BigTIFF” if files are 
> expected to be larger than 4GB) à hint: gdal_translate with “BIGTIFF=YES” and 
> “TILED=YES” … and of course Overviews (gdaladdo; also possible with 
> BigTIFF-option).
>  
> 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…
>  
> 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!


Thanks for the advice.  I was already using GeoTIFFs with internal 
tiling, and compression.

The issue turned out to be a bad directive in the mapfile.  Our 
Mapscript application was misconfigured to set LOAD_WHOLE_IMAGE=yes in the 
processing directives for small-area imagery.  I don't recall why this was 
done, but I changed it, and now the images load fine in tiled mode.  

Thanks for your help.

--
Avi Blackmore
Head Programmer/System Administrator
Satshot Inc.

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Very poor WMS tiling performance with small area, ultra-high resolution image

2016-02-14 Thread Schepers, Benjamin
Hi,

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 ;-)

So converting to GeoTIFF with internal "Tiling" could be the right strategy  
for you (http://www.gdal.org/frmt_gtiff.html;  use "BigTIFF" if files are 
expected to be larger than 4GB) --> hint: gdal_translate with "BIGTIFF=YES" and 
"TILED=YES" ... and of course Overviews (gdaladdo; also possible with 
BigTIFF-option).

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...

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!

Regards
Ben

Luftbild und Geoinformationssysteme
schep...@rvr-online.de

[cid:image001.jpg@01D167C6.4912F620]

Kronprinzenstraße 35
45128 Essen
Germany
www.metropoleruhr.de

Von: mapserver-users [mailto:mapserver-users-boun...@lists.osgeo.org] Im 
Auftrag von Avi Blackmore
Gesendet: Freitag, 12. Februar 2016 23:28
An: mapserver-users@lists.osgeo.org
Betreff: [mapserver-users] Very poor WMS tiling performance with small area, 
ultra-high resolution image

Hello,

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.

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.

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?
--
Avi Blackmore
Head Programmer/System Administrator
Satshot Inc.

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Very poor WMS tiling performance with small area, ultra-high resolution image

2016-02-12 Thread Stephen Woodbridge
What is the file format? This has a huge impact on the memory and 
compute tile to extract a random bbox of pixels.


In some formats you have to extract the WHOLE image to grab any subset 
of pixels which could be your problem.


-Steve W

On 2/12/2016 5:28 PM, Avi Blackmore wrote:

Hello,

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.

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.

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?
--
Avi Blackmore
Head Programmer/System Administrator
Satshot Inc.



___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Very poor WMS tiling performance with small area, ultra-high resolution image

2016-02-12 Thread Avi Blackmore
Hello,

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.

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.

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?
--
Avi Blackmore
Head Programmer/System Administrator
Satshot Inc.

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users