I think r.null does not work on external (r.external) files. Make sure this
is not the issue.
Please excuse brevity. Sent from tiny pocket computer with non-haptic
feedback keyboard.
On Wed, Oct 20, 2021, 07:02 Eric Patton via grass-user <
grass-user@lists.osgeo.org> wrote:
> I'm encountering
Thanks for checking, Micha.
I have had weird behaviour from the wxgui in the last several months. Nothing I
can pin down exactly. Perhaps a missing dependency?
I'll try Grass 7.8.6 and see if that fixes the issue. I think I installed my
version 7.8.5 via git, so what would be the safest way to
Hello,
I've been testing PostGIS to GRASS imports / exports and there are some
things I'm not sure I understand correctly. They are related to keeping
primary keys coming from PostGIS.
My table of origin at PostGIS has a primary key called gid_building
(integer). When using:
grass
Hi
On 10/20/21 4:52 PM, Eric Patton via
grass-user wrote:
I'm encountering some strange behaviour from r.null - when I
use the setnull parameter to assign a particular value to be
null in a raster, the raster areas just set to null
I'm encountering some strange behaviour from r.null - when I use the setnull
parameter to assign a particular value to be null in a raster, the raster areas
just set to null are still visible and coloured according to their previous
values when I refresh the display in the gui map window.
