Peppe,
a) I cannot reproduce the problem. Can you test again with 6620+. In 6619, I
let a println which could eventually throw a NPE. Also in 6619, line 432 is an
empty line (?)
b) We probably must handle memory limitations in a more elegant way, but it is
not easy because the current code may let you load more image than what can be
rendered. Rendering uses more or less memory depending on wether raster is
visible and on the zoom level. I'll try to get a yellow warning when the
image cache is emptied du to the lack of memory.
---
** [bugs:#513] displaying raster layers in a correct way**
**Status:** open
**Milestone:** undecided
**Labels:** raster display
**Created:** Wed Nov 11, 2020 12:35 PM UTC by Giuseppe Aruta
**Last Updated:** Wed Nov 11, 2020 12:44 PM UTC
**Owner:** nobody
**Attachments:**
-
[correct_display.png](https://sourceforge.net/p/jump-pilot/bugs/513/attachment/correct_display.png)
(27.4 kB; image/png)
-
[wrong_display.png](https://sourceforge.net/p/jump-pilot/bugs/513/attachment/wrong_display.png)
(169.1 kB; image/png)
This bug has been described by Roberto Rossi on post:
[JPP-Devel] 6506 loading raster test
It comes out when the RAM used by OpenJUMP is largely engaged to load and
display many raster (Sextante) layers, together with big shape files.
It affects only continuous raster layer with a single band (like DTM or DEM)
Roberto provided some test files and a video that discribes the bug.
The link for the video is provided here:
https://mediaspace.unipd.it/id/1_varzgomj
The files to test the bug are available here:
https://drive.google.com/file/d/1sWFahWBxJnaEherHy3ywGEI5b-CYweOP/view?usp=sharing
In the zip file there 2 shapefile and 26 raster images.
description of the test bug:
1) load the shapefiles
2) load the rasters and wait that they are all displayed
3) zoom to an area that covers a part of the raster set
4) deactivate visibility to all the vector and raster layers
5) start to activate visibility to the layers one by one, starting from vectors
(which should be the last below in the pile of layers)
6) when you reach at one of the continuous raster layer (DTMxx and Depitxx,
Aspect, Slope) it may be show a wrong display (see wrong_display.png) instead
of the right one (see right_display.png).
Note that, depending to the quantity of RAM that your OS uses you may or may
not see the bug:
a) Roberto Rossi who uses Windows 10 with 8 Gb got the bug after reactivating
visibility of few rasters
b) I use Ubuntu Mate with 6 RAM and I had to (re)load other 11 raster layersto
GOT the bug.
Usually the bug disapears if the user zoom in to another area withing the same
raster (not sure about zoom out). The bug disapears if RAM is free removing
some layers (shapefiles) from the OpenJUMP project.
---
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