Hi all.
We recently noticed strange problems with the visualization of rasters.
Transparencies are applied automatically, some layers are not displayed even if
no
custom color is selected, etc.
We'll inspect this deeper tomorrow, but in the meantime: did anybody see the
same?
All the best.
--
yes, i see strange behaviour of one raster.
it is always above every layer even if it is the last onein the toc.
(Versione di QGIS, 1.8.0-Lisboa, Revisione codice QGIS cdd683c)
http://osgeo-org.1560.n6.nabble.com/file/n4978855/1.png 1.png
http://osgeo-org.1560.n6.nabble.com/file/n4978855/2.png
Hi Stefano,
On Mon, Jun 4, 2012 at 12:33 AM, skampus
stefano.cam...@regione.piemonte.it wrote:
it is always above every layer even if it is the last onein the toc.
AFAICS the Control rendering order checkbox is not checked.
Display the Layer order panel (View-Panel-Layer order) or tick
the
opsss...sorry...
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Raster-visualization-tp4978783p4978857.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Hi,
Depending on the number of cells, dealing with 20 raster files
requires a totally different approach.
I agree. There are surely more than one approach type to the raster usage
problem.
Surely there is the user that need a thematic map and need a really good
analysys . It need all the
Andrea,
Depending on the number of cells, dealing with 20 raster files
requires a totally different approach.
Even for visualization, this is clearly a different problem than the
common RGB or multi-spectral imagery.
We cannot deal with 13000 raster layers in the same way as we do with a dozen.
Andrea,
Opening the raster layers very fast but getting a bad visualization
would not be a major
waste of time? This is what currently happens to me: the initial
display is always useless.
If your raster layers have similar statistics and or you want to
display them with the same stretching so
Hi Agus ,
thx for your informations.
Opening the raster layers very fast but getting a bad visualization
would not be a major
waste of time? This is what currently happens to me: the initial
display is always useless.
I understand your point of view, but i guess is not a need for every
Hi all.
Visualizing monoband rasters could be improved:
- why not loading it with a greyscale by default? or with a colour ramp?
- why not adding a dtm colour table (we can take the one
in/usr/lib/grass64/etc/colors/terrain), possibly replacing the Freak out
one?
Small changes, much more pleasant
On Fri, 2012-04-20 at 10:19 +0200, Paolo Cavallini wrote:
Hi all.
Visualizing monoband rasters could be improved:
- why not loading it with a greyscale by default? or with a colour ramp?
- why not adding a dtm colour table (we can take the one
in/usr/lib/grass64/etc/colors/terrain), possibly
Hi
On Fri, Apr 20, 2012 at 10:47 AM, Giovanni Manghi
giovanni.man...@gmail.com wrote:
On Fri, 2012-04-20 at 10:19 +0200, Paolo Cavallini wrote:
Hi all.
Visualizing monoband rasters could be improved:
- why not loading it with a greyscale by default? or with a colour ramp?
- why not adding a
Hi
BTW Freak out will go after resampler branch is merged
I've managed to convert freakout style to singleband pseudocolor in the
project file / qml conversion to the new format :-)
- visualizing monoband rasters could be improved:
- why not loading it with a greyscale by default? or
Hi
On Fri, Apr 20, 2012 at 2:17 PM, Marco Hugentobler
marco.hugentob...@sourcepole.ch wrote:
Hi
BTW Freak out will go after resampler branch is merged
I've managed to convert freakout style to singleband pseudocolor in the
project file / qml conversion to the new format :-)
-
- on initial load of a raster, generate a quicklook that is the larger
of 1/4 screen resolution or 500x500 pixels by sampling every nth pixel
- generate a histogram from the quicklook
- calculate clipped 2% - 96% range min max for each band
- apply a histogram stretch based on the above
- the
14 matches
Mail list logo
