Changes in default interpolation option in WMS-settings has no effect.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Changes in default interpolation option in WMS-settings has no effect.

Hans Gunnar Steen

Hi,

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

plugin with hillshades tiles.

 

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

the interpolation method has no effect any more, “Nearest neighbor” (or, perhaps no interpolation at all) seems to be used no matter what setting we use, rendering nasty pixel borders on the innermost zoomlevels.

 

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.

 

Here’s a comparison of the same area. 2.5.1 vs 2.5.0, both set to use bilinear interpolation:

          

Kind regards Hans


------------------------------------------------------------------------------

_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Changes in default interpolation option in WMS-settings has no effect.

Jonathan Moules-2
Hi Hans,
I'd advise reporting this one as a bug to JIRA. It seems like a regression in 2.5.1.
Might also be worth testing 2.6 before they finalise.

Cheers,
Jonathan



On 14 August 2014 09:15, Hans Gunnar Steen <[hidden email]> wrote:

Hi,

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

plugin with hillshades tiles.

 

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

the interpolation method has no effect any more, “Nearest neighbor” (or, perhaps no interpolation at all) seems to be used no matter what setting we use, rendering nasty pixel borders on the innermost zoomlevels.

 

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.

 

Here’s a comparison of the same area. 2.5.1 vs 2.5.0, both set to use bilinear interpolation:

          

Kind regards Hans


------------------------------------------------------------------------------

_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users



This transmission is intended for the named addressee(s) only and may contain confidential, sensitive or personal information and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users