ImageJ (https://imagej.nih.gov/ij/) manages in a very good way rasters,
including reading values and styling. Just a note to check an alternative
source for the future
Il giorno lun 30 nov 2020 alle ore 11:52 ha scritto:
> the bug is already tagged OJ_future so no hurry there.
>
> we still got
the bug is already tagged OJ_future so no hurry there.
we still got 5 open OJ 1.16 bugs[1] which look like they might be solved
already.. ede
[1] https://t1p.de/oix8
On 11/30/2020 10:40, giuseppe.ar...@gmail.com wrote:
> Hi,
> I agree with Michael that ij this step we can consider a good
Hi,
I agree with Michael that ij this step we can consider a good result to have a
better RasterImageLayer framework for this three reasons: it if faster in
opening images, it requires less ram, it can open more TIF versions than before.
Possibly we can postpone, as Michael suggests, to rewrite
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Hi Ede,Thank you for the overview of the main raster
classes.I don't know if your proposition of saving the displayed image
to disk would improve performance/memory usage. It would need tests. Anyway,
On 11/25/2020 13:15, michael michaud wrote:
> Even after several bug fixes, I still not have a good understanding of the
> image framework.
> To be able to imagine improvements, I would need a more precise idea about
> when the image is read from disk and when/where/what is cached.
for
