Re: [GRASS-user] Mini project 2024: Third progress report

[Veronica Andreo via grass-user]

Thanks for the report Linda!! And congratulations on the new family
member!! 殺

Greetings from the GRASS GIS family!
Vero

El lun, 22 abr 2024 a las 3:51, Linda Karlovská via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hello guys,
>
> I am sending my third progress report from working on the GRASS mini
> project called Easy command history navigation through the History browser
> panel. You can also access the detailed report here: [1].
>
> 1) What did I complete?
> I completed the PR [2] which enables storing more information about
> executed commands. Newly, commands are stored in JSON format and then
> displayed as the command info in the history pane. I also completed the
> relocation of the Export history button from the Console pane to the
> History pane (PR [3]).
>
> Besides that, I am working on [4] and [5]. The first PR creates a new
> button for setting the current region to the region used during the command
> execution. This PR is awaiting the final review. The second contribution
> adds time branching to the history browser tree and is currently waiting
> for the review.
>
> 2) What am I going to achieve for the next two weeks?
> I would like to merge both [4] and [5]. Subsequently, I plan to shift my
> focus toward visualization of command status. I plan to add icons in front
> of command nodes representing possible states (success, failed, in process,
> aborted). Regarding the status, it would also be nice to show the complete
> error text if a command fails. (Now there is “failed” written but no clue
> what happened).
>
> 3) Is there any blocking issue?
> No, it isn’t. I have just been much more busy the last two months since on
> the 19th of February, my two-member family expanded by one little guy, my
> son Vilem. So any work has gone kind of slowly over the last two months… 
>
> Have a nice week.
>
> Linda
>
> [1]
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation#Reportforweeks5and6
> [2] https://github.com/OSGeo/grass/pull/3365
> [3] https://github.com/OSGeo/grass/pull/3402
> [4] https://github.com/OSGeo/grass/pull/3421
> [5] https://github.com/OSGeo/grass/pull/3622
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

Re: [GRASS-user] Using RStudio in a GRASS GIS session

[Veronica Andreo via grass-user]

Ok, so it is on Windows. How did you install GRASS and how/where are you
calling R from? Is it from the GRASS terminal? Does it actually opens an R
session? the library command is a basic R function, so it is weird
that it is not recognized.

This is what I see in my Linux box:

vandreo@arches:~$ grass
Starting GRASS GIS...

  __  ___   _____
 / / __ \/   | / ___/ ___/   / /  _/ ___/
/ / __/ /_/ / /| | \__ \\_  \   / / __ / / \__ \
   / /_/ / _, _/ ___ |___/ /__/ /  / /_/ // / ___/ /
   \/_/ |_/_/  |_///   \/___///

Welcome to GRASS GIS 8.3.0
GRASS GIS homepage:  https://grass.osgeo.org
This version running through:Bash Shell (/bin/bash)
Help is available with the command:  g.manual -i
See the licence terms with:  g.version -c
See citation options with:   g.version -x
If required, restart the GUI with:   g.gui wxpython
When ready to quit enter:exit

Launching  GUI in the background, please wait...

GRASS nc_basic_spm_grass7/PERMANENT:~ > R

R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
Copyright (C) 2023 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

  Natural language support but running in an English locale

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(rgrass)
GRASS GIS interface loaded with GRASS version: GRASS 8.3.0 (2023)
and location: nc_basic_spm_grass7
>

How does it look like there?

El jue, 18 abr 2024 a las 14:02,  escribió:

> Dear Veronica and Micha
>
>
>
> Find enclosed some info about the operative system:
>
>
>
> System
> Info
>
> GRASS version:
> 8.3.2
>
> Code revision:
> 695385bb79
>
> Build date:
> 2024-03-07
>
> Build platform:
> x86_64-w64-mingw32
>
> GDAL:
> 3.8.4
>
> PROJ:
> 9.3.1
>
> GEOS:
> 3.12.1
>
> SQLite:
> 3.41.1
>
> Python:
> 3.9.18
>
> wxPython:
> 4.2.1
>
> Platform: Windows-10-10.0.19045-SP0
>
>
>
>
>
> Similarly when using library(rgrass) the same error: "library" is either 
> misspelled or
>
> could not be found.
>
>
>
> library(rgrass)
>
>
> Der Befehl "library" ist entweder falsch geschrieben oder
>
> konnte nicht gefunden werden.
>
> (Thu Apr 18 19:59:40 2024) Command ended with non-zero return code 1 (0
> sec)
>
>
>
> Kind regards
>
> Sibylle
>
>
>
> *From:* Veronica Andreo 
> *Sent:* Thursday, April 18, 2024 7:56 PM
> *To:* Micha Silver 
> *Cc:* sibylle.stoec...@gmx.ch; grass-user@lists.osgeo.org
> *Subject:* Re: [GRASS-user] Using RStudio in a GRASS GIS session
>
>
>
> Hello Sibylle,
>
>
>
> Perhaps you can tell us some details about your operative system, which
> GRASS installer you are using (i.e., standalone or OSGeo4W), how did you
> start GRASS, if R and RStudio are installed.
>
>
>
> From your email, I do not understand why GRASS is not recognized as a
> command, as it seems you **are** already within a GRASS session on the
> terminal? (i.e. you have a GRASS prompt there `GRASS>`).
>
>
>
> Vero
>
>
>
> El jue, 18 abr 2024 a las 12:06, Micha Silver via grass-user (<
> grass-user@lists.osgeo.org>) escribió:
>
> Silly question, do you have the 'rgrass' library installed?
>
> i.e. can you do `library(rgrass)` at the R command prompt (without
> rstudio)?
>
>
>
>
>
> On 17/04/2024 21:34, sibylle via grass-user wrote:
>
> Dear community
>
>
>
> To use RStudio in a GRASS GIS session I used the command line
>
> GRASS> rstudio &
>
> library(rgrass)
>
> (see https://grasswiki.osgeo.org/wiki/R_statistics/rgrass)
>
>
>
> Unfortunately I was not able to solve the error message:
>
> - The command "GRASS" is either misspelled or
>
> could not be found.
>
> - The command "library" is either misspelled or
>
> could not be found.
>
>
>
> Kind regards
>
> Sibylle
>
>
>
>
>
>
>
> (Wed Apr 17 20:25:17 2024)
>
>
>
> GRASS> rstudio &
>
>
>
> Der Befehl "GRASS" ist entweder falsch geschrieben oder
>
> konnte nicht gefunden werden.
>
> (Wed Apr 17 20:

Re: [GRASS-user] Using RStudio in a GRASS GIS session

[Veronica Andreo via grass-user]

Hello Sibylle,

Perhaps you can tell us some details about your operative system, which
GRASS installer you are using (i.e., standalone or OSGeo4W), how did you
start GRASS, if R and RStudio are installed.

>From your email, I do not understand why GRASS is not recognized as a
command, as it seems you **are** already within a GRASS session on the
terminal? (i.e. you have a GRASS prompt there `GRASS>`).

Vero

El jue, 18 abr 2024 a las 12:06, Micha Silver via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Silly question, do you have the 'rgrass' library installed?
>
> i.e. can you do `library(rgrass)` at the R command prompt (without
> rstudio)?
>
>
>
> On 17/04/2024 21:34, sibylle via grass-user wrote:
>
> Dear community
>
> To use RStudio in a GRASS GIS session I used the command line
> GRASS> rstudio &
> library(rgrass)
> (see https://grasswiki.osgeo.org/wiki/R_statistics/rgrass)
>
> Unfortunately I was not able to solve the error message:
> - The command "GRASS" is either misspelled or
> could not be found.
> - The command "library" is either misspelled or
> could not be found.
>
> Kind regards
> Sibylle
>
>
>
> (Wed Apr 17 20:25:17 2024)
>
> GRASS> rstudio &
>
> Der Befehl "GRASS" ist entweder falsch geschrieben oder
> konnte nicht gefunden werden.
> (Wed Apr 17 20:25:17 2024) Command ended with non-zero return code 1 (0 sec)
>
> (Wed Apr 17 20:25:29 2024)
>
> library(rgrass)
>
> Der Befehl "library" ist entweder falsch geschrieben oder
> konnte nicht gefunden werden.
> (Wed Apr 17 20:25:29 2024) Command ended with non-zero return code 1 (0 sec)
>
>
> ___
> grass-user mailing 
> listgrass-user@lists.osgeo.orghttps://lists.osgeo.org/mailman/listinfo/grass-user
>
> --
> Micha Silver
> Ben Gurion Univ.
> Sde Boker, Remote Sensing Lab
> cell: +972-523-665918
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

[GRASS-user] GRASS GIS Community Meeting in Prague, June 14-19, 2024

[Veronica Andreo via grass-user]

Dear all,

The GRASS GIS team announces its annual Community Meeting!!

Join us in Prague (June 14-19) to:
- Develop & Discuss: Code, docs, translations & integrations (QGIS, GDAL, R)
- Plan the future: Chart the project roadmap & tackle big challenges!
- Celebrate GRASS birthday & community achievements!

Get involved and support! We welcome in person and online participants!
You can sign up at:
https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2024

Sponsor us!
https://opencollective.com/grass/contribute

Shall you have any further questions, contact Vero Andreo at <
veroand...@gmail.com>

Looking forward to meeting you!
The GRASS GIS team
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.svm.* modules and manuals missing in GRASS 8.4 and online

[Veronica Andreo via grass-user]

The library is LIBSVM, for Ubuntu it was libsvm-dev

El mar, 12 mar 2024 a las 10:29, Markus Neteler via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> On Tue, Mar 12, 2024 at 3:10 PM Veronica Andreo via grass-user
>  wrote:
> > El mar, 12 mar 2024 a las 9:52, Veronica Andreo ()
> escribió:
> >>
> >> Hi all,
> >>
> >> I want to try the new i.svm.* modules, but I discovered the manuals are
> not online at https://grass.osgeo.org/grass84/manuals/full_index.html#i
> and the modules are grey in the GUI. I installed the libsvm-dev package and
> added --with-SVM to the conf instruction, but that didn't work. I searched
> around but neither the wiki nor the html manual files have any hint about
> compilation with svm support. How should I specify the conf instruction?
> >
> >
> > found it in the configure file in the source code: --with-libsvm
>
> I can add it to the server compilation. But which library is needed?
> It is missing from
> grep -i svm REQUIREMENTS.md
>
> ?
>
> thanks,
> Markus
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

Re: [GRASS-user] i.svm.* modules and manuals missing in GRASS 8.4 and online

[Veronica Andreo via grass-user]

El mar, 12 mar 2024 a las 9:52, Veronica Andreo ()
escribió:

> Hi all,
>
> I want to try the new i.svm.* modules, but I discovered the manuals are
> not online at https://grass.osgeo.org/grass84/manuals/full_index.html#i
> and the modules are grey in the GUI. I installed the libsvm-dev package and
> added --with-SVM to the conf instruction, but that didn't work. I searched
> around but neither the wiki nor the html manual files have any hint about
> compilation with svm support. How should I specify the conf instruction?
>

found it in the configure file in the source code: --with-libsvm
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] i.svm.* modules and manuals missing in GRASS 8.4 and online

[Veronica Andreo via grass-user]

Hi all,

I want to try the new i.svm.* modules, but I discovered the manuals are not
online at https://grass.osgeo.org/grass84/manuals/full_index.html#i and the
modules are grey in the GUI. I installed the libsvm-dev package and added
--with-SVM to the conf instruction, but that didn't work. I searched around
but neither the wiki nor the html manual files have any hint about
compilation with svm support. How should I specify the conf instruction?

Maybe GRASS main is not being compiled with svm support in the server and
that is why manuals do not appear online?

Thanks in advance!
Vero
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Convert vector to STVDS

[Veronica Andreo via grass-user]

Hello Ken,

Sorry for such a late reply. AFAIU and some old experience with STVDS, the
approach is by date, i.e., you need a map per date. This is because of the
snapshot logic of STDS. I remember having done animations with vector time
series, but again, that was a long time ago. Have you tried calling the
list of vector maps instead of the stvds? At least to understand if it is a
temporal or spatial topology issue.

There was also a QGIS plugin by Soeren to visually explore STDS (
https://www.youtube.com/watch?v=xxHt3jJbnYw), and IIUC the time manager of
QGIS required only a vector file with a date field to show animations.

Best,
Vero

El sáb, 2 dic 2023 a las 14:56, Ken Mankoff via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi List,
>
> On 2023-12-01 at 16:30 -08, Ken Mankoff  wrote...
> > I have a vector with 115284 lines. From db.select I see
> >
> > | cat |  ID |   Date |
> > |   1 | 278 | 1990-07-10 |
> > |   2 | 278 | 1992-07-30 |
> > |   3 | 278 | 1994-08-29 |
> > |   4 | 242 | 1998-06-05 |
> > |   5 | 255 | 2005-03-03 |
> >
> > That is, 115284 cats and 291 IDs.
>
> Using just one ID to start with (with 80 timestamps) I've created 80
> vectors, each with their own layer and v.timestamp. I can then patch these
> together to one product with multiple layers.
>
> If I t.register all of these, I also see what I expect to see with
> g.gui.timeline. If I run "g.gui.animation stvds=t" it reports "Topology
> [...] is invalid".
>
> Is there a way to export STVDs and see the time component in QGIS or
> KMZ/Google Earth?
>
> Thanks,
>
>   -k.
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

Re: [GRASS-user] GRASS-Wiki: new OSGeo-ID login method activated

[Veronica Andreo via grass-user]

Thanks for taking care of this, Markus!

I just tested, all seems to be working.
Cheers,
Vero

El mar, 13 feb 2024 a las 15:09, Markus Neteler via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Dear all,
>
> As of February 2024, we are happy to announce that the GRASS Wiki (
> https://grasswiki.osgeo.org/wiki/) is connected to the OSGeo
> authentication system!
> Many thanks to Regina Obe from OSGeo-SAC (
> https://wiki.osgeo.org/wiki/User:Robe).
>
> *What does it mean?*
>
> In order to keep spammers out of the system and to simplify the overall
> OSGeo login experience, the centralized OSGeo login method is also
> activated for the GRASS GIS Wiki.
> Please note that your current GRASS-Wiki username/password will no longer
> work here in favor of the OSGeo-ID already used elsewhere (OSGeo-Wiki etc.).
>
> *What do I need to log in?*
>
> As before, no login is required to read the wiki content.
>
> To edit the Wiki, you need to login with your OSGeo-ID (technically your
> OSGeo-LDAP account). If you do not have an OSGeo-ID yet, please register
> here: https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/
> .
>
> *What if I already have a GRASS-Wiki account?*
>
> The first time you log in to the GRASS-Wiki with your OSGeo-ID, your
> existing old user account will be merged with the OSGeo-ID. This should
> work automatically. If not, please contact me directly.
>
> Feel free to ask if you have any questions.
>
> Best regards,
> Markus
>
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - company
> https://grass.osgeo.org - FOSS
> https://neteler.org - freelancing & blog
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

Re: [GRASS-user] v.what.strds error creating column with @ name

[Veronica Andreo via grass-user]

Hi Ken,

Were you able to solve the problem or find its cause? Could you create a
reproducible example with the NC dataset? It seems really strange, if the
mapset is named vel why would it add the date to it too?

Cheers,
Vero

El mar, 23 ene 2024 a las 14:48, Ken Mankoff via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi List,
>
> I'm trying to sample an STRDS at some vector points.
>
> My points are generated (from lines in another mapset) with:
>
> v.to.points input=ex1@gates type=line output=points dmax=100
>
> My STRDS is generated in the current mapset (named vel), and then when I
> run
>
> v.what.strds input=points strds=vx,vy output=test
>
> I get the following error:
>
> DBMI-SQLite driver error:
> Error in sqlite3_prepare():
> near "@vel_2007_09_07": syntax error
>
> ERROR: Error while executing: 'ALTER TABLE test_points_1 ADD COLUMN
> vy_2007_09_07_2008_04_23@vel_2007_09_07 DOUBLE PRECISION'
> ERROR: Unable to add column  DOUBLE PRECISION>.
> ERROR: Unable to add column vy_2007_09_07_2008_04_23@vel_2007_09_07
> DOUBLE PRECISION to vector map 
>
>
> '@' is not a valid character name in a DB column. Am I doing something
> wrong that v.what.strds is trying to generate this column name?
>
> Thanks,
>
>   -k.
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

[GRASS-user] Fwd: [OSGeo-Discuss] Reaching out to folks related to OSGEO+energy sector

[Veronica Andreo via grass-user]

FYI :)

-- Forwarded message -
De: Andrea Giacomelli via Discuss 
Date: mié, 24 ene 2024 a las 6:15
Subject: [OSGeo-Discuss] Reaching out to folks related to OSGEO+energy
sector
To: OSGeo Discussions 
Cc: bmp 

Hello,

With the pibinko.org network we are mustering an intercontinental crew for
what we could define as a "situational" event on Feb. 16.

This will be our participation to the twentieth Italian National Day of
Energy Saving and Sustainable Lifestyles.
On its 20th edition, this initiative has obtained institutional recognition
in Italy, and is aiming to connect to people around the world..

If in your capacity as an OSGEO person you are to some extent involved in
energy-related issues, you might be interested to be part of this
initiative.

Please see:
https://www.pibinko.org/buiometria-partecipativa-milluminodimeno24-youtoo/

Many thanks for your attention, and best regards!

Andrea Giacomelli
http://www.pibinko.org Cultura, ambiente, innovazione libera...
http://www.jugbandcm.it ...e musica
+39 3791680739 - voce
+39 3317539228 - whatsapp
PIVA 01582480537
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss


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

Re: [GRASS-user] Installing addons in GRASS 8.2.0 - Ubuntu 22.04.3 LTS

[Veronica Andreo via grass-user]

Hola Mario,

You could download the r.clip folder to your disk and install the extension
using the path to the folder. Something like: g.extension extension=r.clip
url=path/to/folder/r.clip

hth,
Vero

El lun, 15 ene 2024 a las 20:09, Edouard Choinière via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi!
>
> This problem seems to have been fixed proactively 10 months ago in
> https://github.com/OSGeo/grass/pull/2895
>  and released in Grass 8.3.0 on
> June 24. 2023.
>
> GitHub announced last year that it was sunsetting SVN protocol access, and
> has been sunset on January 8 2024. So it’s expected that the installation
> using an now in existing url won’t work.
>
>
> [image: prod...@2x.png]
>
> Sunsetting Subversion support
> 
> github.blog
> 
> 
>
>
> Subversion has been sunset
> 
> github.blog
> 
> [image: cropped-github-favicon-512.png]
> 
> 
>
>
> Apart from using 8.3.0+, like from
> https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable, I
> don’t remember the specific workaround to specify an alternative url that
> won’t use the SVN code path for code stored in GitHub.
> Can someone step in?
>
>
> Edouard Choinière
>
> Le 15 janv. 2024 à 07:52, Mario Reyes  a
> écrit :
>
> 
> Hi,
>
> I want to install the r.clip addon in Ubuntu 22.04.3 LTS. I am using GRASS
> 8.2.0, installed from
> https://launchpad.net/%7Eubuntugis/+archive/ubuntu/ppa. I also installed
> svn and grass-dev. When I use g.extension I get the following error:
>
> g.extension r.clip
> /usr/lib/grass82/scripts/g.extension:167: DeprecationWarning: The distutils 
> package is deprecated and slated for removal in Python 3.12. Use setuptools 
> or check PEP 632 for potential alternatives
>   from distutils.dir_util import copy_tree
> Fetching  from GRASS GIS Addons repository (be patient)...
> svn: E170013: Unable to connect to a repository at URL 
> 'https://github.com/OSGeo/grass-addons/branches/grass8/src/raster/r.clip'
> svn: E160013: '/OSGeo/grass-addons/branches/grass8/src/raster/r.clip' path 
> not found
> ERROR: GRASS Addons  not found
>
> Do you know what the problem is?
>
>
> --
> Mario Reyes
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

[GRASS-user] Fwd: [OSGeo-Discuss] Developers are invited to the 2024 Joint OGC OSGeo ASF Code Sprint

[Veronica Andreo via grass-user]

FYI :)

-- Forwarded message -
De: Tom Kralidis via Discuss 
Date: mié, 10 ene 2024 a las 13:10
Subject: [OSGeo-Discuss] Developers are invited to the 2024 Joint OGC OSGeo
ASF Code Sprint
To: OSGeo Discussions , 


Hi all: the 4th Joint OGC / OSGeo / ASF Code Sprint will be held
from 26-28 February 2024.  Full details on registration can be found at
[1] and [2].

As demonstrated in the past joint code sprints, this is a great
opportunity for cross-pollination of FOSS4G and standards in an agile/sprint
environment.

The OSGeo community is encouraged to sign up and participate!  Feel free
to add your project at [2].  Looking forward to seeing folks at this
upcoming sprint.

Thanks

..Tom

[1] https://www.osgeo.org/events/2024-joint-ogc-osgeo-asf-code-sprint/
[2] 
https://github.com/opengeospatial/developer-events/wiki/2024-Joint-OGC-%E2%80%93-OSGeo-%E2%80%93-ASF-Code-Sprint

___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Introduction to the mini project called Easy command history navigation through the History browser panel

[Veronica Andreo via grass-user]

Great Linda! Thanks for this email to the community! We'll certainly need
feedback and testing!

Perhaps you could then share a link to the wiki or github project where
you'll be reporting and/or managing tasks?

Looking forward to your contributions and more GUI enhancements!
Vero

El mar, 2 ene 2024 a las 4:27, Linda Karlovská via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hello GRASS users,
>
> I'd like to introduce you to the student mini-project that I will be
> working on in the upcoming months. It is once again GUI-related and
> essentially involves refining and extending the new history browser panel,
> which was merged into the GRASS development branch about one month ago.
>
> Right now, the panel is pretty basic. It shows the plain command history
> and you can click on the command and open the module dialog with pre-filled
> items. Quite helpful but any info about commands is completely missing. So
> the plan for this project is to add in some cool stuff, such as:
>
> 1) Allowing more information to be stored for each executed command, such
> as execution time, runtime duration, status code, region settings, if a
> mask was set, etc.
>
> 2) Creating a context menu with options for "Run Command" and "Show Info."
> "Show Info" will display a small dialog showing above-described
> information.
>
> 3) Adding a symbol (green checkmark, yellow dot, or red cross) in front of
> each command in the tree based on the command's status value (completed, in
> progress, failed).
>
> 4) Branching the history tree based on the date of command execution
> (commands from a specific day could be rolled up).
>
> 5) Filtering commands based on the status code (completed, in progress,
> failed)
>
> Possibly some other things could be added “along the way” based on the
> discussion with the community. I plan to set up the mini-project page and
> regularly send updates about the progress. Feel free to let me know if you
> have any questions or suggestions.
>
> Wishing you all a nice week,
> Linda
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


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

Re: [GRASS-user] detrending time series maps

[Veronica Andreo via grass-user]

That's right, Ivan!
End of year mental death, sorry for the noise...

Vero

El vie, 29 dic 2023 a las 15:34, Ivan Marchesini ()
escribió:

> Hi veronica
>
>
> I see what you did with creating the days time series. In that way you
> acknowledge irregular gaps, right?
>
> yes this is the reason
>
>
> However, why do you multiply by days strds? From my understanding,
> detrending by subtracting the results of a model obbeys this rule: value(t)
> = observed(t) - predicted(t). Then, this
> mystrds-(regression_offset+regression_slope*days) should be
> mystrds-(regression_offset+regression_slope*mystrds).
>
> hmm
>
> may be I'm wrong but I used r.regression.series to assess a relationship
> between mystrds values and time (days)
>
> As a consequence the offset and slope maps I obtain are b and a in the
> following linear equation
>
> y=ax+b
>
> i.e.
>
> predicted_mystrds=slope*days+offset
>
> This is why I suppose that for detrending I need to do:
>
> mystrds-(predicted_mystrds)
>
> i.e.
>
> mystrds-(slope*days+offset)
>
>
> I'm I wrong?
>
> thank you
>
> Ivan
>
>
>
>
> Best,
> Vero
>
> El jue, 28 dic 2023 a las 8:14, Ivan Marchesini (<
> ivan.marches...@gmail.com>) escribió:
>
>> Dear Veronica
>>
>> I think I found a simple solution using temporal raster modules. Here is
>> an example:
>>
>> #evaluating info of the strds
>> eval `t.info mystrds -g`
>>
>> #getting the starting day (of the year, 0-365) of my strds
>> startday=$(date -d "$start_time" "+%j")
>>
>> #Creating a new strds where each pixel has the value of the count of the
>> days starting from the start_day of my strds (the start day in my dataset
>> is in 2016)
>> t.rast.mapcalc inputs=mystrds
>> expression="(start_year()-2016)*365-${startday} +start_doy()" output=days
>> basename=days nprocs=xxx --o
>>
>> #fitting the trend equation
>> r.regression.series xseries="`t.rast.list in=days columns=name sep=,
>> format=line`" yseries="` t.rast.list in=mystrds columns=name sep=,
>> format=line`"
>> out=regression_offset,regression_slope,regression_rsq,regression_t
>> meth=offset,slope,rsq,t
>>
>> #detrending
>> t.rast.mapcalc input=mystrds,days expression="mystrds_detrend
>> = mystrds-(regression_offset+regression_slope*days)" output=mystrds_detrend
>> basename=mystrds_detrend nprocs=xxx method=start --o
>>
>>
>> Best
>>
>> Ivan
>>
>>
>>
>>
>> On 23/12/23 14:53, Ivan Marchesini wrote:
>>
>> Hi Veronica
>>
>> Thank you. It goes in the direction of my idea evn if  my problem is
>> exactly trying to take into account the correct gaps between that data
>>
>> I have another idea.
>>
>> if it works I will come back here to explain how I did
>>
>> thank you again
>>
>> Ivan
>>
>>
>> On 22/12/23 13:45, Veronica Andreo wrote:
>>
>> Hello Ivan,
>>
>> AFAIU you could use the slope and offset maps from t.rast.series within
>> t.rast.algebra to detrend the values of the maps within the strds,
>> something like "detrended_strds = trend_strds - (trend_strds*map(slope) +
>> map(offset))". Others suggest, to detrend by subtracting the previous
>> value, i.e. that would imply using the temporal algebra with the temporal
>> index, something like "detrended_strds = trend_strds[1] - trend_strds[0]".
>>
>> I haven't tested any of these, just a couple of ideas ;-) However, I do
>> not know how this might interact with seasonality within data, or irregular
>> gaps.
>>
>> hth somehow
>> Vero
>>
>> El vie, 22 dic 2023 a las 5:10, Ivan Marchesini via grass-user (<
>> grass-user@lists.osgeo.org>) escribió:
>>
>>> Dear colleagues
>>>
>>> I would like to the advantage of the t.* modules for detrending a strd.
>>>
>>> In the strd I have earth observation data irregularly sampled (2 or 3
>>> times per month), in the period November-February, for 7 years. They are
>>> not equally spaced (i.e gaps have different duration)
>>>
>>> A simple t.rast.series analysis (opion=slope,offset) highlights that
>>> probably there is a descending trend when considering the maps ordered
>>> by id.
>>>
>>> I would like to fit a proper time depending fitting curve for each pixel
>>> and then subtract the function from the real data.
>>>
>>> any hints on how I can do this task exploiting the GRASS GIS modules or
>>> some simple bash/python scripting?
>>>
>>> thank you
>>>
>>> Ivan
>>>
>>>
>>>
>>>
>>> ___
>>> grass-user mailing list
>>> grass-user@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] detrending time series maps

[Veronica Andreo via grass-user]

Hello Ivan,

Thanks for coming back to this :)

I see what you did with creating the days time series. In that way you
acknowledge irregular gaps, right? Otherwise, as t.rast.series
method=slope,offset uses r.series in the background, it will use index as
independent variable and therefore maps are considered equally separated in
time.

However, why do you multiply by days strds? From my understanding,
detrending by subtracting the results of a model obbeys this rule: value(t)
= observed(t) - predicted(t). Then, this
mystrds-(regression_offset+regression_slope*days) should be
mystrds-(regression_offset+regression_slope*mystrds).

Best,
Vero

El jue, 28 dic 2023 a las 8:14, Ivan Marchesini ()
escribió:

> Dear Veronica
>
> I think I found a simple solution using temporal raster modules. Here is
> an example:
>
> #evaluating info of the strds
> eval `t.info mystrds -g`
>
> #getting the starting day (of the year, 0-365) of my strds
> startday=$(date -d "$start_time" "+%j")
>
> #Creating a new strds where each pixel has the value of the count of the
> days starting from the start_day of my strds (the start day in my dataset
> is in 2016)
> t.rast.mapcalc inputs=mystrds
> expression="(start_year()-2016)*365-${startday} +start_doy()" output=days
> basename=days nprocs=xxx --o
>
> #fitting the trend equation
> r.regression.series xseries="`t.rast.list in=days columns=name sep=,
> format=line`" yseries="` t.rast.list in=mystrds columns=name sep=,
> format=line`"
> out=regression_offset,regression_slope,regression_rsq,regression_t
> meth=offset,slope,rsq,t
>
> #detrending
> t.rast.mapcalc input=mystrds,days expression="mystrds_detrend
> = mystrds-(regression_offset+regression_slope*days)" output=mystrds_detrend
> basename=mystrds_detrend nprocs=xxx method=start --o
>
>
> Best
>
> Ivan
>
>
>
>
> On 23/12/23 14:53, Ivan Marchesini wrote:
>
> Hi Veronica
>
> Thank you. It goes in the direction of my idea evn if  my problem is
> exactly trying to take into account the correct gaps between that data
>
> I have another idea.
>
> if it works I will come back here to explain how I did
>
> thank you again
>
> Ivan
>
>
> On 22/12/23 13:45, Veronica Andreo wrote:
>
> Hello Ivan,
>
> AFAIU you could use the slope and offset maps from t.rast.series within
> t.rast.algebra to detrend the values of the maps within the strds,
> something like "detrended_strds = trend_strds - (trend_strds*map(slope) +
> map(offset))". Others suggest, to detrend by subtracting the previous
> value, i.e. that would imply using the temporal algebra with the temporal
> index, something like "detrended_strds = trend_strds[1] - trend_strds[0]".
>
> I haven't tested any of these, just a couple of ideas ;-) However, I do
> not know how this might interact with seasonality within data, or irregular
> gaps.
>
> hth somehow
> Vero
>
> El vie, 22 dic 2023 a las 5:10, Ivan Marchesini via grass-user (<
> grass-user@lists.osgeo.org>) escribió:
>
>> Dear colleagues
>>
>> I would like to the advantage of the t.* modules for detrending a strd.
>>
>> In the strd I have earth observation data irregularly sampled (2 or 3
>> times per month), in the period November-February, for 7 years. They are
>> not equally spaced (i.e gaps have different duration)
>>
>> A simple t.rast.series analysis (opion=slope,offset) highlights that
>> probably there is a descending trend when considering the maps ordered
>> by id.
>>
>> I would like to fit a proper time depending fitting curve for each pixel
>> and then subtract the function from the real data.
>>
>> any hints on how I can do this task exploiting the GRASS GIS modules or
>> some simple bash/python scripting?
>>
>> thank you
>>
>> Ivan
>>
>>
>>
>>
>> ___
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] detrending time series maps

[Veronica Andreo via grass-user]

Hello Ivan,

AFAIU you could use the slope and offset maps from t.rast.series within
t.rast.algebra to detrend the values of the maps within the strds,
something like "detrended_strds = trend_strds - (trend_strds*map(slope) +
map(offset))". Others suggest, to detrend by subtracting the previous
value, i.e. that would imply using the temporal algebra with the temporal
index, something like "detrended_strds = trend_strds[1] - trend_strds[0]".

I haven't tested any of these, just a couple of ideas ;-) However, I do not
know how this might interact with seasonality within data, or irregular
gaps.

hth somehow
Vero

El vie, 22 dic 2023 a las 5:10, Ivan Marchesini via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Dear colleagues
>
> I would like to the advantage of the t.* modules for detrending a strd.
>
> In the strd I have earth observation data irregularly sampled (2 or 3
> times per month), in the period November-February, for 7 years. They are
> not equally spaced (i.e gaps have different duration)
>
> A simple t.rast.series analysis (opion=slope,offset) highlights that
> probably there is a descending trend when considering the maps ordered
> by id.
>
> I would like to fit a proper time depending fitting curve for each pixel
> and then subtract the function from the real data.
>
> any hints on how I can do this task exploiting the GRASS GIS modules or
> some simple bash/python scripting?
>
> thank you
>
> Ivan
>
>
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] v.rast.stats skipping polygons. Why?

[Veronica Andreo via grass-user]

Hola Hernán,

Do your polygons have repeated/shared cat values? That might be one
potential cause according to the Notes in the manual:
https://grass.osgeo.org/grass83/manuals/v.rast.stats.html

just my 2 cents
Vero

El mar, 31 oct 2023 a las 6:35, Hernán De Angelis via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi all,
>
> I have a vector layer with 97015 polygons (lakes in real life) many of
> which are complicated, with islands. The layer has been cleaned using
> v.clean (during import, and after as well). I then run v.stats.rast to
> pick statistics from a raster. This works well for about 3/4 of the
> categories while about 1/4 are skipped. Why?
>
>  From v.stats.rast:
> WARNING: Not all vector categories converted to raster. Converted 73078 of
>   97837.
> Processing input data (73078 categories)...
>
> I see that v.to.rast has no problems converting polygons to raster (only
> visually checked). A test running v.rast.stats using the rasterized
> vector reports:
> WARNING: Not all vector categories converted to raster. Converted 97015 of
>   97837.
> Processing input data (97015 categories)...
> That is, it converts all polygons.
>
> I have cleaned, and rebuilt topology to no avail. Also calling
> v.rast.stats using layer (1) and type (centroid) did not change the
> results.
>
> Am I missing something here? Why is this happening and what can be done
> to calculate raster statistics for all polygons?
>
> Thanks in advance!
>
> Hernán
>
>
> v.category report is:
>  > v.category input=lakes option=report
> Layer/table: 1/lakes
> type   countminmax
> point  0  0  0
> line   0  0  0
> boundary   0  0  0
> centroid   97837  1  97015
> area   0  0  0
> face   0  0  0
> kernel 0  0  0
> all97837  1  97015
> Layer: 2
> type   countminmax
> point  0  0  0
> line   0  0  0
> boundary   0  0  0
> centroid  21  2  2
> area   0  0  0
> face   0  0  0
> kernel 0  0  0
> all   21  2  2
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Submission

[Veronica Andreo via grass-user]

Hola Gloria,

te puedes de-suscribir tu misma aquí:
https://lists.osgeo.org/mailman/listinfo/grass-user

Saludos,
Verónica

El mar, 31 oct 2023 a las 16:37, Gloria Rosa Díez via grass-user (<
grass-user@lists.osgeo.org>) escribió:

>  Hola. Me gustaría dejar de estar en la lista de distribución de correos.
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Computing continuous dry spell from strds

[Veronica Andreo via grass-user]

Hi Sajid,

The example uses a weekly mask because I was interested in consecutive
freezing days per week. The idea, as explained to me by Thomas was to use
this weekly mask (a strds with zero value all over the region) as a
placeholder to add 1 only if the day after or before the current one also
met the condition being evaluated. So, this resulting consecutive-days time
series had 0, 2, 3, etc per pixel per week and that made sense to me for
mosquitoes.

For your problem, perhaps you could either create a zeroes strds with
monthly granularity and using the same command you would get consecutive
days of no rain per month, then add that into years and such... or create a
daily zeroes strds and add one every time the condition is met, i.e.,
current day without rain and previous or posterior day without rain. But
then again, you will need some granularity to count how many times you have
10+ days without rain. You could iterate the counts with increasing
granularities, i.e., do the counting for granularities of 10, 15, 20 days
and so on. But that seems a bit too much. Maybe, you can either try lower
level functions in the temporal framework combined with pygrass and python
or create your own function (?) and contribute it :)

There was a question about consecutive days last year:
https://lists.osgeo.org/pipermail/grass-user/2022-August/083037.html.

Perhaps others can share their insight and ideas

I wish I could be of more help!
Cheers,
Vero


El vie, 13 oct 2023 a las 6:37, Sajid Pareeth via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Dear all
>
> I have a temporal database of daily gridded rainfall for the last 40 years.
>
> I want to find:
> 1. Number of times (count) the rainfall was 0 for 'atleast' *continuous *10
> days in each year, in 5 years etc.
> 2. Max number of continuous (> 10days) dry days (rainfall=0) per year, per
> 5 years etc. In this I want to exclude continuous dry spells less than 10
> days.
>
> I am trying to use the `t.rast.algebra` following the example given here
> 
> .
>
> # Create weekly mask to which we will add 1 or 0 according to temperature in 
> the days within it (each map in this week mask will have a value of 7)
> t.rast.aggregate input=temperature_daily output=weekly_mask 
> basename=mask_week granularity="1 weeks" method=count
> # Calculate consecutive days with negative temperatures
> t.rast.algebra base=neg_temp_days expression="consecutive_days = weekly_mask 
> {+,contains,l} if(temperature_daily < 0 && temperature_daily[-1] < 0 || 
> temperature_daily[1] < 0 && temperature_daily < 0, 1, 0)"
>
>
> The example works, but the above code counts every consecutive day in a
> week even if there is a break in between.
> I also didn't understand why the consecutive days are added to the total
> number of days (+7) in the week in 'mask_week' strds.
>
> I tried modifying the aggregate expression, but could not make it work to
> my requirement as stated above.
>
> Could anyone give a hint on how to go about this.
>
> Many thanks in advance,
>
> Best Regards
>
> Sajid
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Fwd: [GRASS-stats] maptools, rgdal, rgeos and rgrass7 retiring Monday, October 16

[Veronica Andreo via grass-user]

Relevant info for GRASS users using R packages

FWD'ing from grass-stats mailing list.

-- Forwarded message -
De: Roger Bivand via grass-stats 
Date: mar, 3 oct 2023 a las 5:22
Subject: [GRASS-stats] maptools, rgdal, rgeos and rgrass7 retiring Monday,
October 16
To: grass-st...@lists.osgeo.org 


The legacy R spatial infrastructure packages maptools, rgdal and rgeos will
be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been
replaced by rgrass and will be archived with the retiring packages.

The choice of date matches the previously announced archiving during
October 2023, and the specific date matches the release schedule of
Bioconductor 3.18 (some Bioconductor packages depend on retiring packages).

sp_2.1-0 was published October 2, 2023, dropping all dependencies on the
retiring packages. sp will continue to be available and maintained, but not
developed further. Users of sp classes may continue to make use of them,
but will have to use sf or terra to read, write or manipulate objects with
coercion (for a guide to coercion, see
https://cran.r-project.org/web/packages/rgrass/vignettes/coerce.html).

Information about the evolution project may be found in reports and
resources at https://r-spatial.github.io/evolution/; a recent blog by Jakub
Nowosad may also be useful as an overview of what has been going on:
https://geocompx.org/post/2023/rgdal-retirement/. For more detail, see
https://r-spatial.github.io/evolution/ogh23_bivand.html and a video
recording of this presentation https://av.tib.eu/media/63141 (August 28).

All directly affected package maintainers have been alerted to the
impending changes, some in December 2022, most others in March-April 2023.
Many have already updated their packages on CRAN - thank you for your
understanding! The remainder received github issue comments and email
reminders in the last ten days, and will receive final notices to update by
October 9.

On R-universe, builds of packages archived on CRAN are dropped
automatically (https://github.com/r-universe-org/help/issues/286).
Read-only github mirrors of archived packages will remain available in
principle while github exists (https://github.com/r-hub/rhub/issues/568),
for example https://github.com/cran/rgdal. Other binary builds (Debian,
Fedora, Ubuntu) have been alerted; support at Anaconda has been alerted.

On CRAN, the retired packages will continue to be available as source
packages on https://cran.r-project.org/src/contrib/Archive. maptools, rgdal
and rgeos also retain their R-forge repositories, which may be used to
retrieve functions for adding to other packages.

A snapshot of Windows and macOS binary packages may be found on
https://github.com/r-spatial/evolution/tree/main/backstore.

Please raise questions by replying to this post, or as issues on
https://github.com/r-spatial/evolution.

--
Roger Bivand
Emeritus Professor
Norwegian School of Economics
Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway
roger.biv...@nhh.no
___
grass-stats mailing list
grass-st...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-stats
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Mouse coordinates in Map Window not following GUI settings projection

[Veronica Andreo]

This is what I have in GRASS 8.2.1

[image: image.png]

[image: image.png]
However, to make it work then, you need to select the preferred CRS in the
GUI main menu: Settings > Preferences > Projections

El mié, 16 ago 2023 a las 12:51, Eric Patton via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> On Tue, Aug 15, 2023 at 03:11:40PM -0400, Anna Petrášová wrote:
> >
> >
> > On Tue, Aug 15, 2023 at 1:39 PM Eric Patton via grass-user <
> > grass-user@lists.osgeo.org> wrote:
> >
> > I am having trouble getting the Grass GUI map window mouse
> coordinates to
> > display Lat-Long WGS84 coordinates in the lower-left corner of the
> display
> > window.
> >
> > I checked the GUI settings Projection tab, and it is set to
> EPSG:4326,
> > and references /usr/local/share/proj/epsg, but I can't find this file
> > anywhere
> > on my system.
> >
> >
> > I have there /usr/share/proj/epsg
> >
> > but even if you can't find it, entering 4326 and proj string
> > +proj=longlat +datum=WGS84 +no_defs +type=crs
> >
> > should do it. Then, you have to switch that on in map display settings
> (see map
> > display toolbar) -> Status bar -> Display coordinates in different CRS
> > The idea was to move the epsg panel in GUI settings to the map display
> > settings, but this part never got finished...
>
> Yes, I have this proj string in place in the Projection tab.
>
> I don't see any option for 'Display coordinates in different CRS' in Map
> Display -> Status Bar though. The options I have are:
>
> Coordinates
> Display Extent
> Computational Region
> Display Geometry
> Map Scale
> Go to XY coordinates
>
> --
> Eric
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Invitation: Virtual toast for GRASS GIS 40th birthday

[Veronica Andreo]

Dear all,

Happy birthday GRASS GIS! 

Here's the link for *today's toast at 17:00 UTC*:
https://meet.jit.si/GRASSGIS-40th-bday-toast

Check local times:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=7=29=17=0=0=485=207=37=25=204=197
.

See you there,
Vero

El mar, 25 jul 2023 a las 9:17, Veronica Andreo ()
escribió:

> Dear all,
>
> Our beloved GRASS GIS becomes 40 years old!
>
> Let's meet this *Saturday July 29th at 17:00 UTC* for a virtual toast and
> celebration 
>
> Some local times here:
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=7=29=17=0=0=485=207=37=25=204=197
> .
>
> I'll share a link here shortly before the meeting.
>
> See you soon!
> Vero
> --
> Dra. Verónica Andreo
> Investigadora Asistente 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-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Invitation: Virtual toast for GRASS GIS 40th birthday

[Veronica Andreo]

Dear all,

Our beloved GRASS GIS becomes 40 years old!

Let's meet this *Saturday July 29th at 17:00 UTC* for a virtual toast and
celebration 

Some local times here:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=7=29=17=0=0=485=207=37=25=204=197
.

I'll share a link here shortly before the meeting.

See you soon!
Vero
-- 
Dra. Verónica Andreo
Investigadora Asistente 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-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] [GRASS-dev] seeking GRASS example dataset for Germany

[Veronica Andreo]

Hi Michael,

There's this course that Martin taught in Jena with data for Jena and
Germany in general:
https://training.gismentors.eu/grass-gis-workshop-jena/index.html

Vero

El mié, 3 may 2023 a las 23:37, Michael Barton ()
escribió:

> I may be doing a GRASS workshop in Germany in a few weeks. While I can
> always use the standard North Carolina demo data, it might be more
> interesting to the participants to have a more local dataset. Does anyone
> have a nice dataset for Germany they could share with me with the range of
> raster and vector files similar to those found in the NC sample data?
>
> Thanks
> 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-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Fwd: [OSGeo-Discuss] GSoC 2023: Contributor Proposals Submission Started | Deadline - April 4th, 2023 1800 UTC

[Veronica Andreo]

FYI :)

GSoC Contributor proposal period has started!

Have a look at GRASS GIS ideas page for 2023 and get in touch if you are
interested: https://trac.osgeo.org/grass/wiki/GSoC/2023


-- Forwarded message -
De: Rajat Shinde via Discuss 
Date: jue, 23 mar 2023 a las 3:09
Subject: [OSGeo-Discuss] GSoC 2023: Contributor Proposals Submission
Started | Deadline - April 4th, 2023 1800 UTC
To: OSGeo-SoC 
Cc: gsoc-adminosgeo.org , OSGeo Discussions <
disc...@lists.osgeo.org>


Dear All,

FYI, the GSoC Contributor proposal period has started. This email is a
gentle reminder to the potential GSoC contributors interested in
participating in GSoC 2023.

*If you are a contributor interested in contributing to the geospatial open
source with OSGeo as an umbrella organization, then this is high time*:

   1. To go through the *OSGeo GSoC 2023 project ideas list* [1]. Make sure
   to check the list frequently, as it is being updated regularly with new
   ideas.
   2. *Contact the project mentors* via the Developers' mailing list or the
   community chat channels to discuss the project idea/ideas of your
   interest.
   3. Start working on the *proposal draft* and share it with the community
   as soon as possible to receive feedback and comments.

Please go through the GSoC Contributors/Students Guide [2] to get an
overall understanding of the problem. *From Google admins:
"GSoC Contributors who engage with their organization early (and often)
are more likely to be accepted and then succeed"*.

Remember to submit your proposal well in advance, so that you can make the
most out of the feedback from mentors and the community at large and refine
your proposal until the final deadline. Read the application instructions
here [3]. The same page contains all the info you need before taking
action, so please read it carefully.

Please note that the contributor application period starts *March 20, 2023
- 18:00 UTC* and all the student proposals must be submitted before *April
4, 2023 - 18:00 UTC*. Please don't wait for the deadline. Refer to the
GSoC Timeline
[4] for more details.

We are looking forward to working with you toward another awesome edition of
 GSoC! Good luck everyone!

Please forward this email to your developer and community mailing list.

Kind regards,
Your OSGeo GSoC Admins

[1]. https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2023_Ideas

[2]. https://google.github.io/gsocguides/student/
[3]. https://wiki.osgeo
.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#Application_instructions
[4]. https://developers.google.com/open-source/gsoc/timeline
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Announcing GRASS GIS 40th birthday community meeting, June 2-6, 2023, Prague

[Veronica Andreo]

Dear all,

The GRASS GIS team is organizing a *Community Meeting* with users,
supporters, contributors, power users and developers to celebrate *the
GRASS GIS 40th birthday!! *The Community Meeting will take place from *June
2 to 6, 2023*, at the Faculty of Civil Engineering from the Czech Technical
University in Prague, Czech Republic.

Keep an eye at this wiki for updates and details:
https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2023

Everyone is welcome to participate and support us with donations! Looking
forward to meeting you!

Cheers!

Vero
(on behalf of the GRASS GIS PSC)

-- 
Dra. Verónica Andreo
Investigadora Asistente 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-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Fwd: [OSGeo-Discuss] GSoC 2023: OSGeo Accepted as Mentor Organization | Form for Mentors

[Veronica Andreo]

FYI :)

-- Forwarded message -
De: Rahul Chauhan via Discuss 
Date: dom, 26 feb 2023 a las 2:18
Subject: [OSGeo-Discuss] GSoC 2023: OSGeo Accepted as Mentor Organization |
Form for Mentors
To: 
Cc: , gsoc-adminosgeo.org ,
Ashish Kumar 


Dear All,

We are happy and elated to announce that OSGeo has been accepted once again
as a mentor organization for GSoC 2023.

   1. The list of accepted organizations is at [0].
   Our OSGeo GSoC 2023 application is available at [1].
   2. Please note the Potential GSoC contributors (Student + Professional)
   discuss application ideas with the mentoring organizations from Feb 22 -
   March 19, 2023. So, be ready to be flooded with queries by potential
   contributors in the coming period. :-)
   3. GSoC contributors will be able to register and submit their
   applications from March 20 -  April 4, 2023. All proposals must be
   submitted by April 4, 2023, at 18:00 UTC.
   4. *Mentors of the projects who have already updated their ideas in
   the OSGeo GSoC 2023 ideas list, kindly fill out the Google Form [2] so that
   we can start sending the invitations.*

We still have time for more projects to participate with ideas [3].
It is a good opportunity to:
• Add functionality to your projects.
• Attract more contributors participating in the projects, times they
become long-term contributors.

OSGeo projects, Incubating projects, and community projects are welcome.

*Note -*
If you are interested in joining the Organization Administration team and
have been involved with the OSGeo GSoC initiative in the past with rich
experience, please reach out to us.

[0] https://summerofcode.withgoogle.com/programs/2023/organizations
[1] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Application_2023
[2] https://forms.gle/LWBMgA8ToL3RyL5v6
[3] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2023_Ideas

Stay tuned for further instructions on the next steps and be
prepared for another geospatial GSoC with OSGeo!

Yours,
OSGeo GSoC Admins
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Fwd: [FOSS4G 2023 Academic Track] Submission deadline and preparation of reviews

[Veronica Andreo]

FYI

-- Forwarded message -
De: Academic Foss4g2023 
Date: lun, 13 feb 2023 a las 15:59
Subject: [FOSS4G 2023 Academic Track] Submission deadline and preparation
of reviews
To: Academic Foss4g2023 

Dear colleague,

we hope this mail finds you well. As co-chairs of the Academic Track of
FOSS4G 2023, we first want to invite you to *submit your work to the
Academic Track *of the upcoming conference in Kosovo. You can send a work
to be presented either as a standard talk or as a lighting talk to the
conference. We’d like to have you, since you are committed to the world of
FOSS4G.

As you may already know, the accepted papers will be published in the
International Archives of the Photogrammetry, Remote Sensing and Spatial
Information Sciences (ISPRS Archives). This is the series of peer-reviewed
proceedings published by the INTERNATIONAL SOCIETY OF PHOTOGRAMMETRY AND
REMOTE SENSING (ISPRS). The Archives are listed in the ISI Conference
Proceedings Citation Index (CPCI) of the Web of Science, SCOPUS, the E/I
Compendex, and the Directory of Open Access Journals (DOAJ).

The deadline for submission is the *19 February 2023*, you can submit you
work here:
https://talks.osgeo.org/foss4g-2023-academic-track/cfp

We also kindly ask you to *spread the news to other colleagues* who may be
interested in sending their work and participating in the conference.

Second, we started to prepare the review process that will take place
between the end of February and the first half of March. Since you
expressed your interest to act as a reviewer, *please send us some 3-4
keywords describing your area of expertise*. This will help us assign you
some abstracts that are relevant to that area (although please take into
account that this might not always be possible). Please send the keywords
by simply replying to this message.

Depending on the number of submissions we will receive, you will be asked
to review some abstracts (indicatively 3-5). Please inform us in case you
believe you will not have time for reviews between the end of February and
mid-March.

Many thanks and hope to hear from you soon,

Marco Ciolli, Marco Minghini, Perparim Ameti and Bashkim Idrisi - Co-chairs
of the Academic Track Scientific Committee
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.skyview

[Veronica Andreo]

Hi Uwe,

Indeed, the r.skyview module is an addon. See:
https://grass.osgeo.org/grass82/manuals/addons/r.skyview.html
So, you need to install it with g.extension.

Cheers,
Vero

El lun, 13 feb 2023 a las 10:38,  escribió:

> Hello,
>
>
>
> there is a GRASS help page for r.skyview.
>
> But when I try to run it (under Win on GRASS 7.8 or under Linux on GRASS
> 8), nothing happens. The module seems to be absent.
>
> Do I have to install first? And if YES, then how?
>
>
>
> Thanks for help, Uwe
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Probabilistic neighborhood analysis

[Veronica Andreo]

Hi Bernardo,

Yes, feel free to open a feature request issue. You can assign it to
yourself if you think you may tackle it afterwards.

Cheers,
Vero

El lun, 16 ene 2023 a las 19:20, Bernardo Santos via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi Makus,
>
> Nice suggestion, I did not know about this function within r.mapcalc (it
> is quite hidden!)
> I still do not know how to operationalize it, though.
> For now, the solution with R worked, but it could be useful to have
> something like that in GRASS in the future.
> Should I open an issue with a suggestion?
> (I do not have time to do it right now)
>
> Best
> Bernardo
> Em quarta-feira, 11 de janeiro de 2023 09:39:17 GMT+1, Markus Neteler <
> nete...@osgeo.org> escreveu:
>
>
> Hi Bernardo,
>
> Not sure if this helps but there is also this function in r.mapcalc:
>
> https://grass.osgeo.org/grass78/manuals/r.mapcalc.html
>
> graph(x,x1,y1[x2,y2..])convert the x to a y based on points
> in a graph F
> graph2(x,x1[,x2,..],y1[,y2..]) alternative form of graph()
>
> The graph() function allows users to specify a x-y conversion using
> pairs of x,y coordinates. In some situations a transformation from one
> value to another is not easily established mathematically, but can be
> represented by a 2-D graph and then linearly interpolated. The graph()
> function provides the opportunity to accomplish this. An x-axis value
> is provided to the graph function along with the associated graph
> represented by a series of x,y pairs. The x values must be
> monotonically increasing (each larger than or equal to the previous).
> The graph function linearly interpolates between pairs. Any x value
> lower the lowest x value (i.e. first) will have the associated y value
> returned. Any x value higher than the last will similarly have the
> associated y value returned.
> [...]
>
> Perhaps a dynamic (set of) graphs could be constructed?
>
> Best,
> Markus
>
> On Wed, Dec 14, 2022 at 2:37 PM Bernardo Santos via grass-user
>  wrote:
> >
> > Hi,
> >
> > I am trying to produce scenarios of past land cover, before hydropower
> reservoirs were built. To do so, I need to fill empty pixels from a raster
> in the locations where the reservoirs are currently present, using as input
> the actual land cover map. I tried doing that with r.neighbors (taking
> method=mode) with neighborhoods of increasing size, to replace null pixels
> with the most common land cover class in the neighborhood. I also tried
> that with r.fill.stats which is basically the same thing.
> > However, the results gets very homogeneous, since the interpolated null
> cells always get the value of the most common land cover class.
> >
> > Do anyway know of a method in GRASS to perform a "probabilistic"
> neirighborhood analysis, where cells in a neighborhood are given weights
> (possibly related to the distance to the central cell and to their
> frequency) and these weights are used to stocastically sample a value to
> fill the central cell?
> > If not in GRASS, does anyway know of such a method in a different
> platform, i.e. R?
> >
> > Thanks!
> > Best
> > Bernardo
> > ___
> > grass-user mailing list
> > grass-user@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/grass-user
>
>
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] How to use g.extension in GRASS7.8

[Veronica Andreo]

Which GRASS 7.8 you have and which operating system? Any chances you can
update to GRASS 8.2?

El lun, 9 ene 2023 a las 10:58, Bernardo Santos via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi Markus,
>
> That was my first try, and then I get the error below:
>
> > g.extension extension=r.area
> Fetching  from GRASS GIS Addons repository (be patient)...
> svn: E17: URL '
> https://github.com/OSGeo/grass-addons/trunk/grass7/raster/r.area' doesn't
> exist
> ERROR: GRASS Addons  not found
>
> B
>
> Em segunda-feira, 9 de janeiro de 2023 14:35:48 GMT+1, Markus Neteler <
> nete...@osgeo.org> escreveu:
>
>
> Hi,
>
> On Mon, Jan 9, 2023 at 11:50 AM Bernardo Santos via grass-user
>  wrote:
> >
> > Hi,
> >
> > I am trying to install the extension r.area using the g.extension tool
> in GRASS 7.8.
> > However, I get the error that it was not found in the Github repo
> (because the repo changed).
> > Here the error:
> >
> > > g.extension extension=r.area
> > Fetching  from GRASS GIS Addons repository (be patient)...
> > svn: E17: URL 
> > 'https://github.com/OSGeo/grass-addons/trunk/grass7/raster/r.area'
> doesn't exist
> > ERROR: GRASS Addons  not found
> >
> > I tried adding url=
> https://github.com/OSGeo/grass-addons/tree/grass8/src/raster/r.area; but
> it also does not work:
> > > g.extension extension=r.area url=
> https://github.com/OSGeo/grass-addons/tree/grass8/src/raster/r.area
> >  The command:
> > g.extension extension=r.area 
> > url=https://github.com/OSGeo/grass-addons/tree/grass8/src/raster/r.area
> operation=add
> > produced an error (1) during execution:
> > Fetching  from
> > <
> https://github.com/OSGeo/grass-addons/tree/grass8/src/raster/r.area/archive/master.zip
> >
> > (be patient)...
> > ERROR: Extension  not found
> >
> > How should I proceed to install it in GRASS 7.8?
>
> It should work like this (g.extension will figure out the correct path):
>
> g.extension extension=r.area
>
> HTH,
> Markus
>
> PS: Full path is only needed when the addon isn't part of the standard
> addon repository but found elsewhere.
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Probabilistic neighborhood analysis

[Veronica Andreo]

Hello Bernardo,

I haven't tested myself, but have you tried r.neighbors with the different
weight-related options?

Vero

El mié, 14 dic 2022 a las 10:38, Bernardo Santos via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi,
>
> I am trying to produce scenarios of past land cover, before hydropower
> reservoirs were built. To do so, I need to fill empty pixels from a raster
> in the locations where the reservoirs are currently present, using as input
> the actual land cover map. I tried doing that with r.neighbors (taking
> method=mode) with neighborhoods of increasing size, to replace null pixels
> with the most common land cover class in the neighborhood. I also tried
> that with r.fill.stats which is basically the same thing.
> However, the results gets very homogeneous, since the interpolated null
> cells always get the value of the most common land cover class.
>
> Do anyway know of a method in GRASS to perform a "probabilistic"
> neirighborhood analysis, where cells in a neighborhood are given weights
> (possibly related to the distance to the central cell and to their
> frequency) and these weights are used to stocastically sample a value to
> fill the central cell?
> If not in GRASS, does anyway know of such a method in a different
> platform, i.e. R?
>
> Thanks!
> Best
> Bernardo
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] export a multi band tif created with r.cross

[Veronica Andreo]

Hi Grazia,

Have a look at r.out.gdal manual page, esp the example "Export group of
image maps as multi-band file"

https://grass.osgeo.org/grass82/manuals/r.out.gdal.html

best,
Vero

El lun, 28 nov 2022 a las 12:37, Gra () escribió:

> Hi,
>
> I would like to export a multi band raster tif generated with r.cross
>
> Does somebody know what to do?
>
> Thanks for answering
>
> Grazia
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Call for student grants

[Veronica Andreo]

Dear all,

The GRASS GIS project announces the 2022 edition of the "Student grants"
program! Bring your idea, discuss with the community, and reach out to
developers. The deadline is October 30th, 2022.

Have a look at the bases and conditions:
https://grasswiki.osgeo.org/wiki/Student_Grants

We are looking forward to your application!

The GRASS team
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Parallelizing r.mapcalc

[Veronica Andreo]

Hi Frank,

While not an expert here, did you see this other wiki:
https://grasswiki.osgeo.org/wiki/Parallel_GRASS_jobs or Anna's presentation
at FOSS4G 2022:
https://htmlpreview.github.io/?https://github.com/petrasovaa/FUTURES-CONUS-talk/blob/main/foss4g2022.html#/
?

Perhaps useful?

Best,
Vero

El jue, 15 sept 2022 a las 14:33, Frank David ()
escribió:

> Hello,
>
> Is there a way to parallelize r.mapcalc in python scripts with
> start_command() as it is with other command ?
>
> https://grasswiki.osgeo.org/wiki/Parallelizing_Scripts
>
> It seems to me r.mapcalc.tiled is not using processors at 100%
>
> Thank you
>
> Regards,
>
> Frank
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] largest number of consecutive days where rainfall >1 mm

[Veronica Andreo]

Hi Ivan,

It does indeed count consecutive days meeting a condition per week. That's
what the [-1] means in the t.rast.algebra command, i.e., it is the temporal
neighbourhood modifier. If you then want to get the largest weekly
consecutive days meeting the condition within a month you can aggregate the
"weekly_consecutive" time series with t.rast.aggregate granularity="1
month" method="maximum"

HTH,
Vero

El jue, 18 ago 2022 a las 14:42, Ivan Marchesini ()
escribió:

> Hi Markus
>
> thank you
>
> Yes I saw that algorithm but, if I'm not wrong, it does not fit with my
> needs. The calculation made returns the number of days, in a given
> interval (here week), that meets a certain condition. Not sure they are
> consecutive. As an example: if negative temperature occur in monday and
> thuesday and then in friday, saturday and sunday then the code count 5
> for that week. In my opinion what we need is 3.
>
> I hope I was enough clear
>
> In any case it would be good to find a solution for this type of problem
> because these type of indexes are  used for climate data analysis (e.g.:
> https://www.ecad.eu/download/millennium/millennium.php
> https://www.climdex.org/learn/indices/ )
>
> thank you
>
> Ivan
>
>
>
> On 17/08/22 20:04, Markus Neteler wrote:
> > Hi Ivan,
> >
> > On Wed, Aug 17, 2022 at 9:07 AM Ivan Marchesini
> >  wrote:
> >> Dear grass user
> >>
> >> I have daily rainfall strds
> >>
> >> I would like to obtain a layer of the largest number of consecutive days
> >> where rainfall >1 mm
> > May this script code help?
> >
> https://grasswiki.osgeo.org/wiki/Temporal_data_processing#How_to_count_consecutive_days_that_meet_a_certain_condition
> ?
> >
> > Markus
> >
> >> Do you have any suggestions on how to calculate this climate index using
> >> grass's time modules?
> >>
> >> thank you very much
> >>
> >> Ivan
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Fwd: [OSGeo-Discuss] FOSS4G Community Sprint 2022

[Veronica Andreo]

FYI :)

-- Forwarded message -
De: Astrid Emde (OSGeo) via Discuss 
Date: dom, 31 jul 2022 a las 17:02
Subject: [OSGeo-Discuss] Less than a month to the FOSS4G Community Sprint
2022 - August 27th and 28th
To: OSGeo Projects , Announce <
annou...@lists.osgeo.org>, Discuss 


Dear FOSS4G community,

as you all know, in less than a month, between August the 27th and 28th,
the University of Florence will be stage for the gathering of the
developers, translators, power users and anyone interested in their most
important hands-on meeting of the year: the codesprint of FOSS4G 2022

This is a gentle reminder to add your name and project to this year's
wiki page:
https://wiki.osgeo.org/wiki/FOSS4G_2022/Community_sprint

The better we get an idea of the number of participants and the better
we will be able to organize rooms and supplies.

And remember, this year we invite seasoned community members to donate
time to guide new members through the setup of the development
environment or translation tools of their projects. Please state
availability in the wiki page.

We are looking forward to meeting you!

The Codesprint Organization Committee
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] GRASS birthday toast tomorrow, July 29th!

[Veronica Andreo]

Hello everyone!!

Tomorrow, the calendar marks 39 years of GRASS development! 邏 Let's
celebrate with some beverage and make a toast in an online meeting at 15
UTC (See local times here:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022=7=29=15=0=0=48=25=207=197
)

Vashek will provide a link before the scheduled time! Keep an eye on the
mailing list!

See you tomorrow!
Vero

-- 
Dra. Verónica Andreo
Investigadora Asistente 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-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] stvds

[Veronica Andreo]

Hello Ivan,

Space-time datasets in GRASS are map based, so, you either need to create
one vector map per date and then create the time series and register the
maps there, or in the case of STVDS, you could also add a different layer
per date to the same vector map and register those as in:
https://grass.osgeo.org/grass80/manuals/t.register.html#north-carolina-dataset
(see the "Register a vector map with layers representing time steps"
example)

HTH,
Vero

El vie, 22 jul 2022 a las 14:34, Ivan Marchesini ()
escribió:

> Dear GRASS users,
>
> I have a question about the creation of a spatio-temporal vector datasets
>
> I have a vector points map representing sample sites and it includes a
> field of the attribute table describing the sampling date (a different
> day, not sequential, for each point).
>
> I would like to transform the vector point map into a stvds in order to
> use it with t.vect.what.strds.
>
> My question is: is it possible to register the vector point map as a stvds?
>
> thank you
>
> Ivan
>
>
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] about geomorphon pattern

[Veronica Andreo]

Hello Ueda,

Indeed there's no pattern.txt in the source code of r.geomorphon, and it
was also not there when the module was moved from addons to core. The only
pattern file is a c file. Maybe a typo in the manual page? Did you have a
look at the pattern.c file?

Vero

El dom, 26 jun 2022 a las 15:05, Mitsunori Ueda ()
escribió:

> Hi GRASS GIS mailing list
>
>
>
> Regarding r.geomorphon,
>
> in the ternary pattern of the analysis result,
>
> there is a description in the manual that you want to see pattern.txt in
> the source code directory to see all the patterns.
>
>
>
> However, there is no file named pattern.txt in the code directory.
>
>
>
> If you know the location of the file,
>
> could you please tell me?
>
>
>
> Thank you.
>
>
>
> Ueda
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] GRASS: Permission denied

[Veronica Andreo]

Hello Wolfgang,

In our PSC meeting, Martin commented on this (last bullet point here:
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220513). Are
you by chance using the standalone installer? Would it be possible for you
to test GRASS installed through the OSGeo4W installer?

Best,
Vero

El lun, 23 may 2022 a las 5:58, Wolfgang Kresse ()
escribió:

> Hi,
>
> I am new to GRASS, but I apply it for giving a course for practitioners
> in Peru.
>
> Problem:
> Permission denied after start of GRASS
>
> Actions:
> I did the installation with my user account (kresse). Right after the
> installation, GRASS worked fine. But after logoff and login I got this
> error message after start:
>
> "C:\Program Files\GRASS GIS 8.0\extrabin\python3.exe: can't open file
> 'C:\Program Files\GRASS GIS 8.0\etc\grass80.py': [Errno 13] Permission
> denied"
>
> I got the same error message when I logged in as admin.
>
> The only work-around that I found was a reinstallation with admin rights
> and then run the program with admin, too. The forums in the Internet
> gave indications to the bug.
>
> What shall I do?
>
> Remark: I scanned through the "grass-user Archives" back to January
> 2020, however with no success.
>
> With best regards
> Wolfgang
>
>
> Neubrandenburg University of Applied Sciences
> Faculty of Landscape Sciences and Geomatics
> Brodaer Strasse 2
> 17033 Neubrandenburg
> Germany
>
> Tel.  +49 (0) 395 5693 4865 or 4002
> Fax   +49 (0) 395 5693 4999
> E-mail kre...@hs-nb.de
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] problem with g.gui.rlisetup on windows 10

[Veronica Andreo]

Hello Cyril,

I do not have Windows, but I made some tests in Linux and, as you said, it
works fine. So, to understand the syntax of the conf file, I clicked random
options and saved a file named bla and then I clicked over Edit/View (see
attachment). It's kinda reverse engineering, but well...

I agree that the output file should be displayed here
https://grass.osgeo.org/grass80/manuals/wxGUI.rlisetup.html. Would you mind
following that example and providing the resulting config file?

Best,
Vero


El lun, 16 may 2022 a las 11:34, Cyril BERNARD ()
escribió:

> Hello everyone,
>
> I met a problem with g.gui.rlisetup tool on Windows.
>
> It is impossible to type the name of the configuration file in the
> dialog (the text zone stays blank), thus impossible to click on "Next"
> button, and to create the file.
>
> Meanwhile I tried on Linux, and it works. So I have to create liconf
> file on Linux and then, import it on
> C:\Users\xxx\AppData\Roaming\GRASS7\r.li ...
>
> What's wrong with g.gui.rlisetup tool on Windows ? Is it a bug already
> described ?
>
> And, where can I find a documentation about the syntax, if I want to
> create & edit the config file for r.li in a classic editor such as
> notepad ?
>
> Regards,
> Cyril Bernard
> UMR Espace-Dev___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Maps with words as styling

[Veronica Andreo]

Google yielded this in the images section (keywords: map made of words
python):
https://towardsdatascience.com/create-word-cloud-into-any-shape-you-want-using-python-d0b88834bc32

Sounds like what you want :)

Vero

El jue, 31 mar 2022 a las 4:26, Dheeraj Chand ()
escribió:

>
> Hi, all,
>
> Is there a way to use GRASS (or Python, I suppose) to make maps with text
> in the shape of a polygon, like this one? (Warning, political content)
>
>
> https://twitter.com/bmaninparadise/status/1509124115709542400?s=21=faDXVAYLQM4ZVKQJKYIEEg
>
> I want to make one like this one that has the most popular foodstuff for
> each state in India, but I didn’t even know how to describe such a map. Any
> assistance would be greatly appreciated.
>
> Dheeraj
>
>
> Sent from my iPhone
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] GRASS GIS 3D View fails

[Veronica Andreo]

Dear Klaus,

7.8.2 is rather old now, is it possible for you to update to the latest
legacy version 7.8.7 or even better, the latest stable version 8.0.1?

Best,
Vero

El dom, 20 mar 2022 a las 14:50, Klaus Mithöfer ()
escribió:

> Dear all,
>
> I have a problem visualizing DEMs in 3D View. The map remains white and
> i get the following message:
>
> wxgui.py gtk-warning drawing a gadget with negative dimensions
>
> I use grass gis version 7.8.2 on Ubuntu.
>
> Thank you and kind regards, Klaus
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] How to detect/remove overlapping polygons (imported with v.in.ogr )based on the data attributes

[Veronica Andreo]

Hello Hemant,

The discussion continued in the thread you linked (see next messages in the
thread). I used the -c flag of v.in.ogr to avoid cleaning polygons when
importing the shapefile as I needed the simple features to extract zonal
stats from raster maps afterwards. Would that be useful to you too in this
case?

Vero





El sáb, 19 feb 2022 a las 0:23, B H () escribió:

> I have data  in a Shapefile which has genuine  cases of overlapping
> geometries. (As documented in  v.in.ogr) the common areas appear with
> multiple categories.
> I need to find these common areas and "dedupe" them.
> Currently I  export the data out via v.out.ogr and in postgis do  select
> distinct on (st_asbinary(geometrycomlum))  from tablename  order by
> priorityattribute
>
> Is there some way to either dedupe it in grass Gis itself, or have
> v.out.ogr output  some common attribute in the two geometries that
> represent the common area
> from two polygons.
> There is a similar question in this old thread. However I could not find
> the solution.
> https://lists.osgeo.org/pipermail/grass-user/2019-May/080293.html
>
>
>
>
> ---
> clip from v.in.ogr  man page describing how  the overlapping polygons are
> handled.
>
> Overlapping polygons
> When importing overlapping polygons, the overlapping parts will become new
> areas with multiple categories, one unique category for each original
> polygon. An original polygon will thus be converted to multiple areas with
> the same shared category. These multiple areas will therefore also link to
> the same entry in the attribute table. A single category value may thus
> refer to multiple non-overlapping areas which together represent the
> original polygon overlapping with another polygon. The original polygon can
> be recovered by using v.extract with the desired category value or where
> statement and the -d flag to dissolve common boundaries
> Thanks,
> Hemant
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Call for ideas to post in social media

[Veronica Andreo]

Dear all,

Some of you might have seen that every week I post something on Twitter (
https://twitter.com/GRASSGIS - follow us and help with a RT if you don't
already ;-)) mainly as a way to show off GRASS new features, releases,
student projects, presentations at conferences, scientific publications,
new addons, etc. This has brought us +800 more followers in the last year,
increased our mentions, impressions and visits significantly (last month
our profile visits increased almost 400%). In the long term, I believe
increasing our presence and showing our software features is good for the
project.

To keep this running, we are collecting ideas and crafting threads here:
https://trac.osgeo.org/grass/wiki/PSC/Marketing#Upcomingpostsmayberecycledandpostedagain.

This upcoming week, I'll post about Caitlin's student grant and the
implementation of the temporal class within grass.jupyter. There are a
couple of other ideas there that need to be developed further, i.e., they
need content.

I'm calling here for help with those and for new ideas, screenshots, small
video tutorials, new addons, new features you would like to see published
in twitter to keep these weekly posts flowing.

Thanks much in advance! And thanks to those of you that eventually ping
with something cool to show :)

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

Re: [GRASS-user] Joining Vectors for Training Data - Object Based Image Analysis

[Veronica Andreo]

Hi Daniel,

Which is the exact command you are using? There's the -e flag to copy also
attributes [1]. Are you using it?

HTH,
Vero

[1] https://grass.osgeo.org/grass80/manuals/v.patch.html

El jue, 17 feb 2022 a las 23:01, Daniel Jeffrey Kozar via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi everyone,
>
> I am generating a workflow for object-based image classification of drone
> imagery and am getting tripped up when utilizing vectors for training data.
> I have ".shp" files for each class created in another software and am
> trying to join them to create one vector file with an ID column
> corresponding to the class. I have been trying to use the command v.patch,
> which does join them, but doesn't seem to allow for maintaining information
> about the class. Does anyone have any recommendations to do this? Any help
> would be greatly appreciated. Ive attached two example ".shp" files for
> reference.
>
>
> Best,
> Daniel
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.mfilter do not process map edges

[Veronica Andreo]

Hello Bernardo,

Could you please create an issue with the reprex here:
https://github.com/OSGeo/grass/issues/new/choose ?

Thanks,
Vero

El mar, 1 feb 2022 a las 7:54, Bernardo Santos via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hello,
>
> I am performing neighborhood analyses with the r.mfilter module.
> It is very good because of its versatility - one can define the filtering
> matrix as one wants.
> However, it does not process the edges of the map, or at least it seems so.
> If the filter matrix size is e.g. 25x25 pixels, the output shows the 25
> pixels of the edge
> similar to the input map.
>
> Other modules for neighborhood analyses, however, such as r.neighbors,
> have a way to
> deal with that in the borders - dealing with null values.
>
> Does anyone know a way of having such an output - without border effects -
> for r.mfilter?
> If not, is it possible to implement it? (I cannot contribute much here
> because of my limited C knowledge...)
>
> If necessary, I can provide a reprex!
> Thanks in advance!
>
> Bernardo
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] installing grass.jupyter

[Veronica Andreo]

Hi Laura,

Indeed, it's shipped with GRASS 8.0 already as experimental, but the newest
stuff will be in the dev branch only.
This workshop from FOSS4G 2021 is a nice example of usage:
https://github.com/ncsu-geoforall-lab/grass-gis-workshop-FOSS4G-2021

HTH,
Vero

El mar, 1 feb 2022 a las 17:58, Stefan Blumentrath (<
stefan.blumentr...@nina.no>) escribió:

> Hi Laura,
>
>
>
> You would need a current development version (GRASS GIS 8.1.dev).
>
>
>
> For MS Windows you can get it here:
>
> https://wingrass.fsv.cvut.cz/grass81/
>
> On Linux you could clone the code and compile…
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* grass-user  *On Behalf Of *Laura
> Poggio
> *Sent:* tirsdag 1. februar 2022 17:45
> *To:* GRASS user list 
> *Subject:* [GRASS-user] installing grass.jupyter
>
>
>
> Dear all,
>
> I came across this project:
> https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS
> .
> It would be great to use it for some training material that I am working on.
>
>
>
> I most likely have missed something, but I could not find instructions on
> how to install grass.jupyter.
>
> Any pointers will be really helpful
>
>
>
> Thanks
>
> Laura
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] R: R: R: NULL values as output of i.atcorr

[Veronica Andreo]

Dear Ilaria,

If you use Level 2A data, you do not need to do atmospheric correction. The
products are already corrected and the only thing you need to do, if you
want floating point data, is to rescale reflectances with the equation
indicated by Moritz. Optionally removing the overshoots by setting a
ceiling for values > 1, as theoretically reflectance range is [0,1].

If, instead, you are using a Level 1C product, then yes, atmospheric
correction is needed, as those products are top of atmosphere (TOA)
reflectance. For Sentinel data you have different options. Either you use
i.atcorr or i.sentinel.preproc. If you do not have a visibility layer, you
need an AOD value (or file) from a station within the scene ideally and of
the ~date when the image was taken. If you can read some Spanish, I have a
presentation with all the details:
https://gitlab.com/veroandreo/maie-procesamiento/-/blob/taller-grass-online/pdf/03_exercise_processing_s2.pdf.
In any case, i.atcorr manual page shows the process of correcting a S2 L1C
scene step by step.

hth,
Vero

El vie, 28 ene 2022 a las 12:07, Moritz Lennert (<
mlenn...@club.worldonline.be>) escribió:

> On 28/01/22 10:55, ilaria.ferrand...@gmail.com wrote:
> > Thank you Moritz, I will do some research on visibility (aerosol model
> concentration) to put a reasonable value there (any suggestion is
> appreciated, also regarding references to look at).
>
> The man page suggests https://aeronet.gsfc.nasa.gov/.
>
> > How can I transform digital number into radiance/reflectance?
>
> This information should be in the metadata that accompanies the Sentinel
> data. I haven't worked with this data in a couple of years, so don't
> remember.
>
> However, in the doc on
> https://docs.sentinel-hub.com/api/latest/data/sentinel-2-l2a/, you can
> read:
>
> For Sentinel-2 optical data, the relation between DN and REFLECTANCE
> (default unit) is: DN = 1 * REFLECTANCE.
>
> Moritz
>
> > Thank you very much for your precious help!
> >
> > -Messaggio originale-
> > Da: Moritz Lennert 
> > Inviato: giovedì 27 gennaio 2022 17:50
> > A: ilaria.ferrand...@gmail.com; 'Maris Nartiss' 
> > Cc: 'GRASS user list' 
> > Oggetto: Re: R: R: [GRASS-user] NULL values as output of i.atcorr
> >
> > On 27/01/22 14:54, ilaria.ferrand...@gmail.com wrote:
> >> The output of r.info is the following
> >>
> >> r.info map=immagine@mapset
> >>
> ++
> >>| Map:  immagine@mapsetDate: Tue Nov 30 12:51:12 2021|
> >>| Mapset:   mapset Login of Creator: [...]  |
> >>| Location: WGS84_UTM32
> |
> >>| DataBase: C:\Users\[...]\grassdata  |
> >>| Title:immagine
>  |
> >>| Timestamp: none
> |
> >>
> ||
> >>|
> |
> >>|   Type of Map:  raster   Number of Categories: 0
>  |
> >>|   Data Type:CELL
>  |
> >>|   Rows: 10980
> |
> >>|   Columns:  10980
> |
> >>|   Total Cells:  120560400
> |
> >>|Projection: UTM (zone 32)
>  |
> >>|N:4900020S:4790220   Res:10
>  |
> >>|E: 609780W: 499980   Res:10
>  |
> >>|   Range of data:min = 0  max = 18876
>  |
> >>|
> |
> >>|   Data Description:
> |
> >>|generato da r.in.gdal
>  |
> >>|
> |
> >>|   Comments:
> |
> >>|r.in.gdal -e input="C:\Users\[...]\T32TNP_2020062\   |
> >>|2T100559_B04.jp2" output="immagine" memory=300 offset=0
> num_digits=0|
> >>|
> |
> >>
> >> +-
> >> ---+
> >
> > This looks to me like the data is in digital number, not in radiance or
> reflectance. You first have to translate it to one or the other before
> feeding it to i.attcor.
> >
> >>
> >> Do you mean the sixth line of the file? From the i.atcorr help it is
> the "mean target elevation above sea level [km]", and it is correct that it
> is negative.
> >> I'm now wondering if the problem can be having put "0" for visibility
> (aerosol model concentration, fifth line). What do you think about it?
> >
> > I am speaking about the value '-0.293' in line 6 (and yes, my bad for
> not paying attention to the value 0 in the line before). The man page
> > states: "If you have an estimate of aerosol optical depth, enter 0 for
> the visibility and in a following line enter the aerosol optical depth at
> 550nm (iaer means 'i' for input and 'aer' for aerosol), for example:"
> > So, if you have 0 on line 5, so line 6 is AOD and not mean target
> elevation above sea level.
> >
> > In this case line 7 is the "mean target elevation above sea level [-km]"
> > with value -1000 :-).
> >
> > Moritz
> >
> >

Re: [GRASS-user] Single GUI window in 8.0.0RC2?

[Veronica Andreo]

Oh, sorry that I wasn't explicit enough.

I meant the appearance in your operative system. In my fedora box is under
Applications or Start  --> settings --> appearance, and there, in the Style
tab, I see adwaita, adwaita dark and such... Once you pick one of the dark
themes among the options, grass will get it too :)

[image: image.png]


El vie., 21 ene. 2022 17:20, Eric Patton 
escribió:

> Hi Vero,
>
> Did you mean the Appearance tab under GUI settings? There is nothing
> controlling color in this tab that I see, but under the Map Display tab,
> there is the background color selector. Changing that only changes the
> background of the map display window, not the GUI toolbar background.
>
> --
> Eric
>
>
> ‐‐‐ Original Message ‐‐‐
> On Friday, January 21st, 2022 at 08:03, Veronica Andreo <
> veroand...@gmail.com> wrote:
>
> Hi Eric,
>
> You need to change the `appeareance` settings to a dark one, and grass
> will get it. At least, that's how it worked for me.
>
> HTH,
> Vero
>
> El vie, 21 ene 2022 a las 4:59, Eric Patton via grass-user (<
> grass-user@lists.osgeo.org>) escribió:
>
>> Nevermind, I see that I had to git clone the main branch. The
>> single-window GUI looks great! I really look forward to using this.
>>
>> I still don't see any options for dark mode, though - where do I find
>> this?
>>
>> --
>> Eric
>>
>> ‐‐‐ Original Message ‐‐‐
>> On Thursday, January 20th, 2022 at 23:23, Eric Patton via grass-user <
>> grass-user@lists.osgeo.org> wrote:
>>
>> Hi All,
>> I just downloaded 8.0.0.RC2 source code for Linux from
>> https://github.com/OSGeo/grass/releases/tag/8.0.0RC2 to try it out
>> today, everything compiled and built fine.
>>
>> I'm not seeing any single-window GUI or options to enable it; did I
>> install the wrong branch?
>>
>> --
>> Eric
>>
>>
>>
>> ___
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Single GUI window in 8.0.0RC2?

[Veronica Andreo]

Hi Eric,

You need to change the `appeareance` settings to a dark one, and grass will
get it. At least, that's how it worked for me.

HTH,
Vero

El vie, 21 ene 2022 a las 4:59, Eric Patton via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Nevermind, I see that I had to git clone the main branch. The
> single-window GUI looks great! I really look forward to using this.
>
> I still don't see any options for dark mode, though - where do I find this?
>
> --
> Eric
>
> ‐‐‐ Original Message ‐‐‐
> On Thursday, January 20th, 2022 at 23:23, Eric Patton via grass-user <
> grass-user@lists.osgeo.org> wrote:
>
> Hi All,
> I just downloaded 8.0.0.RC2 source code for Linux from
> https://github.com/OSGeo/grass/releases/tag/8.0.0RC2 to try it out today,
> everything compiled and built fine.
>
> I'm not seeing any single-window GUI or options to enable it; did I
> install the wrong branch?
>
> --
> Eric
>
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Trouble calling R from GRASS on Mac

[Veronica Andreo]

Any Mac user that can assist here, please?

Thomas, maybe you can also subscribe and write to grass-stats mailing list:
https://lists.osgeo.org/mailman/listinfo/grass-stats

Sorry for not being of much help with this
Best
Vero

El dom, 16 ene 2022 a las 2:28, Thomas Adams () escribió:

> Hi all!
>
> I have R (latest) and GRASS 7.8.6 installed on my Mac. Both R and GRASS
> launch fine from the GUIs. I can launch R from the default Mac zsh terminal
> window, but R will not launch from the GRASS bash shell… however, at a zsh
> prompt, I can startup bash, and R launches as expected fmo the bash prompt.
>
> So, how do I get the settings right to be able to launch R from the GRASS
> bash terminal — this has never been a problem for me with my Ubuntu
> installations
>
> Suggestions are appreciated… thank you.
>
> Tom
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Fwd: [Spatial-Ecology] Course: Geocomputation and Machine Learning for Environmental Applications.

[Veronica Andreo]

FYI :)

-- Forwarded message -
De: Giuseppe Amatulli 
Date: mar, 11 ene 2022 a las 20:06
Subject: [Spatial-Ecology] Course: Geocomputation and Machine Learning for
Environmental Applications.
To: 

Dear Colleagues,

In view of enhancing computation skills in the geographic domain, Spatial
Ecology   is organising a two-month training
course: Geocomputation and Machine Learning for Environmental Applications
.

The course will be offered on-line with a supplementary 5-day in-person
segment at the University of Basilicata, in the magnificent town of Matera
,
Italy. This is a wonderful opportunity for PhD students, Post-Docs and
professionals to acquire advanced computational skills with a Linux
computer.

Please forward to announce this opportunity within your network.

Sincerely, Giuseppe Amatulli  & Spatial Ecology – Team

*Geocomputation and Machine Learning for Environmental Applications
.** (April, May,
June, 2022)*

In this course, students will be introduced to an array of powerful
open-source geocomputation tools and machine learning methodologies under
Linux environment. Students who have never been exposed to programming
under Linux are expected to reach the stage where they feel confident in
using very advanced open source data processing routines. Students with a
precedent programming background will find the course beneficial in
enhancing their programming skills for better modelling and coding
proficiency. Our dual teaching aim is to equip attendees with powerful
tools as well as rendering their abilities of continuing independent
development afterwards. The acquired skills will be beneficial, not only
for GIS related application, but also for general data processing and
applied statistical computing in a number of fields. These essentially lay
the foundation for career development as a data scientist in the geographic
domain.

More information and registration:

www.spatial-ecology.net
twitter: @BigDataEcology
-- 
Giuseppe Amatulli, Ph.D.

Research scientist at
School of the Environment
Yale University
New Haven, CT, USA - 06511
Twitter: @BigDataEcology
Teaching: http://spatial-ecology.net
Work:  https://environment.yale.edu/profile/giuseppe-amatulli/

___
Spatial-Ecology mailing list
spatial-ecol...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/spatial-ecology
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] single window gui in main branch

[Veronica Andreo]

Hello everyone,

Now that single window is merged into main branch I'd like to test :)

Where's the switch? I just updated and compiled main branch and went
through all tabs and options in the settings?preferences menu from the GUI,
but I could not find anything saying single window something. What am I
doing wrong here?

Can this be related to
https://github.com/OSGeo/grass/blob/f57940e8a096c593f23b2ce3f9653547f24b8e92/gui/wxpython/core/settings.py#L156
been set to False? Shall I change that to True to make it appear/work?

Build info
GRASS version: 8.0.dev

Code revision: 563797cd3

Build date: 2022-01-11

Thanks much,
Vero
-- 
Dra. Verónica Andreo
Investigadora Asistente 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-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Invitation: End of year toast :)

[Veronica Andreo]

Here is the link (kindly provided by Vaclav :))

https://ncsu.zoom.us/j/96062234428?pwd=YnRxdVQ1OHFxcFVFV0hDSlpmOVp4Zz09

See you soon!
Vero

El lun, 27 dic 2021 a las 13:46, Veronica Andreo ()
escribió:

> Dear all,
>
> We'd like to invite you all to a virtual end of year toast on *Wednesday,
> December 29th at 20:00 UTC* (See some local times:
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=12=29=20=0=0=485=48=207=197
> )
>
> We'll share the link on this thread a couple of hours before the event.
> Mark your calendars!
>
> Looking forward to seeing you!
> Vero
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] "ERROR: Row cache is too small" r.li.cwed

[Veronica Andreo]

Ciao Enrico,

No idea, but the error is here:
https://github.com/OSGeo/grass/blob/563797cd3bf0a8a394df11f92a9e7174b88851cd/raster/r.li/r.li.cwed/cwed.c#L306
after a condition about row length (rl), AFAI can guess. Does that make any
sense to you?

Vero


El sáb, 25 dic 2021 a las 22:48, bonushenricus ()
escribió:

> Hello (again!)
> What does it mean
> "ERROR: Row cache is too small"?
> Is the exit from this command
>  config=/home/bonushenricus/.grass7/r.li/mw_7
> path=/home/bonushenricus/Documenti/lavoro/cartografia/habitat_arvaia_cw
> ed_weight.csv output=cwed_7>
> (the file raster, setup of r.li and weight in attachments of this
> email)
>
> Thanks
>
> Enrico Gabrielli
> agricultural technician
> Italy
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Invitation: End of year toast :)

[Veronica Andreo]

Dear all,

We'd like to invite you all to a virtual end of year toast on *Wednesday,
December 29th at 20:00 UTC* (See some local times:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=12=29=20=0=0=485=48=207=197
)

We'll share the link on this thread a couple of hours before the event.
Mark your calendars!

Looking forward to seeing you!
Vero
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Pandas installation in GRASS GIS environment

[Veronica Andreo]

Hi Gioia,

Have you tried with `pip3 install pandas` in the terminal? I guess the
pandas you use within pycharm is in a virtualenv or so, and grass might not
have access to it. I do not use Mac but I found this:
https://www.geeksforgeeks.org/how-to-install-python-pandas-on-macos/

hope that helps
Vero

El dom, 19 dic 2021 a las 15:33, Gioia Blayer ()
escribió:

> Hello everyone,
>
> I am trying to install the module r.area.createweight in GRASS GIS
> version 7.8.6 on macOS Monterey 12.1. When I run the command g.extension
> r.area.createweight from the console in GRASS GIS I get the following
> error:
>
> Fetching  from GRASS GIS Addons repository (be
> patient)...
> ERROR: Pandas is not installed
> Compiling...
> [make: *** [r.area.createweight.tmp.html] Error 1
> ERROR: Compilation failed, sorry. Please check the above error messages.
>
> I do have Pandas because I use it for python in pycharm, but I do not
> understand how to install Pandas in the GRASS GIS environment.
> Hope someone can help me with this, I feel it's something quick and
> technical but I'm new to grass gis, so it takes me some time to learn it.
>
> Thank you in advance for the time and help!
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Fwd: [OSGeo-Discuss] FOSDEM 2022 (Online) – geospatial devroom Call for Participation - Deadline: 26.12.2021

[Veronica Andreo]

FYI :)

-- Forwarded message -
De: Astrid Emde (OSGeo) via Discuss 
Date: jue, 9 dic 2021 a las 8:44
Subject: [OSGeo-Discuss] FOSDEM 2022 (Online) – geospatial devroom Call for
Participation - Deadline: 26.12.2021
To: Discuss , Announce 


News item
https://www.osgeo.org/foundation-news/osgeo-at-fosdem-2022-online-call-for-participation-for-the-geospatial-devroom/
2021-12-09


Submission Deadline: 26.12.2021

FOSDEM is the largest free and open source developers meeting in Europe,
with 8000+ participants. It normally takes place in Brussels (Belgium).

FOSDEM 2021 will be Online. As in the last year we will have a
Geospatial devroom. The Geospatial devroom will be on Sunday 6 February
2022. In 2022 it will be our opportunity to bring our global community
to FOSDEM.

The geospatial devroom is the place to talk about the state of the art
of open, geo-related data, free and open source geospatial software and
its ecosystem. This includes standards and tools, e.g. spatial
databases, online mapping tools, geospatial services, used for
collecting, storing, delivering, analysing, and visualizing geodata.

We hope you will submit a talk or come around at FOSDEM 2022.

Call for Participation
-
Submission Deadline: 26.12.2021

We are looking for you to be part of the geospatial devroom. The
geospatial devroom aims to host talks about geospatial topics, GIS, and
geodata projects, standards and open data.

Please submit your talk till 26 December 2021.

About The FOSDEM

FOSDEM is a free event for software developers to meet, share ideas and
collaborate.

-FOSDEM is free to attend. There is no registration.
-FOSDEM website https://fosdem.org/2022/
-FOSDEM code of conduct https://fosdem.org/2022/practical/conduct/

New rules / What changes since last year

For obvious reasons, this year the event will not take place in a
physical location but online.

  -   The reference time will be Brussels local lime (CET).
  -   Talks will be pre-recorded in advance, and streamed during the
event
  -   Q/A session will be take live
  -   A facility will be provided for people watching to chat between
themselves
  -   A facility will be provided for people watching to submit questions
  -   Food and drinks is now allowed during the talks, but you are
responsible for cleaning your own space

Key dates

   -  Submission deadline: 26 December 2021
   -  Announcement of selected talks: 31 December 2021
   -  Conference dates 5 & 6 February 2022 online
   -  Geospatial devroom date: Sunday 6 February 2022 online

Desirable topics

The Geospatial devroom aims to host talks about all geospatial topics,
GIS,  geodata projects and open data. The talks can cover the following
subjects:

- New geo FOSS projects
- Update of existing geo FOSS projects
- User cases using geo FOSS
- Open Geodata or VGI data project
- News about Standards

Practical

General details

- The default duration for talks is about 45 minutes including
discussion.
- If you plan to register your proposal in several tracks to increase
your chances, don’t ! Register your talk once, in the most accurate
track.
- If the Geospatial devroom is not your first choice, just let us
know, and give us a chance to save you a slot.
- Presentations has to be pre-recorded and streamed before the event.

For accepted talks

- Once your talk was accepted, we will assign you a deputy to help
you to produce the pre-recorded content.
- The deputy will review the content and ensure it has the required
quality. The deputy is also responsible to ensure the content is into
the system and ready to broadcast.
- During the stream of your talk, you must be available online for
the Q/A session.

Submit a talk

Visit the FOSDEM 2022 Pentabarf website (see account creation bellow)
https://penta.fosdem.org/submission

Create an “event” and click on “Show all” in the top right corner to
display the full form.

Your submission must include the following information

Your contact Email

- The title and subtitle of your talk (please be descriptive, as
titles will be listed with ~500 from other projects) select “Geospatial
devroom” as the track.
- A short abstract of one paragraph
- A longer description if you wish to do so
- Links to related websites / blogs etc.

Account creation

If you already have a Pentabarf account, please don’t recreate a new
one.

If you forgot your password, reset it. If not, follow the instructions
to create an account.


Contact Us

- Twitter: @osgeo
- Contact Email:

Re: [GRASS-user] error when importing soil grids data into GRASS

[Veronica Andreo]

Hi Laura,

Great! Much appreciated :)

Vero

El mié, 8 dic 2021 a las 7:31, Laura Poggio ()
escribió:

> Hi Veronica,
> thanks for pointing this out. The projection should be defined in the VRTs
> of Soilgrids 2.0 and normally it should be recognised in GRASS-GIS. I have
> been using the same files you mentioned. We will look into the issue and
> let you know.
>
> Thanks
> Laura
>
> On Wed, 8 Dec 2021 at 01:31, Veronica Andreo  wrote:
>
>> Hi Markus,
>>
>> thanks for your answer :)
>>
>> El mar., 7 dic. 2021 14:43, Markus Neteler  escribió:
>>
>>> Hi Vero,
>>>
>>> On Tue, Dec 7, 2021 at 6:12 PM Veronica Andreo 
>>> wrote:
>>> >
>>> > Dear all,
>>> >
>>> > I'm trying to import soil grids data for south america into grass gis
>>> by means of r.import and the vsicurl driver and I'm facing different errors
>>> according to the soilgrid version I use. See below:
>>> >
>>> > Fist attempt:
>>> >
>>> > gdalinfo /vsicurl/
>>> https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt
>>> > Driver: VRT/Virtual Raster
>>> > Files: /vsicurl/
>>> https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt
>>> >/vsicurl/
>>> https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt.ovr
>>> >/vsicurl/
>>> https://files.isric.org/soilgrids/latest/data/ocd/./ocd_0-5cm_mean/tileSG-018-027/tileSG-018-027_2-4.tif
>>> >/vsicurl/
>>> https://files.isric.org/soilgrids/latest/data/ocd/./ocd_0-5cm_mean/tileSG-018-027/tileSG-018-027_1-1.tif
>>> > ...
>>> > Size is 159246, 58034
>>> > Coordinate System is:
>>> > PROJCRS["Interrupted_Goode_Homolosine",
>>>
>>> This is the problem.
>>>
>>
>> Any idea why it's not recognized? I see it is in PROJ and as you show
>> gdalwarp works. Is it something GRASS related?
>>
>> Here my workaround:
>>>
>>> ### ocd
>>> # PROJCRS["Interrupted_Goode_Homolosine" ... :-(
>>> # requires a trick - r.import still fails
>>> eval `g.region -g`
>>> gdalwarp -t_srs epsg:4326 -te $w $s $e $n ocd/ocd_0-5cm_mean.vrt
>>> ocd_0_5cm_mean_epsg4326.tif -co COMPRESS=LZW
>>>
>>
>> Anyway replacing ocd/ocd_0-5cm_mean.vrt by /vsicurl/
>> https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt in
>> your workaround does the trick, takes a while, but does it. Thanks a LOT
>> for the hint!!
>>
>> @Luí­s Moreira de Sousa  would it be
>> possible to provide the version 2.0 with the projection defined? Or
>> additionally in the easy to use epsg 4326 as an alternative for lazy people
>> like me? :)
>>
>> Vero
>> ___
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] error when importing soil grids data into GRASS

[Veronica Andreo]

Hi Markus,

thanks for your answer :)

El mar., 7 dic. 2021 14:43, Markus Neteler  escribió:

> Hi Vero,
>
> On Tue, Dec 7, 2021 at 6:12 PM Veronica Andreo 
> wrote:
> >
> > Dear all,
> >
> > I'm trying to import soil grids data for south america into grass gis by
> means of r.import and the vsicurl driver and I'm facing different errors
> according to the soilgrid version I use. See below:
> >
> > Fist attempt:
> >
> > gdalinfo /vsicurl/
> https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt
> > Driver: VRT/Virtual Raster
> > Files: /vsicurl/
> https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt
> >/vsicurl/
> https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt.ovr
> >/vsicurl/
> https://files.isric.org/soilgrids/latest/data/ocd/./ocd_0-5cm_mean/tileSG-018-027/tileSG-018-027_2-4.tif
> >/vsicurl/
> https://files.isric.org/soilgrids/latest/data/ocd/./ocd_0-5cm_mean/tileSG-018-027/tileSG-018-027_1-1.tif
> > ...
> > Size is 159246, 58034
> > Coordinate System is:
> > PROJCRS["Interrupted_Goode_Homolosine",
>
> This is the problem.
>

Any idea why it's not recognized? I see it is in PROJ and as you show
gdalwarp works. Is it something GRASS related?

Here my workaround:
>
> ### ocd
> # PROJCRS["Interrupted_Goode_Homolosine" ... :-(
> # requires a trick - r.import still fails
> eval `g.region -g`
> gdalwarp -t_srs epsg:4326 -te $w $s $e $n ocd/ocd_0-5cm_mean.vrt
> ocd_0_5cm_mean_epsg4326.tif -co COMPRESS=LZW
>

Anyway replacing ocd/ocd_0-5cm_mean.vrt by /vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt in
your workaround does the trick, takes a while, but does it. Thanks a LOT
for the hint!!

@Luí­s Moreira de Sousa  would it be possible
to provide the version 2.0 with the projection defined? Or additionally in
the easy to use epsg 4326 as an alternative for lazy people like me? :)

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

[GRASS-user] error when importing soil grids data into GRASS

[Veronica Andreo]

Dear all,

I'm trying to import soil grids data for south america into grass gis by
means of r.import and the vsicurl driver and I'm facing different errors
according to the soilgrid version I use. See below:

Fist attempt:

gdalinfo /vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt
Driver: VRT/Virtual Raster
Files: /vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt
   /vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt.ovr
   /vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/./ocd_0-5cm_mean/tileSG-018-027/tileSG-018-027_2-4.tif
   /vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/./ocd_0-5cm_mean/tileSG-018-027/tileSG-018-027_1-1.tif
...
Size is 159246, 58034
Coordinate System is:
PROJCRS["Interrupted_Goode_Homolosine",
BASEGEOGCRS["GCS_WGS_1984 ellipse",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84",6378137,298.257223563,
LENGTHUNIT["metre",1]],
ID["EPSG",6326]],
PRIMEM["Greenwich",0,
ANGLEUNIT["Degree",0.0174532925199433]]],
CONVERSION["unnamed",
METHOD["Interrupted Goode Homolosine"]],
CS[Cartesian,2],
AXIS["(E)",east,
ORDER[1],
LENGTHUNIT["metre",1,
ID["EPSG",9001]]],
AXIS["(N)",north,
ORDER[2],
LENGTHUNIT["metre",1,
ID["EPSG",9001

r.import input="/vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt;
output=ocd_0_5cm_mean extent=region
...
Selected PROJ pipeline:
+proj=pipeline +step +proj=unitconvert +xy_in=deg +xy_out=rad +step
+proj=igh +lon_0=0 +x_0=0 +y_0=0 +ellps=WGS84

Reproyectado primitivas...
Construyendo topología para el mapa vectorial
...
Registrando primitivas...
Construyendo áreas.
 100%
Adjuntando islas...
 100%
Adjuntando centróides...
 100%
Importando mapa ráster ...
ERROR 4: `/vsicurl/
https://files.isric.org/soilgrids/latest/data/ocd/./ocd_0-5cm_mean/tileSG-022-030/tileSG-022-030_2-3.tif'
not recognized as a supported file format.
ERROR: Unable to read row 11740
ERROR: Unable to import GDAL dataset
   https://files.isric.org/soilgrids/latest/data/ocd/ocd_0-5cm_mean.vrt>

Second attempt, newer dataset soilgrids 2.0 pre-release

r.import input="/vsicurl/
https://storage.googleapis.com/isric-share-soilgrids/pre-release/wv1500/wv1500_0-5cm_mean.tif;
output=wv1500_0_5cm_mean extent=region
Warning 1: /vsicurl/
https://storage.googleapis.com/isric-share-soilgrids/pre-release/wv1500/wv1500_0-5cm_mean.tif:
This file used to have optimizations in its layout, but those have been, at
least partly, invalidated by later changes
ADVERTENCIA: Actualizando el sistema de referencia espacial con la
 definición proj4 incrustada.
...
Selected PROJ pipeline:
+proj=pipeline +step +proj=unitconvert +xy_in=deg +xy_out=rad +step
+proj=igh +lon_0=0 +x_0=0 +y_0=0 +ellps=WGS84

Reproyectado primitivas...
Construyendo topología para el mapa vectorial
...
Registrando primitivas...
Construyendo áreas.
 100%
Adjuntando islas...
 100%
Adjuntando centróides...
 100%
Warning 1: /vsicurl/
https://storage.googleapis.com/isric-share-soilgrids/pre-release/wv1500/wv1500_0-5cm_mean.tif:
This file used to have optimizations in its layout, but those have been, at
least partly, invalidated by later changes
ADVERTENCIA: Actualizando el sistema de referencia espacial con la
 definición proj4 incrustada.
Importando mapa ráster ...
 100%
Removiendo vector 
Removiendo vector 
Estimated target resolution for input band :
0.0022003864773300253
Reprojecting ...
ADVERTENCIA: proj_create() failed for '(null)'
ERROR: Unable to initialize coordinate transformation
ERROR: Unable to to reproject raster 

It imports the raster but fails at re-projection... CRS is unknown in the
tif

gdalinfo /vsicurl/
https://storage.googleapis.com/isric-share-soilgrids/pre-release/wv1500/wv1500_0-5cm_mean.tif
Warning 1: /vsicurl/
https://storage.googleapis.com/isric-share-soilgrids/pre-release/wv1500/wv1500_0-5cm_mean.tif:
This file used to have optimizations in its layout, but those have been, at
least partly, invalidated by later changes
Driver: GTiff/GeoTIFF
Files: /vsicurl/
https://storage.googleapis.com/isric-share-soilgrids/pre-release/wv1500/wv1500_0-5cm_mean.tif
Size is 159246, 58034
Coordinate System is:
PROJCRS["unknown",
BASEGEOGCRS["unknown",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84",6378137,298.257223563,
LENGTHUNIT["metre",1]],
ID["EPSG",6326]],
PRIMEM["Greenwich",0,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8901]]],
CONVERSION["unknown",
METHOD["Interrupted Goode Homolosine"],
PARAMETER["Longitude of natural origin",0,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8802]],
...

Any 

Re: [GRASS-user] Error trying to export a database table

[Veronica Andreo]

Hello Tom

It is the same error as reported here:
https://lists.osgeo.org/pipermail/grass-dev/2021-November/095454.html

I have encountered it myself but it's not clear where it comes from. It
happens in only one location (an old latlong one) and I can't reproduce
with other locations. I use Fedora Linux.

Sorry for not being of more help.

Vero

El jue, 2 dic 2021 a las 19:40, Thomas Adams () escribió:

> Hi all:
>
> I'm using GRASS on a Mac:
>
> GRASS version: 7.8.6dev
>
> Code revision: 0d636df8f
>
> Build date: 2021-09-09
>
> Build platform: x86_64-apple-darwin20.6.0
>
> GDAL: 3.1.4
>
> PROJ: 7.1.1
>
> GEOS: 3.8.1
>
> SQLite: 3.35.4
>
> Python: 3.8.8
>
> wxPython: 4.1.1
>
> Platform: macOS-10.16-x86_64-i386-64bit
>
> I get an error trying to export a database table using…
>
> db.out.ogr --overwrite input=CEATI_dams_not_RR_gauge_rfc_fcst@teaiii
> output=/Users/teaiii/CEATI_dams_not_RR_gauge_rfc_fcst format=CSV
> table=CEATI_dams_not_RR_gauge_rfc_fcst
>
> ERROR:
>
> GRASS 7.8.6dev (global-dataset):~ >
>
>  format=CSV table=CEATI_dams_not_RR_gauge_rfc_fcst
>
> WARNING: The combination of types is not supported by all formats.
>
> ERROR 10: Pointer 'hSRS' is NULL in 'OSRImportFromWkt'.
>
>
> ERROR: Unable to create OGR spatial reference
>
> ERROR: Module  failed
>
> This happens using with the GRASS GUI or from the command line.
>
> Any suggestions?
>
> Regards,
> Tom
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] PSC meeting minutes - November 12, 2021

[Veronica Andreo]

Dear all,

Have a look the PSC meeting minutes of our recent meeting on November 12,
2021:
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_2022

Topics covered:
- Decide a fixed day and hour for PSC meetings
- GRASS GIS 8 release schedule
- GRASS plugin in QGIS
- Budget - discuss student grants
- Presence in social media
- rgrass8
- Website

Thanks everyone!

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

Re: [GRASS-user] gui not working in 7.9 after debian uprade to bullseye

[Veronica Andreo]

Hi Frank,

Did you `make distclean`, configure and recompile your grass79 after the
system upgrade?
Also, maybe update your local copy as there have been changes.

So, if you only did a simple git clone to get the source code and compile,
then:
make distclean
git fetch --all --prune && git checkout main && git pull && sh
conf_grass_dev.sh && make

## Note we now also have a releasebranch_8_0 :)
## conf_grass_dev.sh is my configuration script

my 0.2 cents

Vero

El jue, 18 nov 2021 a las 9:56, Frank David ()
escribió:

> Hello,
>
> I have upgraded my distro from debian buster to bullseye. I had two grass
> release installed installed : 1- grass 7.8.5 from repository, still works
> fine. 2- a grass 7.9 compiled. When I run this one I get this message :
>
> Lancement de l'interface graphique  en tâche de fond, merci de
> patienter ...
> GRASS 7.9.dev (France_L93):~ > free(): double free detected in tcache 2
> Impossible de déterminer la version de GRASS
> free(): double free detected in tcache 2
> Traceback (most recent call last):
>   File "/usr/local/grass79/scripts/g.extension", line 2177, in 
> version = grass_version['version'].split('.')
> KeyError: 'version'
> free(): double free detected in tcache 2
> Traceback (most recent call last):
>   File "/usr/local/grass79/gui/wxpython/wxgui.py", line 106, in OnInit
> mainframe = GMFrame(parent=None, id=wx.ID_ANY,
>   File "/usr/local/grass79/gui/wxpython/lmgr/frame.py", line 143, in
> __init__
> self.notebook = self._createNoteBook()
>   File "/usr/local/grass79/gui/wxpython/lmgr/frame.py", line 337, in
> _createNoteBook
> self.goutput = GConsoleWindow(
>   File "/usr/local/grass79/gui/wxpython/gui_core/goutput.py", line 118, in
> __init__
> self.cmdPrompt = GPromptSTC(parent=self, menuModel=self._menuModel)
>   File "/usr/local/grass79/gui/wxpython/gui_core/prompt.py", line 138, in
> __init__
> GPrompt.__init__(self, parent=parent, menuModel=menuModel)
>   File "/usr/local/grass79/gui/wxpython/gui_core/prompt.py", line 56, in
> __init__
> self.mapList = self._getListOfMaps()
>   File "/usr/local/grass79/gui/wxpython/gui_core/prompt.py", line 100, in
> _getListOfMaps
> result['raster'] = grass.list_strings('raster')
>   File "/usr/local/grass79/etc/python/grass/script/core.py", line 1347, in
> list_strings
> for line in read_command("g.list",
>   File "/usr/local/grass79/etc/python/grass/script/core.py", line 565, in
> read_command
> return handle_errors(returncode, stdout, args, kwargs)
>   File "/usr/local/grass79/etc/python/grass/script/core.py", line 392, in
> handle_errors
> raise CalledModuleError(module=module, code=code,
> grass.exceptions.CalledModuleError: Module run g.list g.list --q -m
> type=raster ended with error
> Process ended with non-zero return code -6. See errors in the (error)
> output.
> OnInit returned false, exiting...
> Error in atexit._run_exitfuncs:
> wx._core.wxAssertionError: C++ assertion "GetEventHandler() == this"
> failed at ../src/common/wincmn.cpp(477) in ~wxWindowBase(): any pushed
> event handlers must have been removed
>
> Do you have an idea to solve this problem ?
>
> Thank you
>
> Frank
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Raster null values unchanged by r.null

[Veronica Andreo]

Hi Eric,

I've tested with GRASS 7.8.5, NC location, setting null values with the
GUI, refreshing the map display and all works just fine, values set to null
are no longer visible.

What doesn't work for me is removing the null bitmap neither from the GUI
nor the terminal (and it does not work in GRASS 7.8.6 nor in 8.0 - this one
deserves a bug report).

My system:
GRASS version: 7.8.5

Build date: 2021-02-08

Build platform: x86_64-redhat-linux-gnu

GDAL: 3.2.1

PROJ: 7.2.1

GEOS: 3.9.0

SQLite: 3.34.1

Python: 3.9.7

wxPython: 4.0.7


Vero


El jue, 21 oct 2021 a las 22:00, Eric Patton via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi Ken,
>
> This is on a native Grass raster, not through a file linked by r.external.
> It seems to be some problem with the rendering/refreshing in the WXGUI.
>
> ~ Eric.
>
> Sent from ProtonMail for iOS
>
>
> On Wed, Oct 20, 2021 at 6:43 PM, Ken Mankoff  wrote:
>
> I think r.null does not work on external (r.external) files. Make sure
> this is not the issue.
>
> Please excuse brevity. Sent from tiny pocket computer with non-haptic
> feedback keyboard.
>
> On Wed, Oct 20, 2021, 07:02 Eric Patton via grass-user <
> grass-user@lists.osgeo.org> wrote:
>
>> I'm encountering some strange behaviour from r.null  - when I use the
>> setnull parameter to assign a particular value to be null in a raster, the
>> raster areas just set to null are still visible and coloured according to
>> their previous values when I refresh the display in the gui map window.
>> Querying these values shows they haven't been set to null.
>>
>> Using version 7.8.5 on Linux Mint. Can anyone confirm?
>>
>> --
>> Eric
>>
>> ___
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Help needed with a coordinate projection problem

[Veronica Andreo]

Hi Thomas,

I have no suggestion other than to create an issue here
https://github.com/OSGeo/grass/issues with a reproducible example so others
can easily test. Also report the GDAL and PROJ versions you have.

Best,
Vero

El mar, 19 oct 2021 a las 14:50, Thomas Adams () escribió:

> Hi all,
>
> I have run into a problem with the development version of GRASS 7.8.6 and
> with the latest versions of PROJ and GDAL. I had a significant issue a
> couple of months ago and had to re-build GRASS, etc. and I have been trying
> to get back where I was since that time.
>
> A major part of the work I do is working with US NOAA/NWS raster radar
> precipitation data in what's called xmrg format... a binary grid file that
> relies on a very obtuse 'projection' called HRAP, described here (and
> within linked files): https://www.weather.gov/owp/oh_hrl_distmodel_hrap
> -- it basically relies on a polar stereographic projection with a spherical
> Earth model with these parameters:
>
> -PROJ_INFO-
> name   : Stereographic
> proj   : stere
> a  : 1337.784777
> es : 0.0
> f  : 0.0
> lat_0  : 90.00
> lat_ts : 60.00
> lon_0  : -105.00
> k_0: 1.00
> x_0: 401.0
> y_0: 1601.0
> -PROJ_UNITS
> unit   : meters
> units  : meters
> meters : 1.00
>
> Previously, I had been able to re-project raster and vector maps to/from
> this location from other map locations with different projections. Now I
> cannot do this; I now get this error:
>
> v.proj location=world_location mapset=teaiii input=st_us
>
> proj_create_operations: Source and target ellipsoid do not belong to the
> same celestial body
> proj_create_operations: Source and target ellipsoid do not belong to the
> same celestial body
> WARNING: proj_create() failed for '(null)'
> ERROR: Unable to initialize coordinate transformation
>
> Any ideas what I might try?
>
> Thank you,
> Tom
>
>
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] GRASS GIS 7.8.6 released

[Veronica Andreo]

*GRASS GIS 7.8.6 released*

This is an update release of the GRASS GIS 7.8 series.

Download source code tarball at

   - https://grass.osgeo.org/grass78/source/grass-7.8.6.tar.gz
   - https://grass.osgeo.org/grass78/source/grass-7.8.6.md5sum

For further release details (bug fixes and enhancements), see

   - https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures78
   - https://trac.osgeo.org/grass/wiki/Release/7.8.6-News

The GRASS GIS 7.8.6 release provides more than 140 fixes and improvements

with respect to the release 7.8.5. Most importantly, this release comes
with a critical bugfix: the addon extension manager has been updated to
match the new addon repository structure which solves issues found when
installing addons in UNIX-like systems.

Visit the release page 
to download the source code of GRASS GIS 7.8.6.

Thanks to all contributors!
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Startup menu small. Why?

[Veronica Andreo]

Hola Hernán,

Which OS do you use and which version of wxpython? I compiled the release
branch today and here, in my fedora 34 with Python 3.9.7 and wxPython
4.0.7, I don't have that issue. Maybe worth a bug report?

best,
Vero

El mar, 12 oct 2021 a las 17:43, Hernán De Angelis (<
variablestarli...@gmail.com>) escribió:

> Dear grassers
>
> I compiled and installed 7.8.6 yesterday. Everything seemed to go well
> and GRASS works as good as ever. However, a small nuisance that I am
> experiencing is that the startup menu window shows up sort of "minimized",
> instead of the classical larger size showing the locations and mapsets from
> which to choose:
>
> I have to manually increase its size to what formally was a normal size in
> order to see which location and mapset to choose:
>
>
> This is not a problem, just a minor nuisance. And perhaps GRASS is not
> even involved in this but rather something else related with wxPython etc.
>
> Has anyone experienced this before? Does someone has any idea on how to
> overcome this?
>
> Thanks in advance
>
> Hernán
>
>
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] GRASS GIS 8.0.dev Reference Manual

[Veronica Andreo]

Hi Rich,

Thanks for pointing that out. We need to fix the link. Please find the new
content here: https://grass.osgeo.org/grass80/manuals/grass.html

best,
Vero

El vie, 17 sept 2021 a las 17:04, Rich Shepard ()
escribió:

> The GRASS startup page has apparently self-quarantined. Clicking on that
> link produces a notice, "Sorry, there's nothing here. home".
>
> Rich
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.atcorr - range/rescale issues

[Veronica Andreo]

Hi Carlos,

Did you try with rescale=0,1? Or 0,1 and then divide the result by
1?

Vero

El mar, 31 ago 2021 a las 16:43, Carlos Henrique Grohmann de Carvalho (<
carlos.grohm...@gmail.com>) escribió:

> Hello all
>
> I'm preparing a tutorial on remote sensing with GRASS (already have 7
> videos - in portuguese - here: https://www.youtube.com/c/SPAMLabUSP)
>
> What I'm planning now is to run i.landsat.toar and i.atcorr, and then
> compare the results with the surface reflectance products from Landsat
> collection 2.
>
> I got it all running but the results are a bit different and it seems that
> the "range" and "rescale" options are the ones to tweak.
>
> checking the metadata:
>
> L2 before scale factor: {'min': '3783', 'max': '65535'}
> L2 after scale factor: {'min': '-0.0959675', 'max': '1.6022125'}
>
> L1 radiance at sensor: {'min': '-6.2', 'max': '191.6'}
>
> L1 reflectance dos1: {'min': '0', 'max': '0.398754597845553'}
>
> L1 reflectance 6S: {'min': '8.560894e-11', 'max': '255'}
>
> I can use the min/max from radiance-at-sensor as the "range" in i.atcorr,
> but what would be best for the "rescale" option? If I don't set it, I end
> up with 0-255
> values. How to get the floating-point result?
>
> thank you for any input
>
>
> Carlos
>
>
> --
> Prof. Carlos Henrique Grohmann
> Institute of Energy and Environment - Univ. of São Paulo, Brazil
> - Digital Terrain Analysis | GIS | Remote Sensing -
>
> http://carlosgrohmann.com
> http://orcid.org/-0001-5073-5572
> 
> Can’t stop the signal.
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Error in installing r.futures addons in Pop!_OS 20.04

[Veronica Andreo]

Dear Firman,

What GRASS version are you using? g.extension is currently failing for
GRASS 7.8.5. See
https://grass.osgeo.org/news/2021_08_01_g_extension_currently_not_working/
for an explanation and options.

We released yesterday the second RC for grass 7.8.6 where this problem
should be fixed: https://github.com/OSGeo/grass/releases/tag/7.8.6RC2

Best regards,
Vero

El mar, 10 ago 2021 a las 10:20, Firman Hadi via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Dear all,
>
> I tried to install r.futures addons in Ubuntu-based 20.04 system (Pop!_OS
> 20.04).
> The installation failed with the error message as follows:
> "svn: E17: URL 'https://github.co
> m/OSGeo/grass-addons/trunk/grass7/r.futures'
> doesn't exist"
>
> The modules can be found in this link '
> https://github.com/OSGeo/grass-addons/tree/grass7/src/raster/r.futures'
> 
> So, I used console to install with this command: g.extension
> extension=r.futures url="https://github.co
> m/OSGeo/grass-addons/tree/grass7/src/raster/r.futures"
> Then another error message was shown:
> "ERROR: Extension  not found. Please check 'url' and 'branch'
> options".
>
> Any help regarding the error would be very much appreciated.
>
> Best regards,
>
> *Firman Hadi*
> E: firmanh...@me.com
> 
> P: +6281220001994
> W: http://www.sigro.org
> 
> [image: Facebook]
> [image:
> LinkedIn]
> [image:
> Twitter]
> [image:
> Instagram]
> 
> [image: Sent from Mailspring]
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] PSC meeting minutes on GRASS b'day (July 29, 2021)

[Veronica Andreo]

Dear all,

Please have a look at the PSC minutes of our recent meeting for GRASS GIS
birthday on July 29, 2021:
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210729

Topics covered were:
- PSC meetings date
- GRASS GIS 8 release schedule
- New splash screen
- GRASS GIS 7.8.6 release schedule
- Sponsoring
- Presence in social media
- Website
- AGM at FOSS4G 2021
- Binder button in PR and commits to increase testing by the community
- GRASS green color

Meeting plus: Helena and Jeff showed their GRASS 4 printed manuals 8-)

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

[GRASS-user] Nabble Forum shut down

[Veronica Andreo]

FYI

best,
Vero

-- Forwarded message -
De: Jorge Sanz via Discuss 
Date: jue, 5 ago 2021 a las 8:35
Subject: [OSGeo-Discuss] Fwd: Your Nabble Forum
To: System Administration Committee Discussion/OSGeo ,


Hi all,

Unfortunately, Nabble , a popular
interface to OSGeo mailing lists, is shutting down. Nabble has been very
useful to users that are not keen to use email to interact with their
community but rather a web interface. It also conveniently offered a way to
search through many mailing lists under a single entry point.

This is not really surprising, as the service has been struggling for a
couple of years. The OSGeo tickets 2574
 and 2616
 are just the most recent
examples.

Please find below the link to the official announcement, and forward this
message to anyone interested.

Happy to answer any questions.
Jorge

-- Forwarded message -
From: 
Date: Thu, 5 Aug 2021 at 05:57
Subject: Your Nabble Forum
To: 


We are downsizing Nabble to one server.  If you want to preserve your forum:

http://osgeo-org.1560.x6.nabble.com/

Then you should follow the instructions here:

http://support.nabble.com/Downsizing-Nabble-tp7609715.html


-- 
Jorge Sanz
http://jorgesanz.net
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] GRASS birthday meeting today!

[Veronica Andreo]

UPDATE!

Vaclav kindly provided a zoom link for today:
https://ncsu.zoom.us/j/96895562516?pwd=NTEzQVJvYXFIYkdETGVBZE5yUGFidz09
We meet there in one hour and a half from now :D

Just in case, here's the world clock link once again:
https://www.timeanddate.com/worldclock/converter.html?iso=20210729T17=1440=204=195=51=207=197=25=671

Looking forward to seeing you soon!

Vero

El jue, 29 jul 2021 a las 14:00, Veronica Andreo ()
escribió:

> Dear GRASS community,
>
> Our beloved software turns 38! We have planned a birthday call for today
> at 17:00 UTC [0]. You are all invited and welcome for a toast!
>
> We'll post the meeting link here one hour before the event.
>
> Cheers,
> Vero
>
> [0]
> https://www.timeanddate.com/worldclock/converter.html?iso=20210729T17=1440=204=195=51=207=671
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] GRASS birthday meeting today!

[Veronica Andreo]

Dear GRASS community,

Our beloved software turns 38! We have planned a birthday call for today at
17:00 UTC [0]. You are all invited and welcome for a toast!

We'll post the meeting link here one hour before the event.

Cheers,
Vero

[0]
https://www.timeanddate.com/worldclock/converter.html?iso=20210729T17=1440=204=195=51=207=671
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] GRASS SCRIPT Execute Error

[Veronica Andreo]

Hi Ayush

GRASS 7.8 already has the r.external module, so no need to patch it. I'd
try first by using a clean installation of grass 7.8.5 (or compilation of
7.8.6 for that matter).

Also the same way there's v.import for vector data, there's r.import for
quick raster import, so you could try that for importing your raster map.

my 0.02 cents
Vero

El lun, 19 jul 2021 a las 8:16, Ayush Chauhan ()
escribió:

> Hi,
>
> I am using the below code in my grass script to calculate volume from the
> DSM file input into the script and the polygon points on the DSM.
> ```
>
> # %module
> # % description: Calculate volume of area and prints the volume to stdout
> # %end
> # %option
> # % key: area_file
> # % type: string
> # % required: yes
> # % multiple: no
> # % description: Geospatial file containing the area to measure
> # %end
> # %option
> # % key: points_file
> # % type: string
> # % required: yes
> # % multiple: no
> # % description: Geospatial file containing the points defining the area
> # %end
> # %option
> # % key: dsm_file
> # % type: string
> # % required: yes
> # % multiple: no
> # % description: GeoTIFF DEM containing the surface
> # %end
>
> import sys
> from grass.pygrass.modules import Module
> import grass.script as grass
>
>
> def main():
>
> Module(
> "v.import",
> input=opts['area_file'],
> output="polygon_area",
> overwrite=True
> )
> Module(
> "v.import",
> input=opts['points_file'],
> output="polygon_points",
> overwrite=True
> )
> Module(
> "v.buffer",
> input="polygon_area",
> s=True,
> type="area",
> output="region",
> distance=1,
> minordistance=1,
> overwrite=True
> )
> Module("r.external", input=opts['dsm_file'], output="dsm",
> overwrite=True)
> # Set Grass region and resolution to DSM
> Module("g.region", raster="dsm")
> # Set Grass region to vector bbox
> Module("g.region", vector="region")
> # Create a mask to speed up computation
> Module("r.mask", vector="region")
> # Transfer dsm raster data to vector
> Module("v.what.rast", map="polygon_points", raster="dsm",
> column="height")
> # Decimate DSM and generate interpolation of new terrain
> Module("v.surf.rst", input="polygon_points", zcolumn="height",
>elevation="dsm_below_pile", overwrite=True)
> # Compute difference between dsm and new dsm
> Module("r.mapcalc",
>expression='pile_height_above_dsm=dsm-dsm_below_pile',
> overwrite=True)
> # Set region to polygon area to calculate volume
> Module("g.region", vector="polygon_area")
> # Volume output from difference
> Module("r.volume", input="pile_height_above_dsm", f=True)
>
> return 0
>
>
> if __name__ == "__main__":
> opts, _ = grass.parser()
> sys.exit(main())
>
> ```
>
> The area file I am providing contains the below
> contents(area_file.geojson):
>
> ```
>
> {"type": "Feature", "properties": {}, "geometry": {"type": "Polygon",
> "coordinates": [[[73.31231666938123, 26.22297239890824],
> [73.31241572405983, 26.222379996744422], [73.3134282830031,
> 26.222577464467804], [73.31281194277611, 26.222906576595037],
> [73.31231666938123, 26.22297239890824]]]}}
>
> ```
>
> The points file I am providing contains the below
> contents(points_file.geojson):
>
> ```
>
> {"type": "FeatureCollection", "features": [{"type": "Feature",
> "properties": {}, "geometry": {"type": "Point", "coordinates":
> [73.31231666938123, 26.22297239890824]}}, {"type": "Feature", "properties":
> {}, "geometry": {"type": "Point", "coordinates": [73.31241572405983,
> 26.222379996744422]}}, {"type": "Feature", "properties": {}, "geometry":
> {"type": "Point", "coordinates": [73.3134282830031, 26.222577464467804]}},
> {"type": "Feature", "properties": {}, "geometry": {"type": "Point",
> "coordinates": [73.31281194277611, 26.222906576595037]}}, {"type":
> "Feature", "properties": {}, "geometry": {"type": "Point", "coordinates":
> [73.31231666938123, 26.22297239890824]}}]}
>
> ```
>
> When I run the below command,
>
> ```
>
> */home/ec2-user/grass/bin.x86_64-pc-linux-gnu/grass78 -c \*
> */home/ec2-user/volume_calc/media/tour_id/files/dsm_volume.tif location \*
> *--exec python3 /home/ec2-user/volume_calc/grass_calc_vol.py \*
> *area_file=/home/ec2-user/volume_calc/media/tour_id/tmpo99fe5bi_grass_engine/area_file.geojson
> \*
> *points_file=/home/ec2-user/volume_calc/media/tour_id/tmpo99fe5bi_grass_engine/points_file.geojson
> \*
> *dsm_file=/home/ec2-user/volume_calc/media/tour_id/files/dsm_volume.tif*
>
> ```
>
> I get below output.
> ```
>
> (.venv) [ec2-user@ip-10-0-3-14 volume_calc]$
> /home/ec2-user/grass/bin.x86_64-pc-linux-gnu/grass78 -c
> /home/ec2-user/volume_calc/media/tour_id/files/dsm_volume.tif location
> --exec python3 /home/ec2-user/volume_calc/grass_calc_vol.py
> 

[GRASS-user] Fwd: [Projects] Join the FOSS4G 2021 Community Sprint on Saturday October 2nd, 2021 - please register

[Veronica Andreo]

FYI

Invitation to register and participate in the online community sprint after
FOSS4G 2021, on October 2nd

Our designer is doing a great job with the workadventu.re environment ;)
We are looking forward to seeing you there!

Vero

-- Forwarded message -
De: Astrid Emde (OSGeo) 
Date: vie, 2 jul 2021 a las 16:58
Subject: [Projects] Join the FOSS4G 2021 Community Sprint on Saturday
October 2nd,  2021 - please register
To: Announce , Discuss ,
OSGeo Projects 

See News Item
https://www.osgeo.org/foundation-news/foss4g-2021-community-sprint/

The FOSS4G 2021 Community Sprint [1] will be right after the global
FOSS4G 2021 conference [2] and has the aim to bring people together to
discuss and improve OSGeo projects. It will take place online on
Saturday October 2nd, 2021, using WorkAdventu.re [3] plus a bounce of
Jitsi channels for each project.

The Community Sprint offers an excellent opportunity to meet other OSGeo
members and get involved in OSGeo projects! It is a golden opportunity
for developers and non-developers to meet with the core team of those
projects, get a deeper insight into the software and participate in
development, testing or documentation. We follow this tradition since
2009.

Since we need to create the Workadventu.re environment, we ask all
projects to register on the wiki page by July 15th. Projects that have
registered on time will have their own Workadventu.re environment, those
that register later will only have a Jitsi channel reported on the
community sprint wiki page.

The OSGeo Code Sprint is open to all who wish to participate in one or
more projects. WorkAdventu.re environment is open only to people
registered to FOSS4G 2021 whereas the Jitsi channels are open to
everyone.

There is always plenty to do – it’s not all about programming;
translation, documentation, feedback, discussions, testing – all this is
also important for projects, so everyone is cordially invited to attend
the community sprint!

The Organizing Team is looking forward to your coming!

Please register soon [1]

See you at FOSS4G 2021!

The FOSS4G 2021 Community Sprint Team

[1] https://wiki.osgeo.org/wiki/FOSS4G_2021/Community_sprint
[2] https://2021.foss4g.org/
[3] https://workadventu.re/



___
Projects mailing list
proje...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/projects
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Removing name from users list.

[Veronica Andreo]

Hello Omkar,

Have you tried to unsubscribe yourself by filling in your email address at
the bottom of this page: https://lists.osgeo.org/mailman/listinfo/grass-user
?

[image: image.png]

Have a good day,
Vero

El jue, 20 may 2021 a las 12:43, Omkar Kadlag ()
escribió:

> Hello respected member,
>
> I have finished my work with grass software and don't need any further
> mails from your mailing list as I don't have any answers for them.
>
> May I request you to please ensure that I will not get any further mails
> from your mailing list.
>
> Thank you for your consideration.
>
> Yours sincerely,
> Omkar.
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] legend not showing in 3D view

[Veronica Andreo]

Hi Matthew,

I can confirm this in GRASS-dev version and 7.8.5. Is this a bug or the
raster legend is not supposed to appear while in 3d view?

best,
Vero

El vie, 23 abr 2021 a las 22:51, Matthew Kratochvil ()
escribió:

> Hi
> I am a new user to grass-GIS and I have been using the 3D view to
> investigate bathymetry data. I have been trying to make legends for the 3D
> view so I can make figures with them. Everytime I attempt to make a legend
> for the 3D window for the raster I am investigating it ends up on the 2D
> raster.
>
> I have followed the 3D view instructions that are in the NCSU video
> series. I think I a missing something like a radio button or a check box.
>
> Please advise
> Matt K
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] setting a color value to transparent

[Veronica Andreo]

Hi Chris,

Would choosing the categories (cat values) of features you want displayed
help? AFAIU from the ps.map manual, it is possible to select cats to be
displayed. Also, there's the possibility to use a where clause.

Just out of curiosity: why are you still running GRASS 7.4? We are at 7.8.5
already with python 3 support and soon to release GRASS 8.0 ;)

Best,
Vero

El vie, 23 abr 2021 a las 20:19, Chris Bartolomei via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Good afternoon all,
>
> I have a polygon map with a handful of features, I've added a column I use
> for setting RGB values "RRR:GGG:BBB" to color them. I use three (3) colors
> - red, orange, and yellow - but I would like some of them to be transparent
> but I can't find anywhere in the manuals what the code would be for
> transparent. Searching Google-land I see there's an RGBa standard which can
> set tranparency but GRASS doesn't seem to support that. I've tried setting
> the value to NULL, to "", to "none", and tried "0:0:0:0" (RGBa) all to no
> avail ...
> I am using ps.map to create an image so the ps rules file tells GRASS to
> use the RGB column to define the colors ... I believe I'm stuck with this
> methodology for now.
> Am I going to have to select the features which I do want colored and make
> a new map with just those features? or do I have to remove the postscript
> command for the RGB column and create a color table then reset my category
> values to 1, 2, 3, or 4 using a color table something like:
>   nv white
>   1 red
>   2 orange
>   3 yellow
>   4 white
>   end
>
> I was hoping to avoid creating a color table and changing the category
> values as this map gets modified twice a day... It's running in GRASS 7.4
> on Linux ...
> Thanks and happy weekend!
> :)
> Chris
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Problems using v.surf.idw

[Veronica Andreo]

[bringing the issue back to the list for reference]

Dear Luis,

Thanks for your feedback!

If you didn't provide a column name, and the module didn't fall back to the
cat column as it is supposed to, please report it as a bug (ideally with a
reproducible example). According to the manual and my very little
understanding of the c code, it should.

All the best,
Vero

El lun, 19 abr 2021 a las 16:00, Luí­s Moreira de Sousa (<
luis.de.so...@protonmail.ch>) escribió:

> Hi Vero,
>
> from what I understand the module is seeking neither the value column, not
> the cat column. This map was created with r.to.vect, these are its
> attributes:
>
> > v.info -c soil_map_rcl_no_water
> Displaying column types/names for database connection of layer <1>:
> INTEGER|cat
> INTEGER|value
> CHARACTER|label
>
> If v.surf.idw was indeed seeking the cat column I would expect the module
> to succeed with this input, producing a nice Voronoi map.
>
> My suggestion would be to explicitly reference the name of the default
> column/attribute in the manual.
>
> Thank you.
>
> --
> Luís
>
> ‐‐‐ Original Message ‐‐‐
> On Monday, April 19, 2021 1:56 PM, Veronica Andreo 
> wrote:
>
> Dear Luis,
>
>
> El lun, 19 abr 2021 a las 8:45, Luí­s Moreira de Sousa via grass-user (<
> grass-user@lists.osgeo.org>) escribió:
>
>> Dear Anna,
>>
>> thank you for the reply, indeed once I added the column parameter the
>> module completed successfully. The manual includes the following on this
>> parameter:
>>
>>column=name
>>Name of attribute column with values to interpolate
>>If not given and input is 2D vector map then category values
>> are used. If input is 3D vector
>>map then z-coordinates are used.
>>
>> If I read that correctly, the module should pick up the "value" column by
>> defualt. This particular layer was created by GRASS itself and includes a
>> "value" column:
>>
>
> I might be biased, but the description is clear to me: provide the name of
> a column that contains the values/quantities that will be used to
> interpolate. If you do not provide a column name, cat will be used (i.e.,
> the IDs) in a 2D vector, or the z column in a 3D vector.
>
>
>
>>
>> >  v.info -c soil_map_rcl_no_water
>> Displaying column types/names for database connection of layer <1>:
>> INTEGER|cat
>> INTEGER|value
>> CHARACTER|label
>>
>> It is now clear this is not the case, `v.surf.idw` is seeking another
>> column by default, one that is not created by vector creating modules.
>>
>
> It does not seek for another column, it defaults to cat if you do not
> provide a column name where the variable you want to interpolate is. It
> would be annoying, IMO, if I was forced to name a column `value` just
> because a module only takes that name. Also, there might be many columns
> with quantities/values in the attr table of a vector. How is the module
> supposed to know which one to use, if the user does not provide a name?
>
> Perhaps this could be made more explicit in the manual page.
>>
>
> Maybe the fact that value appears in the description and your column is
> called value triggered the confusion?
> We really appreciate any suggestions on how to improve the wording to make
> it clearer.
>
> Best,
> Vero
>
>
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Problems using v.surf.idw

[Veronica Andreo]

Dear Luis,

El lun, 19 abr 2021 a las 8:45, Luí­s Moreira de Sousa via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Dear Anna,
>
> thank you for the reply, indeed once I added the column parameter the
> module completed successfully. The manual includes the following on this
> parameter:
>
>column=name
>Name of attribute column with values to interpolate
>If not given and input is 2D vector map then category values
> are used. If input is 3D vector
>map then z-coordinates are used.
>
> If I read that correctly, the module should pick up the "value" column by
> defualt. This particular layer was created by GRASS itself and includes a
> "value" column:
>

I might be biased, but the description is clear to me: provide the name of
a column that contains the values/quantities that will be used to
interpolate. If you do not provide a column name, cat will be used (i.e.,
the IDs) in a 2D vector, or the z column in a 3D vector.


> >  v.info -c soil_map_rcl_no_water
> Displaying column types/names for database connection of layer <1>:
> INTEGER|cat
> INTEGER|value
> CHARACTER|label
>
> It is now clear this is not the case, `v.surf.idw` is seeking another
> column by default, one that is not created by vector creating modules.
>

It does not seek for another column, it defaults to cat if you do not
provide a column name where the variable you want to interpolate is. It
would be annoying, IMO, if I was forced to name a column `value` just
because a module only takes that name. Also, there might be many columns
with quantities/values in the attr table of a vector. How is the module
supposed to know which one to use, if the user does not provide a name?

Perhaps this could be made more explicit in the manual page.
>

Maybe the fact that value appears in the description and your column is
called value triggered the confusion?
We really appreciate any suggestions on how to improve the wording to make
it clearer.

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

[GRASS-user] FOSS4G 2021 - Call for Papers and Workshops

[Veronica Andreo]

Dear GRASS community

On behalf of the Local Organizing Committee of the FOSS4G 2021 - Buenos
Aires, I would like to remember you of the opportunity to submit talks and
workshops. The *call for papers is open until April 19th*. You still have 4
days to put up a nice abstract for a talk or workshop! Don't miss it!

https://2021.foss4g.org/call-for-papers/call-for-papers.html

Given the global circumstances, the conference will be held online. We are
doing our best to make it interesting, enriching and fun and provide the
best experience for the social, business and academic facets of the
conference!

Let us all make this online FOSS4G a great conference!

See you soon!

Vero Andreo
Program Committee - LOC
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.watershed identify inland watershed

[Veronica Andreo]

Dear Ming,

To avoid that your suggestion gets lost in emails, please fill in a
*feature request* issue with all details here:
https://github.com/OSGeo/grass/issues/new/choose

Best,
Vero


El vie, 2 abr 2021 a las 16:37, ming han () escribió:

> Maybe I am the only one who has this demand. Following is just a
> recommendation to GRASS r.watershed function.
> Maybe it is worth having an option to avoid r.watershed overcome
> depressions.
> The reasons are 1) there are many hydrologically pre condition DEM data
> available globally, such as:HydroSHEDS, MERIT
> 2) the depression in these DEM are real
> depressions, overcome these depressions will make the entire drainage
> system incorrectly.
>
> I understand GRASS has other functions to solve this problem, but just a
> user recommendation. I use GRASS a lot.
>
> Thanks
> Ming
>
> ming han  于2021年3月30日周二 上午8:06写道：
>
>> Got it, thanks everyone~
>> Ming
>>
>> Micha Silver  于2021年3月29日周一 下午2:40写道：
>>
>>> Hello:
>>>
>>> You might try `r.param.scale`, or even better `r.geomorphons` modules to
>>> identify geomorphology features, then filter out all pixels identified
>>> as pits.
>>>
>>>
>>> r.watershed is purposely designed to overcome depressions, and find flow
>>> routing thru these spots. So I don't think you can use that module to
>>> identify depressions.
>>>
>>>
>>> On 3/27/21 8:49 PM, ming han wrote:
>>> > Hi  Everyone
>>> >
>>> >  When I do watershed delineation using r.watershed for great salt
>>> > lake watershed. I found r.watershed always tried to assign an outlet
>>> > for a great salt lake, which does actually not exist because it is an
>>> > inland lake and the great salt lake has no watershed outlet at all.
>>> >
>>> >   I noticed that there is a depression option. But is there any
>>> > way that  r.watershed can automatically identify depressions while
>>> > defining flow accumulation and stream network?
>>> >
>>> > Thanks
>>> > Ming
>>> >
>>> > ___
>>> > grass-user mailing list
>>> > grass-user@lists.osgeo.org
>>> > https://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>> --
>>> Micha Silver
>>> Ben Gurion Univ.
>>> Sde Boker, Remote Sensing Lab
>>> cell: +972-523-665918
>>>
>>> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] FOSS4G 2021: Call for Papers for Talks and Workshops Deadline Extended

[Veronica Andreo]

View this email in your browser


*SUBMIT AN ABSTRACT FOR FOSS4G 2021*
*Deadline for Talks and Workshops extended until April 19th 2021!*

It's your chance to be part of this FOSS4G 2021, online edition!
As a local organizing team, we are very excited to learn how you apply your
FOSS technologies to your projects, or daily jobs, as well, we are hungry
for new knowledge.
Do not miss it!
SUBMIT HERE

*WORKSHOPS*
Workshops are hands-on sessions in which attendees have the chance to learn
about FOSS4G software with direct interaction.
Share your knowledge and help others learn through these sessions.

*TALKS*
Talks will be assigned a 25 minutes slot: 15 minutes for the talk itself
and 10 for Q
Remember that although we have few places for talks in Spanish or
Portuguese, you have more chances that your talk will be accepted if
submitted in English.



*ACADEMIC*
The Academic track is the perfect place to showcase your latest research
and innovation. If you are looking for exposure and collaborations, this is
the perfect place to present your results.
With a peer reviewed process, the selected papers will be pusblished
through ISPRS Archives.
*You can still send your proposal before tomorrow!*


[image: Twitter]

[image: Facebok]

[image: Instragram]

[image: LinkedIn]

[image: Email] 
[image: Website]

OSGeo Foundation
You can update your preferences

or unsubscribe from this list

.
FOSS4G 2021 - 9450 SW Gemini Dr - Beaverton, Oregon 97008 - United States
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Building grass version grass-7.8.5

[Veronica Andreo]

Hi Steve,

I'm no expert in compiling at all, but I always run configure in the source
code directory. Have you tried?
Once configure runs without errors, just run make, if no errors at the end,
you are good to go

Here's a wiki with instructions for diverse linux platforms:
https://grasswiki.osgeo.org/wiki/Compile_and_Install

hth,
Vero

El vie, 26 mar 2021 a las 18:07, Stephen Kirby ()
escribió:

> Hi,
>
> I am trying to build the version of GRASS listed in the subject line.
> However, when I run configure, it does not produce a "Makefile" even though
> configure appears to complete without error.  The closest thing I see to a
> Makefile is this file:  include/Make/Platform.make.  I am not running
> configure in the source code directory as one is always told this is a bad
> idea (for ex., when building gcc).  I am running configure in a separate
> directory ("/build-grass").  Let me know what I should try next as I am
> excited to get GRASS running!
>
> Best regards,
> Steve
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] error in g.extension while installing i.fusion.hpf in windows

[Veronica Andreo]

Thanks both!

So the solution in the meantime is to:
1. download the zip file from
https://wingrass.fsv.cvut.cz/grass78/x86_64/addons/latest/
2. unzip and remove the __pychache__ folder
3. copy everything to C:\Users\YourUserName\AppData\Roaming\GRASS7\addons\

Is that correct?

I hope the g.extension problem can be fixed soon? @Helli would you mind
opening an issue for that, please?

Cheers,
Vero

El sáb, 20 mar 2021 a las 23:33,  escribió:

> That's great Helmut :-)
>
> Nikos
>
> ---
>
>
> On 2021-03-19 22:39, Helmut Kudrnovsky wrote:
> ..
>
> > the script itself (downloaded from
> > https://wingrass.fsv.cvut.cz/grass78/x86_64/addons/latest/) works.
> >
> > now we have to solve the g.extension issue.
> >
> > kind regards
> > helli
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] error in g.extension while installing i.fusion.hpf in windows

[Veronica Andreo]

Hi Nikos

I can try it because I'm using Linux, but installing branches or installing
add-ons from urls is not supported for windows, and the error comes when
students using windows try to install the add-on (not in linux). So even if
I try the gitlab branch here, I cannot tell if all will be fine in windows
then...

Vero

El vie, 19 mar 2021 a las 13:02,  escribió:

> Can you try this branch
> https://gitlab.com/NikosAlexandris/i.fusion.hpf/-/tree/encoding
>
> (commit:
> https://gitlab.com/NikosAlexandris/i.fusion.hpf/-/commit/86c2ae92f158c09947ae366bf20dbf3794b8f191
> )
>
> ?
> ---
>
>
>
> On 2021-03-19 12:18, Veronica Andreo wrote:
>
> I'd really appreciate Nikos! :)
>
> El vie, 19 mar 2021 a las 8:28,  escribió:
>
> Vero,
>
>
> I'll try to have a quick look on that during the WE (work overloaded here).
>
> Hopefully it's something trivial, like this suggestion:
>
> https://stackoverflow.com/a/60197939/1172302
>
>
> Nikos
> ---
>
>
>
> On 2021-03-18 13:35, Veronica Andreo wrote:
>
> Hello list,
>
> A student is getting the following error when trying to install
> i.fusion.hpf
>
> C:\>g.extension extension=i.fusion.hpf
> Downloading precompiled GRASS Addons ...
> Fetching  from
> <
> http://wingrass.fsv.cvut.cz/grass78/x86_64/addons/grass-7.8.5/i.fusion.hpf.zip
> >
> (be patient)...
> Traceback (most recent call last):
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line
> 2350, in 
> sys.exit(main())
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line
> 2330, in main
> install_extension(source=source, url=url, xmlurl=xmlurl, branch=branch)
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line 871,
> in install_extension
> ret1, new_modules_ext, new_files_ext = install_extension_win(extension)
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line
> 1259, in install_extension_win
> for line in file:
>   File "C:\OSGEO4~1\apps\Python37\lib\fileinput.py", line 252, in __next__
> line = self._readline()
>   File "C:\OSGEO4~1\apps\Python37\lib\fileinput.py", line 366, in _readline
> return self._readline()
>   File "C:\OSGEO4~1\apps\Python37\lib\encodings\cp1252.py", line 23, in
> decode
> return codecs.charmap_decode(input,self.errors,decoding_table)[0]
>
> UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position
> 401: character maps to 
>
> Here his settings:
>
> Versión de GRASS: 7.8.5
> Code revision: 2b6ab2893
> Fecha de compilación: 2020-12-21
> Construir plataforma: x86_64-w64-mingw32
> GDAL: 3.1.4
> PROJ: 6.3.2
> GEOS: 3.8.1
> SQLite: 3.29.0
> Python: 3.7.0
> wxPython: 4.0.7
> Plataforma: Windows-10-10.0.19041-SP0 (OSGeo4W)
>
> Any ideas?? He can install other extensions without problems.
>
> Thanks in advance
>
> Vero
>
>
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] error in g.extension while installing i.fusion.hpf in windows

[Veronica Andreo]

I'd really appreciate Nikos! :)

El vie, 19 mar 2021 a las 8:28,  escribió:

> Vero,
>
>
> I'll try to have a quick look on that during the WE (work overloaded here).
>
> Hopefully it's something trivial, like this suggestion:
>
> https://stackoverflow.com/a/60197939/1172302
>
>
> Nikos
> ---
>
>
>
> On 2021-03-18 13:35, Veronica Andreo wrote:
>
> Hello list,
>
> A student is getting the following error when trying to install
> i.fusion.hpf
>
> C:\>g.extension extension=i.fusion.hpf
> Downloading precompiled GRASS Addons ...
> Fetching  from
> <
> http://wingrass.fsv.cvut.cz/grass78/x86_64/addons/grass-7.8.5/i.fusion.hpf.zip
> >
> (be patient)...
> Traceback (most recent call last):
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line
> 2350, in 
> sys.exit(main())
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line
> 2330, in main
> install_extension(source=source, url=url, xmlurl=xmlurl, branch=branch)
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line 871,
> in install_extension
> ret1, new_modules_ext, new_files_ext = install_extension_win(extension)
>   File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line
> 1259, in install_extension_win
> for line in file:
>   File "C:\OSGEO4~1\apps\Python37\lib\fileinput.py", line 252, in __next__
> line = self._readline()
>   File "C:\OSGEO4~1\apps\Python37\lib\fileinput.py", line 366, in _readline
> return self._readline()
>   File "C:\OSGEO4~1\apps\Python37\lib\encodings\cp1252.py", line 23, in
> decode
> return codecs.charmap_decode(input,self.errors,decoding_table)[0]
>
> UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position
> 401: character maps to 
>
> Here his settings:
>
> Versión de GRASS: 7.8.5
> Code revision: 2b6ab2893
> Fecha de compilación: 2020-12-21
> Construir plataforma: x86_64-w64-mingw32
> GDAL: 3.1.4
> PROJ: 6.3.2
> GEOS: 3.8.1
> SQLite: 3.29.0
> Python: 3.7.0
> wxPython: 4.0.7
> Plataforma: Windows-10-10.0.19041-SP0 (OSGeo4W)
>
> Any ideas?? He can install other extensions without problems.
>
> Thanks in advance
>
> Vero
>
>
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] error in g.extension while installing i.fusion.hpf in windows

[Veronica Andreo]

Hello list,

A student is getting the following error when trying to install i.fusion.hpf

C:\>g.extension extension=i.fusion.hpf
Downloading precompiled GRASS Addons ...
Fetching  from
<
http://wingrass.fsv.cvut.cz/grass78/x86_64/addons/grass-7.8.5/i.fusion.hpf.zip
>
(be patient)...
Traceback (most recent call last):
  File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line 2350,
in 
sys.exit(main())
  File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line 2330,
in main
install_extension(source=source, url=url, xmlurl=xmlurl, branch=branch)
  File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line 871,
in install_extension
ret1, new_modules_ext, new_files_ext = install_extension_win(extension)
  File "C:\OSGEO4~1\apps\grass\grass78/scripts/g.extension.py", line 1259,
in install_extension_win
for line in file:
  File "C:\OSGEO4~1\apps\Python37\lib\fileinput.py", line 252, in __next__
line = self._readline()
  File "C:\OSGEO4~1\apps\Python37\lib\fileinput.py", line 366, in _readline
return self._readline()
  File "C:\OSGEO4~1\apps\Python37\lib\encodings\cp1252.py", line 23, in
decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]

UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 401:
character maps to 

Here his settings:

Versión de GRASS: 7.8.5
Code revision: 2b6ab2893
Fecha de compilación: 2020-12-21
Construir plataforma: x86_64-w64-mingw32
GDAL: 3.1.4
PROJ: 6.3.2
GEOS: 3.8.1
SQLite: 3.29.0
Python: 3.7.0
wxPython: 4.0.7
Plataforma: Windows-10-10.0.19041-SP0 (OSGeo4W)

Any ideas?? He can install other extensions without problems.

Thanks in advance

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

Re: [GRASS-user] KEYLINE; installing new module add-on (of 7.8) in GRASS 7.6

[Veronica Andreo]

Hi Enrico,

GRASS 7.6 is the last using python 2, and in 7.8 we moved to python 3,
though still supporting python 2. Could that be a problem?

What about compiling GRASS 7.8+ if not in the Debian stable repos?
https://grasswiki.osgeo.org/wiki/Compile_and_Install#Debian

my 0.2 cents
Vero

El lun, 8 mar 2021 a las 11:37, Enrico Gabrielli bonushenricus (<
bonushenricu...@gmail.com>) escribió:

> Thanks
> some problems:
> > File "/home/bonushenricus/.grass7/addons/scripts/r.slope.d
> > irection.py", line 291, in 
> > options, flags = gscript.parser()
> >   File "/usr/lib/grass76/etc/python/grass/script/core.py",
> > line 800, in parser
> > return _parse_opts(lines[1:])
> >   File "/usr/lib/grass76/etc/python/grass/script/core.py",
> > line 751, in _parse_opts
> > os.environ[var] = val
> >   File "/usr/lib/python3.7/os.py", line 682, in __setitem__
> > key = self.encodekey(key)
> >   File "/usr/lib/python3.7/os.py", line 753, in encode
> > raise TypeError("str expected, not %s" %
> > type(value).__name__)
> > TypeError: str expected, not bytes
> It seems that the files are all there, but perhaps they must be
> updated. That's pity. Alternatively I will use MAPCALC with
> ABS (ATAN (TAN (slope) * COS (aspect - raster_direction)))
> but unfortunately with an extra passage and without the possibility of
> defining calculation steps.
>
>
> Il giorno lun, 08/03/2021 alle 09.04 +, Stefan Blumentrath ha
> scritto:
> > Hm, maybe some fixes for g.extension should be backported to 7.6...
> >
> > Anyway, as a workaround, you can just save the python script from (as
> > r.slope.direction
> >
> https://raw.githubusercontent.com/OSGeo/grass-addons/master/grass7/raster/r.slope.direction/r.slope.direction.py
> > ) to:
> > ~/.grass7/addons/scripts/
> >
> > Then make it executable:
> > chmod u+x ~/.grass7/addons/scripts/r.slope.direction
> >
> > And it should work...
> >
> > Cheers
> > Stefan
> >
> > -Original Message-
> > From: Enrico Gabrielli bonushenricus 
> > Sent: mandag 8. mars 2021 09:44
> > To: Stefan Blumentrath ;
> > grass-user@lists.osgeo.org
> > Subject: Re: [GRASS-user] KEYLINE; installing new module add-on (of
> > 7.8) in GRASS 7.6
> >
> > Hi Stefan
> > and thanks
> > Thanks to all and all developers! And here I have the answer directly
> > from those who have developed R-Slope.Direction, no ??
> > Here's what happens:
> > > g.extension extension=r.slope.direction
> > > operation=add
> > > Fetching  from GRASS GIS Addons repository (be
> > > patient)...
> > > ERROR: Extension  not found
> >
> > Il giorno lun, 08/03/2021 alle 08.38 +, Stefan Blumentrath ha
> > scritto:
> > > Hi Enrico,
> > >
> > > GRASS 7.6 should not be a limiting factor. Did you try to install
> > > the
> > > addon through g.extension?
> > >
> > > g.extension extension=r.slope.direction operation=add
> > >
> > > If not, please try. If you did but get an error message, please
> > > provide the error message you got...
> > >
> > > Cheers
> > > Stefan
> > >
> > >
> > > -Original Message-
> > > From: grass-user  On Behalf Of
> > > Enrico Gabrielli bonushenricus
> > > Sent: søndag 7. mars 2021 23:59
> > > To: grass-ita...@listserv.unipr.it; grass-user@lists.osgeo.org
> > > Subject: [GRASS-user] KEYLINE; installing new module add-on (of
> > > 7.8)
> > > in GRASS 7.6
> > >
> > > Hello everyone and everyone.
> > > I write maybe once every one or two years!
> > > I am a geographer and agricultural consultant.
> > > I am using GRASS to design in KeyLine (you can easily find news
> > > about
> > > this ingenious technique, which is also the basis of permaculture,
> > > on
> > > the internet).
> > > I found that in GRASS 7.8 there is a new add-on module called
> > > r.slope.direction which would be very useful for keyline designs.
> > > Unfortunately I use Debian stable, and therefore GRASS 7.6.
> > > I have tried to use the r.slope.direction source script which I
> > > find
> > > here
> > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> > > ub.com%2FOSGeo%2Fgrass-
> > > addons%2Ftree%2Fmaster%2Fgrass7%2Fraster%2Fr.sl
> > > ope.directiondata=04%7C01%7C%7C6f03009d912c4bed9a9e08d8e20e5a2
> > > 0%7
> > > C6cef373021314901831055b3abf02c73%7C0%7C0%7C637507898555085492%7CUn
> > > kno
> > > wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW
> > > wiL
> > > CJXVCI6Mn0%3D%7C1000sdata=QpindTE6R0zQP6ArlP9rc2d3nFOYLMHhwtDn
> > > iM8
> > > EksA%3Dreserved=0 but can't use it. If I install it following
> > > the
> > > instructions I find here
> > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgras
> > > swiki.osgeo.org%2Fwiki%2FGRASS_and_Python%23Installationdata=0
> > > 4%7
> > > C01%7C%7C6f03009d912c4bed9a9e08d8e20e5a20%7C6cef373021314901831055b
> > > 3ab
> > > f02c73%7C0%7C0%7C637507898555085492%7CUnknown%7CTWFpbGZsb3d8eyJWIjo
> > > iMC
> > > 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000
> > > ;sd
> > > 

Re: [GRASS-user] temporal vector loading example

[Veronica Andreo]

Hi Richard,

To create a vector time series, you need to think of each vector map as
either a time instance or an interval. Here's a reproducible example to run
in North Carolina Location

Save the following as coords.txt

1664619|5103481
1664473|5095782
1664273|5101919
1663427|5105234
1663709|5102614

# create a vector of points
v.in.ascii input=coords.txt output=mymap1

# copy it over
for i in `seq 2 9` ; do
g.copy vector=mymap1,mymap${i}
done

# get the list of maps
g.list vect pattern=mymap* > list

# create the stds
t.create type=stvds temporaltype=absolute output=bla title="Bla bla"
description="Bla bla bla"

# assign time stamps to maps
t.register -i type=vector input=bla file=list start="2018-09-01"
increment="1 month"

# check info
t.info type=stvds input=
bla

# check list of maps with dates
t.vect.list bla

HTH,
Vero


El vie, 5 mar 2021 a las 16:50, Richard Duivenvoorde ()
escribió:

> Hi Users,
>
> I'm a virgin GRASS user, let's be honest.
>
> I'm able to load some shp file with 2 datetime columns in it, in GRASS.
>
> But now I try to register it as a Temporal dataset... but fail.
> I packed it, and try to 'import' it
> I tar'ed the location and tried to import it (grass was asking for a tar
> so...)
>
> I see: "grass.exceptions.ScriptError: Unable to find init file" a lot...
>
> Most docs/examples I see are about rasterdata.
> Does anybody have some example or pointer to howto to 'easy load' a shape
> file with 2 datetime columns?
>
> Thanks,
>
> Richard Duivenvoorde
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Geo-Vox modeling

[Veronica Andreo]

Hola Maria Cecilia :)

Would you mind sharing a link to the paper or platform? I was not aware of
it, but sounds pretty interesting!

BTW, I'm based at Instituto Gulich in Cordoba, Argentina :)

Cheers,
Vero

El mar, 2 mar 2021 a las 22:59, Maria Cecilia Zalazar (<
zalazarmariaceci...@gmail.com>) escribió:

> Hello everybody, I´m interested in a new web-GIS platform for Geologic
> Voxel modeling and visualization recently published (Nemoto, T., Masumoto,
> S., Raghavan, V., Nonogaki, S., & Nakada, F. 2020. Development of open
> source Web-GIS platform for three-dimensional geologic modeling and
> visualization).
>
> It comprises GRASS and others FOSS4G and I wonder if anybody knows if I
> could get access to Geo-Vox in any way (OSGeoLive virtual machine or
> desktop application).
>
> Any free alternative geologic voxel model will be welcome.
>
> Thanks in advance!
>
> Cecilia.
>
> --
> MSc. (Lic. Mat.) María Cecilia Zalazar
> Laboratorio de Geología de llanuras (UADER-CONICET)
> Facultad de Ciencia y Tecnología (UADER)
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Problem with r. mapcalc

[Veronica Andreo]

Would you mind adding them and creating a PR, Nikos??
That'd be great :)


El dom, 28 feb 2021 a las 10:22,  escribió:

> I think an overview table, like https://gitlab.com/-/snippets/2083412,
> should be part of both the raster introduction text and the manual of
> r.mapcalc.
>
>
> Thank you, Nikos
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] ASF - OGC - OSGeo code sprint - Feb 17-19, 2021

[Veronica Andreo]

Hello everyone :)

Shall we join the 2021 Joint ASF – OGC – OSGeo Code Sprint [0]?

AFAIU, the focus is on OGC standards implementation. Is anyone in the GRASS
community currently working on that and wishes to participate? They have
created a repo with further details [1] in case you are interested.

Best,
Vero

[0] https://portal.ogc.org/public_ogc/register/20210217_code_sprint.php
[1] https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] raster reclassification or map calculator to simulate past sea-level change

[Veronica Andreo]

Hi Erik,

IIUC, you would need something like the following:

r.mapcalc expression="bla = if(elev <= 25, 0.0, elev)"

or

r.mapcalc expression="bla = if(elev <= 25, null(), elev)"

HTH,
Vero

El mié, 10 feb 2021 a las 8:47, Erik Victor Lundstrøm (<
victor.lundst...@uib.no>) escribió:

> Hi everyone,
>
> I've done some google searches related to my problem. Granted, by no
> means exhaustive, but unsuccessful nonetheless.
> Thus, I hereby by contribute with my first post in the email group
> hoping to find some help.
>
> I work in coastal Norway, and I'd like to produce different rasters
> based on estimates for when the sea-level was either higher, or lower,
> than today.
> When I started doing this years ago, it was simply enough for me to use
> the raster calculator and then produce binary maps using the "<=" or
> ">=" expression as I only wanted to visualise the difference.
> However, today I'd like to continue to work with the rasters where the
> values on the other side of the threshold that I assign remain intact
> but
> I find it way too tedious having to 1) produce a binary map, 2) convert
> the cells denoting the sea-level change into vector polygons, and then
> 3) clipping the old raster into a new one.
>
> I'll try and use an example for what I'd like to try and achieve
> instead.
>
> Let's say I have an elevation raster with values ranging from -0.001 to
> 1500m. Now, if I'd be interested in producing a raster where anything
> below 25m is submerged, then the method that I alluded
> to above would produce the following raster = 0 & 1
>
> What I'm interested in doing now instead, is to find some method where I
> still reset anything below 25m as "0", but where I still have all the
> remaining values intact.
>
> I'm thinking that there should be a way, either through the raster
> calculator or the reclassify tool, where I could simply reset anything
> above or below a certain threshold as either "0", or perhaps even "no
> data" but at the same time keep all the other elevation values of the
> raster intact.
>
> This message should hopefully be enough to indicate that I have
> relatively poor experience with both the reclassify or mapcalc-tool and
> thus any
> brief guide on how I could solve my problem would be greatly
> appreciated!
>
> If anything is unclear just let me know and I can try to reformulate.
>
> Best,
> Victor
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

[Veronica Andreo]

Does the example in v.rast.stats manual [1] work for you, Luis? Is your
polygon vector map "healthy"? The error you get seems to be while
converting the vector to raster, hence I wonder if boundaries of all areas
in your vector are right.

my 0.02 cents
Vero

[1] https://grass.osgeo.org/grass78/manuals/v.rast.stats.html

El lun, 1 feb 2021 a las 16:31, Luí­s Moreira de Sousa via grass-user (<
grass-user@lists.osgeo.org>) escribió:

> Hi Micha, thank you for replying.
>
> I recreated the PSU layer in another mapset with the default SQLite
> back-end, v.rast.stats fails with the exact same error. So this is not
> related to the back-end.
>
> Below are the outputs you requested. Thank you.
>
> > v.info PSU
>
> ++
> | Name:
> PSU   |
> | Mapset:
> MAL   |
> | Location:
> S4AHomolosine |
> | Database:
> /home/duque004/Work/GRASSDATA |
> |
> Title: |
> | Map scale:
> 1:1   |
> | Name of creator:
> duque004  |
> |
> Organization:  |
> | Source date: Fri Jan 29 08:13:08
> 2021  |
> | Timestamp (first layer):
> none  |
>
> ||
> | Map format:
> native|
>
> ||
> |   Type of map: vector (level:
> 2)   |
> |
> |
> |   Number of points:   0   Number of centroids:
> 19468516   |
> |   Number of lines:0   Number of boundaries:
> 38945853   |
> |   Number of areas:19468516Number of islands:
> 1  |
> |
> |
> |   Map is 3D:
> No   |
> |   Number of dblinks:
> 1|
> |
> |
> |   Projection:
> unknown  |
> |
> |
> |   N:  4289569.27224353S:
> -4452930.72775647 |
> |   E:  6679312.25515029W:
> -2226387.74484971 |
> |
> |
> |   Digitization threshold:
> 0|
> |
> Comment: |
> |
> |
>
> ++
>
> > r.info MAL_Mode_5x5
>
> ++
> | Map:  MAL_Mode_5x5   Date: Thu Jan 28 09:08:14
> 2021|
> | Mapset:   MALLogin of Creator:
> duque004|
> | Location:
> S4AHomolosine|
> | DataBase:
> /home/duque004/Work/GRASSDATA|
> | Title:5x5 neighborhood: mode of
> MAL_AFRICA |
> | Timestamp:
> none|
>
> ||
> |
> |
> |   Type of Map:  raster   Number of Categories:
> 0   |
> |   Data Type:
> CELL   |
> |   Rows:
> 87425  |
> |   Columns:
> 89057  |
> |   Total Cells:
> 7785808225 |
> |Projection:
> unknown |
> |N: 4289569.27224353S: -4452930.72775647   Res:
> 100|
> |E: 6679312.25515029W: -2226387.74484971   Res:
> 100|
> |   Range of data:min = 0  max =
> 1   |
> |
> |
> |   Data
> Description:|
> |generated by
> r.neighbors|
> |
> |
> |
> Comments:|
> |r.neighbors input="MAL_AFRICA" output="MAL_Mode_5x5" method="mode"
> s\   |
> |
> ize=5   |
> |
> |
>
> ++
>
>
> --
> Luís
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Friday, January 29, 2021 3:31 PM, Micha Silver 
> wrote:
>
>
>
> On Fri, Jan 29, 2021