[Qgis-developer] Large raster (ecw) identify very long

Hi all, I'm ready to support developpement now, so let's undig a topic discussed previously here: http://hub.qgis.org/issues/4594 http://hub.qgis.org/issues/4594 Identify for very large ecw (from 1 to 100 Go - 1 080 000 * 1 090 000 pixels) is extremely long (more than 1min) and results to memor

Re: [Qgis-developer] Large raster (ecw) identify very long

On Wed, Aug 22, 2012 at 11:40 AM, haubourg wrote: > Hi all, > I'm ready to support developpement now, so let's undig a topic discussed > previously here: > http://hub.qgis.org/issues/4594 http://hub.qgis.org/issues/4594 > > Identify for very large ecw (from 1 to 100 Go - 1 080 000 * 1 090 000 > pi

Re: [Qgis-developer] Large raster (ecw) identify very long

Radim Blazek-2 wrote > > > QGIS is using GDALRasterIO() which reads a single pixel on original > resolution. AFAIK, ECW is using tiles internally so it should be all > very fast. I can imagine 2 problems: > > - the tiles in ECW file are too big - can you verify somehow how big > are the tiles?

Re: [Qgis-developer] Large raster (ecw) identify very long

On Wed, Aug 22, 2012 at 12:29 PM, haubourg wrote: > > Radim Blazek-2 wrote >> >> >> QGIS is using GDALRasterIO() which reads a single pixel on original >> resolution. AFAIK, ECW is using tiles internally so it should be all >> very fast. I can imagine 2 problems: >> >> - the tiles in ECW file are

Re: [Qgis-developer] Large raster (ecw) identify very long

Selon Radim Blazek : > On Wed, Aug 22, 2012 at 12:29 PM, haubourg > wrote: > > > > Radim Blazek-2 wrote > >> > >> > >> QGIS is using GDALRasterIO() which reads a single pixel on original > >> resolution. AFAIK, ECW is using tiles internally so it should be all > >> very fast. I can imagine 2 prob

[Qgis-developer] Python plugin: open a project file in "append" mode

Hi, in the documentation, at the QgsProject entry, I read this: boolread (QFileInfo const &file) read project file boolread () presuming that the caller has already reset the map canvas, map registry, and legend the first read (QFileInfo const &file) sets the project

Re: [Qgis-developer] Large raster (ecw) identify very long

Even Rouault wrote > > Selon Radim Blazek : > > Regis, > > what are the dimensions (in pixels) of your big ECW ? > My ecw is 1 080 000 * 1 090 000 pixels (IGN orthophotos for 28 French departement.. 1/4 of France surface) but I have also problem with scan25 and scan 100 that ar

[Qgis-developer] No data value in raster transparency list

Hi, does anybody know why raster no data value is automatically added to transparency list in properties dialog? It makes no sense IMO. No data values are always rendered as transparent, no need to define them also in transparent list. Radim ___ Qgis-dev

Re: [Qgis-developer] No data value in raster transparency list

It isn't the only odd thing/bug with nulls and transparency. For example not always nulls are rendered transparent and when you try to add them to the transparency list the entry is added as 0 instead. On Aug 22, 2012 4:49 PM, "Radim Blazek" wrote: > > Hi, > does anybody know why raster no data v

Re: [Qgis-developer] No data value in raster transparency list

I've seen nodata with huge float32 values. Unfortunately they are rendered in qgis and I can not make them transparent by adding the value to the transparency list. On Aug 22, 2012 8:56 AM, "Giovanni Manghi" wrote: > It isn't the only odd thing/bug with nulls and transparency. For example > not

Re: [Qgis-developer] No data value in raster transparency list

On Wed, Aug 22, 2012 at 1:11 PM, Bob and Deb wrote: > I've seen nodata with huge float32 values. Unfortunately they are rendered > in qgis and I can not make them transparent by adding the value to the > transparency list. that's because gdal provider chooses a nodata value that is out of the ra

Re: [Qgis-developer] Large raster (ecw) identify very long

Even, thanks for exhaustive explanation and testing. On Wed, Aug 22, 2012 at 2:37 PM, Even Rouault wrote: >> I found in GDAL ecwdataset.cpp that it is treating single row >> requests in IRasterIO in a special way: > > I tried the following Python script that must be representative of how QGIS >

Re: [Qgis-developer] Large raster (ecw) identify very long

On Wed, Aug 22, 2012 at 3:25 PM, haubourg Radim, > I'll try to to check if tiles are present, but I don't think so. We > compressed it with ERmapper without tile option. No more important, we know already the problem. > I'm afraid I'm not yet able to test patches since I never compiled QGIS and

Re: [Qgis-developer] Large raster (ecw) identify very long

Le mercredi 22 août 2012 20:13:39, Radim Blazek a écrit : > Even, > thanks for exhaustive explanation and testing. > > On Wed, Aug 22, 2012 at 2:37 PM, Even Rouault > > wrote: > >> I found in GDAL ecwdataset.cpp that it is treating single row > > > >> requests in IRasterIO in a special way: >

Re: [Qgis-developer] Python support in project file

Hi Larry, Nathan On Tue, Aug 21, 2012 at 9:58 PM, Larry Shaffer wrote: > For a cleaner look for the message bar, I created two svg icons output to > png, one for the warning and one for close [0]. Also, the Enable action is > more of a link. Basically, removing the tool button backgrounds via a >

[Qgis-developer] Symbol transparency, wrong value stored and displayed

Hi all, I noticed that the alpha value stored in the QML for QgsSimpleFillSymbolLayer objects is wrong. Here's the QML generated when the symbol transparency is 70%: ... The alpha value for the whole symbol is right (~0.30), instead the layer's

Re: [Qgis-developer] Python support in project file

Hi Giuseppe, On Wed, Aug 22, 2012 at 4:58 PM, Giuseppe Sucameli wrote: > Hi Larry, Nathan > > On Tue, Aug 21, 2012 at 9:58 PM, Larry Shaffer wrote: >> For a cleaner look for the message bar, I created two svg icons output to >> png, one for the warning and one for close [0]. Also, the Enable act

Re: [Qgis-developer] No data value in raster transparency list

Hi Radim Nodata should be rendered transparent in most cases. But it could also be possible you want to render it differently. E.g. the interpolation plugin writes nodata value in case it encounters numerical problems. Then it is useful to have the nodata values coloured to see where problems