[GRASS-user] Null values in attribute table get converted to 0 (zero) during v.to.rast
markus.metz.giswork at gmail.com
Thu Oct 31 11:30:47 PDT 2019
On Tue, Oct 29, 2019 at 7:40 PM Veronica Andreo <veroandreo at gmail.com>
> Hi Daniel,
> I agree that if there's a NULL in the column, there should be NULL in the
resulting raster. I suggest to open a ticket here:
that would require to change db_select_CatValArray on library level here
I can't estimate the side effects of any changes, this is a widely used
function, thus no easy fix. Please open a ticket.
> El jue., 24 oct. 2019 a las 14:40, Daniel Victoria (<
daniel.victoria at gmail.com>) escribió:
>> Hi list,
>> I have a vector polygon map that I'm converting to raster. The attribute
column that I process has some empty rows (no data / null). When I run
v.to.rast, these empty rows become 0 (zero) on my resulting raster map.
>> Shouldn't v.to.rast respect the empty attribute table and create null
values for those polygons?
>> For now I'll use r.null to fix this problem. But what if 0 is a valid
>> PS - Running Grass 7.6.1 on Ubuntu
>> grass-user mailing list
>> grass-user at lists.osgeo.org
> grass-user mailing list
> grass-user at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-user