Handling of nodata values at raster borders for modules which involve focal
functions would be handy to have for several GRASS GIS modules, not just
for r.slope.aspect. IMHO r.mapcalc, r.texture, and r.resamp.interp (if
using bilinear or cubic resampling) would also benefit from this option
(perhap
On Sat, Apr 28, 2018 at 12:33 AM, Luca Delucchi wrote:
> On 25 April 2018 at 05:40, Anna Petrášová wrote:
>> Hi Sanjeet,
>>
> Hi Sanjeet, Anna
>>
>> welcome! For start, please create a wiki page on trac wiki (you should
>> already have access there), look at the examples from the past years,
>> a
#3554: r.slope.aspect: add flag/functionality to not shrink
-+-
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 8.0.0
Component: Raster |Version: svn-t
#3550: USGS url changed
--+-
Reporter: frankie | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
Component: Default |Version: unspecified
Resolution: | K
On 28 April 2018 at 14:54, Markus Neteler wrote:
> Hi all,
>
Hi,
>
> Just as a reminder, please edit and add your suggestions.
>
It is fine for me, we should start to modify the website, I can help
moving the content but not with the style
> Best,
> Markus
>
--
ciao
Luca
www.lucadelu.o
Hi all,
Veronica Andreo schrieb am Fr., 23. März 2018, 15:22:
> Hi devs,
>
> We have created a wiki:
> https://grasswiki.osgeo.org/wiki/GRASS-Wiki/CMS_migration_plan_2018
> with a draft list of priorities on pages from our current website that we
> should migrate and some ideas of which current
Gh
Veronica Andreo schrieb am Fr., 23. März 2018, 15:22:
> Hi devs,
>
> We have created a wiki:
> https://grasswiki.osgeo.org/wiki/GRASS-Wiki/CMS_migration_plan_2018
> with a draft list of priorities on pages from our current website that we
> should migrate and some ideas of which current p