2009/1/4 Patrick Giraudoux <patrick.giraud...@univ-fcomte.fr>: > 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 ?
Hi Patrick, we're using GDAL library to access GRASS rasters, so the problem may be there. I would suggest you to try reading the raster in some other GDAL-based software [1] to see whether it also suffers slow performance. If so, file a bug for GDAL, if the problem happens only in QGIS file a ticket for QGIS with details. Martin [1] https://trac.osgeo.org/gdal/wiki/SoftwareUsingGdal _______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
