I’m currently trying to diagnose a problem in my geoserver setup, which I am increasingly starting to believe may be a bug in the geoserver GWC implementation. Any input would be great.
My setup is as follows:
1 - A GeoTiff coverage file (EPSG4326, extent [-180, -60, 180, 85])
2 - GeoServer 2.8.1
3 - A coverage store in geoserver based on that file, same srs/extent
4 - A layer in geoserver based on that store, with a custom SLD style, same srs/extent
5 - WMS enabled & GWC set for direct integration into the WMS
6 - Leaflet front end, configured to display that layer, same srs
At most zoom levels this displays correctly, but at one zoom level I get the wrong data displayed in some tiles (screenshot: http://i.imgur.com/jl2sNsf.png). Having traced this through, I’m confident that the issue is on the geoserver side, not the leaflet end (the WMS GET requests are correct). Specifically it seems that the bbox on some tile requests is being incorrectly shifted to the top of the geotiff extent.
If I disable use of the GWC (by removing titled=true from tile requests) I get the correct tiles.
I'm currently trying to diagnose a problem in my geoserver setup, which I am increasingly starting to believe may be a bug in the geoserver GWC implementation. Any input would be great.
My setup is as follows:
1 - A GeoTiff coverage file (EPSG4326, extent [-180, -60, 180, 85])
2 - GeoServer 2.8.1
3 - A coverage store in geoserver based on that file, same srs/extent
4 - A layer in geoserver based on that store, with a custom SLD style, same srs/extent
5 - WMS enabled & GWC set for direct integration into the WMS
6 - Leaflet front end, configured to display that layer, same srs
At most zoom levels this displays correctly, but at one zoom level I get the wrong data displayed in some tiles (screenshot: http://i.imgur.com/jl2sNsf.png). Having traced this through, I'm confident that the issue is on the geoserver side, not the leaflet end (the WMS GET requests are correct). Specifically it seems that the bbox on some tile requests is being incorrectly shifted to the top of the geotiff extent.
If I disable use of the GWC (by removing titled=true from tile requests) I get the correct tiles.
As it turns out Leaflet 0.7.x (stable) does not have a correct definition of EPSG4326 and requests tiles which that are not aligned to the gridset correctly at low zoom levels (I’m using the geoserver/gwc builtin EPSG4326 gridset on the server end). https://github.com/Leaflet/Leaflet/issues/1207. This is fixed in the Leaflet 1.0x betas, so upgrading has resolved my issue.
I’m currently trying to diagnose a problem in my geoserver setup, which I am increasingly starting to believe may be a bug in the geoserver GWC implementation. Any input would be great.
My setup is as follows:
1 - A GeoTiff coverage file (EPSG4326, extent [-180, -60, 180, 85])
2 - GeoServer 2.8.1
3 - A coverage store in geoserver based on that file, same srs/extent
4 - A layer in geoserver based on that store, with a custom SLD style, same srs/extent
5 - WMS enabled & GWC set for direct integration into the WMS
6 - Leaflet front end, configured to display that layer, same srs
At most zoom levels this displays correctly, but at one zoom level I get the wrong data displayed in some tiles (screenshot: http://i.imgur.com/jl2sNsf.png). Having traced this through, I’m confident that the issue is on the geoserver side, not the leaflet end (the WMS GET requests are correct). Specifically it seems that the bbox on some tile requests is being incorrectly shifted to the top of the geotiff extent.
If I disable use of the GWC (by removing titled=true from tile requests) I get the correct tiles.
Has anyone encountered anything like this?
Thanks,
Mathias
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
