Ticket #2364 (closed defect: fixed)

Opened 10 months ago

Last modified 9 months ago

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

Reported by: jratike80 Assigned to: 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 (1.5 kB) - added by jratike80 on 10/25/07 10:20:50.
WCS mapfile
test2_wcs.tif (232.5 kB) - added by jratike80 on 10/25/07 10:23:35.
WCS mapfile

Change History

10/25/07 10:20:50 changed by jratike80

  • attachment wcs_minimal.map added.

WCS mapfile

10/25/07 10:23:35 changed by jratike80

  • attachment test2_wcs.tif added.

WCS mapfile

10/25/07 10:29:19 changed 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.

11/30/07 12:32:47 changed by warmerdam

  • owner changed from Frank Warmerdam to warmerdam.

11/30/07 17:13:16 changed by warmerdam

  • keywords set to RESAMPLE AVERAGE BILINEAR.
  • 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.