Hi Topias, I am not close enough to this code to know if it is a bug, but I like that your fix includes an example.
It would be preferable to know exactly where CRS.transform is producing a null reference, perhaps by stepping through with a debugger, to determine if that code could be made more robust. Your example does not show the same request passing or failing based on interpolation method. - - Jody Garnett On Mar 18, 2025 at 10:54:20 AM, Topias Rusanen <topias.rusa...@fluidit.fi> wrote: > Hello, > > > > I’m currently experiencing issues when rendering coverages with bicubic > interpolation on GeoTools 32.1. > > > > When rendering my coverage, the API returns a null reference, which per > documentation would state that the coverage does not intersect the area to > be rendered. However, if I disable interpolation, the area is rendered fine > albeit the result is ugly. > > > > I created a fork of the main repo and was able to reproduce the issue in > unit tests. A simple CRS transformation would solve my issue, see the > modified unit test and a fix for the rendering issue in here: > https://github.com/FluiditLtd/geotools/commit/9a8fd3ebdb4321957c7f7dc10d290e36b25f7d04 > > > > My question is: Is this a bug? If this is indeed a bug, I can create a PR > from the fork if the fix is deemed adequate. > > > > Best regards, > > > > Topias Rusanen > > Software Team Lead > > Fluidit Oy > _______________________________________________ > GeoTools-GT2-Users mailing list > GeoTools-GT2-Users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users >
_______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
