Hans Gunnar Steen created an issue |
Changes in default interpolation option in WMS-settings has no effect. |
Issue Type: |
Bug |
---|---|
Affects Versions: |
2.5.2, 2.4.7, 2.5.1, 2.6-beta |
Assignee: |
|
Attachments: |
250.png, 251.png |
Components: |
WMS |
Created: |
14/Aug/14 4:27 AM |
Environment: |
CentOS 6.5, Java 1.7 & 1.8 |
Priority: |
Major |
Reporter: |
Having recently switched from Geoserver 2.5.0 to 2.5.1, we have become aware of an unfortunate change in the way the WMS renders rasters. We have a postgis vector database with topographic data. As backdrop, we use the image mosaic In 2.5.0, the hillshades where easy to render smoothly (despite a relative course resolution) by adjusting the WMS default raster rendering interpolation from âNearest neighborâ to âBilinearâ or âBicubicâ. Transferring the same setup to 2.5.1, changing Weâve done some testing with different versions, and it seems that changing the interpolation worked fine in 2.4.6, failed in 2.4.7, worked fine again in 2.5.0 and failed again in 2.5.1 and all later versions including 2.6 beta. The image mosaic tiles have the same resolution, bit depth and coordinate system (EPSG:3857). Asking the WMS in another coordinate system is not relevant to this problem, as it occurs in 3857 as well. Attached is a comparison of the same area. 2.5.1 vs 2.5.0, both set to use bilinear interpolation: |
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |