Re: [GRASS-user] i.topo.corr ignores pixel at the edge of the computational region

On Fri, Dec 4, 2015 at 4:34 PM, Panagiotis Mavrogiorgos wrote: > Hi all, > > Why is i.topo.corr ignoring/throwing away some pixel rows at the edge of > the computational region? It is not a big deal but am I doing >

Re: [GRASS-user] r.damflood example

On Fri, Dec 4, 2015 at 9:50 AM, Panagiotis Mavrogiorgos wrote: > > > On Wed, Dec 2, 2015 at 4:46 PM, Anna Petrášová > wrote: > >> >> >> On Wed, Dec 2, 2015 at 7:20 AM, Panagiotis Mavrogiorgos > > wrote: >> >>> Hi all, >>> >>> I am

Re: [GRASS-user] r.damflood example

On Wed, Dec 2, 2015 at 4:46 PM, Anna Petrášová wrote: > > > On Wed, Dec 2, 2015 at 7:20 AM, Panagiotis Mavrogiorgos > wrote: > >> Hi all, >> >> I am trying to run r.damflood but I am running into trouble. >> Unfortunately the documentation has no

[GRASS-user] Fwd: Geospatial devroom at FOSDEM 2016

FYI - please submit (GRASS GIS related) talk proposals! -- Forwarded message -- From: Johan Van de Wauw Date: Fri, Dec 4, 2015 at 1:21 PM Subject: Geospatial devroom at FOSDEM 2016 To: fosdem-geospatial Hello, All of you

Re: [GRASS-user] Unique IDs for network segments

Moritz, thank you! Your proposed approach solved my problem! On Thu, Dec 3, 2015 at 3:04 PM, Moritz Lennert wrote: > On 03/12/15 14:19, Johannes Radinger wrote: > >> Hi Moritz, >> >> The two-step v.category approach (del + add) and an additional v.to.db() >>

[GRASS-user] i.topo.corr ignores pixel at the edge of the computational region

Hi all, Why is i.topo.corr ignoring/throwing away some pixel rows at the edge of the computational region? It is not a big deal but am I doing something wrong? In the following image the purple is the illumination model while the brown area

Re: [GRASS-user] i.topo.corr ignores pixel at the edge of the computational region

Even when I use the resampled DEM, i.topo.corr still creates maps with null cells at the edge... Here is a sceenshot from mapswipe. After digging a little bit deeper it seems that the created maps have null cells

Re: [GRASS-user] i.topo.corr ignores pixel at the edge of the computational region

On Fri, Dec 4, 2015 at 6:21 PM, Markus Neteler wrote: > On Fri, Dec 4, 2015 at 4:37 PM, Panagiotis Mavrogiorgos > wrote: > > > Question. Is the output we get from a higher resolution dem usable, or > > should we resample it? > > For i.topo.corr I would

Re: [GRASS-user] i.topo.corr ignores pixel at the edge of the computational region

On Fri, Dec 4, 2015 at 4:37 PM, Panagiotis Mavrogiorgos wrote: > On Fri, Dec 4, 2015 at 4:34 PM, Panagiotis Mavrogiorgos > wrote: >> >> Hi all, >> >> Why is i.topo.corr ignoring/throwing away some pixel rows at the edge of >> the computational region? It is

Re: [GRASS-user] Do filters available in GRASS takes care of cell padding?

Uttam Kumar wrote: > 4.) Which one of the above GRASS commands would be best suited to perform > window operation (high pass filtering) along with cell padding? One caveat to my previous reply: Ignoring nulls often doesn't work so well for kernels with a zero sum (e.g your high-pass filter).

Re: [GRASS-user] Do filters available in GRASS takes care of cell padding?

Uttam Kumar wrote: > If I am trying to use > > r.mfilter input=band5 output=band5_highpassfilter > filter=/Users/Uttam/high_pass_filter > > where high_pass_filter is > > TITLE 5x5 High Pass > MATRIX 5 > -1 -1 -1 -1 -1 > -1 -1 -1 -1 -1 > -1 -1 24 -1 -1 > -1 -1 -1 -1 -1 > -1 -1 -1 -1 -1 >

Re: [GRASS-user] i.topo.corr ignores pixel at the edge of the computational region

Il 04/12/2015 18:43, Panagiotis Mavrogiorgos ha scritto: Even when I use the resampled DEM, i.topo.corr still creates maps with null cells at the edge... This is not a issue per se, sometimes it's expected, could also be a wanted behaviour because at the border you don't have enough data to

Re: [GRASS-user] i.topo.corr ignores pixel at the edge of the computational region

Il 04/12/2015 18:43, Panagiotis Mavrogiorgos ha scritto: Even when I use the resampled DEM, i.topo.corr still creates maps with null cells at the edge... This is not a issue per se, sometimes it's expected, could also be a wanted behaviour because at the border you don't have enough data to