Seems that I can narrow the question now. Actually, QGIS Kore reads
GRASS maps well except when the maps have been created from raster ramp
color have been optimized with i.landsat.rgb. For example in GRASS:
r.composite r=etm7 g=etm5 b=etm2 out=south752brut
makes a map 'south752brut' which is well read within QGIS
Now if I do:
i.landsat.rgb r=etm7 g=etm5 b=etm2
r.composite r=etm7 g=etm5 b=etm2 out=south752opt
it makes a map 'south752opt' which is extremly long to read (several
minutes), and when read makes change (displacement, zoom, etc...)
extremely long to be displayed at a speed that prevent any work
However, 'south752opt' and 'south752brut' are quick/normally displayed
both at the same speed when on work within GRASS (e.g. d.rast south752opt)
Any hint ?
Patrick
Patrick Giraudoux a écrit :
Dear all,
I am working on Ubuntu Hardy. I have just updated from QGIS Metis to
Kore 1.0.0, and to my surprise, GRASS raster reading has become
extremely slow, whatever the context (QGIS launched withing GRASS 6.3
or from outside). Even small rasters take minutes before being
displayed (against fraction of second on Metis).
Otherwise, raster import (eg tif) is working OK when GRASS is not
concerned...
Any idea about what is happening ?
Patrick
begin:vcard
fn:Patrick Giraudoux
n:Giraudoux;Patrick
org;quoted-printable:Universit=C3=A9 de Franche-Comt=C3=A9;Chrono-environnement, UMR CNRS 6249 usc INRA
adr;quoted-printable:;;1 place Leclerc;Besan=C3=A7on;;25030;France
email;internet:[email protected]
title;quoted-printable:Professeur d'=C3=A9cologie
tel;work:+33 381 665 745
tel;fax:+33 381 665 797
version:2.1
end:vcard
_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user
