On 10/13/2020 9:48, Michaud Michael wrote: > Ede, > > Crop operation also uses floats, so I'm not sure it solves the problem. > Difficult to guess the impact without a try though. > > The change may not be trivial as the scale operation which is currently > performed at first place is also used to cache a scaled image which can be > re-used when scale does not change (pan).
right, didn't think about that. > Another track : during my test (commented code), I observed that displaying a > very small part of the full image without scaling/cropping with jai first was > efficient and precise (drawRenderedImage(RenderedImage,AffineTransform)). how do you mean? how do you fit the image without scaling/cropping? > The problem is with the rendering of the full image. Then, > graphics2D.drawRenderedImage is very slow (like the scaling operation with > jai). you mean when the full image i visable in the viewport, right? >The only way to interpolate the image efficiently when the full image has to >be displayed seems to be the subsampling operation with jai. Mixing >subsampling for certain scales and normal affine transform for others may do >the trick, but it seems over complicated. isn't that what we do with 2000/2000px special case currently? like a built in overview? > Another track to be explored is the capability to use subsampled overviews > wrapped in geotiff images (as described in Gary's mail about COG geotiff > format). May be after migration... wrapping any image format into a virtual geotiff sounds even more complicated. ..ede _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
