[#GEOS-2057] WMS raster interpolation settings are ignored - jira.codehaus.org

GeoServer

WMS raster interpolation settings are ignored

Created: 28/Jul/08 07:48 AM Updated: 30/Jul/08 09:02 AM Resolved: 29/Jul/08 06:18 AM

Component/s:

WMS

Affects Version/s:

1.7.0-beta1

Fix Version/s:

1.6.5, 1.7.0-beta2

Time Tracking:

Not Specified

File Attachments:

12_1020_6055_gdalinfo.txt (0.6 kB)
2.

12_1020_6055_identify_verbose.txt (15 kB)

Image Attachments:

1. wms-164b-bicubic-2.jpg
(71 kB)

2. wms-164b-bilinear-2.jpg
(71 kB)

3. wms-164b-nn-2.jpg
(70 kB)

Issue Links:

Related

This issue is related to:

~~GEOS-2060~~ WMS rendering options are not honored on apply, only on save

Description

« Hide

This happens at least on 1.7.x, haven't tried out in 1.6.x

Sort Order:

[ Permalink | « Hide ]

Guillaume Lathoud added a comment - 29/Jul/08 02:04 AM

Geoserver 1.6.4b with WMS > Rendering > Nearest neighbour

[ Permalink | « Hide ]

Guillaume Lathoud added a comment - 29/Jul/08 02:04 AM

Geoserver 1.6.4b with WMS > Rendering > Bilinear

[ Permalink | « Hide ]

Guillaume Lathoud added a comment - 29/Jul/08 02:05 AM

Geoserver 1.6.4b with WMS > Rendering > Bicubic

[ Permalink | « Hide ]

Guillaume Lathoud added a comment - 29/Jul/08 02:07 AM

With 1.7.0-beta1 I obtained exactly (=pixelwise) the same result for all three settings of WMS > Rendering.

With 1.6.4b I obtained very slight differences (effective size and bounding box) but the processing seems to be the same (I suspect nearest neighbour).

[ Permalink | « Hide ]

Andrea Aime added a comment - 29/Jul/08 02:09 AM

Daniele, Simone, any idea about what's going on here? Maybe the new raster renderer code has issues with intepolation settings?
Guillame, one question, do you have overviews embedded in your raster data? GeoServer will use them, so the starting point for interpolation will look just as good as the overview you have. I'm asking because most tools default on nn interpolation when creating the overviews.