[GRASS-user] GRASS GIS Mentoring Program

2023-11-06 Thread Anna Petrášová via grass-user
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:

Re: [GRASS-user] Learn more about NSF funded project for GRASS ecosystem

2023-09-21 Thread Anna Petrášová via grass-user
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

[GRASS-user] GRASS Working Groups

2023-10-03 Thread Anna Petrášová via grass-user
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,

Re: [GRASS-user] GRASS Working Groups

2023-10-10 Thread Anna Petrášová via grass-user
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

[GRASS-user] NSF POSE project progress report

2023-12-12 Thread Anna Petrášová via grass-user
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

Re: [GRASS-user] re-setting bathymetry data using the raster calculator.

2023-12-26 Thread Anna Petrášová via grass-user
On Thu, Dec 21, 2023 at 4:45 AM Victor Lundström wrote: > Hi Anna, thank you for responding! > > No I haven't tried running r.walk using negative values, I guess I could > give it a try. But, if I remember correctly, didn't Michael Barton inquired > about the use of negative values and r.walk

Re: [GRASS-user] re-setting bathymetry data using the raster calculator.

2023-12-20 Thread Anna Petrášová via grass-user
Hi Victor, I am not sure I understand your concern. Have you tried running r.walk with the original raster with negative values? Theoretically, I don't see why r.walk couldn't work with negative elevation, although I haven't tried it. It should work the same if you add a constant value as you

[GRASS-user] GRASS annual report 2023

2023-12-20 Thread Anna Petrášová via grass-user
Dear all, We are preparing a report on all GRASS-related achievements in the year 2023 and we would like your input! For example, if you presented at a conference about GRASS, we would like to hear about this and include it. The report will be posted as a news item on grass.osgeo.org. See the

Re: [GRASS-user] GRASS annual report 2023

2023-12-29 Thread Anna Petrášová via grass-user
Thanks for the input, the news item is now live: https://grass.osgeo.org/news/2023_12_19_annual_report/ On Thu, Dec 21, 2023 at 12:04 AM Anna Petrášová wrote: > Dear all, > > We are preparing a report on all GRASS-related achievements in the year > 2023 and we would like your input! For

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

2023-11-29 Thread Anna Petrášová via grass-user
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

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

2023-11-30 Thread Anna Petrášová via grass-user
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-user@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

[GRASS-user] Student grants

2023-11-13 Thread Anna Petrášová via grass-user
Dear all, We would like to announce a paid opportunity for students to contribute to GRASS GIS! GRASS GIS will offer a number of student grants for projects that include development of GRASS documentation, tests, new features or geospatial tools and bug fixing. Check the wiki for details on how

Re: [GRASS-user] Open GRASS at remote grassdata

2024-05-01 Thread Anna Petrášová via grass-user
Yes, this has changed, you can add a new directory from the data catalog: https://youtu.be/OCcM1XfxHW8?feature=shared=370 On Wed, May 1, 2024 at 2:45 PM Stuart Edwards via grass-user < grass-user@lists.osgeo.org> wrote: > Hi - > > I am trying to open GRASS 8.3 using a grassdata directory located

Re: [GRASS-user] How to avoid Grass84 compiling against the system Python3.6?

2024-03-22 Thread Anna Petrášová via grass-user
There is GRASS_PYTHON variable you can try. Running GRASS in virtual environment should work too. On Thu, Mar 21, 2024 at 2:39 AM Hernán De Angelis via grass-user < grass-user@lists.osgeo.org> wrote: > I understand you are using openSUSE Leap. At the moment I cannot check > which Python version

Re: [GRASS-user] [GRASS-dev] Can GRASS import a *.ige file?

2024-03-01 Thread Anna Petrášová via grass-user
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-...@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 >

Re: [GRASS-user] computing percent cover

2024-06-05 Thread Anna Petrášová via grass-user
Hi Janet, you could run r.report: r.report map=patches,landcover But the output is not easily parseable. r.report internally runs r.stats: r.stats -a input=patches,landcover separator=comma you get output like (patch id, landcover id, area): 2,1,1205379.00 1,5,938148.75