Ticket #2364 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

IMAGEMODE BYTE/INT16/FLOAT32 Fails with Multiband with Bilinear/Average resampler

Reported by: jratike80 Owned by: warmerdam
Priority: normal Milestone: 5.0.1 release
Component: WCS Server Version: svn-trunk (development)
Severity: normal Keywords: RESAMPLE AVERAGE BILINEAR
Cc:

Description

GeoTIFF image downloaded from MapServer WCS with request option interpolation=bilinear is three-band image but it looks like greyscale as if all the three bands were just the same. Without interpolation option the result is OK. MapServer version is 5.1-dev from FWTools 1.4.1.

Attachments

wcs_minimal.map Download (1.5 KB) - added by jratike80 6 years ago.
WCS mapfile
test2_wcs.tif Download (232.5 KB) - added by jratike80 6 years ago.
WCS mapfile

Change History

Changed 6 years ago by jratike80

WCS mapfile

Changed 6 years ago by jratike80

WCS mapfile

Changed 6 years ago by jratike80

This is the request that works:

wget -O testi321bil.tif " http://localhost:8060/cgi-bin/mapserv.exe?map=d:/ms4w/apps/ms101/data/wcs_minimal.map&SERVICE=WCS&VERSION=1.0.0&REQUEST=getcoverage&coverage=Baltic&CRS=epsg:3067&format=GEOTIFF&BBOX=544809.000,7301945.000,549807.000,7306943.000&ResX=30&ResY=30&bands=3,2,1"

Adding &interpolation=bilinear gave me an invalid output.

Changed 5 years ago by warmerdam

  • owner changed from Frank Warmerdam to warmerdam

Changed 5 years ago by warmerdam

  • keywords RESAMPLE AVERAGE BILINEAR added
  • status changed from new to closed
  • summary changed from Mapserver WCS makes invalid output with option interpolation=bilinear to IMAGEMODE BYTE/INT16/FLOAT32 Fails with Multiband with Bilinear/Average resampler
  • resolution set to fixed
  • milestone set to 5.0.1 release

I have confirmed the problem.

It occurs any time bilinear or average resampling are used with IMAGEMODE BYTE, INT16 or FLOAT32 regardless of whether it is WCS (though that is the most common case where this would apply).

Fixed in trunk (r7130) and 5.0 branch (r7131).

Thanks for the good report! Sorry I didn't get it fixed before 5.0.

Note: See TracTickets for help on using tickets.