Re: [GRASS-dev] [GRASS GIS] #3554: r.slope.aspect: add flag/functionality to not shrink

[Steven Pawley]

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
(perhaps other tools as well). Although some users may be concerned that
filling nodata values at raster borders can create edge effects, in most
cases the common approaches (such as mirroring, reflecting or wrapping)
leave little in the way of an obvious edge effect, and also satisfy what I
think are most user's expectations that the output raster will have the
same dimensions as the input.

Although a similar effect can be achieved by growing the input raster
first, this can be inconvenient when used as part of a complex set of focal
function operations. An example is that I have just completed working on an
updated r.valley.bottom module, which required multiple r.grow operations
as the algorithm repeatedly generalizes the input DEM and calculate
flatness and lowness using r.slope.aspect and r.mapcalc focal functions. It
also appears that most other tools, including SAGA-GIS, scipy (image
filters), and gdaldem  provide a method to handle raster borders.


On Sat, Apr 28, 2018 at 2:55 PM GRASS GIS  wrote:

> #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-trunk
>  Keywords:   |CPU:  All
>  Platform:  All  |
> -+-
>  at the moment, the result maps of r.slope.aspect, e.g. slope etc, are
>  shrinked by 1 pixel.
>
>  adding a flag/functionality to not shrink the result maps e.g. by adding
>  the same value as the -1 off pixel, some interpolations or similar as an
>  enhancement.
>
> --
> Ticket URL: 
> GRASS GIS 
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Introduction

[Sanjeet]

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,
>> and follow similar structure:
>> https://trac.osgeo.org/grass/wiki/GSoC
>>
> yes please create the page looking at previous year projects.

Hi,

Here is my wiki page link:
https://trac.osgeo.org/grass/wiki/GSoC/2018/FullSupportPython3

-- 
Sanjeet Bhatti
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3554: r.slope.aspect: add flag/functionality to not shrink

[GRASS GIS]

#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-trunk
 Keywords:   |CPU:  All
 Platform:  All  |
-+-
 at the moment, the result maps of r.slope.aspect, e.g. slope etc, are
 shrinked by 1 pixel.

 adding a flag/functionality to not shrink the result maps e.g. by adding
 the same value as the -1 off pixel, some interpolations or similar as an
 enhancement.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3550: USGS url changed

[GRASS GIS]

#3550: USGS url changed
--+-
  Reporter:  frankie  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  All
--+-

Comment (by lucadelu):

 The link doesn't work, could you provide a working one.

 However do you speak about the
 [https://grass.osgeo.org/grass74/manuals/r.in.srtm.html r.in.srtm manual]?

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] new website: draft roadmap and collection of ideas

[Luca Delucchi]

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.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] new website: draft roadmap and collection of ideas

[Markus Neteler]

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 pages should/might be
> combined into something new.
>
> May this wiki also serve as a place to collect your ideas and examples
> about what we want in the new website (which is currently empty here:
> https://staging.grass.osgeo.org/).
>
> Please edit, add your opinion and ideas :)
>


Just as a reminder, please edit and add your suggestions.

Best,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] new website: draft roadmap and collection of ideas

[Markus Neteler]

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 pages should/might be
> combined into something new.
>
> May this wiki also serve as a place to collect your ideas and examples
> about what we want in the new website (which is currently empty here:
> https://staging.grass.osgeo.org/).
>
> Please edit, add your opinion and ideas :)
>
> Cheers,
> Vero
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Introduction

[Luca Delucchi]

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,
> and follow similar structure:
> https://trac.osgeo.org/grass/wiki/GSoC
>

yes please create the page looking at previous year projects.

> We will need to decide how to manage your contributions, since you
> won't have access rights to the svn repository. We might need to do it
> similarly as we did with one student 2 years ago, he tracked the
> applied changesets in his github repository, which could be then
> submitted to Google in the end of the program. You could post your
> changes in tickets (created specifically for this GSoC) and they will
> be applied by me, Luca or other developers. I understand this is not
> ideal workflow, so if anybody has better idea, let me know.
>

I fully agree, I think small patches (for example a patch for each
file you modify) is better then bigger, so we can look it

> For the community bonding period there are couple things I suggest.
> * make sure you have all the development environment ready (you
> probably have that already)
> * have good idea about the code structure
> * make yourself familiar with the testing framework, I would like you
> to use it to update current tests of the libraries, adjust them to
> work with Python3 and write new tests:
>   https://grass.osgeo.org/grass74/manuals/libpython/gunittest_testing.html
>   http://fatra.cnr.ncsu.edu/grassgistests/summary_report/
> * specifically start looking at Python scripting library, it would be
> great if you could start working on it during the bonding period,
> specific challenges you may encounter there may help us get the
> discussion going.
>

yes, to start you can just launch GRASS and from the command line in
GRASS launch a Python3 console, it work.

Please use standard North Carolina dataset [0], the tests actually use
the "basic" version of the dataset

> I will let you know if I think of more things. Please send your
> questions/concerns either directly to me and Luca, or copy also the
> grass-dev mailing list, so that we can keep other developers in the
> loop.
>
> Thank you and looking forward to working with you,
>
> Anna
>


[0] http://grass.osgeo.org/download/sample-data/

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev