Re: [GRASS-user] Error when launching GRASS GIS 8.3.2

[Markus Neteler via grass-user]

Hi Filipe,

On Fri, Apr 26, 2024 at 4:13 PM Filipe Dias via grass-user
 wrote:
>
> Dear All,
> When I try to launch grass 8.3.2 (Pop OS/ Ubuntu 22.04) I get this error. I 
> did a clean installation from ubuntugis unstable. "grass-gui" is installed.
> Is this a bug or am I doing something wrong?
> Thank you
> Best
>
>
> Starting GRASS GIS...
>
>   __  ___   _____
>  / / __ \/   | / ___/ ___/   / /  _/ ___/
> / / __/ /_/ / /| | \__ \\_  \   / / __ / / \__ \
>/ /_/ / _, _/ ___ |___/ /__/ /  / /_/ // / ___/ /
>\/_/ |_/_/  |_///   \/___///
>
> Welcome to GRASS GIS 8.3.2
> 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 tmploc/PERMANENT:~ > Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/wx/core.py", line 3427, in 
> lambda event: event.callable(*event.args, **event.kw) )
>   File "/usr/lib/grass83/gui/wxpython/wxgui.py", line 95, in show_main_gui
> mainframe = GMFrame(
>   File "/usr/lib/grass83/gui/wxpython/main_window/frame.py", line 174, in 
> __init__
> self.workspace_manager.CreateRecentFilesMenu(
>   File "/usr/lib/grass83/gui/wxpython/lmgr/workspace.py", line 515, in 
> CreateRecentFilesMenu
> file_menu = menu.GetMenu(
> wx._core.wxAssertionError: C++ assertion ""node"" failed at 
> ./src/common/menucmn.cpp(923) in GetMenu(): bad index in wxMenuBar::GetMenu()

AFAIK the shipped wxPython version is too old.

You may try to update it:

pip3 install -U -f
https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04
wxPython

Then GRASS GIS should start properly.

HTH,
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

[GRASS-user] GRASS GIS 8.3.2 released

[Markus Neteler via grass-user]

*GRASS GIS 8.3.2 released*

This new patch release includes important fixes and improvements to the
GRASS GIS modules
and the graphical user interface (GUI), making it even more stable for
daily work.

Some of the most important changes are: fixes for r.horizon and other
modules; improvements
in database connections for vector data as well as selected manual pages.

Translations continue in Weblate
, which automatically
creates pull requests with the translated
chunks. We’d like to thank the translators of all languages for their
ongoing support!
Full list of changes and contributors

For all changes, see our detailed announcement at GitHub / Releases / 8.3.2
.

*News article*

https://grass.osgeo.org/news/2024_03_07_grass_gis_8_3_2_released/

Thanks to all contributors!
___
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

[Markus Neteler via grass-user]

On Tue, Mar 12, 2024 at 3:32 PM Veronica Andreo  wrote:
>
> The library is LIBSVM, for Ubuntu it was libsvm-dev

Ok, in Fedora:
dnf install libsvm-devel

Please someone may open a pul request (PR) to update REQUIREMENTS.md
accordingly.

hint: "Good first PR" :-) [1]

Markus

[1] https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md#first-time-setup
___
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

[Markus Neteler via grass-user]

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

Re: [GRASS-user] Multidirectional hillshading scripts / addons?

[Markus Neteler via grass-user]

Hi HB,

Here is one more:

r.shaded.pca - Creates relief shades from various directions and
combines them into RGB composition.
https://grass.osgeo.org/grass8/manuals/addons/r.shaded.pca.html

Best
Markus

On Fri, Feb 16, 2024 at 11:20 PM B H via grass-user
 wrote:
>
> Hi,
> I am trying to create a hillshading effect using DEM rasters similar to ESRI 
> multidirectional hillshading, but I am unable to get anything  in. grass to 
> perform as good as ESRI (or even gdaldem multidirectional shading).
> I am hoping someone in this group has some scripts /addon/tips that I can try.
>
> So far I have tried the following on a few DEMs ( from 3m  to 100 m grid 
> sizes).
> 1) gdaldem  multidirectional hillshading : It's not grass based, but so far 
> has performed better than other grass options :  with the parameter zfactor 
> between 1 and 10. But  it does not seem to be quite as good as ESRI.
> 2) Following code is based on some old discussion on this email list.(Its 
> seems to exaggerate the hills and valleys more than I would expect)
> https://gist.github.com/amcox/b54d65f08fe4448840462901fd6350d4
> 3) Other variants of hillshading like r.skyview : Tried with several 
> parameters but it seems to be inferior to gdaldem (It seems to be a 'washed 
> out' version of the multidirectional. hillshading).
>
> Thanks,
> HB
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user



-- 
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

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

[Markus Neteler via grass-user]

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

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

[Markus Neteler via grass-user]

Hi Ken,

On Fri, Feb 9, 2024 at 12:23 AM Ken Mankoff via grass-user
 wrote:
>
> Hi Veronica,
>
> On 2024-02-03 at 02:52 +13, Veronica Andreo 
> wrote...
> > 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?
>
> I'm guessing the problem and cause is me, not GRASS. Before I try to 
> replicate in the NC data set, I hope you can help answer a question.
>
> I'm trying to work in multiple mapsets and with multiple tables. I find this 
> hard to do when they're in different databases, so when I create a new mapset 
> I set the DB connection to PERMANENT:
>
> db.connect database=${LOCATION_NAME}/PERMANENT/sqlite/sqlite.db

I believe that the quotes are missing - so the variable is immediately
interpreted.

It is important that it really contains '$GISDBASE' etc. and not the
value of $GISDBASE:

db.connect database='$GISDBASE/$LOCATION_NAME/$MAPSET/vector/$MAP/sqlite.db'

The VAR file then contains

-->
DB_DRIVER: sqlite
DB_DATABASE: $GISDBASE/$LOCATION_NAME/$MAPSET/vector/$MAP/sqlite.db
<--

See
https://grass.osgeo.org/grass-stable/manuals/grass-sqlite.html#connecting-grass-to-sqlite

HTH,
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

Re: [GRASS-user] Square root in SQL Builder

[Markus Neteler via grass-user]

Hi Thiago,

On Tue, Jan 30, 2024 at 1:05 AM Thiago Statella via grass-user
 wrote:
>
> Hi everyone!
>
> I need to populate a column in attribute table based on the square root of 
> entries from another column.
> I tried the field calculator with no success. It seams that SQRT function is 
> not supported by SQLite driver.
> Any help would be highly appreciated.

Functionalities like sqrt() or log() are not available in base SQLite
(an issue unrelated to GRASS GIS). You will have to install an SQLite extension.

See the v.db.update manual page and these wiki pages:
- https://grasswiki.osgeo.org/wiki/Build_SQLite_extension_on_Linux
- https://grasswiki.osgeo.org/wiki/Build_SQLite_extension_on_windows

Regards,
Markus

--
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - blog & freelancing
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] writing MicroStatioin DGN files

[Markus Neteler via grass-user]

Uwe,

On Tue, Jan 16, 2024 at 11:11 AM  wrote:
>
> Markus,
>
> the conversion to DGN works fine with OGR2OGR (using a GPKG as intermediate 
> format, that means the data go DGN -> GRASS -> GPGK -> DGN).
> No error messages, result looks fine, even the DGN symbology is preseved as 
> desired.
> That means, the problem must be in GRASS. How to solve?

As already said:

On Sun, Jan 14, 2024 at 1:45 PM Markus Neteler  wrote:
> Overall: the only reasonable way to find out is - since we don't have
> your data - to create a reproducible example with e.g. the North
> Carolina sample data (essentially what I tried not knowing your
> workflow).
> Could you provide that?

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

Re: [GRASS-user] writing MicroStatioin DGN files

[Markus Neteler via grass-user]

Uwe,

On Sat, Jan 13, 2024 at 12:38 AM  wrote:
>
> Markus,
>
> thank you very much for your answer.
> In your example, you used any GRASS map with any columns. They can obviously 
> not be written to DGN (eg. MAJORRDS_).

I see - I am not familiar with the DGN format.

> Please note that in my workflow, the DGN is imported into GRASS, then 
> processed and then written back. So the GRASS map must have the correct DGN 
> colums because it was created from DGN by GRASS itself.
> When I import a DGN and use db.select right after that, I get:
>
> cat|Type|Level|GraphicGroup|ColorIndex|Weight|Style|EntityNum|MSLink|Text|ULink
> 1|17|1|0|2|2|0|||423|{ "32047": [ { "size": 8, "raw": [ "0x1003", "0x7d2f", 
> "0x0871", "0x" ], "type": "ODBC" } ] }
> 2|17|1|0|2|2|0|||424|{ "32047": [ { "size": 8, "raw": [ "0x1003", "0x7d2f", 
> "0x0872", "0x" ], "type": "ODBC" } ] }
> 3|17|1|0|2|2|0|||426|{ "32047": [ { "size": 8, "raw": [ "0x1003", "0x7d2f", 
> "0x0873", "0x" ], "type": "ODBC" } ] }
>
> Then, when I use v.out.ogr -s to skip the cat column, the driver complains 
> about the Type column. But that one is undoubtedly part of the fixed DGN 
> schema, as you can see above.
> I understand that writing any random colums can not work, but I try to write 
> exactly the DGN schema.
>
> Please let me emphasize again that it worked fine for years in GRASS 7.0.

GRASS GIS 7.0 was from Feb 20, 2015 :-) A lot has happened since then.

> I assume there is a bug in the younger GRASS versions. Or has anybody 
> succeeded in writing out DGNs?

Note that GRASS GIS is offloading the write-out of the data to
GDAL/OGR. Does ogr2ogr conversion work with your data and a recent
GDAL version?

Overall: the only reasonable way to find out is - since we don't have
your data - to create a reproducible example with e.g. the North
Carolina sample data (essentially what I tried not knowing your
workflow).
Could you provide that?

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

Re: [GRASS-user] writing MicroStatioin DGN files

[Markus Neteler via grass-user]

On Fri, Jan 12, 2024 at 10:12 AM gisfisch--- via grass-user
 wrote:
>
> Hello list,
>
> I try to write MicroStation V7 DGN files in GRASS 7.8.7. using v.out.ogr.
>
> The same has been working for me without problems since years in GRASS 7.0.
>
> Now I get the following messages:
>
> v.out.ogr -s input=mymap@tempwork output=C:\Users\Documents\mydgn.dgn 
> format=DGN
>
> ERROR 6: CreateField() not supported by this layer.
> ERROR: Unable to create column 
>
> The DGN file is created, but there are no data written to it.
>
> Please help, because writing those files is critical for my workflow.
>

I have made a test with the North Carolina sample dataset:

GRASS nc_spm_08_grass7/user1:~ >
v.out.ogr input=roadsmajor type=line output=/tmp/roadsmajor.dgn format=DGN  --o
ERROR 6: CreateField() not supported by this layer.

ERROR: Unable to create column 

==> so, add -s flag to supress "cat".

v.out.ogr input=roadsmajor type=line output=/tmp/roadsmajor.dgn
format=DGN  --o -s
ERROR 6: CreateField() not supported by this layer.

ERROR: Unable to create column 

Apparently that column is also disliked.

Googling shows:
https://lists.osgeo.org/pipermail/gdal-dev/2006-February/008089.html
"The CreateField() messages are expected with DGN output.  The
 DGN format has a fixed schema and doesn't support user defined
 fields.
"

Looking further in the OGR DGN driver docs shows:
https://gdal.org/drivers/vector/dgn.html

"Creation Issues

2D DGN files may be written with OGR with significant limitations:

- Output features have the usual fixed DGN attributes. Attempts to
create any other fields will fail.
- ...
- A seed file must be provided (or if not provided,
$PREFIX/share/gdal/seed_2d.dgn will be used). Many aspects of the
resulting DGN file are determined by the seed file, and cannot be
affected via OGR, such as initial view window.
- ...
"

I assume that in your case the attribute table names need to follow
this fixed DGN attributes scheme.

HTH,
Markus


-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] GRASS GIS 8.3.1 released

[Markus Neteler via grass-user]

*GRASS GIS 8.3.1 released*

The GRASS GIS 8.3.1 release provides more than 60 improvements and fixes
with respect to the release 8.3.0.
Highlights

   - g.extension: fix installing addons on MS Windows
   - r.watershed: fix streams and basins
   - graphical user interface: multiple bugs fixed

Visit the release page 
(see https://github.com/OSGeo/grass/releases/tag/8.3.1) to download the
source code.

*News article*

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

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

Re: [GRASS-user] [GRASS-dev] GRASS Working Groups

[Markus Neteler via grass-user]

Dear all,

On Tue, Oct 10, 2023 at 9:35 PM Anna Petrášová via grass-dev
 wrote:
>
> Thanks to everyone who responded! I will keep the survey [1] open until the 
> end of the week. Alternatively, just let me know directly if you want to join.
>
> Based on the responses I created wiki pages for the different working groups 
> [2] and added the respondents to the particular group. I assigned a group 
> coordinator to each group to get us started. For those of you who already 
> have access to the wiki, please add what kind of issues you are interested in 
> within the working group. If you don't have a GRASS wiki account, you can 
> either try to create it or ask me or the other group coordinators to fill 
> those details for you. There may be some changes in the wiki authentication 
> now [3], so I am unsure whether signing up at this point is feasible or not.

Yes, please subscribe to the Wiki as before. We don't know when the
new, simplified method will become available.
Just register here: https://grasswiki.osgeo.org/wiki/Special:RequestAccount
and notify by email me (or another wiki admin).

The (still) annoying part is to manually approve the good account
registrations. But having your notification it will be doable.

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

Re: [GRASS-user] [SAC] [OSGeo] #2966: GRASS GIS wiki: connect to OSGeo LDAP

[Markus Neteler via grass-user]

Hi,

Please note that test emails may be issued: they come from the staging VM
which is a test clone of the wiki.

These emails please ignore.
See below for the original notification about LDAP migration.

Markus



Markus Neteler  schrieb am Do., 5. Okt. 2023, 09:43:

> Hi devs,
>
> See below for some efforts to connect the GRASS GIS Wiki to OSGeo-LDAP
> (to finally get rid of all the spam registrations).
>
> Cheers
> Markus
>
> -- Forwarded message -
> From: OSGeo via Sac 
> Date: Thu, Oct 5, 2023 at 4:46 AM
> Subject: Re: [SAC] [OSGeo] #2966: GRASS GIS wiki: connect to OSGeo LDAP
> Cc: OSGeo , 
>
>
> #2966: GRASS GIS wiki: connect to OSGeo LDAP
> -+---
>  Reporter:  neteler  |   Owner:  sac@…
>  Type:  task |  Status:  new
>  Priority:  normal   |   Milestone:  Sysadmin Contract 2023-I
> Component:  Systems Admin|  Resolution:
>  Keywords:  mediawiki, ldap  |
> -+---
> Comment (by robe):
>
>  I set up a dev server to get the ball rolling which is just snapshot of
>  prod
>
>  https://grasswiki.staging.osgeo.org/wiki/GRASS-Wiki
>
>  I'll test out upgrading the wiki and then incorporating LDAP
>  authentication on this. I'll let you know once it's ready to test out.
>
> --
> Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2966#comment:5>
> OSGeo <https://osgeo.org/>
> OSGeo committee and general foundation issue tracker.
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Trying to use GRASS with Jupyter note books in Windows

[Markus Neteler via grass-user]

On Sat, Sep 30, 2023 at 12:36 AM Vishal Mehta  wrote:
>
> Thanks Markus,
> I installed bash kernel; and it seems that it is there (#lsmagic lists bash 
> as one of the cell magics)
>
> but I get the error below:
>
> ##bash
> g.list type=rast

[...]

Probably worth a bug report in GitHub.

> Also I am unable to install extensions r.stream.distance:
>
> !g.extension r.stream.distance
>
> as well as through the GUI
>
>
> both give me a "cannot find executable git" error

This has been this bug:
https://github.com/OSGeo/grass/issues/3077

which was fixed last week:
https://github.com/OSGeo/grass/pull/3166

It will be fixed in GRASS GIS 8.3.1 - release in preparation.

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

Re: [GRASS-user] Trying to use GRASS with Jupyter note books in Windows

[Markus Neteler via grass-user]

On Thu, Sep 28, 2023 at 10:09 PM Vishal Mehta  wrote:
>
> Thanks Markus and Vaclav,
>
> This is what worked for me on Windows:
> # Ask GRASS GIS where its Python packages are.
> sys.path.append(
> subprocess.check_output(["C:\GRASS GIS 8.3/grass83.bat", "--config", 
> "python_path"], text=True).strip()
> )

Perfect, added to the Wiki page, too.

> Also, can I use bash within the jupyter notebook?

Seems yes, after:

pip install bash_kernel

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

Re: [GRASS-user] Trying to use GRASS with Jupyter note books in Windows

[Markus Neteler via grass-user]

On Thu, Sep 28, 2023 at 5:22 AM Vaclav Petras via grass-user
 wrote:
>
> Hi Vishal,
>
> The executable on Windows is not called "grass" like on Linux but "grass8" or 
> "grass83" (to avoid a strange Python
> import error). That should do the trick. If not, try simply providing a full 
> path yourself including the extension (C:\...\...bat).

I have taken liberty to cite this note here:

https://grasswiki.osgeo.org/wiki/GRASS_GIS_Jupyter_notebooks#Windows_tricks

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

Re: [GRASS-user] Fwd: [GRASS-web] Inclusion of your Website in the Library of Congress Web Archives

[Markus Neteler]

On Wed, Sep 13, 2023 at 6:44 PM Rich Shepard  wrote:
>
> On Wed, 13 Sep 2023, Markus Neteler wrote:
>
> > FYI!
>
> Markus,
>
> That's great news. Who would have thought back in the CERL days that so much
> could be accomplished by your leadership of the GRASS development team over
> the decades?

Thanks Rich.
Indeed, it is a great team effort!

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

[GRASS-user] Fwd: [GRASS-web] Inclusion of your Website in the Library of Congress Web Archives

[Markus Neteler]

FYI!

-- Forwarded message -
From: Webcapture [Library of Congress] 
Date: Tue, Sep 12, 2023 at 6:20 PM
Subject: [GRASS-web] Inclusion of your Website in the Library of Congress
Web Archives
To: 

To Whom It May Concern:

The United States Library of Congress has selected your website for
inclusion in the Geospatial Software and File Formats Web Archive, which is
part of a larger collection of historically and culturally significant
websites that have been designated for preservation. The following URL has
been selected: https://grass.osgeo.org/.

The Library of Congress or its agent will engage in the collection of
content from your website at regular intervals over time. In order to
properly archive the above URL, we may archive other portions of the
website and public content that your page links to on third party sites
such as social media platforms. In addition to the aforementioned
collection, archived content from your website may be added to other
relevant collections in the future. This content will be available to
researchers at Library facilities and by special arrangement. It may also
become more broadly available through hosting on the Library’s public
website, which would be done no sooner than one year after it was
collected. For more information on the web archiving process, please read
our frequently asked questions

.

The Library hopes that you share its vision of preserving digital content
and making it available to current and future generations of researchers.
As the internet has become an increasingly important and influential part
of our lives, we believe the historical record would be incomplete if
websites like yours are not preserved and made a part of it. We encourage
you to learn more about the Library’s Web Archiving program
 and explore our collections
 to see examples of how we archive
websites. If you have any questions, comments, or recommendations
concerning the archiving of your website, please email the Library's Web
Archiving Team at webcapt...@loc.gov.

Thank you.

*Library of Congress Web Archiving Team*
webcapt...@loc.gov
[image: Library of Congress logo]

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

[GRASS-user] GRASS GIS 7.8.8 released

[Markus Neteler]

The new GRASS GIS 7.8.8 release provides more than 80 improvements and
fixes compared to the 7.8.7 release.

For details see
https://github.com/OSGeo/grass/releases/tag/7.8.8

Binary packages are ready for download at
https://grass.osgeo.org/news/2023_08_06_grass_gis_7_8_8_released

NOTE: This release is expected to be the last 7.8 release.
Development continues with GRASS GIS 8.x.

Thanks to all contributors!

Happily,
GRASS Development Team
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] How can I remove steps artefacts in digital

[Markus Neteler]

On Mon, Aug 14, 2023 at 9:46 PM Michael Barton  wrote:
>
> Perito,
>
> I don't know where you are getting your points file. But here are some 
> suggestions.
>
> Often stepped DEMs are a result of someone starting with a scanned or vector 
> contour map and then transforming that to a DEM using somewhat 
> unsophisticated algorithms. So how to get rid of these.
>
> You can create a a file of points by generating random points (v.random) and 
> assigning them elevation values from your DEM. Then you can use an 
> interpolation algorithm like v.surf.rst or v.surf.bspline. Random points can 
> help get rid of the steps. The fewer points, the smoother the DEM. More 
> points will provide more topographic detail but may also show up some steps.

In addition: you find an overview (interpolation and resampling) here:
https://grasswiki.osgeo.org/wiki/Interpolation

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

[GRASS-user] OSGeo code sprint at Big Data from Space 2023, November, in Vienna

[Markus Neteler]

The Annual Code Sprint comes to Vienna (Austria)!
The OSGeo Community Sprint 2023 will be hosted by the Big Data from
Space 2023 (BiDS) event.

BiDS brings together key actors from industry, academia, EU entities
and government to reveal user needs, exchange ideas and showcase
latest technical solutions and applications touching all aspects of
space and big data technologies, providing a unique opportunity to
discuss and present the most recent innovations and challenges
encountered in the context of big data from space. The 2023 edition of
BiDS will focus not only technologies enabling insight and foresight
inferable from big data from space. Together, we want to emphasize how
breakthrough space data driven technologies impact on society’s grand
challenges, such as climate change and the green transition.
The event, organized by the European Space Agency (ESA) together with
the European Union Satellite Center (SatCen) and the Joint Research
Center (JRC), will take place at the Austria Center Vienna, and counts
with the support of the partners FFG, Austria in Space and the Federal
Ministry Republic of Austria.

Date: November 6 to 9, 2023
Time: 9:00am to 1:30pm each day

Details at:
https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023

A great occasion to meet in person!
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] grass crashes

[Markus Neteler]

Please consider to update to GRASS GIS 8:

https://grass.osgeo.org/download/linux/
--> ubuntu

It is confusingly called "ubuntugis-unstable" but contains the stable GRASS
GIS 8.

On Fri, Jun 30, 2023 at 3:58 PM Gra  wrote:

>
> I have grass 7.8.7 on a ubuntu machine.
>
> It crashes often with this message, any clue? thanks
>
> [image: image.png]
> ___
> 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] GRASS GIS 8.3.0 released

[Markus Neteler]

GRASS GIS 8.3.0 released

The GRASS GIS 8.3.0 release provides *more than 360 improvements and fixes*
with respect to the release 8.2.0.
Highlights

   - graphical user interface: single-window GUI is now the default
   - PyWPS export in GRASS GIS modeler
   - Improved Jupyter Notebooks integration
   - parallelization: more parallel C tools (openMP) and parallel Python
   tools
   - many fixes and improvements in GRASS GIS modules and graphical user
   interface (see below)
   - move translations from Transifex (thanks for your long-term support)
   to https://weblate.osgeo.org/projects/grass-gis/
   - move of docker images from mundialis organization to
   https://hub.docker.com/r/osgeo/grass-gis/
   - update of docker images
   - improvement of the automated release creation
   - major cleanup of C/C++ code: fix of almost all compiler warnings
   - C/C++ code: adoption of Clang-Format, indent most of C code accordingly
   - support for "pre-commit" in order to reduce unnecessary runs of the
   automated checks (GitHub Actions)
   - notable improvements in the code checking section (GitHub Actions)
   - activate renovatebot to automatically maintain GitHub Actions
   - we have nine new contributors!

Visit the release page 
(see https://github.com/OSGeo/grass/releases/tag/8.3.0) to download the
source code.

*News article:*

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

Re: [GRASS-user] grass82 with_opencl in Debian 12

[Markus Neteler]

Richard Duivenvoorde  schrieb am Mo., 26. Juni 2023,
21:36:

> Wel there IS an openCL too :-)


Sure, it exists. But:

In QGIS:
>
> https://www.itopen.it/opencl-acceleration-now-available-in-qgis/
>
> 'naming is important' :-)
>

And this works in GRASS GIS as well?

Cheers
Markus


> Regards,
>
> Richard Duivenvoorde
>
> On 6/26/23 16:04, Markus Neteler wrote:
> > Hi Enrico,
> >
> > On Mon, Jun 26, 2023 at 3:59 PM bonushenricus 
> wrote:
> >>
> >> Hello everyone
> >> I installed Debian 12.
> >> I found grass-gis 8.2.1
> >> But it's not configured to work in opencl, and 3d rendering is very
> >> slow.
> >
> > It is actually "openGL" to be installed, see
> >
> >
> https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md#optional-packages
> >
> > HTH,
> > Markus
> >
> >
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] grass82 with_opencl in Debian 12

[Markus Neteler]

Hi Enrico,

On Mon, Jun 26, 2023 at 3:59 PM bonushenricus  wrote:
>
> Hello everyone
> I installed Debian 12.
> I found grass-gis 8.2.1
> But it's not configured to work in opencl, and 3d rendering is very
> slow.

It is actually "openGL" to be installed, see

https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md#optional-packages

HTH,
Markus


-- 
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

Re: [GRASS-user] Fwd: skipping MEM driver with r.out.gdal for large files

[Markus Neteler]

Hi Laura,

On Thu, Jun 15, 2023 at 5:00 PM Laura Poggio  wrote:
>
> Dear all,
> Apologies, sent to the developer mailing list by mistake.
> I am trying to save a rather large file from GRASS
>
> Versions:
> GRASS GIS 8.2.1
> GDAL 3.6.3, released 2023/03/07
> Linux: almalinux:9.1
>
> The size of the file is:
> rows=141120
> cols=362880
> cells=51209625600
>
> This the command
> r.out.gdal -c input=out output=output.tif format=COG type=Int16 
> createopt=COMPRESS=LZW,PREDICTOR=2,BIGTIFF=YES --overwrite --quiet
>
> This the output
> Warning 6: driver MEM does not support creation option COMPRESS
> Warning 6: driver MEM does not support creation option PREDICTOR
> Warning 6: driver MEM does not support creation option BIGTIFF
> ERROR 2: /usr/gdal-3.6.2/frmts/mem/memdataset.cpp, 1289: cannot allocate 
> 1x102419251200 bytes
> ERROR: Unable to create dataset using memory raster driver
>
> Is there any option not to use the MEM driver when writing to disk?

I am not sure, in this code section it doesn't look like this:

https://github.com/OSGeo/grass/blob/51e962abbc1176211ad2c4cb7857a61a2b6d1c6f/raster/r.out.gdal/main.c#L377

Maybe someone else in the list has more insights?

Some options:
- try first the GTiff driver, then convert to COG with gdal_translate
- enlarge RAM using a swap file (no reboot needed but sudo access
needed) as disk space is relatively cheap and r.out.gdal will not
realize then that it gets swapped.

Best,
Markus

-- 
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] Pre-release GRASS GIS 8.3.0RC1

[Markus Neteler]

GRASS GIS 8.3.0RC1 released

The *GRASS GIS 8.3.0RC1 release* provides more than *360* improvements and
fixes with respect to the release 8.2.0.
What's Changed Highlights

   - many fixes and improvements in GRASS GIS modules and graphical user
   interface (see below)
   - move translations from Transifex (thanks for your long-term support)
   to https://weblate.osgeo.org/projects/grass-gis/
   - update of docker images
   - move of docker images from mundialis organization to
   https://hub.docker.com/r/osgeo/grass-gis/
   - improvement of the automated release creation
   - C/C++ code: adoption of Clang-Format, indent most of C code accordingly
   - major cleanup of C/C++ code: fix of almost all compiler warnings
   - support for "pre-commit" in order to reduce unnecessary runs of the
   automated checks (GitHub Actions)
   - notable improvements in the code checking section (GitHub Actions)
   - activate renovatebot to automatically maintain GitHub Actions
   - we gained nine new contributors!

*Full Changelog*: 8.2.0...8.3.0RC1

—

This release has 5 assets:

   - ChangeLog.gz
   - core_modules_with_last_commit.json
   - core_modules_with_last_commit.patch
   - Source code (zip)
   - Source code (tar.gz)

Visit the release page
 to download them.
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Active Tropical Cyclone Tracking with GRASS GIS and Jupyter Notebook

[Markus Neteler]

On Wed, May 24, 2023 at 6:23 PM Thomas Adams  wrote:
>
> I guess I’m pathetically old school 臘‍♀️

It is "just" for reducing the workload - still we need to be able to
check what the AI suggests :-)
Just wanted to point out that some new helper tools are available.

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

Re: [GRASS-user] Active Tropical Cyclone Tracking with GRASS GIS and Jupyter Notebook

[Markus Neteler]

On Wed, May 24, 2023 at 5:57 PM Thomas Adams  wrote:
>
> Hi all,
>
> Yes — agreed that a lot of scripting would be needed, but importing readily 
> available data is very doable.

Being in modern times, you can generate the majority of the script
(Jupyter notebook) even with an AI.

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

Re: [GRASS-user] ps.map: add elevation scale? [RESOLVED]

[Markus Neteler]

Rich Shepard  schrieb am Di., 16. Mai 2023, 23:27:

> On Tue, 16 May 2023, Markus Neteler wrote:
>
> > Do you mean in this manual page?
> > https://grass.osgeo.org/grass-stable/manuals/ps.map.html#colortable
> >
> > For wording improvements, please (ideally) suggest them here:
> > https://github.com/OSGeo/grass/blob/main/ps/ps.map/ps.map.html#L214
>
> Markus,
>
> Okay. Earlier today you asked how I would change the colortable name and I
> responded in the email. I'll put the same suggestion on the tracking page.
>

Please keep in mind that we cannot change the parameter names, only once
GRASS GIS 9 comes out. The reason is that it would be a breaking change.

So "only" the description can be changed in a release cycle.

Regards,
Markus


> ___
> 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] ps.map: add elevation scale? [RESOLVED]

[Markus Neteler]

On Tue, May 16, 2023 at 3:21 PM Rich Shepard  wrote:
>
> On Tue, 16 May 2023, Markus Neteler wrote:
>
> > Please suggest how to improve the documentation to make it more obvious.
>
> Markus,
>
> Reading the colortable manual page shows that it's the raster equivalent of
> vlegend. Why not change 'colortable' to 'rlegend' as that's what it
> produces?
> When I saw 'colortable' I assumed it was a version of r.colors, defining the
> map colors, not providing a legend.

Do you mean in this manual page?
https://grass.osgeo.org/grass-stable/manuals/ps.map.html#colortable

For wording improvements, please (ideally) suggest them here:
https://github.com/OSGeo/grass/blob/main/ps/ps.map/ps.map.html#L214

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

Re: [GRASS-user] Selecting most appropriate r.resample.* module

[Markus Neteler]

On Tue, May 16, 2023 at 4:02 PM Rich Shepard  wrote:
>
> I have a DEM with a 1 foot resolution and I want to re-sample it to a 10
> foot resolution.

To me this sounds like
https://grasswiki.osgeo.org/wiki/Interpolation#Resampling_of_raster_maps_to_coarser_resolution

"Resampling of raster maps to coarser resolution"
--> r.resamp.stats

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

Re: [GRASS-user] ps.resamp.rst: invalid argument

[Markus Neteler]

Rich,

On Tue, May 16, 2023 at 5:28 PM Rich Shepard  wrote:
>
> While waiting to learn the uses of the various r.resamp* modules, I tried
> r.resamp.rst with this result:
> r.resamp.rst in=dem2014 ew_res=10 ns_res=10 elevation=base10ft 
> slope=slope10ft aspect=aspect10ft --o
> Processing all selected output files will require
> 129.19 KB of disk space for temp files.
> Temporarily changing the region to desired resolution ...
> Changing back to the original region ...
> Percent complete:
> ERROR: Unable to seek: Invalid argument

I cannot reproduce it:

GRASS nc_spm_08_grass7/user1:~ > g.region raster=elevation -p
projection: 99 (Lambert Conformal Conic)
zone:   0
datum:  nad83
ellipsoid:  a=6378137 es=0.006694380022900787
north:  228500
south:  215000
west:   63
east:   645000
nsres:  10
ewres:  10
rows:   1350
cols:   1500
cells:  2025000

GRASS nc_spm_08_grass7/user1:~ > r.resamp.rst in=elevation ew_res=10
ns_res=10 elevation=elevation slope=slope aspect=aspect
Processing all selected output files will require
23.17 MB of disk space for temp files.
Temporarily changing the region to desired resolution ...
Changing back to the original region ...
Percent complete:
 100%
dnorm in ressegm after grid before out2= 124.899960
dnorm in mainc after grid before out1= 124.899960
dnorm in mainc after grid before out2= 124.899960
r.resamp.rst complete.

Please report the output of `g.region -p`.

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

Re: [GRASS-user] ps.map: add elevation scale? [RESOLVED]

[Markus Neteler]

Rich,

On Tue, May 16, 2023 at 2:38 PM Rich Shepard  wrote:
>
> On Tue, 16 May 2023, Frank David wrote:
>
> > colortable  ? :
> > https://grass.osgeo.org/grass82/manuals/ps.map.html#colortable
>
> Frank,
>
> Well, I completely missed that one.

Please suggest how to improve the documentation to make it more obvious.

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

Re: [GRASS-user] Spearfish datatset for GRASS 4.x and earlier.

[Markus Neteler]

Hi Peter,

On Sat, May 13, 2023 at 11:47 AM Peter Löwe  wrote:
>
> Hi all,
>
> (where) is the Spearfish demo data set still available online for GRASS 4.x 
> and possibly also earlier GRASS versions ?

Please see here:
https://grass.osgeo.org/sampledata/
--> spearfish_grass4data.tar.gz1999-03-08 15:24 6.5M

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

Re: [GRASS-user] v.to.rast: advice needed

[Markus Neteler]

Hi,

In addition, here is an overview page:

https://grasswiki.osgeo.org/wiki/Interpolation

Markus

On Wed, May 10, 2023 at 8:16 PM Maris Nartiss  wrote:
>
> I think you need to interpolate and not simply convert vector lines to
> raster lines. Make sure lines have an attribute with elevation (or z
> coordinate) and use e.g. v.surf.rst module.
>
> Māris.
>
> trešd., 2023. g. 10. maijs, plkst. 17:29 — lietotājs Rich Shepard
> () rakstīja:
> >
> > I need to convert a vector contour map to a raster so I can apply the
> > hydrologic models modules.
> >
> > Reading the v.to.rast manual page I learned that I needed to add categories
> > to the input contour map. Running v.category added no categories: "0
> > features added."
> >
> > v.info does not tell me anything about the elevation values of the contour
> > lines. Looking at the v.* modules, and trying v.univar, didn't help. I could
> > try v.to.3d, but I need information about the vector map's contents.
> >
> > Which v.db* should I use to find the elevation colum associated with each
> > contour line?
> >
> > TIA,
> >
> > 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



-- 
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

Re: [GRASS-user] v.in.ascii syntax help needed

[Markus Neteler]

Rich,

On Tue, May 9, 2023 at 2:40 PM Rich Shepard  wrote:
>
> On Tue, 9 May 2023, Maris Nartiss wrote:
>
> > On the first row you have specified a line with 5 coordinates and one
> > category (L 5 1). You have not provided the last line containing that one
> > category. Just add „1 1“ (layer 1, cat 1) as a last row and you should be
> > fine.
>
> Māris.
>
> Thank you. I searched the manual page to learn what the first and last lines
> in the example meant, but didn't find what they represent.
>
> So, on the top line 'L' means to draw lines, '5' means 5 data rows, and '1'
> means one category. And on the bottom line the layer and category number are
> defined.
>
> I'll add a recommendation to add these explanations to the manual page on
> the bug/feature request web page.

Please consider to edit the page right away:

https://github.com/OSGeo/grass/blob/main/vector/v.in.ascii/v.in.ascii.html

In the upper right of the page is a pen symbol. Then you can submit it
as a pull request by saving the changes.

Thanks
Markus

PS: Manual improvements  are always welcome!
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Is this a bug in 8.3.dev?

[Markus Neteler]

Rich,

On Thu, May 4, 2023 at 10:25 PM Rich Shepard  wrote:
> On Thu, 4 May 2023, Markus Neteler wrote:
...
> > There is an easy debugging option integrated:
> >
> > # switch on
> > g.gisenv set="DEBUG=1"
> > d.mon wx0
>
> Very interesting:
>
> GRASS NSR_TaxLot/PERMANENT:~ > g.gisenv set="DEBUG=1"
> D1/1: G_set_program_name(): g.gisenv
...
> D1/1: G_set_program_name(): g.gisenv
> wxnviz.py: This module requires the NumPy module, which could not be 
> imported. It probably is not installed (it's not part of the standard Python 
> distribution). See the Numeric Python site (http://numpy.scipy.org) for 
> information on downloading source or binaries.

Still your numpy installation appears to be broken.
Perhaps python3-numpy-1.22.3-x86_64-1.SBo does not match your python
version at binary level?

...
> GRASS NSR_TaxLot/PERMANENT:~ >
>
> and the GUI window displayed.

Good.

> > # switch off
> > g.gisenv set="DEBUG=0"
>
> Why are lines repeated?

Perhaps there are loops in the code. It is harmless and just debugging
output which can be a bit noisy.

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

Re: [GRASS-user] Is this a bug in 8.3.dev?

[Markus Neteler]

On Thu, May 4, 2023 at 5:19 PM Rich Shepard  wrote:
> On Thu, 4 May 2023, Anna Petrášová wrote:
>
> > Rich, it would be extremely helpful, if you always show the errors you are
> > getting, otherwise, it's very difficult for us to help you.
>
> Anna,
>
> My apologies; I do know better.
>
> Here's the session:
>
> GRASS metro100/PERMANENT:~ > g.list type=vect
> met100
> GRASS metro100/PERMANENT:~ > d.mon start=wx0
> ERROR: Monitor  already running
> GRASS metro100/PERMANENT:~ > d.mon stop=wx0
> WARNING: Unable to open file
>   
> 
> GRASS metro100/PERMANENT:~ >
>
> When I look for that file the MONITORS subdirectory does not exist:
>
> [rshepard@caddis ~]$ cd 
> /data1/grassdata/metro100/PERMANENT/.tmp/caddis.appl-ecosys.com/
> [rshepard@caddis caddis.appl-ecosys.com]$ ls

Are these directories writable?

ls -la /data1/grassdata/metro100/PERMANENT/.tmp
and
ls -la /data1/grassdata/metro100/PERMANENT/.tmp/caddis.appl-ecosys.com/

will tell.

> [rshepard@caddis caddis.appl-ecosys.com]$
>
> Re-install grass?

Not now, this will not necessarily help.
There is an easy debugging option integrated:

# switch on
g.gisenv set="DEBUG=1"
d.mon wx0
--> what are the messages?

# switch off
g.gisenv set="DEBUG=0"

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

Re: [GRASS-user] Need help importong LiDAR file with r.in.gdal

[Markus Neteler]

Rich,

On Mon, May 1, 2023 at 11:01 PM Rich Shepard  wrote:
>
> I'm trying to import a LiDAR data set. I've used EPSG:6559 while the data
> source manager tells me it imports into ARC/gis using EPSG:6557. I've tried
> both and grass doesn't work for me regardless of which code I use.

[...]
> r.in.gdal -o 
> in=$HOME/projects/oregon/northside-rock/data/LDQ-45122F8/2014-OLC-Metro/Bare_Earth/be45122f8/hdr.adf
>  out=topo_2010 mem=2000 --o
> Over-riding projection check
> Importing raster map ...
> ERROR 1: Block is corrupt, block size was 21532, but expected to be 16384.
> ERROR 1: 
> /home/rshepard/projects/oregon/northside-rock/data/LDQ-45122F8/2014-OLC-Metro/Bare_Earth/be45122f8,
>  band 1: IReadBlock failed at X offset 15, Y offset 308: Block is corrupt, 
> block size was 21532, but expected to be 16384.
> ERROR: Unable to read row 4928

What does it show in GDAL?

gdalinfo  
$HOME/projects/oregon/northside-rock/data/LDQ-45122F8/2014-OLC-Metro/Bare_Earth/be45122f8/hdr.adf

The point is that GDAL needs to be able to read it (since r.in.gdal
depends on it).

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

[GRASS-user] Message translations: GRASS GIS moved from transifex to OSGeo Weblate!

[Markus Neteler]

Dear translators,

Please see below about our move to the Weblate platform at OGGeo (
https://weblate.osgeo.org/projects/grass-gis/) which
also offers a convenient machine translation tool.

Thanks to Huidae Cho for transferring the remaining translated messages
from transifex to Weblate.

Best,
Markus

-- Forwarded message -
From: Transifex Notifications 
Date: Sun, Apr 30, 2023 at 4:01 AM
Subject: New announcement in the organization GRASS GIS




  New announcement in the organization GRASS GIS




Huidae Cho  posted the
following announcement:


* FINAL NOTICE: GRASS GIS Moved to OSGeo Weblate!

*

Dear GRASS GIS Translators,

Once again, we have moved to Weblate [1] and won't be using Transifex
anymore. All the translations in Transifex as of April 29, 2023 3:13AM UTC
have already been pushed to the GRASS repository [2] and no more Transifex
data will be pushed. Since Transifex does not support private or read-only
projects for free accounts, we will delete this Transifex project once the
pull request [2] has successfully been merged into the main branch.

You'll need an OSGeo account [3] to use the new translation platform,
Weblate. To create an account, please request the mantra by sending a
message through the web page [3] or by email to mantra-requ...@osgeo.org.
Don't forget to mention that you request an account to help translate GRASS
GIS. We look forward to welcoming you to the new Weblate translation
platform.

Best Regards,
GRASS GIS Team

[1] https://weblate.osgeo.org/projects/grass-gis/
[2] https://github.com/OSGeo/grass/pull/2942
[3] https://id.osgeo.org/ldap/create
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] LiDAR data CRS issue

[Markus Neteler]

On Sat, Apr 29, 2023 at 5:40 PM Rich Shepard  wrote:
>
> I've defined a location using NAD83(2011) / Oregon North (ft). But, the
> prj.adf file for the data is:
> ProjectionLAMBERT
> Spheroid  GRS80
> Units 3.280839895013123
> ZunitsNO
> Xshift0.0
> Yshift0.0
> Parameters
>43  0  0.0 /* 1st standard parallel
>45 30  0.0 /* 2nd standard parallel
> -120 30  0.0 /* central meridian
>41 45  0.0 /* latitude of projection's origin
> 40.0 /* false easting (meters)
> 0.0 /* false northing (meters)
>
> This is EPSG: 7019, but it's not a CRS, is it?

Here you may find valid codes for a specific area:

https://crs-explorer.proj.org/?latlng=44.552901,-123.266602=false=false=EPSG=PROJECTED_CRS

A click then brings you to EPSG.org, Find in the upper right a tiny
"WKT" button which shows eg.:

https://epsg.org/crs/wkt/id/6559
-> WKT:

PROJCRS["NAD83(2011) / Oregon North
(ft)",BASEGEOGCRS["NAD83(2011)",DATUM["NAD83 (National Spatial
Reference System 2011)",ELLIPSOID["GRS
1980",6378137,298.257222101,LENGTHUNIT["metre",1,ID["EPSG",9001]],ID["EPSG",7019]],ID["EPSG",1116]],ID["EPSG",6318]],CONVERSION["SPCS83
Oregon North zone (International feet)",METHOD["Lambert Conic
Conformal (2SP)",ID["EPSG",9802]],PARAMETER["Latitude of false
origin",43.9,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8821]],PARAMETER["Longitude
of false 
origin",-120.5,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8822]],PARAMETER["Latitude
of 1st standard
parallel",46,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8823]],PARAMETER["Latitude
of 2nd standard
parallel",44.6,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8824]],PARAMETER["Easting
at false 
origin",8202099.738,LENGTHUNIT["foot",0.3048,ID["EPSG",9002]],ID["EPSG",8826]],PARAMETER["Northing
at false 
origin",0,LENGTHUNIT["foot",0.3048,ID["EPSG",9002]],ID["EPSG",8827]],ID["EPSG",15351]],CS[Cartesian,2,ID["EPSG",4495]],AXIS["Easting
(X)",east],AXIS["Northing
(Y)",north],LENGTHUNIT["foot",0.3048,ID["EPSG",9002]],ID["EPSG",6559]]

More human readable output you get with `projinfo`:

projinfo EPSG:6559
PROJ.4 string:
+proj=lcc +lat_0=43.7 +lon_0=-120.5 +lat_1=46
+lat_2=44.3 +x_0=250.0001424 +y_0=0 +ellps=GRS80
+towgs84=0,0,0,0,0,0,0 +units=ft +no_defs +type=crs

WKT2:2019 string:
PROJCRS["NAD83(2011) / Oregon North (ft)",
BASEGEOGCRS["NAD83(2011)",
DATUM["NAD83 (National Spatial Reference System 2011)",
ELLIPSOID["GRS 1980",6378137,298.257222101,
LENGTHUNIT["metre",1]]],
PRIMEM["Greenwich",0,
ANGLEUNIT["degree",0.0174532925199433]],
ID["EPSG",6318]],
CONVERSION["SPCS83 Oregon North zone (International feet)",
METHOD["Lambert Conic Conformal (2SP)",
ID["EPSG",9802]],
PARAMETER["Latitude of false origin",43.7,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8821]],
PARAMETER["Longitude of false origin",-120.5,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8822]],
PARAMETER["Latitude of 1st standard parallel",46,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8823]],
PARAMETER["Latitude of 2nd standard parallel",44.3,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8824]],
PARAMETER["Easting at false origin",8202099.738,
LENGTHUNIT["foot",0.3048],
ID["EPSG",8826]],
PARAMETER["Northing at false origin",0,
LENGTHUNIT["foot",0.3048],
ID["EPSG",8827]]],
CS[Cartesian,2],
AXIS["easting (X)",east,
ORDER[1],
LENGTHUNIT["foot",0.3048]],
AXIS["northing (Y)",north,
ORDER[2],
LENGTHUNIT["foot",0.3048]],
USAGE[
SCOPE["Engineering survey, topographic mapping."],
AREA["United States (USA) - Oregon - counties of Baker;
Benton; Clackamas; Clatsop; Columbia; Gilliam; Grant; Hood River;
Jefferson; Lincoln; Linn; Marion; Morrow; Multnomah; Polk; Sherman;
Tillamook; Umatilla; Union; Wallowa; Wasco; Washington; Wheeler;
Yamhill."],
BBOX[43.95,-124.17,46.26,-116.47]],
ID["EPSG",6559]]

Note that I just showed an example, it is not necessarily the code you
are hunting for.
Just to illustrate a method.

Cheers,
Markus

-- 
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

Re: [GRASS-user] Building 8.2.1: not finding OpenBLASS

[Markus Neteler]

Rich,

On Wed, Apr 26, 2023 at 12:20 AM Rich Shepard  wrote:
>
> I'm trying to build 8.2.1 on Slackware64-15.0. My configuration file is:
> ./configure \
> --enable-64bit \
> --with-libs=/usr/lib64 \
> --with-postgres \
> --with-postgres-includes=/usr/include/postgresql/server/ \
> --with-postgres-libs=/usr/lib64/postgresql/14/lib/ \
> --with-sqlite \
> --with-sqlite-includes=/usr/include/ \
> --with-sqlite-libs=/usr/lib/ \
> --with-cairo \
> --with-blas \
> --with-lapack \
> --with-freetype \
> --with-freetype-includes=/usr/include/freetype2 \
> --with-cxx \
> --with-geos \
> --with-gdal \
> --with-nls \
> --with-python3 \
> --with-pthread \
> --with-proj-share=/usr/share/proj \
> --with-wxwidgets \
> --enable-largefile \
> --with-openmp \
> --with-x \
> --with-pdal=/usr/bin/pdal \
> --with-libLAS
>
> After checking for needed components the script stops telling me it cannot
> locate a BLAS library.

Please check "config.log" for the error message.

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

Re: [GRASS-user] GRASS RDBMS

[Markus Neteler]

Hi Thiago,

On Thu, Mar 23, 2023 at 8:26 PM Thiago Statella  wrote:
>
> Hi everyone,
>
> what is the RDBMS Grass uses by default?

The default attribute (!) data storage happens in a SQLite database
(default DB backend).

For an overview, see
https://grass.osgeo.org/grass82/manuals/sql.html

The vector geometry is by default stored in files using the native
GRASS GIS topological vector format.

> Is there an option to choose a different one in the moment I create a 
> Location (using GUI)? Is it possible to set up PostGis to be the default?

So your aim is to also store the vector geometry in PostGIS?
Then please see

https://grasswiki.osgeo.org/wiki/PostGIS

best,

Markus

> I’m using GRASS 8 with Windows 11.
>
> Thanks in advance!
>
>
> --
>
> Dr. Thiago Statella, Professor Titular
>
> Instituto Federal de Educação, Ciência e Tecnologia de São Paulo - IFSP
>
> Campus Presidente Epitácio
>
> http://lattes.cnpq.br/8559753273123798
>
> https://sites.google.com/view/statella
>
> https://orcid.org/-0002-8656-9147
>
>
>
> ___
> 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

Re: [GRASS-user] help r.forestfrag

[Markus Neteler]

Hi Celeste,

On Thu, Mar 16, 2023 at 2:06 PM María Celeste Galizzi
 wrote:
>
> Hi Markus!
>
> Yes,  I installed the plugin with g.extension.
>
> I had already calculated those indices for that or other rasters.

Mhh - you wrote that you use GRASS GIS 7.8 (please consider to
update!) but the error shows GRASS8 in the path:

File "C:\Users\Cele\AppData\Roaming\GRASS8\addons\scripts\r.forestfrag.py",
line 452, in 

When using g.extension in GRASS GIS 7.8 it should fetch r.forestfrag
from the grass7 branch in the addon repository.

Best,
Markus

> Best,
>
> Celeste
>
> El mié, 15 mar 2023 a las 18:26, Markus Neteler () 
> escribió:
>>
>> Hi María Celeste,
>>
>> On Wed, Mar 15, 2023 at 3:24 PM María Celeste Galizzi
>>  wrote:
>> >
>> > Mi nombre es Ma. Celeste Galizzi.
>> > Estoy trabajando con imágenes Landsat 5 y 8.
>> >
>> > Hice las correcciones, apilado de bandas, kmeans y reclasificación.
>> >
>> > Sobre la imagen reclasificada es con la que estoy tratando de calcular los 
>> > índices de fragmentación en Grass gis 7.8
>>
>> You are using GRASS GIS 7.8, but ...
>>
>> > Para ello importo la imagen raster, con la calculadora clasifico en 
>> > bosque-no bosque y uso r.forestfrag para calcular los indices (tamaño de 
>> > la ventana 15).
>> >
>> > En ese momento me aparece este mensaje
>> >
>> > WARNING: The window option is deprecated, use the option size instead
>> > Traceback (most recent call last):
>> > File "C:\Users\Cele\AppData\Roaming\GRASS8\addons\scripts\
>>
>> ... seem to use the addon version for GRASS GIS 8 which may not be 
>> compatible.
>>
>> Did you install the addon with g.extension?
>>
>> Best,
>> Markus
>>
>> > r.forestfrag.py", line 452, in 
>> > sys.exit(main(*gs.parser()))
>> > File "C:\Users\Cele\AppData\Roaming\GRASS8\addons\scripts\
>> > r.forestfrag.py", line 239, in main
>> > _(
>> > TypeError: %d format: a number is required, not NoneType
>> >
>> >
>> > Ya había trabajo con la imagen con otros tamaños de ventana.
>> >
>> > Por favor, podrían ayudarme a solucionar el problema?
>> >
>> > Desde ya muchas gracias!!!
>> >
>> > Saludos cordiales
>> >
>> > Ma. Celeste Galizzi
>> > ResponderReenviar
>> >
>> > ___
>> > 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



-- 
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

Re: [GRASS-user] help r.forestfrag

[Markus Neteler]

Hi María Celeste,

On Wed, Mar 15, 2023 at 3:24 PM María Celeste Galizzi
 wrote:
>
> Mi nombre es Ma. Celeste Galizzi.
> Estoy trabajando con imágenes Landsat 5 y 8.
>
> Hice las correcciones, apilado de bandas, kmeans y reclasificación.
>
> Sobre la imagen reclasificada es con la que estoy tratando de calcular los 
> índices de fragmentación en Grass gis 7.8

You are using GRASS GIS 7.8, but ...

> Para ello importo la imagen raster, con la calculadora clasifico en bosque-no 
> bosque y uso r.forestfrag para calcular los indices (tamaño de la ventana 15).
>
> En ese momento me aparece este mensaje
>
> WARNING: The window option is deprecated, use the option size instead
> Traceback (most recent call last):
> File "C:\Users\Cele\AppData\Roaming\GRASS8\addons\scripts\

... seem to use the addon version for GRASS GIS 8 which may not be compatible.

Did you install the addon with g.extension?

Best,
Markus

> r.forestfrag.py", line 452, in 
> sys.exit(main(*gs.parser()))
> File "C:\Users\Cele\AppData\Roaming\GRASS8\addons\scripts\
> r.forestfrag.py", line 239, in main
> _(
> TypeError: %d format: a number is required, not NoneType
>
>
> Ya había trabajo con la imagen con otros tamaños de ventana.
>
> Por favor, podrían ayudarme a solucionar el problema?
>
> Desde ya muchas gracias!!!
>
> Saludos cordiales
>
> Ma. Celeste Galizzi
> ResponderReenviar
>
> ___
> 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

Re: [GRASS-user] Development build not finding PDAL version installed

[Markus Neteler]

On Sat, Feb 11, 2023 at 9:22 PM Rich Shepard  wrote:
>
> Trying to build source pulled from the repo failed here:
> checking whether to use GDAL... yes
> checking for gdal-config... /usr/bin/gdal-config
> checking whether to use libLAS... no
> checking whether to use PDAL... yes
> checking for pdal-config... /usr/bin/pdal-config
> configure: error: *** Unable to locate suitable (>=1.7.1) PDAL library.
>
> Yet, installed here is pdal-2.0.1-x86_64-1_SBo, which is certainly newer
> than 1.7.1.
>
> Please suggest how I make the installed pdal visible to the build process.

Did you install pdal-dev(el)? (the name depends on your Linux distro)

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

[GRASS-user] GRASS GIS 8.2.1 released

[Markus Neteler]

We are pleased to announce that GRASS GIS 8.2.1 was released!

The GRASS GIS 8.2.1 release offers over 80 improvements and bug fixes
compared to the previous release, 8.2.0. The update includes a range
of enhancements to the software’s modules. The graphical user
interface has also seen improvements, with issues being resolved for
the database manager, the image group dialog, the import of PostGIS
and SQLite geometry data, the Postscript-based mapping tool, and the
Single-Window GUI toolbar. For mobile devices, viewport support and
hamburger menu-style table of content have been added to the manual
pages. The PROJ library support received important fixes for area
bounding boxes and longitude estimation. Compatibility fixes for PDAL
2.5.0 have been added as well.

Special thanks to all contributors!

For all changes, see our detailed announcement with the full
contributors and list of features and bugs fixed at GitHub:
https://github.com/OSGeo/grass/releases/tag/8.2.1
Packages and installers are now available for Windows, macOS, Debian,
and Fedora, with more coming soon.

See more at our release announcement:
https://grass.osgeo.org/news/2023_01_21_grass_gis_8_2_1_released/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Probabilistic neighborhood analysis

[Markus Neteler]

Hi Bernardo,

On Mon, Jan 16, 2023 at 11:19 PM Bernardo Santos
 wrote:
>
> Hi Makus,
>
> Nice suggestion, I did not know about this function within r.mapcalc (it is 
> quite hidden!)

Do you (or anyone else) have a suggestion how to make it more visible?
Ideas welcome.

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

Re: [GRASS-user] Probabilistic neighborhood analysis

[Markus Neteler]

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

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

[Markus Neteler]

Hi Bernardo,

On Mon, Jan 9, 2023 at 2:58 PM Bernardo Santos
 wrote:
>
> 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

Ah right. Then your GRASS GIS 7.8 version may be too old. G 7.8.7
should be ok (G 7.8.8 is on the way these days) but in any case, as
Vero pointed out, we highly recommend to upgrade to GRASS GIS 8.2.x.

Best,
Markus
___
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

[Markus Neteler]

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
> 
> (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

Re: [GRASS-user] single window gui crash with Ubuntu 22.04 LTS

[Markus Neteler]

On Tue, Jan 3, 2023 at 10:26 AM Frank David  wrote:
>
> Hello Micha,
>
> Thank you for your message. I never succeed to compile grass 8.2 on 
> debian11...

FYIY, I have added instructions here:

https://grasswiki.osgeo.org/wiki/Compile_and_Install#GRASS_8_on_Debian_11_(bullseye)

HTH,

Markus

--
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] GRASS GIS presence on Mastodon/Fediverse

[Markus Neteler]

Hi all,

The PSC has decided to create a Mastodon [1] account on Fosstodon (a
request-only node - we got quickly approved):

https://fosstodon.org/@grassgis

I have enabled twitter-mastodon cross-posting with the https://moa.party/ tool.

Eventually I searched for some followers using https://fedifinder.glitch.me/
The resulting CSV file I imported via Mastodon settings. Some already
followed back.
Finally, I added the Fosstodon handle to the Twitter profile text.

So, now let's see how it goes. Come and join :-)

Cheers,
Markus

[1] https://en.wikipedia.org/wiki/Mastodon_(software)

PS: The Twitter account is still active but we tend to feed it from
Mastodon via the automated bridge.
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.histo.match

[Markus Neteler]

Hi Giuseppe,

Giuseppe Amatulli  schrieb am Di., 27. Sep.
2022, 15:38:

> Dear Grass team
> I'm trying to use the add on i.histo.match in grass 7.8.2 but something is
> not going well.
>
> GRASS 7.8.2 (tmploc):/tmp > i.histo.match
> input=570-00-023296.1,570-00-023296.1
>  output=mosaic max=4000 --overwrite --verbose
> WARNING: Bug in UI description. Missing module description
>

I assume that you compiled GRASS GIS yourself?

This error usually indicates that a clean recompilation is needed, with

make distclean

as the first step.



> The warning also appears during the i.histo.match installation.
>

So, first a clean GRASS compilation, then add-ons on top.

Hope this helps,
Markus

PS: GRASS GIS 8 is highly recommended!
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Parallelizing r.mapcalc

[Markus Neteler]

Hi Frank,

On Thu, Sep 15, 2022 at 2:32 PM Frank David  wrote:
> 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%

You may also check the source code of this addon where r.mapcalc is
used in parallel:

https://github.com/OSGeo/grass-addons/blob/grass8/src/raster/r.mapcalc.tiled/r.mapcalc.tiled.py

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

Re: [GRASS-user] Export raster to PostGIS

[Markus Neteler]

Hi,

Stefan Blumentrath  schrieb am So., 28. Aug.
2022, 15:27:

> Hi Asim,
>
> You could try to use raster2pgsql after making sure you have the
> GDAL-GRASS plugin installed.
>

FYI:
This GDAL-GRASS driver you find here:

https://github.com/OSGeo/gdal-grass

Markus


> Then you should be able to load GRASS GIS raster maps directly into
> PostGIS by pointing to the header of your GRASS GIS maps. Something like:
> raster2pgsql -s 4326 -C -l 2,4 -I -F -t 2700x2700
> /your_grassdb/location/mapset/cellhd/your_raster_map output_pg_shema_name.
> output_table_name | psql -h your_host -p 5432 -U postgres -d
> your_pg_database
> (obviously you have to adjust options and flags of raster2pgsql to your
> case...).
>
> Hope that helps.
>
> Cheers
> Stefan
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

[Markus Neteler]

Hi all,

Greetings from Florence!

On Thu, Aug 25, 2022 at 10:24 AM Wolf Bergenheim
 wrote:
>
> Hello all,
>
> For the FOSS4G community sprint we have a sign up sheet here.
>
> I'm not there physically, but I'd still love to work together on the weekend.
> I'm planning on working more on the command line stuff I've been looking at 
> recently. It would be nice to have some sort of video chat to plan the sprint 
> a bit.
>
> What would be a good way to live communicate? Should we use IRC or something 
> else? A video conference could also be nice. Once we know who plans to attend 
> and whet schedule they have we can organize some kind of kick off meeting?
>
> Let's use this thread to get organized!

I just created a dedicated page in our Wiki:

https://grasswiki.osgeo.org/wiki/GRASS_GIS_at_OSGeo_Community_Sprint_2022

See you all tomorrow, onsite or online :)

Best,
Markus
___
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

[Markus Neteler]

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

Re: [GRASS-user] Need help identifying missing wxgtk dependencies

[Markus Neteler]

On Fri, Aug 12, 2022 at 3:49 PM Eric Patton via grass-user
 wrote:
> On Thursday, August 11th, 2022 at 19:29, Markus Neteler  
> wrote:
...
> > > Launching g.gui gives a popup window that says "Unable to get geographic 
> > > extent. Force quitting wxGUI. Please manually run g.region to fix the 
> > > problem."
> > >
> > > On the terminal, this was printed after launhcing g.gui:
> > >
> > > > g.gui
> > > > Launching  GUI in the background, please wait...
> > > > wxdigit.py: Could not load grass_gis.8.3.
> > > > wxnviz.py: Could not load grass_gis.8.3.

And libgrass_gis.8.3.so etc are existing?

> I still seem to have the wxdigit error, though.
>
> wxdigit.py:
>
> > locate wxdigit.py
> /usr/local/grass/dist.x86_64-pc-linux-gnu/gui/wxpython/vdigit/wxdigit.py
> /usr/local/grass/gui/wxpython/vdigit/wxdigit.py
> /usr/local/grass83/gui/wxpython/vdigit/wxdigit.py
>
> wxnviz.py:
>
> > locate wxdigit.py
> /usr/local/grass/dist.x86_64-pc-linux-gnu/gui/wxpython/vdigit/wxdigit.py
> /usr/local/grass/gui/wxpython/vdigit/wxdigit.py
> /usr/local/grass83/gui/wxpython/vdigit/wxdigit.py

Pls run this to print the Python and wxPython versions:

python3 -c "import sys, wx; print(sys.version); print(wx.version())"

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

Re: [GRASS-user] Need help identifying missing wxgtk dependencies

[Markus Neteler]

On Thu, Aug 11, 2022 at 8:06 PM Eric Patton via grass-user
 wrote:
>
> HI,
>
> I'm doing a fresh install of Grass 8.3dev on a new laptop running Linux Mint 
> 20.3. It's been a while since I've had to
> do a new install, so used the Linux Mint wiki instructions here: 
> https://grasswiki.osgeo.org/wiki/Compile_and_Install#Linux_Mint
>
> I had no obvious error during configure/make/install.
>
> > g.version -gre
> version=8.3.dev
> date=2022
> revision=c1b1ff69d
> build_date=2022-08-11
> build_platform=x86_64-pc-linux-gnu
> build_off_t_size=8
> libgis_revision=2b85ab5eb
> libgis_date=2022-07-25T15:37:35+00:00
> proj=7.2.1
> gdal=3.5.1
> geos=3.11.0
> sqlite=3.31.1
>
> After launching Grass, g.region -p gives:
>
> > g.region -p
> projection: 99 (unnamed)
> zone:   0
> datum:  wgs84
> ellipsoid:  wgs84
> north:  149300
> south:  124200
> west:   -25900
> east:   7800
> nsres:  100
> ewres:  100
> rows:   251
> cols:   337
> cells:  84587
> free(): invalid pointer
> Aborted (core dumped)

Please check if you have by chance PROJ libraries twice on your system
(maybe a leftover from a local compilation vs distro packages.

sudo updatedb
locate libproj

may be of help here. Also check the output of

ldd $(which g.region)

for anything suspicious.

> Launching g.gui gives a popup window that says "Unable to get geographic 
> extent. Force quitting wxGUI. Please manually run g.region to fix the 
> problem."
>
> On the terminal, this was printed after launhcing g.gui:
>
> > g.gui
> Launching  GUI in the background, please wait...
> wxdigit.py: Could not load grass_gis.8.3.
> wxnviz.py: Could not load grass_gis.8.3.

Please check (with locate, see above) if the library is on your system.

> I noticed in the wxGUI console these messages:
>
> "3D view mode not available
> Reason: cannot import name 'DM_FLAT' from 'nviz.wxnviz' "
>
> and also this one:
>
> "Vector digitizer not available.
> Reason: name 'sys' is not defined".

Mhh, weird. Maybe an error caused by another error?

> I thought I had all python/wxwidgets dependcies satisfied, but I must be 
> missing something obvious??
>
> Additionally, I wanted to ask if we have a searchable Grass mailing list 
> site? The mailman site is kind of useless for trying to search old messages.

I want that, too :-)
For the time being, here is a 3rd party search interface
https://marc.info/?l=grass-user=1=2

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

Re: [GRASS-user] temporal raster accumulation

[Markus Neteler]

Hi Ivan,

In addition, see also

https://grasswiki.osgeo.org/wiki/Temporal_data_processing#Aggregation_of_seasonal_data_using_time_ranges

best,
Markus

On Tue, Aug 9, 2022 at 11:40 AM Stefan Blumentrath
 wrote:
>
> Hi Ivan,
>
> A simple, quick-and-dirty approach could be:
> t.rast.algebra basename=rain5 expression="rain5=rain + rain[-1] + rain[-2] + 
> rain[-3] + rain[-4] + rain[-5]"
>
> Temporal selection (start_date(rain)...) is probably more elegant...
>
> See:
> https://grass.osgeo.org/grass78/manuals/t.rast.algebra.html
>
> Cheers
> Stefan
>
> -Original Message-
> From: grass-user  On Behalf Of Ivan 
> Marchesini
> Sent: tirsdag 9. august 2022 09:45
> To: GRASS user list 
> Subject: [GRASS-user] temporal raster accumulation
>
> Dear GRASS users
>
> I'm a little bit confused about which can be the best module/tool to perform 
> the following task I have a strd having a daily granularity. It contains 
> total daily cumulated rainfall.
>
> I would like to create a new strd where, for each day, I have the cumulated 
> rainfall in the antecedent 5 days
>
> can you kindly suggest which is the best tool (or combination of tools) to 
> reach this aim?
>
> thank you very much
>
> Ivan
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Help regarding i.ortho.photo

[Markus Neteler]

Hi,

On Sat, Jun 25, 2022 at 1:10 AM  wrote:
>
> Hi.
> I cannot find the "i.ortho.photo" suite in GRASS 8.2. I tried accessing it in 
> the add ons menu.

Please note that i.ortho.photo is a core module set (not an addon), see:
https://grass.osgeo.org/grass-stable/manuals/i.ortho.photo.html

> I tried installing GRASS 8.2 in Windows 10 and later tried using Fedora, but 
> couldn't find it.
> Can anyone please help me out?

i.ortho.photo you can access from command line.

> Is this discontinued from the latest version of GRASS or am I missing 
> something on how to proceed?

It is there but it doesn't appear in the search box which looks like a
but to me.

> I will be highly grateful if someone points me in the right direction

To start, you may run on command line:

i.ortho.photo --ui

Please report a but that i.ortho.* is missing from the GUI search:
https://github.com/OSGeo/grass/issues

It is indeed not in the menu (not all commands are listed there) - it
could be debated it it should be added there or not.

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

[GRASS-user] Fwd: RFC: New version numbering (PR #2357)

[Markus Neteler]

Hi devs, all,

To avoid that this remains unnoticed by all those not following the
issues and pull requests in https://github.com/OSGeo/grass (note that
you can subscribe easily to get email notofications about issues and
pull requests where a lot of discussion happens nowadays!), here a
forward of the RFC for a new GRASS GIS version numbering system:

On Tue, May 3, 2022 at 5:10 AM Vaclav Petras  wrote:
>
> This PR is a RFC for a new version numbering system. The main point is not 
> making any distinction between even and odd version numbers. After 8.2.z, 
> 8.3.0 would follow.
>
> Notably, this RFC does not follow the current RFC procedure (if any), but 
> creates a PR as suggested in the past as a possible improvement of the 
> procedure.
>
> 
>
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/OSGeo/grass/pull/2357

Importantly, after 8.2.z, 8.3.0 would follow (once the RFC is
accepted, we would change the "8.4.0" milestone label to "8.3.0").

Please see the RFC and comment as needed.

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

Re: [GRASS-user] I can't get Grass to run

[Markus Neteler]

Hi Chris,

Since yesterday there is the new GRASS GIS 8.2.0 available, with a
standalone installer available at:

https://grass.osgeo.org/grass82/binary/mswindows/native/WinGRASS-8.2.0-1-Setup.exe

Could you try that?

Markus

On Sat, Jun 4, 2022 at 12:24 AM Chris Arai  wrote:
>
>   Hi, I'm trying to get started but I can't get Grass to run. I'm on a 
> Windows 10 platform running Grass 8.0.
> I get this error:
>
> 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
>
> If I run as administrator I get a python Traceback
>
> Traceback (most recent call last):
>   File "C:\Program Files\GRASS GIS 8.0\etc\grass80.py", line 2741, in 
> main()
>   File "C:\Program Files\GRASS GIS 8.0\etc\grass80.py", line 2490, in main
> ensure_home()
>
>File "C:\Program Files\GRASS GIS 8.0\etc\grass80.py", line 874, in 
> ensure_home
>os.environ["HOME"] = os.path.join(os.getenv("HOMEDRIVE"), 
> os.getenv("HOMEPATH"))
>
>File "C:\Program Files\GRASS GIS 8.0\Python39\lib\ntpath.py", line 78, in 
> join
>path = os.fspath(path)
>   TypeError: expected str, bytes or os.PathLike object, not NoneType
>
> Any ideas how to fix this?
> ___________
> 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] GRASS GIS 8.0.2 released

[Markus Neteler]

The GRASS GIS 8.0.2 release provides more than 30 fixes and improvements

with respect to the release 8.0.1.
See also our detailed announcement with the full list of changes and bugs
fixed
at https://github.com/OSGeo/grass/releases/tag/8.0.2.

Full Changelog: 8.0.1...8.0.2


For download of installers and packages, see
https://grass.osgeo.org/news/2022_05_12_grass_gis_8_0_2_released/

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

Re: [GRASS-user] standalone grass installer version 7.6

[Markus Neteler]

Hi Bernado,

On Mon, Apr 25, 2022 at 9:48 AM Stefan Blumentrath
 wrote:
>
> Hi Bernado,
>
> Seems the download directory of older Windows Standalone installers is empty 
> indeed:
>
> https://grass.osgeo.org/grass76/binary/mswindows/native/x86_64/

Searching online for "WinGRASS-7.6.1-1-Setup-x86_64.exe" I found it
here (if trustable, you need to decide):

https://softfamous.com/grass-gis/download/
-> download

Due to lack of space on the server, the very old binaries have not
been preserved. Also, to not overwhelm our mirror sites.

Otherwise, I'd also recommend what Stefan suggests:

> For Wndows you can get older packages with osgeo4w version 1:
>
> http://download.osgeo.org/osgeo4w/v1/osgeo4w-setup-x86_64-v1.exe
>
> There (OSGeo4W V1) are many older GRASS packages available:
>
> http://download.osgeo.org/osgeo4w/v1/x86_64/release/grass/grass/
>
> Here are older generic Linux binaries:
>
> https://grass.osgeo.org/grass74/binary/linux/snapshot/
>

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

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

[Markus Neteler]

FYI!

-- Forwarded message -
From: andrea antonello via Discuss 
Date: Mon, Mar 21, 2022 at 3:34 PM
Subject: [OSGeo-Discuss] FOSS4G 2022 - Code Sprint
To: ML osgeo discuss , 

Dear all!

Between August 27th and 28th the University of Florence will be stage
for the gathering of  developers, translators, power users and anyone
interested in their most important hands-on meeting of the year: the
codesprint of FOSS4G 2022

For those who wonder, a codesprint has the form of a community camp to
which everyone is invited to participate and contribute with her/his
point of view, ideas, open mindset and positive aura.

This year we will invite seasoned community members to donate time for
welcoming new members and introduce them to different projects or
guide them through the setup of the development environment or
translation tools and get started on the Foss4G journey.

Don’t miss out this opportunity to meet many like-minded people, have
stimulating chats and get some kick-start help.

If you are interested to participate, please add your name and project
to this wiki page:

https://wiki.osgeo.org/wiki/FOSS4G_2022/Community_sprint

The Organizing Team is looking forward to meeting you!

If you have questions/comments/ideas please let us know:
https://2022.foss4g.org/contact.php

On behalf of the Codesprint Organization Committee, Andrea

___
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: OpenDataScience Europe Workshop 2022 in Prague - Registrations and abstract submission are open! 

[Markus Neteler]

FYI

-- Forwarded message -
From: OpenGeoHub Foundation 
Date: Tue, Mar 15, 2022 at 3:00 PM
Subject: Registrations and abstract submission are open! 



How to participate as a speaker or attend the workshop in June
View this email in your browser


*Edition March 2022*
Dear readers,

After the last finalization from Prague's Technical University partners, we
are opening the registrations to attend the 2-day training sessions and
2-day conference talks at the OpenDataScience Europe Workshop 2022 in
Prague. Also, meet the keynote speakers and discover how to submit your
abstract to be selected as a speaker!
Connecting Europe through Earth Observation and Open Data Missions

*REGISTRATIONS ARE OPEN*
Registrations are now open! If you wish to attend the training sessions

and/or
attend the conference, you have time until *May 1st. *Why attending?
Learn, share and connect with peers and experts in open data science!
Register now!


*CALL FOR ABSTRACTS - UPCOMING DEADLINE: APRIL 1ST*
Do not forget to submit your abstract by* the 1st of April via Pretalx *to
have the chance to present at the workshop, discuss your work and
network! Remember
that submitting and presenting your work at ODSE workshop 2022 is free of
charge!

The workshop follows the main topics of the project:

   1. Dynamic mapping of land cover, vegetation, climate and environmental
   quality indices
   2. Spatiotemporal Machine Learning using Ensemble techniques,
   3. Earth Data Cubes: spatiotemporal overlay, modelling and visualization
   4. Geocomputing and geo-harmonization using Python, R and Open Source
   GIS GDAL, GRASS GIS, QGIS
   5. Processing large raster datasets using High Performance and
   Distributed Computing
   6. Using geospatial harmonized European map products
   7. Using AR/VR for geospatial data visualisation

Submit abstract

[image: Share]

Share

[image: Tweet]

Tweet

[image: Forward]

Forward

[image: Share]

Share


*TRAINING SESSIONS*
It is now possible to* explore the schedule of the two days dedicated to
training sessions (13-14 June)* around AI and open-source software, big
data management, mapping of land cover, soil, vegetation and other
environmental variables at the European level! Check out the schedule here:
View schedule


*ODSE 2022 CONFERENCE*
We are glad to introduce three additional keynote speakers that will expand
the discussion around the harmonization of Earth Observations at the ODSE
Conference on June 15-16:
*“Spatio-temporal modelling of changing topographies: from point clouds to
tangible interfaces”*

by Dr Helena Mitasova

from the North Carolina State University
*“**European Commission’s data policy in 2022**”*

by Jiří Pilař

from the Data Policy and Innovation Unit at the European Commission’s
Directorate-General for Communications Networks, Content & Technology (DG
CONNECT)
*"The JRC Big Data Analytics Platform (BDAP) Screen reader support enabled*
*”*

by Pierre Soille

from the Joint Research Centre (JRC) of the European Commission
View all keynote speakers


*ODSE 2022 SPECIAL ISSUE*
The Civil engineering journal
,
the online peer-reviewed Open Access scientific journal published by the

[GRASS-user] GRASS GIS 8.0.1 released

[Markus Neteler]

*GRASS GIS 8.0.1 released*

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

Download source code tarball at

   - https://grass.osgeo.org/grass80/source/grass-8.0.1.tar.gz
   - https://grass.osgeo.org/grass80/source/grass-8.0.1.md5sum

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

   - https://trac.osgeo.org/grass/wiki/Grass8/NewFeatures80

The GRASS GIS 8.0.1 release provides more than 20 fixes and improvements
 with respect to the
release 8.0.0.
What's Changed

Important fixes

   - utils/mkhtml: fix print warning/fatal message during compilation to
   not break offline compilations (#2139
   ) by @tmszi
   
   - r.quantile, r.stats.quantile, lib/stats: fix quantile algorithm (#2108
   ) by @metzm
   

Module fixes

   - r.colors: fix order of rules (#2167
   ) by @metzm
   
   - r.geomorphon: combine profile parser rules to allow usage as pygrass
   module (#2154 ) (#2226
   ) by@ninsbl
   - TGIS: fix semantic label (#2215
   ) by @metzm
   
   - t.rast.mapcalc: transfer semantic label (#2219
   ) by @metzm
   
   - t.rast.neighbors: transfer semantic label (#2218
   ) by @metzm
   

GUI

   - wxGUI: do not import from pygrass on gui startup (#2202
   ) by @petrasovaa
   
   - wxGUI: Thread.setDaemon deprecated in Python 3.10 (#2145
   ) by @petrasovaa
   

Portability

   - MS Windows packaging: add missing dlls from MSYS (#2204
   ) by @ninsbl
   

Documentation

   - CONTRIBUTING.md: describe the fork process more in detail by @pesekon2
   
   - Fix typo in v.import documentation (#2142
   ) by @agiudiceandrea
   
   - howto_release.md: cleanup of marketing section by @neteler
   
   - manual pages: remove unneeded SVN Date entry and selected cleanup (
   #2143 ) by @neteler
   

Singularity

   - singularity: Minor fixes of definition file (#2179
   ) by @lucadelu
   

*Full Changelog*: 8.0.0...8.0.1

—

This release has 2 assets:

   - Source code (zip)
   - Source code (tar.gz)

Visit the release page 
to download them.
Thanks to all contributors!
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Error with pansharpening

[Markus Neteler]

Hi Vishal,

On Wed, Feb 23, 2022 at 9:04 PM Vishal Mehta  wrote:
>
> Thanks Markus,
>
> It's 7.8.2
> g.version -rge
> version=7.8.2
> date=2019

.. your installation is a few years old - please consider updating to
7.8.6 or even 8.0.x.

> I did see your email recently about 7.8.7..
> I could just try version 8?

Sure, that would be best.

BTW: For the QGIS integration of GRASS GIS 8.0:
QGIS has been updated in master (QGIS 3.24) and everything backported
to QGIS 3.22 LTR.

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

Re: [GRASS-user] Error with pansharpening

[Markus Neteler]

Hi Vishal,

On Wed, Feb 23, 2022 at 8:22 PM Vishal Mehta  wrote:
>
> Hi all,
>
> I'm using GRASS 7.8 on WIndows 10, and trying out some of the Landsat 
> routines.

Which version do you precisely use?

g.version -rge

Is it 7.8.6 or older?

Markus

PS: Just a few minutes ago I released 7.8.7 :-)
   https://github.com/OSGeo/grass/releases/tag/7.8.7
  (Windows and other binaries aren't ready yet)

>
> I'm getting an error on pan sharpening, at the very end of the processing: 
> and i see some temp files have been created. is there a way to fix this? 
> Thanks, Vishal
> ---
> Wed Feb 23 11:14:22 2022)
> i.pansharpen red=Refl_3@PERMANENT green=Refl_2@PERMANENT 
> blue=Refl_1@PERMANENT 
> pan=LC08_L1TP_044033_20180225_20180308_01_T1_B8@PERMANENT 
> output=brovey_pansharpen method=brovey bitdepth=8
> Using 8bit image channels
> Performing pan sharpening with hi res pan image: 15.00
> Pan channel/intensity histogram matching using linear regression
> Histogram matching...
> Traceback (most recent call last):
>   File "C:\PROGRA~1\QGIS3~1.10\apps\grass\grass78/scripts/i.
> pansharpen.py", line 632, in 
> main()
>   File "C:\PROGRA~1\QGIS3~1.10\apps\grass\grass78/scripts/i.
> pansharpen.py", line 257, in main
> brovey(pan, ms1, ms2, ms3, out, pid, sproc)
>   File "C:\PROGRA~1\QGIS3~1.10\apps\grass\grass78/scripts/i.
> pansharpen.py", line 315, in brovey
> panmatch1 = matchhist(pan, ms1, outname)
>   File "C:\PROGRA~1\QGIS3~1.10\apps\grass\grass78/scripts/i.
> pansharpen.py", line 552, in matchhist
> stats = stats_out.communicate()[0].split('\n')[:-1]
> TypeError: a bytes-like object is required, not 'str'
> (Wed Feb 23 11:14:31 2022) Command finished (9 sec)
...
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] GRASS GIS 7.8.7 released

[Markus Neteler]

*GRASS GIS 7.8.7 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.7.tar.gz
   - https://grass.osgeo.org/grass78/source/grass-7.8.7.md5sum

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

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

The GRASS GIS 7.8.7 release provides more than 40 fixes and improvements
 with respect to the
release 7.8.6.
What's Changed

Modules:

   - g.extension.all: fix reinstall multi-addons by @tmszi
    in #2082
   
   - g.extension: disable checking multi-addon addons metadata by @tmszi
    in #2090
   
   - g.extension: fix get get_addons_paths func json_file attribute by
   @tmszi  in #2094
   
   - g.extension: fix link generation in multi-addon man page for addons by
   @tmszi  in #2097
   
   - i.spectral: show error message if one of the supported monitor isn't
   running by @tmszi  in #1991
   
   - i.vi: fix PVI formula by @pesekon2  in
   #1985 
   - r.sun: Fix metadata update on parallel computation by @aaronsms
    in #1514
   
   - tgis db version mismatch: promote t.downgrade by @landam
    in #2002
   

wxGUI:

   - wxGUI: font size Python 3.10 fix by @petrasovaa
    in #2036
   
   - wxGUI: no is_shell_running available by @neteler
    in #2056
   
   - wxGUI: fix unexpected type float error with Python 3.10 by @petrasovaa
    in #2030
   
   - wxGUI/gui_core: fix change opacity level dialog min/max size by @tmszi
    in #2067
   
   - wxGUI: more Python 3.10 fixes by @neteler 
   in #2050 
   - wxGUI/preferences.py: fix loading default user settings by @tmszi
    in #2041
   
   - wxGUI/splashscreen: use standard one, try to show it before main app,
   increase timeout by @petrasovaa  in #1718
   
   - wxGUI/xml/toolboxes.xml: add missing 'r.fill.stats' module item inside
   'InterpolateSurfaces' toolbox by @tmszi  in
   #1977 
   - remove .setpdfwrite option on MS Windows by @ninsbl
    in #1962
   

Translations

   - i18n: Update for release branch 7.8 by @HuidaeCho
    in #2104
   

Unit tests/CI:

   - grass.gunittest: Use collections.abc for Iterable (#2006
   ) by @wenzeslaus
    in #2008
   
   - CI: Remove Ubuntu 16.04 from GH Actions for 7.8 branch by @wenzeslaus
    in #2009
   
   - grass.gunittest: Use collections.abc for Iterable by @wenzeslaus
    in #2008
   

GRASS GIS addons management:

   - tools/mkhtml.py: fix module/official addons source code and history
   URL branch by @tmszi  in #2038
   
   - tools/mkhtml.py: replace f-string with format() function to maintain
   compatibility with Python 3.5/2.7 version by @tmszi
    in #2077
   
   - tools/mkhtml.py: fix git cherry-pick commit cba6a7a
   

   by @tmszi  in #2110
   

Portability:

   - Fix linker flags on FreeBSD by @neteler 
   in #1936 
   - winGRASS: GRASS-Installer.nsi.tmpl to change form BU Execute to
   S-1-5-32-545 Generic User Read and Generic User Execute by @hellik
    in #2068
   
   - 

Re: [GRASS-user] hexagon rasters

[Markus Neteler]

Hi Ken,

On Thu, Feb 10, 2022 at 1:16 AM Ken Mankoff  wrote:
>
> Hi Markus,
>
> Yes - that works but requires downstream hacks because of the different 
> resolutions.

Of course those could be scripted as well using eval():

eval `g.region -g`
# or:
#  eval $(g.region -g)
echo $n $w $e $s

> Still, it is a workable solution I didn't think of. Thank you!

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

Re: [GRASS-user] hexagon rasters

[Markus Neteler]

Hi Ken,

On Tue, Feb 8, 2022 at 4:44 AM Ken Mankoff  wrote:
>
> Hello List,
>
> I'm interested in working with hexagonal rasters. I know I can make hexagon 
> vectors with "v.mkgrid -h",
> but is there any way to then work with these in raster space? I'd like to use 
> r.walk and r.cost to estimate
> costs to move around the hex grid.

I am sure you considered v.to.rast?

# North Carolina sample dataset
g.region raster=elevation res=5000 -pa

# create vector hexagons
v.mkgrid map=hexagons -h
v.info -c hexagons

# convert to raster model, requires the resolution to be increased
(example: 5000m -> 250m)
g.region res=250 -p
v.to.rast input=hexagons output=hexagons use=cat

# viz
d.rast hexagons
d.vect hexagons type=boundary

Now you may turn them into cost surfaces.

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

Re: [GRASS-user] grass command to subset the columns of a vector

[Markus Neteler]

Hi Bernardo,

On Wed, Feb 9, 2022 at 1:39 AM Bernardo Santos via grass-user
 wrote:
>
> Dear list,
>
> Is there a GRASS GIS command (maybe a v.db.* one) to subset, in a single 
> command, the columns of a vector?
>
> What I have: vector "vect" with 5 columns "a, b, c, d, e" in the attribute 
> table
> What I want: vector "vect_sub" with only, for instance, "a, c, e"
>
> I can use v.extract to subsample rows, but not columns. What is the easiest 
> way of doing that, what needing many commands (like creating or copying the 
> vector to a new one, creating a new attribute table, then copying only the 
> columns I want).

Isn't this simply

https://grass.osgeo.org/grass80/manuals/vector.html
--> v.db.dropcolumn - Drops a column from the attribute table
connected to a given vector map.
--> It offers single and multiple column dropping: columns=name[,name,...]

> I looked for that in the documentation but did not found it so easily.

Please suggest where to improve the documentation.

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

[GRASS-user] Fwd: [OSGeo-Discuss] OSGeo at FOSDEM 2022 (Online) - join us in the geospatial devroom an Sunday February 6th 2022

[Markus Neteler]

Up and running now!

Join the video stream at
https://live.fosdem.org/watch/dgeospatial

GRASS GIS will be on stage as well:
   Spatial query of coordinate reference systems and its integration
with GRASS GIS (Huidae Cho)

Best,
Markus

-- Forwarded message -
From: Astrid Emde (OSGeo) via Discuss 
Date: Sun, Jan 30, 2022 at 1:25 PM
Subject: [OSGeo-Discuss] OSGeo at FOSDEM 2022 (Online) - join us in
the geospatial devroom an Sunday February 6th 2022
To: Discuss , Announce 


Event page:
https://www.osgeo.org/events/geospatial-devroom-at-fosdem-2022-online/

Due to the pandemic FOSDEM 2022 will be an online event like in 2021. We
will have a geospatial devroom again and are pleased to invite you to
join us there. No registration is necessary.

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

FOSDEM  geospatial devroom
-
Sunday 6. February 2022 10:30 - 14:05+
https://fosdem.org/2022/schedule/room/dgeospatial/

- Introducing a new JS+WebGL map library or «why neither Leaflet,
  OpenLayers nor MapLibreGL meet my needs» (Iván Sánchez Ortega)
- Explore OSM data with ARLAS Get instant geo-analytic view of billions
  OSM data entries (Mohamed Hamou)
- Open Geodata Digital Spaces Exploring the digital spaces of
  OpenStreetMap (Muhammad Saleem)
- Fast, robust predicates for geometric algorithms A C++ metaprogramming
  implementation of fast, robust floating-point arithmetics for geometric
  predicates (Tinko Sebastian Bartels)
- A Better Public Transport App (Ilya Zverev)
- Spatial query of coordinate reference systems and its integration with
  GRASS GIS (Huidae Cho)

FOSDEM 2022 schedule
-
See the schedule to find out about the program in the other rooms:
https://fosdem.org/2022/schedule/

How to join the Geospatial devroom?

You find information about how to join here:
https://fosdem.org/2022/practical/


About the Open Source Geospatial Foundation
--
The Open Source Geospatial Foundation is a not-for-profit 501(c)(4)
organization to empower everyone with open source geospatial. The
software foundation directly supports projects serving as an outreach
and advocacy organization providing financial, organizational and legal
support for the open source geospatial community.

OSGeo works with GeoCat, OPENGIS.ch, Gaia3D, Astun Technology and other
sponsors, along with our partners to foster an open approach to
software, standards, data and education.

Open Source Geospatial Foundation
https://www.osgeo.org/

See you at FOSDEM 2022
___
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 GIS 8.0.0 released

[Markus Neteler]

GRASS GIS 8.0.0 released

Overview of changes

After more than 3 year of development the *first stable release GRASS GIS
8.0.0* is available. Efforts have concentrated on making the user
experience even better, providing many new useful additional
functionalities to modules and further improving the graphical user
interface.

*Breaking news: new graphical user interface with entirely rewritten
startup sequence!*

This re-establishes user experience compatibility with QGIS and other
connected software packages.

The GRASS GIS 8.0.0 release provides more than 1,400 fixes and improvements
 with respect to the
release 7.8.6.

With the introduction of the semantic label raster metadata class, the
temporal database was modified to version 3. Hence, to be able to read and
process GRASS 7.x space-time datasets, users will be prompted to run
t.upgrade. If users want to read newly created space-time datasets back in
GRASS 7.x, they can run t.downgrade.
Launching the software

The user experience of the graphical user interface has been completely
rewritten: no more clumsy selection screens - just enter the menu system
directly!

And on command line, GRASS GIS now starts versionless, i.e. as grass.

*Downloads*

   - Source code (zip)
    | Source
   code (tar.gz)
   
   - https://grass.osgeo.org/grass80/source
   - Binaries: https://grass.osgeo.org/download/

Visit the release page 
for detailed release notes.
*Thanks to all contributors!*
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] "double free or corruption" when calling e.g. g.version, g.list, g.region

[Markus Neteler]

Hi Maximilian,

On Fri, Jan 21, 2022 at 12:03 PM Maximilian Stahlberg
 wrote:
>
> Hello,
>
> I'm using GRASS 7.8.6 on openSUSE Leap 15.2 and experience the
> following crashes:
>
> > Welcome to GRASS GIS 7.8.6
> > GRASS GIS homepage:  https://grass.osgeo.org
> > This version running through:Z Shell (/bin/zsh)
> >   [...]
> > GRASS 7.8.6 : ~ > g.version
> > GRASS 7.8.6 (2021)
> > *** Error in `g.version': double free or corruption (out): 
> > 0x55866fc655b0 ***
> > [1]9995 abort (core dumped)  g.version
> > GRASS 7.8.6 : ~ > g.list
> > Lists available GRASS data base files of the user-specified data type 
> > optionally using the search pattern.
> >   [...]
> > *** Error in `g.list': double free or corruption (out): 0x55a24a9f75b0 
> > ***
> > [1]1 abort (core dumped)  g.list
>
> Some other tools like g.gisenv work and GRASS used to work fully in the
> past (using, potentially, older versions of GRASS and SUSE).

The (only?) way is to use a debugger. This isn't too difficult, see

https://grasswiki.osgeo.org/wiki/GRASS_Debugging#Using_GDB

In any case, the error is quite unusual and may be caused by some
library conflict on your system.

...
> > *** Error in `g.version': double free or corruption (out): 
> > 0x5588157c15b0 ***

You may start with `g.version -rge` and the debugger. I suppose that
all errors you see originate from the same problem.

Best,
Markus
___
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?

[Markus Neteler]

On Fri, Jan 21, 2022 at 12:04 PM Markus Neteler  wrote:
> On Fri, Jan 21, 2022 at 4:58 AM Eric Patton via grass-user
> > Nevermind, I see that I had to git clone the main branch.
>
> This reminded me of the fact that this directory isn't populated yet:
> https://grass.osgeo.org/grass81/source/

done:
... this folder now contains the GRASS GIS 8.1.dev source code
snapshot, the new cronjob is up & running to generate it weekly.

Markus

-- 
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

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

[Markus Neteler]

On Fri, Jan 21, 2022 at 4:58 AM Eric Patton via grass-user
 wrote:
>
> Nevermind, I see that I had to git clone the main branch.

This reminded me of the fact that this directory isn't populated yet:
https://grass.osgeo.org/grass81/source/

I have now created a new cronjob, once approved, GRASS GIS 8.devel
(currently 8.1.dev) will be generated:
https://github.com/OSGeo/grass-addons/pull/682

Coming soon!

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

[GRASS-user] GRASS GIS 7.8.7RC1 released

[Markus Neteler]

*GRASS GIS 7.8.7RC1 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.7RC1.tar.gz
   - https://grass.osgeo.org/grass78/source/grass-7.8.7RC1.md5sum

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

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

The GRASS GIS 7.8.7 release provides more than 40 fixes and improvements
 with respect to
the release 7.8.6.
What's ChangedSee
https://github.com/OSGeo/grass/releases/tag/7.8.7RC1

*Full Changelog*: 7.8.6...7.8.7RC1

—

This release has 2 assets:

   - Source code (zip)
   - Source code (tar.gz)

Visit the release page
 to download them.

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

Re: [GRASS-user] r.fillnulls hang on one computer, not on another

[Markus Neteler]

Hi Ken,

On Tue, Jan 18, 2022 at 9:23 PM Ken Mankoff  wrote:
>
> Hello,
>
> I'm trying to run 'r.fillnulls' and it hangs on one computer but not on 
> another.
>
> On my laptop running Ubuntu 20.04 it runs fine in GRASS 7.8.6. It also runs 
> in a docker container running GRASS 7.8.4.
>
> On our server it just hangs. This is running Ubuntu 18.04 and grass 7.8.2. It 
> also hangs running *the same docker image* Ubuntu 20.04 GRASS 7.8.4
>
> Do you have any suggestions how to debug this?

You can find out the process ID (the columns are
USER PID %CPU %MEM ...
so that it is the number after the user name):

ps aux | grep r.fillnulls

and then run strace on it

strace -p 

The result may be hard to read yet give some insights if it is waiting
for something (e.g., a device) on that machine.

Markus

> Examining it with top sows it is churning away with 100 % CPU usage. It takes 
> ~5 minutes on my laptop then completes. It never completes on the server 
> (which is much more powerful - it should complete faster).
>
> Thank you,
>
>   -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] GRASS-Wiki system upgrade testing - please help

[Markus Neteler]

On Sat, Jan 15, 2022 at 11:44 AM Markus Neteler  wrote:
> On Fri, Jan 7, 2022 at 11:06 AM Markus Neteler  wrote:
> >
> > Dear all,
> >
> > At time Regina from OSGeo-SAC (system administration committee)
> > updates the old GRASS-Wiki system to a fresh Virtual Machine (VM) +
> > fresh Mediawiki.
> >
> > Temporarily this machine is accessible here (the content has been
> > synced some days ago, so latest "real" changes are not visible here):
> > https://staging.grasswiki.osgeo.org/wiki/
> >
> > Wish: please check if all is functioning including macros, images, etc.
>
> Apparently nothing missing - so I'll ask Regina to sync once more and
> switch the servers.

Done - now the GRASS GIS Wiki is a fresh new VM:
https://grasswiki.osgeo.org/wiki/

Thanks to Regina for the migration!

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

[GRASS-user] GRASS GIS 8.0.0RC2 released

[Markus Neteler]

GRASS GIS 8.0.0RC2 releasedOverview of changes

After more than 3 year of development the *first stable release GRASS GIS
8.0.0* is available. Efforts have concentrated on making the user
experience even better, providing many new useful additional
functionalities to modules and further improving the graphical user
interface.

*Breaking news: new graphical user interface with entirely rewritten
startup sequence!*

This re-establishes user experience compatibility with QGIS and other
connected software packages.

The GRASS GIS 8.0.0 release provides more than 1,300 fixes and improvements
 with respect to
the release 7.8.6.

With the introduction of the semantic label raster metadata class, the
temporal database was modified to version 3. Hence, to be able to read and
process GRASS 7.x space-time datasets, users will be prompted to run
t.upgrade. If users want to read newly created space-time datasets back in
GRASS 7.x, they can run t.downgrade.
Release details

https://github.com/OSGeo/grass/releases/tag/8.0.0RC2
Launching the software

The user experience of the graphical user interface has been completely
rewritten: no more clumsy selection screens - just enter the menu system
directly!

And on command line, GRASS GIS now starts versionless, i.e. as grass.
Assets

   - Source code (zip)
   
   - Source code (tar.gz)
   
   - https://grass.osgeo.org/grass80/source/

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

Re: [GRASS-user] GRASS-Wiki system upgrade testing - please help

[Markus Neteler]

Hi,

On Fri, Jan 7, 2022 at 11:06 AM Markus Neteler  wrote:
>
> Dear all,
>
> At time Regina from OSGeo-SAC (system administration committee)
> updates the old GRASS-Wiki system to a fresh Virtual Machine (VM) +
> fresh Mediawiki.
>
> Temporarily this machine is accessible here (the content has been
> synced some days ago, so latest "real" changes are not visible here):
> https://staging.grasswiki.osgeo.org/wiki/
>
> Wish: please check if all is functioning including macros, images, etc.

Apparently nothing missing - so I'll ask Regina to sync once more and
switch the servers.

Markus

> If you should identify any error, please comment here:
> https://trac.osgeo.org/osgeo/ticket/2533
>
> Once confirmed that all is fine Regina will do a final sync and
> activate this new VM and replace the old instance running at
> https://grasswiki.osgeo.org/wiki/
>
> Please check the new "staging" deployment,
> thanks
> Markus
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] GRASS-Wiki system upgrade testing - please help

[Markus Neteler]

Dear all,

At time Regina from OSGeo-SAC (system administration committee)
updates the old GRASS-Wiki system to a fresh Virtual Machine (VM) +
fresh Mediawiki.

Temporarily this machine is accessible here (the content has been
synced some days ago, so latest "real" changes are not visible here):
https://staging.grasswiki.osgeo.org/wiki/

Wish: please check if all is functioning including macros, images, etc.

If you should identify any error, please comment here:
https://trac.osgeo.org/osgeo/ticket/2533

Once confirmed that all is fine Regina will do a final sync and
activate this new VM and replace the old instance running at
https://grasswiki.osgeo.org/wiki/

Please check the new "staging" deployment,
thanks
Markus

-- 
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

Re: [GRASS-user] r.le.pixel addons not found

[Markus Neteler]

Hi Enrico,

On Sat, Dec 25, 2021 at 9:44 PM bonushenricus  wrote:
>
> Hello
> and happy holidays!
> (I'm in quarantine for having a lunch where a person found out the next
> day they were COVID positive and so I'm spending the holidays studying
> and working!)
> GRASS 7.8.5 under Debian 11
> 
> points to a wrong URL
> 'https://github.com/OSGeo/grass-
> addons / trunk / grass7 / raster / r.le.pixel '
> the correct url is without "trunk" and with "/ tree / master"

Please update to GRASS GIS 7.8.6:
https://trac.osgeo.org/grass/wiki/Release/7.8.6-News#Majormodulechanges

--> g.extension: updated to match new addon repository structure (PR:1762)

> P.S.: I know that "r.le" has been replaced by "r.li"
> but I wanted to see how it worked, I understand that such a thing
> "r.le.pixel map = ... string = w att = b4 t1 = m7 te2 = t5"
> is not possible with "r.li", where the closest form could be
> "r.li.cwed" (where, however, I don't understand what "path =" refers
> to,

It is the path a weights  CSV file, see
https://grass.osgeo.org/grass78/manuals/r.li.cwed.html

> but now I try to study a lot: in the meantime I have several days ,
> hoping that how he seems to continue to feel good!)

Please report your findings (and suggestions how to improve the
documentation are welcome!).

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

Re: [GRASS-user] Inquiry about GRASS GIS Windows Binary Stand-Alone Build Configuration

[Markus Neteler]

Hi,

On Fri, Dec 17, 2021 at 9:27 PM Synper311 via grass-user
 wrote:
>
> Hi,
>
> Just writing to inquire if the GRASS GIS Windows Binary Stand-Alone Builds 
> are using the –with-openmp Build Configuration flag to enable multithreading 
> across all applicable modules.

(see the email by Helmut)

> Tangential to this question is whether or not it is expected that r.contour 
> will use N-Number of threads when processing
> on a system with greater than 4 threads. This question arises as it was 
> observed to only use 4 threads on a Ryzen
> machine with 24+ threads.

To my knowledge these commands have openMP support so far:

r.proj
r.series.accumulate
r.sim.sediment
r.sim.water
r.sun
v.surf.rst

and several more are in the pipeline:

https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aopen+openMP

> For a bit more context, this all relates to the usage of the Binary GRASS GIS 
> files being used within the context of generating contours within WebODM 
> (OpenDroneMap).

Would be nice to see r.contour to be the next candidate!

Alternative solution (say, an idea) for now:

- r.tile the data into chunks (perhaps with small overlap, not sure if
needed or useful)
- run r.contour on the tiles, in parallel (SLURM, gnu-parallel, something else)
- v.patch the resulting vector maps
- v.build.polylines to generate polylines from lines

Best,
Markus
___
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

[Markus Neteler]

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.

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

r.import input=ocd_0_5cm_mean_epsg4326.tif output=ocd_0_5cm_mean extent=region
r.colors ocd_0_5cm_mean color=bgyr

HTH,
Markus
___
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

[Markus Neteler]

Hi Frank,

On Thu, Nov 18, 2021 at 2:54 PM Frank David  wrote:
>
> Hi Vero,
>
> Thanks for your reply.
>
> Shall I do "Make distclean" from the folder where I have built grass7.9 ?
>
> I get :
>
> sudo make distclean
> include/Make/Vars.make:1: include/Make/Platform.make: Aucun fichier ou 
> dossier de ce type
> make: *** Aucune règle pour fabriquer la cible « include/Make/Platform.make 
> ». Arrêt.
>
> Something seems wrong ??

Same here, something I didn't fully understand yet. Trivial
workaround, after "make distclean":

touch include/Make/Platform.make

>
> For the moment I prefer to keep on 7.9, but if I can't manage to repair 7.9 I 
> will go to 8.0.

Let me highly recommend 8...

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

Re: [GRASS-user] grass gis equivalent of st_subdivide

[Markus Neteler]

Hi,

Moritz Lennert  schrieb am Do., 14. Okt.
2021, 02:28:

> Hi HB,
>
> Le 13 octobre 2021 22:57:21 GMT+01:00, B H  a
> écrit :
> >Hi,
> >How do I divide an area into smaller areas ( I am looking for
> functionality
> >of st_subdivide in postgis).
> >I need to  split some big areas into smaller ones (and all smaller ones
> >should have the same attributes).
> >I understand that it means that underlying topology would change( It would
> >add more boundaries).
> >
> >When v.in.ogr imports a shapefile in Grass GIS, it automatically splits
> the
> >overlapping areas to make them topologically correct, so I am hoping that
> >there is already some way to just split a topologically valid area as
> >well...
>
>
> I don't think that there is any readymade module for this. You could just
> create a fixed grid with v.mkgrid and v.overlay it with something like this:
>
> v.overlay ain=orig bin=grid out=subdivided operator=and olayer=0,1,0
>


Another option to try may be this one:

https://grass.osgeo.org/grass-stable/manuals/v.voronoi.html#skeletons-and-center-lines-of-areas

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

Re: [GRASS-user] city gis data

[Markus Neteler]

Hi Janet,

On Tue, Oct 5, 2021 at 8:36 PM Janet Choate  wrote:
>
> Hi -
> This may seem a ridiculous question -

(it is not)

> Can anyone tell me where I can obtain simple city boundary gis data?
> I need city boundary gis data for cities in Santa Barbara County that I can 
> download and import into GRASS.
> thank you,
> Janet

You can fetch admin boundaries from OpenStreetMap here:

https://osm-boundaries.com/

(click on the small triangles to expand the list)

--> United States
 --> California
   --> [x] Santa Barbara County

etc.

HTH,
Markus

-- 
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

Re: [GRASS-user] r.vol.dem error on Windows

[Markus Neteler]

Hi,

Tünde Tóth  schrieb am Fr., 23. Juli 2021, 11:34:

> Dear Grass users,
>
> I'would like to create a 3D voxel from my geological surfaces with
> r.vol.dem modul.
> I use the Windows version of GRASS.
> The checking and interpolation section work, but could not create the
> voxeltmp.tmp file.
> Have you any idea to solve this problem?
>

I suppose that Windows dislikes the plain definition of TMPFILE without
path:

https://github.com/OSGeo/grass-addons/blob/5775eb7806a36aa8d00dbf6e1603f3e1a197c5ca/grass7/raster/r.vol.dem/globals.h#L20

The common temp file mechanism isn't used here (yet)...

Best
Markus


Thank you
> Tunde
>
>
> "C:\>r.vol.dem -f --overwrite input=Battonya_Base_Shift_fl@tifek
> ,Battonya_Rift_initiation_Shift_fl@tifek
> ,Battonya_Rift_climax_Shift_fl@tifek,Battonya_Base_slope_Shift_fl@tifek
> ,Battonya_Top_slope_Shift_fl@tifek,Battonya_srtm_Shift_fl@tifek
> output=proba@tifek algorithm=down
> Validating data:
>  Z-range checking, pass 1:
>  100%
>  z-range-checking, pass 2:
>  100%
>  Checking DEM topologies:
>  100%
>
> Interpolating:
>  100%
>
> ERROR: Could not create temporary file for writing ASCII output
>(voxeltmp.tmp)"
> ___
> 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] Advice on importing V5 data sets?

[Markus Neteler]

Hi,

On Thu, Jun 24, 2021 at 10:06 AM brendon wolff-piggott
 wrote:
>
> Sorry, thought I had answered yesterday. It is both vector and raster. 
> Created in GRASS 5.1 (not sure of .x number).

I finally found back this page and updated the links therein:

https://grasswiki.osgeo.org/wiki/Upgrading_GRASS_database

It contains:
Upgrading the GRASS database from older to recent GRASS versions
1.1 Migrating from GRASS 4 to GRASS 5
1.2 Migrating from GRASS 4 to GRASS 6
1.3 Migrating from GRASS 5 to GRASS 6
1.4 Migrating from GRASS 6 to GRASS 7

> I would like to import the data into PostGIS, so I can access it in GRASS or 
> QGIS.

That should be doable, since conversion tools are included.

> I have quite a lot of the original shape files that I could import again, but 
> not the raster data and DEMs created from it.

I would expect that the raster maps from GRASS GIS 5 can be opened in
any later version without problems.
If not, please send the error message.

Markus

-- 
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

Re: [GRASS-user] Advice on importing V5 data sets?

[Markus Neteler]

On Tue, Jun 22, 2021 at 4:33 PM brendon wolff-piggott
 wrote:
>
> Is there a conversion utility, guide or other resource for importing old data 
> to V7.8? This is over 50GB of data and I need to recover it.

Is it raster or vector data, or both?

> I've tried viewing it in QGIS desktop and opening the mapset in V7.8 but the 
> data simply isn't recognised at all. Googling hasn't helped.

Please describe a bit more what you try to achieve: Your "old data"
have been generated in which GRASS GIS version?

Markus

-- 
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] Fwd: [Projects] OSGeo6 will have a dist upgrade today

[Markus Neteler]

FYI - periods of outage with mailing lists ahead...

-- Forwarded message -
From: Regina Obe 
Date: Fri, Jun 18, 2021 at 5:13 PM
Subject: [Projects] OSGeo6 will have a dist upgrade today
To: , , System
Administration Committee Discussion/OSGeo 

I plan to upgrade OSGeo6 from Jessie to Stretch later tonight.
While this is happening, there may be periods of outage with mailing lists
and osgeo mail.

I'll send a note just before I start the process and after I am done.

That said, since OSGeo6 holds our mailing lists and is our mail server, I
will not be able to email with any issues during the process.

Any such issues will be announced in OSGeo and OSGeo SAC  irc libera
channels (matrix bridges).
I will also announce completion in these channels in addition to the mailing
lists

Thanks,
Regina
SAC Team member

___
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] bayesian belief network analysis (was r.binfer)

[Markus Neteler]

On Sat, May 29, 2021 at 4:20 AM Donovan Cameron  wrote:
>
> Evening,
>
> I'm attempting to analyze a set of layers (slope, aspect, vegetation,
> soil, etc) that have been coded/scored based on expert opinion to output
> a probability/suitability map.
>
> I'm looking to apply a bayesian belief network [1] and i've got the
> raster layers ready for the inputs and coded like seen in this figure [2].
>
> There was a grass4 module called r.binfer [3] that did this and I can't
> seem to find it with GRASS 78 - deprecated or replaced?

The latest code trace which I could find is this one:

GRASS GIS 5.5:
https://github.com/OSGeo/grass-legacy/tree/releasebranch_5_5/src/raster/r.binfer

I do not recall why the module has been abandoned in GRASS GIS 6
(maybe no particular reason and a volunteer could update it...?).

Another option might be to rely on R and use "rgrass7" to exchange
data between GRASS GIS and R.

Best,
Markus

> Searches lead me to either r.regression.multi [4] or r.learn.ml [5] but
> i'm not sure where to start with these to get a BBN processed thru them.
>
>
> SaultDon
>
> [1] https://www.gislounge.com/gis-bayesian-belief-networks/
> [2]
> https://www.sciencedirect.com/science/article/pii/S0169204618307497#f0010
> [3] https://grass.osgeo.org/grass43/manuals/html_grass4/html/r.binfer.html
> [4] https://grass.osgeo.org/grass78/manuals/r.regression.multi.html
> [5] https://grass.osgeo.org/grass78/manuals/addons/r.learn.ml.html
> ___
> 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

Re: [GRASS-user] v.select disjoint operation. Grass 7.8.2

[Markus Neteler]

Hi Chris,

On Thu, May 20, 2021 at 2:00 PM Christopher Lloyd
 wrote:
>
> Hi Markus, Having split my input data into smaller sized shp files, these now 
> process fine using v.select. So clearly the problem that I had lies with some 
> file size limitation with the v.select 'disjoint' algorithm - also failing 
> with one input file prior using the v.extract algorithm. The original (large) 
> input files input to grass ok using v.in.ogr,

The vector limit is as follows:

https://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance#Large_vector_data_processing
--> In all GRASS versions, the limit with topology is at time 2^31 - 1
(about 2 billion) features per vector map.

> but then failed when using v.select. Might you be able to indicate the file 
> size limitation for the v.select algorithm and the reasons for this? Thanks.

This said, perhaps v.select lacks a proper declaration?

Could you tell us how many vector features per map you are dealing
with (say: those which work and those which fail)?

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