the use of JAI operations saves memory afaik. . it ideally creates a chain
from loading over computing to rendering.
the scaling you mention above seems to use BufferedImage in memory, which of
course is faster but needs the whole source image in memory. for cases like
Sextante, where images are currently held in memory anyway this may not be a
limiting factor so i'm all for the faster solution.
ReferencedImage uses JAI RenderedOP up to rendering the image and *should* be
therefore able to show bigger source images. never tested though.
..ede
---
** [bugs:#509] GeoImage and RasterImageLayer : why JAI**
**Status:** open
**Milestone:** OJ_future
**Created:** Sat Nov 07, 2020 09:12 PM UTC by michael michaud
**Last Updated:** Sat Nov 07, 2020 09:12 PM UTC
**Owner:** michael michaud
GeoImage and RasterImageLayer process image using JAI :
It crops and scales the visible part of the image. See also ticket 507.
This ticket is about the choice of JAI to rescale the image. Following baeldung
post https://www.baeldung.com/java-resize-image i tried with awt and graphics2D
and rescaling seems to be much faster.
Maybe JAI has a richer api for those who want more complex processing, but
graphics2D propose several kind of interpolation through the RenderingHints,
which may be enough.
To be tested further after the move to github.
---
Sent from sourceforge.net because jump-pilot-devel@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/jump-pilot/bugs/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/jump-pilot/admin/bugs/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
