Re: [GRASS-dev] Migration to Discourse

[Anna Petrášová via grass-dev]

Hi Roger,

regarding the maintenance of rgrass, I suggest to seek new maintainers by
posting a new, dedicated email thread to grass-dev and grass-stats. Is
there any documentation that would help onboard potential maintainers?

Anna

On Wed, Oct 2, 2024 at 4:55 PM Michael Barton via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> Hi Roger,
>
> I've looked at the Discourse site and a couple things might be helpful to
> you.
>
> 1. I have not yet seen this in action, but it look like you can request an
> email digest of recent posts, pretty much like the current digest.
>
> 2. You can filter and search the forum more easily than you could with the
> old MailMan online email threads. This may make it easier to find posts
> about rgrass
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On Oct 2, 2024, at 12:00 PM, grass-dev-requ...@lists.osgeo.org wrote:
>
> Date: Wed, 2 Oct 2024 17:16:33 +
> From: Roger Bivand 
> To: "grass-dev@lists.osgeo.org" 
> Subject: Re: [GRASS-dev] Migration to Discourse
> Message-ID:
> <
> sv0p279mb047530a799478dffda02ec5eee...@sv0p279mb0475.norp279.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Moving to discourse replacing digested grass-dev is not a viable option
> for me. Such platforms raise the noise to signal ratio, so picking out
> information relevant for the R/GRASS interface will simply become much more
> time consuming, compared to scanning the daily digest. So I will not be
> accepting the invitation.
>
> Should anyone involved in the R rgrass package and transitioning to
> discourse themselves be willing to take over maintaining the package now,
> I'd be grateful if you could express your willingness now.
>
> Roger
>
> --
> Roger Bivand
> Emeritus Professor
> Norwegian School of Economics
> Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway
> roger.biv...@nhh.no
>
>
> ___
> 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

[GRASS-dev] Migration to Discourse

[Anna Petrášová via grass-dev]

As we previously announced [1], we are going ahead with the transition to
Discourse for the grass-dev mailing list. Currently, the history is all
ported to discourse and anybody can now conveniently view the entire
archive and search through here [2]. The mailing list is now mirrored, new
posts to the the mailing list are visible in discourse. This gives us time
to finish the transition, allowing everybody to migrate. Some time in
November if everything goes well, we will close the current mailing list
(the archive stays).

To continue receiving messages, please register [3] now and join the grass
developer group [4]. Once you are set, you can post new messages to
grass-...@discourse.osgeo.org in the same way as before (just different
email address).

We hope to be able to send out automatic invites for people to join the
group sometime next week, but I suggest not to wait and register now.

Thank you for your patience during this transition.
Anna

[1]
https://discourse.osgeo.org/t/grass-dev-planned-transition-of-grass-dev-mailing-list-to-osgeo-discourse/85537
[2] https://discourse.osgeo.org/c/grass/developer/61
[3] https://discourse.osgeo.org/t/welcome-to-osgeo/5
[4] https://discourse.osgeo.org/g/grass-developers
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Planned transition of grass-dev mailing list to OSGeo Discourse

[Anna Petrášová via grass-dev]

Hi all,

During our last PSC meeting [1] we decided to go ahead with moving the
grass-dev mailing list to OSGeo Discourse [2]. Our intention is to make
this transition as smooth as possible and later proceed with other grass
mailing lists. The history of the grass-dev list should be ported to
discourse and preserved. Once we start using discourse, you have the option
of using the web interface to interact with this list or still using email
for correspondence, with the only difference being sending to the new email
address if you want to start a new topic, or replying to a topic email (
grass-...@discourse.osgeo.org). At this point, you don't need to do
anything yet, we will inform you once an action is required from you. Let
us know if you have any concerns.

Best,
Anna




[1] https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-08-09#Minutes
[2] https://discourse.osgeo.org/t/welcome-to-osgeo/5
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC 2024

[Anna Petrášová via grass-dev]

Just a reminder, we are meeting today to kick off the Google Summer of Code
community bonding period:

Time: May 8, 2024 01:00 PM Eastern Time (US and Canada)
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=5&day=8&hour=17&min=0&sec=0&p1=207&p2=48&p3=51&p4=671

Join Zoom Meeting
https://ncsu.zoom.us/j/91478802764?pwd=NzlNc3ZvN3FMMzZxcVNzUEFsYWV3dz09

On Thu, May 2, 2024 at 3:48 PM Markus Neteler  wrote:

> On Thu, May 2, 2024 at 5:29 PM Anna Petrášová via grass-dev
>  wrote:
> >
> > Hi devs,
> >
> > We plan to have a call with the new Google Summer of Code students. If
> you want to learn more about the projects and meet the students, please
> join the call:
> >
> > Topic: GRASS GIS GSoC 2024
> > Time: May 8, 2024 01:00 PM Eastern Time (US and Canada)
> >
> > Join Zoom Meeting
> > https://ncsu.zoom.us/j/91478802764?pwd=NzlNc3ZvN3FMMzZxcVNzUEFsYWV3dz09
> >
> > Meeting ID: 914 7880 2764
> > Passcode: 868437
> >
> > Best,
> > Anna
>
> Here in some other timezones:
>
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=5&day=8&hour=17&min=0&sec=0&p1=207&p2=48&p3=51&p4=671
>
> (hope I got it right)
>
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2024

[Anna Petrášová via grass-dev]

Hi devs,

We plan to have a call with the new Google Summer of Code students. If you
want to learn more about the projects and meet the students, please join
the call:

Topic: GRASS GIS GSoC 2024
Time: May 8, 2024 01:00 PM Eastern Time (US and Canada)

Join Zoom Meeting
https://ncsu.zoom.us/j/91478802764?pwd=NzlNc3ZvN3FMMzZxcVNzUEFsYWV3dz09

Meeting ID: 914 7880 2764
Passcode: 868437

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

Re: [GRASS-dev] An applicant for GSoC 2024

[Anna Petrášová via grass-dev]

Hi Hamish, good to hear from you! Thanks for pointing that out, I added it
to the GSoC ideas wiki, so in case it won't happen this year, we can try
later.

Anna

On Sun, Apr 7, 2024 at 7:30 AM Hamish B via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> Welcome Chung-Yuan,
>
> Huidae wrote:
> > Please check this feature request at
> https://github.com/OSGeo/grass/issues/2644
> > for testing your skills and let me know if you have any questions.
>
> For whatever it is worth, it always struck me that v.surf.bspline was
> low hanging fruit for OpenMP parallelization, as the code already
> splits the data up into a manageable number of overlapping
> tiles/segments, then processes them serially before recombining them.
>
> See
> https://github.com/OSGeo/grass/blob/main/vector/v.surf.bspline/main.c#L529
> and further comment on line 607 and debug message on line 475.
>
>
> all the best from deep in the South Pacific,
> Hamish
> ___
> 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 2024] OSGeo Grass: Add JSON output to different tools in C

[Anna Petrášová via grass-dev]

Hi Kriti,

I think you can go ahead and submit it!

Anna

On Wed, Mar 27, 2024 at 3:22 PM Kriti Birda 
wrote:

> Hi Anna,
>
> Thanks for the feedback and the insights. I had put 1 per week as a
> conservative estimate but yes I think more should be doable too. Please let
> me know if I should make any other changes to the proposal.
>
> Regards.
>
> On Thu, Mar 28, 2024 at 12:38 AM Anna Petrášová 
> wrote:
>
>> Hi Kriti,
>>
>> Welcome and thank you for your interest! I provided some suggestions in
>> terms of which tools to prioritize. I put two tools per week, I think it's
>> feasible, but please understand this is flexible and one tool a week would
>> be a success as well. The priority of the tools may change as well based on
>> the community input and other factors.
>>
>> Best,
>> Anna
>>
>>
>> On Wed, Mar 27, 2024 at 9:44 AM Kriti Birda via grass-dev <
>> grass-dev@lists.osgeo.org> wrote:
>>
>>> Hello Grass devs,
>>>
>>> I am Kriti Birda, an undergraduate student of Bachelor of Science at
>>> Indian Institute of Technology, Madras. I would like to apply to your
>>> organisation for Google Summer of Code this year. I find the idea to add
>>> JSON output to various tools in Grass particularly interesting. I have also
>>> worked closely with Grass devs over the past few days to add JSON output
>>> support to one module (https://github.com/OSGeo/grass/pull/3528). Here
>>> is a draft project proposal I wrote for my application:
>>> https://docs.google.com/document/d/1CQOAkjKINPeWt7pW561Jp1WEWV90ws-m_ybOQLIWvOM/edit?usp=sharing.
>>> It would be awesome if you could review and provide feedback on how I can
>>> improve it.
>>>
>>> Looking forward to hearing from you. Warm Regards.
>>> ___
>>> 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 2024] OSGeo Grass: Add JSON output to different tools in C

[Anna Petrášová via grass-dev]

Hi Kriti,

Welcome and thank you for your interest! I provided some suggestions in
terms of which tools to prioritize. I put two tools per week, I think it's
feasible, but please understand this is flexible and one tool a week would
be a success as well. The priority of the tools may change as well based on
the community input and other factors.

Best,
Anna


On Wed, Mar 27, 2024 at 9:44 AM Kriti Birda via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> Hello Grass devs,
>
> I am Kriti Birda, an undergraduate student of Bachelor of Science at
> Indian Institute of Technology, Madras. I would like to apply to your
> organisation for Google Summer of Code this year. I find the idea to add
> JSON output to various tools in Grass particularly interesting. I have also
> worked closely with Grass devs over the past few days to add JSON output
> support to one module (https://github.com/OSGeo/grass/pull/3528). Here is
> a draft project proposal I wrote for my application:
> https://docs.google.com/document/d/1CQOAkjKINPeWt7pW561Jp1WEWV90ws-m_ybOQLIWvOM/edit?usp=sharing.
> It would be awesome if you could review and provide feedback on how I can
> improve it.
>
> Looking forward to hearing from you. Warm Regards.
> ___
> 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] [release planning] GRASS GIS 8.3.2

[Anna Petrášová via grass-dev]

+1

Anna

On Wed, Mar 6, 2024 at 9:54 AM Martin Landa  wrote:

> Hi Markus,
>
> I'd now move on and publish GRASS GIS 8.3.2 unless there are objections
>>
>
> +1
>
> Martin
>
> Markus
>>
>> --
>> Markus Neteler, PhD
>> https://www.mundialis.de - company
>> https://grass.osgeo.org - FOSS
>> https://neteler.org - freelancing & blog
>> ___
>> 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 Ideas

[Anna Petrášová via grass-dev]

On Sun, Mar 3, 2024 at 4:07 PM Luca Delucchi  wrote:

> Hi Anna,
>
> On Fri, 1 Mar 2024 at 17:30, Anna Petrášová  wrote:
> >
> > We have already students wanting to work on github issues linked as test
> of skills. Martin and Luca, your ideas don't have a test of skills, please
> add it there as soon as possible, otherwise we can't really use the idea,
> test of skills is required by OSGeo.
> >
>
> Thanks for the reminder, I created this issue
> https://github.com/OSGeo/grass-addons/issues/1033, is it doable or too
> complicated?
>
> Sure, that works!


> > Thank you
> >
>
> --
> 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] Can GRASS import a *.ige file?

[Anna Petrášová via grass-dev]

There should be an .img file, try open that instead.

On Fri, Mar 1, 2024 at 4:51 PM Michael Barton via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> It doesn't look like r.in.gdal does this. Is there an extension or other
> way to import an ERDAS *.ige file?
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> ___
> 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 Ideas

[Anna Petrášová via grass-dev]

Martin, how about using https://github.com/OSGeo/grass/issues/2599 as a
test?

On Fri, Mar 1, 2024 at 11:29 AM Anna Petrášová 
wrote:

> We have already students wanting to work on github issues linked as test
> of skills. Martin and Luca, your ideas don't have a test of skills, please
> add it there as soon as possible, otherwise we can't really use the idea,
> test of skills is required by OSGeo.
>
> Thank you
>
> On Mon, Feb 26, 2024 at 1:32 PM Anna Petrášová 
> wrote:
>
>> Good news, OSGeo was accepted [1]. We need to do some advertising now.
>>
>> [1] https://lists.osgeo.org/pipermail/discuss/2024-February/040113.html
>>
>> On Sat, Feb 24, 2024 at 9:04 AM Anna Petrášová 
>> wrote:
>>
>>>
>>>
>>> On Fri, Feb 23, 2024, 6:11 PM Martin Landa 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev <
>>>> grass-dev@lists.osgeo.org> napsal:
>>>>
>>>>> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac
>>>>> wiki, which I think we should be moving away from):
>>>>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>>>>>
>>>>> It's not updated yet, I plan to add more topics. If you want to mentor
>>>>> a topic, we can discuss it here.
>>>>>
>>>>
>>>> I add a new topic related to space-time datasets and Data Catalog [1].
>>>> Martin
>>>>
>>>
>>> Thanks for adding the topic, please also include a test of skills and at
>>> least for now assign yourself as a mentor, I can be a co-mentor.
>>>
>>> Anna
>>>
>>>>
>>>> [1]
>>>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog
>>>>
>>>> --
>>>> Martin Landa
>>>> https://geomatics.fsv.cvut.cz/en/employees/martin-landa/
>>>> http://gismentors.cz/mentors/landa
>>>>
>>>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Anna Petrášová via grass-dev]

We have already students wanting to work on github issues linked as test of
skills. Martin and Luca, your ideas don't have a test of skills, please add
it there as soon as possible, otherwise we can't really use the idea, test
of skills is required by OSGeo.

Thank you

On Mon, Feb 26, 2024 at 1:32 PM Anna Petrášová 
wrote:

> Good news, OSGeo was accepted [1]. We need to do some advertising now.
>
> [1] https://lists.osgeo.org/pipermail/discuss/2024-February/040113.html
>
> On Sat, Feb 24, 2024 at 9:04 AM Anna Petrášová 
> wrote:
>
>>
>>
>> On Fri, Feb 23, 2024, 6:11 PM Martin Landa 
>> wrote:
>>
>>> Hi,
>>>
>>> so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev <
>>> grass-dev@lists.osgeo.org> napsal:
>>>
>>>> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
>>>> which I think we should be moving away from):
>>>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>>>>
>>>> It's not updated yet, I plan to add more topics. If you want to mentor
>>>> a topic, we can discuss it here.
>>>>
>>>
>>> I add a new topic related to space-time datasets and Data Catalog [1].
>>> Martin
>>>
>>
>> Thanks for adding the topic, please also include a test of skills and at
>> least for now assign yourself as a mentor, I can be a co-mentor.
>>
>> Anna
>>
>>>
>>> [1]
>>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog
>>>
>>> --
>>> Martin Landa
>>> https://geomatics.fsv.cvut.cz/en/employees/martin-landa/
>>> http://gismentors.cz/mentors/landa
>>>
>>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Anna Petrášová via grass-dev]

Good news, OSGeo was accepted [1]. We need to do some advertising now.

[1] https://lists.osgeo.org/pipermail/discuss/2024-February/040113.html

On Sat, Feb 24, 2024 at 9:04 AM Anna Petrášová 
wrote:

>
>
> On Fri, Feb 23, 2024, 6:11 PM Martin Landa  wrote:
>
>> Hi,
>>
>> so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev <
>> grass-dev@lists.osgeo.org> napsal:
>>
>>> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
>>> which I think we should be moving away from):
>>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>>>
>>> It's not updated yet, I plan to add more topics. If you want to mentor a
>>> topic, we can discuss it here.
>>>
>>
>> I add a new topic related to space-time datasets and Data Catalog [1].
>> Martin
>>
>
> Thanks for adding the topic, please also include a test of skills and at
> least for now assign yourself as a mentor, I can be a co-mentor.
>
> Anna
>
>>
>> [1]
>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog
>>
>> --
>> Martin Landa
>> https://geomatics.fsv.cvut.cz/en/employees/martin-landa/
>> http://gismentors.cz/mentors/landa
>>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Anna Petrášová via grass-dev]

On Fri, Feb 23, 2024, 6:11 PM Martin Landa  wrote:

> Hi,
>
> so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev <
> grass-dev@lists.osgeo.org> napsal:
>
>> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
>> which I think we should be moving away from):
>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>>
>> It's not updated yet, I plan to add more topics. If you want to mentor a
>> topic, we can discuss it here.
>>
>
> I add a new topic related to space-time datasets and Data Catalog [1].
> Martin
>

Thanks for adding the topic, please also include a test of skills and at
least for now assign yourself as a mentor, I can be a co-mentor.

Anna

>
> [1]
> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog
>
> --
> Martin Landa
> https://geomatics.fsv.cvut.cz/en/employees/martin-landa/
> http://gismentors.cz/mentors/landa
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Anna Petrášová via grass-dev]

On Thu, Feb 22, 2024 at 12:33 PM Markus Neteler  wrote:

> On Thu, Feb 22, 2024 at 3:59 PM Anna Petrášová 
> wrote:
> > On Tue, Feb 20, 2024 at 5:45 PM Markus Neteler via grass-dev <
> grass-dev@lists.osgeo.org> wrote:
> ...
> >> Hopefully no RC2 is needed.
> >
> > Markus,
> >
> > a bug in r.horizon came up on gitter recently:
> > https://github.com/OSGeo/grass/pull/3441
> >
> > It would be nice to include it in 8.3.2 (with all the other fixes in
> r.horizon) but at the same time I don't want to
> > trigger RC2 because of this... The bug fix is a small change in
> r.horizon not impacting anything else, so
> > perhaps we wouldn't need RC2? What do you think?
>
> For me that's okay as it is very isolated.
> Feel free to backport it.
>
>
Done!


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

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Anna Petrášová via grass-dev]

On Tue, Feb 20, 2024 at 5:45 PM Markus Neteler via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> Hi devs,
>
> On Thu, Feb 1, 2024 at 10:40 PM Markus Neteler  wrote:
> > We have accumulated a number of fixes in the past weeks.
> >
> > Here the milestone:
> > https://github.com/OSGeo/grass/milestone/24
>
> The RC1 release is now available, please test it:
> https://github.com/OSGeo/grass/releases/tag/8.3.2RC1
>
> The open issues/PR I have moved to a new 8.3.3 milestone. But let's
> focus on 8.4.0.
>
> And yay, the Zenodo bridge works again:
> Version 8.3.2RC1: https://zenodo.org/records/10685321
> DOI: https://doi.org/10.5281/zenodo.10685321 (resolver link will work
> in some hs from now)
>
> Hopefully no RC2 is needed.
>

Markus,

a bug in r.horizon came up on gitter recently:
https://github.com/OSGeo/grass/pull/3441

It would be nice to include it in 8.3.2 (with all the other fixes in
r.horizon) but at the same time I don't want to trigger RC2 because of
this... The bug fix is a small change in r.horizon not impacting anything
else, so perhaps we wouldn't need RC2? What do you think?


> Thanks to all contributors,
> Markus
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - company
> https://grass.osgeo.org - FOSS
> https://neteler.org - freelancing & blog
> ___
> 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 Ideas

[Anna Petrášová via grass-dev]

of black
> magick (e.g. three clicks or less to have everything ready for any of
> our intro tutorials, including opening a web browser with the chosen
> tutorial and adding some layers to the map view; two clicks (+ file
> browsing) to have users raster or vector data displayed).
>

 I think Vashek's point was to gently remind you there has been a lot of
discussion going on in the past, not to resurrect one of those ideas:)

>
> Linda, in your paper you wrote: „Since both options were favorably
> rated (85% responded positively to the first-run wizard and 74% to
> info bars), we decided to implement an info bar as a technically
> simpler and more flexible solution.“ The idea of this GSOC proposal
> was to implement in some form the second option that would allow to
> perform A/B testing with real users. As you (et al.) have done a huge
> work with the codebase, now it would be much easier to implement than
> some years a go.
> I also understand that users want to start working with the software
> right away. But here is a catch – most likely nobody will start GRASS
> to work with data provided by the demo project. Either they will start
> GRASS to do some exercises in a training course / to follow a tutorial
> (= download one of sample datasets, add some layer to the map view),
> or to work with data they have to solve the analysis problem they are
> facing (= create a new project from supplied data, import file, add it
> to the map view, display warning about computational region in your
> info bar, if imported data were vectors and not raster). If user
> cancels the wizard, just fine. Let him enjoy the demo project and
> display first time screen also on the next startup iff there is no
> project with data in the GISDBASE. This would not interfere with a
> big, fat warning if someone tries to import external data into sample
> projects (NC, Spearfish, ...) or any other enhancements that could be
> done.
>

 I agree with a lot of points you are making but I guess I still don't
understand exactly what your suggestion is and how it would make things
better and for whom...


> Huh, I think I answered most of points from previous emails (except
> going into details of potential architecture (thus Anna for wxPython
> expertise) or user friendliness (thus Vero)). Thank you to everyone
> who read this far and sorry for all unintentional fuss I caused.
> Probably Linda you are right – it is too ambitious for an experimental
> project that might get tossed away at the end. I see that Anna has
> already removed the idea from the wiki, most likely for good. Do not
> restore it, let it be so. We can return to this idea at any point
> later if we feel need for it. I have plenty to do to fix pointer
> juggling bugs in the new module I have almost finished (anisotropic
> smoothing).
> Māris.
>
> piektd., 2024. g. 16. febr., plkst. 10:41 — lietotājs Linda Kladivová
> () rakstīja:
> >
> > Hello Māris,
> >
> > just to add some other info, we did several surveys among GRASS users
> about first-time user experience with Anna, Martin and Vashek and we also
> tested old and new startup mechanisms in a real environment within the
> usability testing - you can have a look at our article:
> https://www.mdpi.com/2220-9964/12/9/376.
> >
> > As Anna has already written, the results of usability testing were
> indeed mixed but I would like to emphasize one thing - most of the
> usability participants (first-time users) said to me that they simply
> expect they will be directly redirected to the main software window where
> they can start working without knowing anything about the software. The
> current "info bar" solution goes in that direction and although I have to
> admit that it has flaws there are ways how to make it better and Anna has
> already written some points.
> >
> > I think it would be nice to focus on how to make the current solution
> better (it is definitely doable and even desirable) and not go back to some
> alternatives to the old solution.
> > Above that, it would be extremely time-consuming to implement any dialog
> wizards and at the same time the impact of that "dialog" solution is very
> uncertain - one important thing we also learned from surveys and
> discussions inside/outside the community is that the one good generally
> acceptable solution simply does not exist here - it will always be a
> compromise.
> >
> > Just my two cents. :-)
> > Linda
> >
> > -- Původní e-mail --
> > Od: Maris Nartiss via grass-dev 
> > Komu: Anna Petrášová , Veronica Andreo <
> veroand...@gmail.com>
> > Kopie: GRASS-dev 
> > Datum: 15. 2. 2024 13:04:24
> > Předmět: Re: 

Re: [GRASS-dev] GSoC Ideas

[Anna Petrášová via grass-dev]

I believe the welcome screen would most likely be dismissed. The other
possible solutions Brendan brings up may be difficult to implement with
wxpython. But we tried to do something similar with Linda using the info
bar, which shows info/buttons for first-time users. She tested that with
mixed results, people often just dismissed it. But I think it could be
further refined. For example, maybe we could move it to map display to make
it more prominent. The other direction is to better detect when users are
doing something likely wrong (import projected data to default project) and
then suggest alternatives.

On Thu, Feb 15, 2024 at 12:05 PM Brendan  wrote:

> Personally I like the new interface, but Maris' proposal for wizards to
> create new projects sounds helpful. Rather than a startup screen that
> stalls users, there could be temporary icons floating on the map canvas
> that prompt users to create a new project in different ways. Would
> disappear as soon as data is added to the map. A helpful guide/shortcut
> that users could choose to ignore. Still, any startup hints might be
> annoying like Clippy the infamous paperclip. I can find an example from
> other software if the idea is of interest. Or the logo that pops up when
> you start GRASS could have buttons for creating new projects; if a user
> doesn't click on them while GRASS is starting, then it will open in the
> default / previous project.
> Best, Brendan
>
> On Thu, Feb 15, 2024 at 8:35 AM Anna Petrášová via grass-dev <
> grass-dev@lists.osgeo.org> wrote:
>
>> I agree with Vero. I am not sure we had enough time to evaluate the
>> current state yet. I don't remember the details of our discussions, so if
>> you provide a description of what exactly you mean, that would be helpful.
>> In terms of a GSoC project, the main issue I see is that the mentors need
>> to provide clear instructions on what the student should do, especially for
>> this case, and we apparently don't have a consensus here. So I would be
>> willing to mentor it only as long as we develop a plan ahead of time we can
>> all agree on. Given the past experience, I am somewhat skeptical we can all
>> agree on something:) But I'll try to be open to ideas!
>>
>> On Thu, Feb 15, 2024 at 8:12 AM Veronica Andreo 
>> wrote:
>>
>>> Hi Maris,
>>>
>>> Would you mind sharing more details on this idea? I'm afraid I was not
>>> able to attend/hear the discussion about this welcome screen in Prague. I
>>> hope though we do not end up with a new startup screen. It took so much
>>> time to reach an agreement and finally remove it.
>>>
>>> Vero
>>>
>>> El jue, 15 feb 2024 a las 9:00, Maris Nartiss ()
>>> escribió:
>>>
>>>> Hello Anna, Vero.
>>>> I added the welcome screen idea we discussed during our Prague
>>>> meeting. I think it would be a good GSOC project as it is quite easy
>>>> and at the same time will allow to understand if it is the way to go.
>>>> Anna, would you be able to be a co-mentor as it is a GUI project? Or
>>>> who else could be?
>>>> Vero, your user-centric view also would be valuable.
>>>> Please edit the wiki accordingly.
>>>>
>>>> Thanks,
>>>> Māris.
>>>>
>>>> sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via
>>>> grass-dev () rakstīja:
>>>> >
>>>> > Hi,
>>>> >
>>>> > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac
>>>> wiki, which I think we should be moving away from):
>>>> > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>>>> >
>>>> > It's not updated yet, I plan to add more topics. If you want to
>>>> mentor a topic, we can discuss it here.
>>>> >
>>>> > Anna
>>>> > ___
>>>> > grass-dev mailing list
>>>> > grass-dev@lists.osgeo.org
>>>> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>>>>
>>>
>>>
>>> --
>>> Dra. Verónica Andreo
>>> Investigadora Adjunta de CONICET
>>> Instituto Gulich (CONAE - UNC)
>>> Centro Espacial Teófilo Tabanera (CETT)
>>> Falda del Cañete - Córdoba, Argentina
>>> +54 3547 40 int. 1153
>>> https://veroandreo.gitlab.io/
>>>
>> ___
>> 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 Ideas

[Anna Petrášová via grass-dev]

I agree with Vero. I am not sure we had enough time to evaluate the current
state yet. I don't remember the details of our discussions, so if you
provide a description of what exactly you mean, that would be helpful. In
terms of a GSoC project, the main issue I see is that the mentors need to
provide clear instructions on what the student should do, especially for
this case, and we apparently don't have a consensus here. So I would be
willing to mentor it only as long as we develop a plan ahead of time we can
all agree on. Given the past experience, I am somewhat skeptical we can all
agree on something:) But I'll try to be open to ideas!

On Thu, Feb 15, 2024 at 8:12 AM Veronica Andreo 
wrote:

> Hi Maris,
>
> Would you mind sharing more details on this idea? I'm afraid I was not
> able to attend/hear the discussion about this welcome screen in Prague. I
> hope though we do not end up with a new startup screen. It took so much
> time to reach an agreement and finally remove it.
>
> Vero
>
> El jue, 15 feb 2024 a las 9:00, Maris Nartiss ()
> escribió:
>
>> Hello Anna, Vero.
>> I added the welcome screen idea we discussed during our Prague
>> meeting. I think it would be a good GSOC project as it is quite easy
>> and at the same time will allow to understand if it is the way to go.
>> Anna, would you be able to be a co-mentor as it is a GUI project? Or
>> who else could be?
>> Vero, your user-centric view also would be valuable.
>> Please edit the wiki accordingly.
>>
>> Thanks,
>> Māris.
>>
>> sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via
>> grass-dev () rakstīja:
>> >
>> > Hi,
>> >
>> > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
>> which I think we should be moving away from):
>> > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>> >
>> > It's not updated yet, I plan to add more topics. If you want to mentor
>> a topic, we can discuss it here.
>> >
>> > Anna
>> > ___
>> > grass-dev mailing list
>> > grass-dev@lists.osgeo.org
>> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
> --
> Dra. Verónica Andreo
> Investigadora Adjunta de CONICET
> Instituto Gulich (CONAE - UNC)
> Centro Espacial Teófilo Tabanera (CETT)
> Falda del Cañete - Córdoba, Argentina
> +54 3547 40 int. 1153
> https://veroandreo.gitlab.io/
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Anna Petrášová via grass-dev]

I sent the ideas page to OSGeo admins (the deadline is today), although I
think we can keep adding topics. Please also fill out this form
https://forms.gle/dZDYovvmhrQRah73A if you plan to mentor.

Thanks,
Anna

On Mon, Feb 5, 2024 at 7:33 AM Veronica Andreo  wrote:

> That would be cool Luca! eodag allows you to download different EO
> datasets.
>
> Do you think of a GSoC project idea to include eodag support for
> i.sentinel.download, i.landsat.download and i.modis.download or as a new
> module to download EO data in general? If you are willing to mentor, I can
> be your second... mainly to test and make annoying questions :)
>
> Vero
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Anna Petrášová via grass-dev]

On Sat, Feb 3, 2024 at 4:39 AM Luca Delucchi  wrote:

>
>
> Il sab 3 feb 2024, 05:34 Anna Petrášová via grass-dev <
> grass-dev@lists.osgeo.org> ha scritto:
>
>> Hi,
>>
>> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
>> which I think we should be moving away from):
>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>>
>> It's not updated yet, I plan to add more topics. If you want to mentor a
>> topic, we can discuss it here.
>>
>
> Do you think an interface to eodag library, to download sentinel and
> Landsat images for example, could be a topic for gsoc?
>

I suppose so. As long as somebody (you?) would mentor it, we can add it
(including test of skills etc).


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

[GRASS-dev] GSoC Ideas

[Anna Petrášová via grass-dev]

Hi,

I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
which I think we should be moving away from):
https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024

It's not updated yet, I plan to add more topics. If you want to mentor a
topic, we can discuss it here.

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

[GRASS-dev] NSF POSE project progress report

[Anna Petrášová via grass-dev]

Dear all,

In September we announced a new grant [1] that was awarded to enhance GRASS
GIS ecosystem. We would like to share a progress report for 1st quarter [2]
with the community to highlight the efforts that span various repositories
and include participation in several events. The report also includes the
project roadmap.

Best,
Anna for the POSE team (Helena, Vaclav, Anna, Huidae, Michael, Giuseppe)

[1] https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/
[2] https://grasswiki.osgeo.org/wiki/NSF_POSE_Project_2023-2025_Timeline
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS Windows issues

[Anna Petrášová via grass-dev]

Even if the GUI doesn't start, could you still type in:

g.findfile element=cell file=MASK

and also:

g.gisenv

and see what you get?

On Mon, Dec 11, 2023 at 3:04 AM Gandalf the Gray via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> Hi Maris.
>
> Yes I always had ArcGIS installed and it has never given any issues with
> GRASS.
>
> Pieter
>
> On Mon, 11 Dec 2023, 09:19 Maris Nartiss,  wrote:
>
>> Windows issues are hard to debug as most of developers are on Linux boxes.
>> Do you have an ArcGIS install by any chance? In the past ArcGIS was a
>> source of different problems for GRASS as it would register its Python
>> globally and then GRASS would pick wrong Python version resulting
>> myriad of strange errors.
>>
>> M.
>>
>> svētd., 2023. g. 10. dec., plkst. 17:25 — lietotājs Gandalf the Gray
>> via grass-dev () rakstīja:
>> >
>> > Hi Jeff
>> >
>> > Thanks for the link.  I installed the 8.4 dev version. and it gives
>> exactly the same error as with GRASS standalone from grass,osgeo.org,
>> GRASS installed with OSGeo4W, and from the QGIS standalone installer.
>> >
>> > I am now suspecting that it might not be the wxpython included in the
>> installers, but my pc itself.
>> >
>> > Regards
>> >
>> > Pieter
>> >
>> > On Sun, Dec 10, 2023 at 2:52 PM Jeff McKenna via grass-dev <
>> grass-dev@lists.osgeo.org> wrote:
>> >>
>> >> Hi Pieter,
>> >>
>> >> I personally always recommend using WinGRASS, it is very reliable.
>> >> (thanks to MartinL)  https://wingrass.fsv.cvut.cz/grass84/
>> >>
>> >> Merry Christmas to you and the GRASS GIS family,
>> >>
>> >> -jeff
>> >>
>> >>
>> >>
>> >> --
>> >> Jeff McKenna
>> >> GatewayGeo: Developers of MS4W, & offering MapServer Consulting/Dev
>> >> co-founder of FOSS4G
>> >> http://gatewaygeo.com/
>> >>
>> >>
>> >>
>> >> On 2023-12-09 12:17 a.m., Gandalf the Gray via grass-dev wrote:
>> >> > Hi guys.
>> >> >
>> >> > In desperation I am posting to this list.  I have posted on the
>> OSGeo4W
>> >> > list a week ago to no avail.
>> >> >
>> >> > I hope someone can help me.
>> >> >
>> >> > On a clean install of OSGeo4W (and for that matter standalone QGIS
>> and
>> >> > GRASS installers), I get the following error (see attached
>> screenshot)
>> >> > starting any version of GRASS.
>> >> >
>> >> > On GRASS 7, I can do a mapset selection before crash, but the other 2
>> >> > just crashes.
>> >> >
>> >> > Install is on a machine that ran GRASS up until a week ago, until I
>> >> > uninstalled the OSGeo4W stack, and deleted everything.  There is
>> nothing
>> >> > strange about my Windows Setup
>> >> >
>> >> > I hope anyone can help me, and I hope you can see the screenshot.
>> >> >
>> >> > Regards
>> >> >
>> >> > Pieter
>> >> >
>> >> > _
>> >>
>> >> ___
>> >> 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
>>
> ___
> 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] Parallelizing algorithms

[Anna Petrášová via grass-dev]

Hi Shreyas,

That's a great effort, would you be able to share the progress with us?
Usually, it's good if multiple people test it on different hardware, see
for example a previous parallelization contribution [1]. To measure the
performance, there is a benchmarking library [2] you can use. There are
benchmarking scripts in the source code for some tools, see for example [3]
or see a benchmarking example in a jupyter notebook [4].

Anna

[1] https://github.com/OSGeo/grass/pull/1782
[2] https://grass.osgeo.org/grass83/manuals/libpython/grass.benchmark.html
[3] https://github.com/OSGeo/grass/tree/main/raster/r.neighbors/benchmark
[4]
https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023/blob/main/01_intro_to_GRASS_parallelization.ipynb

On Tue, Dec 5, 2023 at 3:28 AM Shreyas Udaya via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> I am currently parallelizing raster algorithms of grass using OpenMP and I
> am supposed to evaluate their performance compared to original algorithm.
> Is there any standard way to do this?
> ___
> 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] [GRASS-user] cost surface with negative friction odd behavior

[Anna Petrášová via grass-dev]

Michael, could you please create a PR for the documentation?

On Wed, Nov 29, 2023 at 3:56 PM Michael Barton via grass-user <
grass-u...@lists.osgeo.org> wrote:

> Thanks Anna and Doug,
>
> I did not expect it to work (thought it would be useful if it did). Rather
> I was surprised by the fact that r.walk DID run and that it gave very odd
> results.
>
> Adding to the docs is a good idea. Even better would also to have a
> friction map with a negative value (min<0) raise an error in r.walk, saying
> that all values in a friction map must be ≥ 0
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On Nov 29, 2023, at 1:00 PM, grass-user-requ...@lists.osgeo.org wrote:
>
> Date: Wed, 29 Nov 2023 10:17:19 -0500
> From: Anna Petr??ov? 
> To: Michael Barton 
> Cc: GRASS developers , GRASS user list
> 
> Subject: Re: [GRASS-user] cost surface with negative friction odd
> behavior
> Message-ID:
> 
> Content-Type: text/plain; charset="utf-8"
>
> I think r.walk was not written for negative friction and while I imagine
> some small (in absolute sense) negative values may work, your negative
> values are pretty extreme, meaning the resulting travel time through a cell
> would be negative. That can cause all kinds of issues in the algorithm. So
> I would say friction should not be negative. I am not sure I would check
> that in the code, because you would need to check that for each cell and I
> think it's unnecessary overhead. Maybe just adding a note to documentation
> may be enough. I haven't looked into the code itself, so this is just my
> guess.
>
> Anna
>
> On Tue, Nov 28, 2023 at 5:48?PM Michael Barton via grass-user <
> grass-u...@lists.osgeo.org> wrote:
>
>
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-user] cost surface with negative friction odd behavior

[Anna Petrášová via grass-dev]

I think r.walk was not written for negative friction and while I imagine
some small (in absolute sense) negative values may work, your negative
values are pretty extreme, meaning the resulting travel time through a cell
would be negative. That can cause all kinds of issues in the algorithm. So
I would say friction should not be negative. I am not sure I would check
that in the code, because you would need to check that for each cell and I
think it's unnecessary overhead. Maybe just adding a note to documentation
may be enough. I haven't looked into the code itself, so this is just my
guess.

Anna

On Tue, Nov 28, 2023 at 5:48 PM Michael Barton via grass-user <
grass-u...@lists.osgeo.org> wrote:

> In teaching a class about modeling movement, we talked about how to
> represent a cost surface when some areas of terrain (e.g., water or paved
> roads), could be crossed more rapidly than walking across unmodified
> topography. Since a friction map for r.walk adds cost in seconds/meter to
> the cost of walking across unmodified terrain, I wondered if a friction map
> with **negative costs** would decrease the movement costs across a
> landscape.
>
> Using the SC demo data set, I tried this with a set of maps I prepared for
> class. Previously, I had created a friction map from the landclass96 map
> such that cells with water (class 20) have a value of 90 sec/m, dense
> vegetation (classes 7-19) have a value of 20 sec/m, and the rest of the
> cells have a value of 0 sec/m. I generated a cost surface with r.walk using
> elevation and this friction map with a starting point from the Dorothea Dix
> Hospital.
>
> r.walk --overwrite -k elevation=elevation@PERMANENT
> friction=landclass96_friction output=dd_hospital_seconds_friction
> outdir=dd_hospital_directions_friction start_points=DD_hospital memory=1000
>
> This behaved as expected and created a cost surface that represented
> different degrees of difficulty in crossing vegetated and inundated
> terrain.
>
> To explore what would happen with a friction surface with negative
> numbers, I simply subtracted the previous friction map from 0 so that dense
> vegetation = -20, water = -90, and the rest of the cells = 0. Then I used
> it with r.walk and the elevation DEM.
>
> r.walk -k elevation=elevation@PERMANENT
> friction=landclass96_friction_negative
> output=dd_hospital_seconds_negativefriction
> outdir=dd_hospital_directions_negativefriction start_points=DD_hospital
> memory=2000
>
> There was no error, but the resulting cost surface is very strange.
>
> The data range of the original cost surface with the positive values
> friction map is:
>
> Range of data:min = 0  max = 103883.003593944 (max of 28.8 hours to
> reach the hospital given added costs of walking through dense vegetation or
> avoiding water).
>
> However, the data range of the cost surface made with the friction map
> with negative values is completely weird.
>
> Range of data:min = -166202271.811971  max = -154320.938078961 (-46167
> to -43 hours)
>
> Since a friction map simply adds cost to the cost surface, if a negative
> friction map did not work, I might expect it to raise an error or have no
> impact (values < 0 become 0). But the values in the resulting cost surface
> don't make any sense at all.
>
> Does anyone have any thoughts on this?
>
> I will try to attach attach the original friction map made from the SC
> landclass96 map, the cost surface made with elevation and friction map, and
> cost surface made with elevation and negative friction map.
>
> Michael
>
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Contents for FOSS4G Asia 2023

[Anna Petrášová via grass-dev]

I created a PR with some small improvements. Looks good!

On Fri, Nov 24, 2023 at 10:15 PM Huidae Cho  wrote:

> Dear All,
>
> I'm currently working on slides for FOSS4G Asia 2023 next week. If I
> missed any important things, please let me know or feel free to create PRs.
> Any help would be appreciated!
>
> https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023
>
> Best,
> Huidae
> --
> Huidae Cho, Ph.D., GISP, /hidɛ 
> t͡ɕo/, 조희대, 曺喜大
> GRASS GIS Developer
> https://idea.isnew.info/
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS Mentoring Program

[Anna Petrášová via grass-dev]

Dear all,

I would like to bring to your attention a newly started
development-oriented mentoring program focused on students, researchers,
and software developers who want to integrate GRASS GIS into their
projects. See the announcement with details and application form on GRASS
website:

https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/

Let me know if you have any questions about applying to the program and
please share this announcement in your circles.

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

Re: [GRASS-dev] GRASS Working Groups

[Anna Petrášová via grass-dev]

Thanks to everyone who responded! I will keep the survey [1] open until the
end of the week. Alternatively, just let me know directly if you want to
join.

Based on the responses I created wiki pages for the different working
groups [2] and added the respondents to the particular group. I assigned a
group coordinator to each group to get us started. For those of you who
already have access to the wiki, please add what kind of issues you are
interested in within the working group. If you don't have a GRASS wiki
account, you can either try to create it or ask me or the other group
coordinators to fill those details for you. There may be some changes in
the wiki authentication now [3], so I am unsure whether signing up at this
point is feasible or not.

The coordinators (me, Vashek, Helena) will reach out to the members of each
group to discuss preferred communication channels. We would like to use the
current development platform as much as possible so it would be helpful for
you to have a GitHub account.

Thanks again,
Anna


[1] https://forms.gle/BXzooNYBjgkjMmYk9
[2] https://grasswiki.osgeo.org/wiki/Working_Groups
[3] https://lists.osgeo.org/pipermail/grass-dev/2023-October/096070.html


On Tue, Oct 3, 2023 at 11:23 PM Anna Petrášová 
wrote:

> Dear all,
>
> We would like to establish working groups to better coordinate the GRASS
> community activities such as software development, documentation, promotion
> and fostering relations with other communities. If you are interested in
> any of these topics or are already involved in these activities, please
> consider joining the particular working group. Joining a working group is
> also a great way for you to provide feedback on various issues, plug into
> the community and contribute your expertise.
>
> See the form for the proposed working groups and consider signing up:
>
> https://forms.gle/BXzooNYBjgkjMmYk9
>
> There is also a place in the form for your feedback. Once we get your
> responses I will be back with more details to get the working groups
> started.
>
> Thank you,
> Anna
>
>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS Working Groups

[Anna Petrášová via grass-dev]

Dear all,

We would like to establish working groups to better coordinate the GRASS
community activities such as software development, documentation, promotion
and fostering relations with other communities. If you are interested in
any of these topics or are already involved in these activities, please
consider joining the particular working group. Joining a working group is
also a great way for you to provide feedback on various issues, plug into
the community and contribute your expertise.

See the form for the proposed working groups and consider signing up:

https://forms.gle/BXzooNYBjgkjMmYk9

There is also a place in the form for your feedback. Once we get your
responses I will be back with more details to get the working groups
started.

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

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Anna Petrášová via grass-dev]

On Thu, Sep 28, 2023 at 1:15 AM Markus Neteler  wrote:

> Hi devs,
>
> May we schedule RC1 by end of the week?
>

+1 from me

>
> Markus
>
>
> Anna Petrášová  schrieb am Mo., 25. Sep. 2023,
> 23:08:
>
>>
>>
>> On Mon, Sep 25, 2023 at 3:23 PM Tomas Zigo via grass-dev <
>> grass-dev@lists.osgeo.org> wrote:
>>
>>> Citát Markus Neteler :
>>> > In addition, we have plenty of wxGUI fixes, which might well go in:
>>> >
>>> > https://github.com/OSGeo/grass/labels/backport%20to%208.3
>>> >
>>> > Markus
>>>
>>> I am in favor of including all necessary wxGUI fixes soon as possible
>>> in the 8.3.1 release.
>>>
>>> https://github.com/OSGeo/grass/labels/backport%20to%208.3
>>>
>>> Tomas
>>>
>>
>> Thanks for all the fixes, I started to go through them and will continue
>> the reviews.
>>
>> Anna
>>
>>>
>>>
>>>
>>> ___
>>> 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] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Anna Petrášová via grass-dev]

On Mon, Sep 25, 2023 at 3:23 PM Tomas Zigo via grass-dev <
grass-dev@lists.osgeo.org> wrote:

> Citát Markus Neteler :
> > In addition, we have plenty of wxGUI fixes, which might well go in:
> >
> > https://github.com/OSGeo/grass/labels/backport%20to%208.3
> >
> > Markus
>
> I am in favor of including all necessary wxGUI fixes soon as possible
> in the 8.3.1 release.
>
> https://github.com/OSGeo/grass/labels/backport%20to%208.3
>
> Tomas
>

Thanks for all the fixes, I started to go through them and will continue
the reviews.

Anna

>
>
>
> ___
> 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] Learn more about NSF funded project for GRASS ecosystem

[Anna Petrášová via grass-dev]

We just successfully finished the first session and the second one is
coming up tomorrow (EST/New York at 10am, CEST/Brussels at 4pm).
We recorded the presentation part, for those who joined late or can't join
tomorrow, I can privately share the recording.

Best,
Anna


On Tue, Sep 19, 2023 at 10:33 AM Anna Petrášová 
wrote:

> For those interested to join us, the first session is coming up this
> Thursday (EST/New York at 2pm, CEST/Brussels at 8pm). You can join with a
> zoom link:
> https://ncsu.zoom.us/j/97419521476?pwd=cmx3TitGYjZiYWxzd241U0J0TzVUdz09
>
> If you can't make it, you can join the second session on Friday (EST/New
> York at 10am, CEST/Brussels at 4pm).
>
> Looking forward to seeing you there!
>
> Anna
>
> On Mon, Sep 11, 2023 at 4:57 PM Anna Petrášová 
> wrote:
>
>> As a follow up on our announcement about the NSF funded project to
>> enhance GRASS ecosystem [1] I would like to invite everybody interested to
>> an info session! We will briefly explain what we hope to achieve in this
>> project and how you can get involved. There will be time for Q&A as well.
>> To allow as many people to join, we plan two 1-hour info sessions at
>> different days and times:
>>
>> * Thursday, September 21
>> 
>>  (EST
>> 2pm, Europe 8pm)
>> * Friday, September 22
>> 
>>  (EST
>> 10am, Europe 4pm)
>>
>> The content of both sessions will be the same. I will send zoom links a
>> day before each event.
>> Hope to see you there!
>>
>> Anna
>>
>>
>> [1] https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/
>>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev