Re: [GRASS-user] Status of ITZI in GRASS?

[Markus Neteler via grass-user]

Hi Venka,

On Tue, Sep 3, 2024 at 6:38 AM Venka  wrote:
>
> Hi Thomas,
>
> Some progress here in building a docker image with GRASS and itzi.
> First of all, Thanks to Gérald and Markus for helping out with
> this.
>
> My experiment was done using Ubuntu_22.04 machine

[...]

> P.S. Could be useful if grass_with_itzi image is made available on
> https://grass.osgeo.org/download/docker/

What about adding a new "docker" subdirectory to
https://github.com/OSGeo/grass-addons/ and host user-contributed
Dockerfiles there (maybe even with setting up of the continuous
integration for auto-generating the docker images from that)?

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

Re: [GRASS-user] About grass-gis:main-ubuntu_wxgui docker

[Markus Neteler via grass-user]

Hi Venka,

On Sat, Aug 31, 2024 at 1:28 AM Venka via grass-user
 wrote:
>
> Hi All,
>
> I build my docker image using main-ubuntu_wxgui [1] as the base.
> I need to have the GRASS GUI working in my docker container.
>
> After successfully building my docker image and running the
> docker image, GRASS starts only in text mode. I was expecting
> that it would start in GUI mode.
>
> When I run the command "grass --gui" in the docker bash shell,
> I get a message
>
> "Launching  GUI in the background, please wait.."
> and the GRASS GUI never starts up.
>
> I can only use GRASS in CLI mode inside the docker.
>
> Any suggestion to get the GRASS GIS running in docker?

Two suggestions:
- I just submitted a bugfix (say, two) in this pull request (PR):
   https://github.com/OSGeo/grass/pull/4268
- to run it, be sure to redirect the display. E.g. (also works nicely
with podman):

docker run -it --rm --volume="$(pwd)/:/data"
--volume="/tmp/.X11-unix:/tmp/.X11-unix:rw" \
--env DISPLAY=$DISPLAY
--device="/dev/dri/card0:/dev/dri/card0" some_hash_or_image_name \
grass --gui

Once the PR above is accepted and merged, the updated docker image
should be generated and available to you.

Best,
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] i.sentinel add-on incomplete in WinGrass 8.4?

[Markus Neteler via grass-user]

Hi again,

On Tue, Aug 27, 2024 at 10:07 AM Markus Neteler  wrote:
>
> Hi Vishal,
> (cc Martin who maintains the wingrass server)
...

Update from Martin, who is currently traveling:

Addons for GRASS GIS 8.4.0 are OK:
https://wingrass.fsv.cvut.cz/grass84/addons/grass-8.4.0/

(so, please get the ZIP file from there for these days, he's check
8.4.dev addons once back)

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

Re: [GRASS-user] i.sentinel add-on incomplete in WinGrass 8.4?

[Markus Neteler via grass-user]

Hi Vishal,
(cc Martin who maintains the wingrass server)

Good catch.

On Tue, Aug 27, 2024 at 4:10 AM Vishal Mehta via grass-user
 wrote:
>
> Hi,
>
> I wanted to try out the sentinel toolset, trying to follow :
> https://training.gismentors.eu/grass-gis-workshop-jena/units/20.html
>
> However, the i.sentinel extension seems to be missing i.sentinel.coverage:
> https://wingrass.fsv.cvut.cz/grass84/addons/grass-8.4.0/
>
> Any idea if that can be added?

There seems to be some issue on the wingrass server:

https://grass.osgeo.org/grass84/manuals/addons/
--> Windows log files

Basically all jobs fail with:

Traceback (most recent call last):
  File 
"C:\Users\landamar\grass_packager\grass84\addons\db.join\scripts\db.join.py",
line 64, in 
import grass.script as grass
ModuleNotFoundError: No module named 'grass'

Needs to be investigated on the server (I don't have access) by Martin.

Best
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] Is ther a quick way to install grass8.3.2 in Ubuntu Jammy?

[Markus Neteler via grass-user]

Hi Amedeo,

On Sun, Aug 4, 2024 at 12:13 PM Amedeo Fadini AF via grass-user
 wrote:
...
> Well It will be a good choice to learn using GRASS GIS from CLI :-)

and in addition, you can use the nice improved GRASS GIS GUI.
See here how it looks like:

https://grass.osgeo.org/learn/gallery/#user-interface
--> Click: View more

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

[GRASS-user] GRASS GIS 8.4.0 released

[Markus Neteler via grass-user]

The GRASS GIS 8.4.0 release provides more than 520 improvements and fixes
with respect to the release 8.3.2. Highlights

   - *location* becomes *project*: The Python API, command line, and
   graphical user interface are now using *project* instead of *location*
   for the main component of the data hiearchy while maintaining backward
   compatibility.
   - v.fill.holes: New tool to remove inner isles and to keep outer
   boundary only
   - i.svm: New support vector machine image classification (SVM)
   - r.horizon: Output for multiple points, distances, and many other
   improvements
   - r.univar: Parallelization computation extended statistics
   - JSON output format support (format="json") in multiple tools (e.g.,
   r.report, r.info, v.db.select, t.rast.list, etc.)
   - New *grass.jupyter.SeriesMap* class for animating series of vectors or
   rasters
   - ipyleaflet integration for *grass.jupyter* to create a map in
   ipyleaflet and add GRASS data in a single line
   - Greatly simplified the creation of new projects in Python (no more
   chicken and egg problems) - also in Jupyter notebooks
   - GUI: New easy command history navigation through the History browser
   panel browser panel (details
   

   )
   - GUI: Further improvements of new single-window GUI with undockable map
   display window, for a smoother user experience
   - New GRASS GIS Programming Style Guide
   

New Addon Tools

   - i.eodag
   :
   Downloads imagery datasets from various providers through the EODAG API.
   - r.flowaccumulation
   
:
   Calculates flow accumulation from a flow direction raster map using the
   Memory-Efficient Flow Accumulation (MEFA) parallel algorithm by Cho (2023).
   - r.fusion
   :
   image fusion, generalized pan-sharpening.
  - This work was funded by mundialis GmbH & Co. KG
  
   - r.windfetch: addon for computing wind fetch.
   - r.maxent.train
   
   & r.maxent.predict
   :
   train, and predict a Maxent model to create a suitability distribution
   layer.

For further details, see

   - https://grass.osgeo.org/news/2024_07_27_grass_gis_8_4_0_released
   - https://grass.osgeo.org/download/
   - https://github.com/OSGeo/grass/releases/tag/8.4.0

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.resamp.bspline vs. v.surf.bspline

[Markus Neteler via grass-user]

Hi Victor,

On Tue, Jun 18, 2024 at 7:07 AM Victor Lundström via grass-user
 wrote:
>
> Hi everyone,
>
> I'm trying to interpolate a, for my machine, fairly large raster of 
> 340,779,478 cells with 246x246 meter resolution.
> The way I've gone about it before has been to first use r.random, sample 100% 
> of the cells and then use v.surf.bspline for
> interpolation. This always works on smaller data sets, but with this large 
> one, I repeatedly only get a point layer that
> doesn't include the column with the values that should be interpolated.

This part I don't fully get yet: which column do you expect? In the
end, you can only use what's generated by r.random (unless you do
further steps not described above).

> Not sure if I'm missing a step or two in r.random, or
> if it's a size thing. Since my attempts repeatedly fail, I started looking at 
> using r.resamp.bspline instead, as it only requires for
> me to load the input raster and, just like v.surf.bspline, r.resamp.bspline 
> is said to also perform "bicubic or bilinear spline interpolation
> with Tykhonov regularization".
>
> Should I expect a different result from using just r.resamp.bspline as 
> opposed to my r.random -> v.surf.bspline? Seeing as it is found
> under the "resamp" modules?
>
> I hope I can get some clarification on this!

Looking at the methods:

A) r.random + v.surf.bspline:
- r.random: This tool samples the raster cells at random. If you
sample 100% of the cells, you are essentially converting the raster to
points. Wouldn't r.to.vect do that as well?
- v.surf.bspline: This tool interpolates a raster surface from the
point data using B-spline interpolation.

Pros:
- Allows for selective sampling if needed.
- Can be used when you need to perform additional processing on the
point data before interpolation.

Cons:
- More complex workflow.
- May lead to issues with very large datasets, as you've experienced.

B) r.resamp.bspline:
- This tool directly performs bicubic or bilinear spline interpolation
on the raster without needing to convert it to points.

Pros:
- Simpler and more direct workflow.
- Designed for resampling and interpolating large rasters.

Cons:
- Less flexibility in terms of intermediate data manipulation.

Some recommendations:
Given that you are dealing with a very large raster and have
encountered issues with the r.random and v.surf.bspline approach,
using r.resamp.bspline might be more efficient and reliable. This tool
is designed specifically for resampling and should handle large
datasets better.

Expected Results
- Performance: r.resamp.bspline should handle large raster maps more
efficiently.
- Accuracy: Both methods use spline interpolation, so the results
should be similar in terms of interpolation quality.
- Simplicity: r.resamp.bspline offers a more straightforward process
without the intermediate steps.

Switching to r.resamp.bspline might be a practical approach here.

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

[GRASS-user] GRASS GIS 8.4.0RC1 release

[Markus Neteler via grass-user]

GRASS GIS 8.4.0RC1 release

The GRASS GIS 8.4.0RC1 release provides more than 515 improvements and
fixes with respect to the release 8.3.2.

Please support us in testing this release candidate.
Highlights

   - *location* becomes *project*: The Python API, command line, and
   graphical user interface are now using *project* instead of *location*
   for the main component of the data hiearchy while maintaining backward
   compatibility.
   - v.fill.holes: New tool to remove inner isles and to keep outer
   boundary only
   - i.svm: New support vector machine image classification (SVM)
   - r.horizon: Output for multiple points, distances, and many other
   improvements
  - This work was funded was developed with funding from NSF Award
  #2322073 ,
  granted to Natrx, Inc. 
   - r.univar: Parallelization computation extended statistics
   - JSON output format support (format="json") in multiple tools (e.g.,
   r.report, r.info, v.db.select, t.rast.list, etc.)
   - New *grass.jupyter.SeriesMap* class for animating series of vectors or
   rasters
   - ipyleaflet integration for *grass.jupyter* to create a map in
   ipyleaflet and add GRASS data in a single line
   - Greatly simplified the creation of new projects in Python (no more
   chicken and egg problems) - also in Jupyter notebooks
  - This work was funded was developed with funding from NSF Award
  #2322073 ,
  granted to Natrx, Inc. 
   - GUI: New easy command history navigation through the History browser
   panel browser panel (details
   

   )
   - GUI: Further improvements of new single-window GUI with undockable map
   display window, for a smoother user experience
   - New GRASS GIS Programming Style Guide
   

New Addon Tools

   - i.eodag
   :
   Downloads imagery datasets from various providers through the EODAG API.
   - r.flowaccumulation
   
:
   Calculates flow accumulation from a flow direction raster map using the
   Memory-Efficient Flow Accumulation (MEFA) parallel algorithm by Cho (2023).
   - r.fusion
   :
   image fusion, generalized pan-sharpening.
  - This work was funded by mundialis GmbH & Co. KG
  
   - r.windfetch: addon for computing wind fetch.
   - r.maxent.train
   
   & r.maxent.predict
   :
   train, and predict a Maxent model to create a suitability distribution
   layer.

Monthly Financial Supporters

OpenPlains Inc. , Luis Bojórquez

What's ChangedSee https://github.com/OSGeo/grass/releases/tag/8.4.0RC1New
Contributors

   - Luís de Sousa (@ldesousa ) made their
   first contribution in #3006 
   - Alexandre Detiste (@a-detiste ) made
   their first contribution in #3076
   
   - Michael Barton (@cmbarton ) made their
   first contribution in #3279 
   - Alessandro Frigeri (@afrigeri ) made
   their first contribution in #3258
   
   - Florian Weimer (@fweimer-rh ) made
   their first contribution in #3325
   
   - Gregory Power (@gregorywaynepower
   ) made their first contribution in
   #3338 
   - Sharan Jamanani (@Sharansrj567 ) made
   their first contribution in #3356
   
   - @ymdatta  made their first contribution in
   #3247 
   - @Ntp9413  made their first contribution in
   #3444 
   - Jaden Abrams (@jadenabrams100 )
   made their first contribution in #3451
   
   - @VeronicaKoess  made their first
   contribution in #3311 
   - @naidneelttil  made their first
   contribution in #3469 

Re: [GRASS-user] Status of ITZI in GRASS?

[Markus Neteler via grass-user]

Hi,

FWIW, I was able to compile ITZI today on Fedora 39 (gcc version
13.3.1 20240522; Python 3.12.3), using

# install dependencies
pip install numpy setuptools cython

# generate some needed C files
cython -3 itzi/swmm/swmm_c.pyx itzi/flow.pyx

# build
python setup.py build

# install
python setup.py install --user

# test if it starts
itzi version
20.5

# pytest (see docs/prog_manual.rst)
pytest -v
[...]

Due to lack of time I could not continue yet.

Perhaps I can try these days during the
https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2024

Best
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] r.threshold not found in repository -- GRASS 7.8.6 ubuntu machine

[Markus Neteler via grass-user]

Hi,

On Mon, May 27, 2024 at 1:54 PM Micha Silver via grass-user
 wrote:
>
> (cc-ing the list also)
>
>
> I can confirm this problem. The `g.extension` module is looking at the
> wrong URL, it seems.


The solution would be a backport to older GRASS GIS versions of
https://github.com/OSGeo/grass/pull/2895 which replaces SVN checkout
(no longer supported by GitHub) with git sparse checkout.

best,
Markus


> $ g.extension r.traveltime
>
> Unable to connect to a repository at URL
> 'https://github.com/OSGeo/grass-addons/branches/grass8/src/raster/r.traveltime'
>
>
> Here is the correct source for the addon:
>
> https://github.com/OSGeo/grass-addons/tree/grass8/src/raster/r.traveltime
>
>
> I submitted an issue for this on github:
>
> https://github.com/OSGeo/grass-addons/issues/1089
>
>
> Regards,
>
> Micha
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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