1 respuesta
- 10-1
I am not sure what you mean by "load" - the system doesn't technically "load" files, it will open them (clearly not loading into memory) and then contextualize what you ask for. If you ask for extremely high resolutions it will take a long time to go through the pixels, although the times you mention sound beyond excessive.
When the contextualization is done, a memory-mapped temporary storage is created, which, depending on the machine and OS, may hit the disk and be sensitive to issues like disk space, fragmentation etc. in ways that the software cannot know. If there is very limited disk space for temporary storage, you may see lots of swapping and long access times.
Loading from files is managed through the Geotools API, which is state-of-the-art but will use the underlying Java image functions, which are dependent on RAM (although they obviously do not load the whole file in it). So a first course of action would be to up the memory the system can use, as Java enforces an upper limit (you can find the setting in the control center).
In general, files from disk should be considered a prototyping-only approach, especially if the files are large. Installing a geoserver (www.geoserver.org) on either your own machine or a more capable institutional server is a much better idea, as subsetting, reprojection etc. would be taken care of there. You would at that point create a WCS resource instead of a raster one, and things should be much smoother. That's the approach we default to in all applications.
Añada su comentario...
To whom it might concern,
I am trying to run some models where I replaced some of the input raster files, and the time it takes to load them is very long. When I run the same model using the standard data from ARIES, the rasters from the web load many times faster than my own (at the same resolution).
The image below shows where I was trying to load a raster file for Land Cover Type (at 100 m resolution) and it took 26 hr and 40 min, and it still could not load it properly (the original file had a resolution of 10 m).
I also tried to load this, and other raster files in a stronger computer and it did not work either.
Could this be a problem with the latest update of the software in early September 2020. I believe that I was able to run these models in the past.
Is there a way that I can load my own rasters differently?
Geronimo