On Fri, Aug 24, 2012 at 10:49 AM, Marco Hugentobler
wrote:
> Hi Radim
>
> I don't have a strong opinion about wether to show nodata value in
> transparency list in the GUI or not. After all, the renderer sees only the
> transparency list and does not care which of them is the nodata value
> (excep
Hi Radim
I don't have a strong opinion about wether to show nodata value in
transparency list in the GUI or not. After all, the renderer sees only
the transparency list and does not care which of them is the nodata
value (except for the decision if the renderer is using transparency or
not).
On Wed, Aug 22, 2012 at 5:56 PM, Giovanni Manghi
wrote:
> It isn't the only odd thing/bug with nulls and transparency. For example not
> always nulls are rendered transparent
It was true, it should be fixed now, nodata are always transparent.
> and when you try to add them to the
> transparency
On Thu, Aug 23, 2012 at 9:30 AM, Radim Blazek wrote:
> On Thu, Aug 23, 2012 at 2:08 PM, Etienne Tourigny
> wrote:
>> I also find it puzzling that the data type changes (say from byte to
>> int). I understand that it is needed to have a nodata value when none
>> is given, but it would be nice to h
On Thu, Aug 23, 2012 at 2:08 PM, Etienne Tourigny
wrote:
> I also find it puzzling that the data type changes (say from byte to
> int). I understand that it is needed to have a nodata value when none
> is given, but it would be nice to hide this from the user as well.
User should not know about i
I also find it puzzling that the data type changes (say from byte to
int). I understand that it is needed to have a nodata value when none
is given, but it would be nice to hide this from the user as well.
Etienne
On Thu, Aug 23, 2012 at 9:05 AM, Radim Blazek wrote:
> On Wed, Aug 22, 2012 at 6:1
On Wed, Aug 22, 2012 at 6:13 PM, Etienne Tourigny
wrote:
> 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
On Thu, Aug 23, 2012 at 8:15 AM, Marco Hugentobler
wrote:
> 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
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
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
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
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
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
13 matches
Mail list logo
