Re: [GRASS-user] Announcing new command line interface of `grass` program in trunk

Great news ! thank you Vaclav for this new step in gis system integration : Shell one-liners surely will enjoy... Vincent Le mercredi 03 juin 2015 à 20:44 -0400, Vaclav Petras a écrit : Hi all, I'm happy to announce new command line interface of the `grass` program [1, 2] available in

[GRASS-user] v.external on a spatialite layer

Hi, Here is a grass6.4 (fresh build) related issue : in order to put some spatialite data within a project, I used the command v.external, which ran fine. When I try to show attribute table I get the following error message : Traceback (most recent call last): File

Re: [GRASS-user] grass6.4.6 on debian 8

Hello Markus, thank you for caring for my rather 'dated' question indeed! I keep a permanent update build of grass7 from svn, but do not (yet) use it for production purpose. Last time I tried to work on a project with it, I noticed the digiting tool was very unstable, where I had no problem with

Re: [GRASS-user] grass6.4.6 on debian 8

> I meant, is the menu in English or French? No, menus usually displayed in english. Things began to be on the blink after I upgraded my system -- python version jumped from 2.7.3 to 2.7.9. Could be a python-related issue... Anyway, as you half-suggested I'll take a leap in "seven", then

Re: [GRASS-user] grass6.4.6 on debian 8

Yes Vaclav, I will; I believe it's the very least one should do when using free software as professional set of tools... V. Le samedi 07 novembre 2015 à 12:55 -0500, Vaclav Petras a écrit : > > On Sat, Nov 7, 2015 at 9:32 AM, Vincent Bain <b...@toraval.fr> wrote: > Anyw

Re: [GRASS-user] v.external on a spatialite layer

Le samedi 07 novembre 2015 à 21:18 +0100, Markus Neteler a écrit : > > I compared > meld grass71/gui/wxpython/dbmgr/base.py grass64/gui/wxpython/dbmgr/manager.py > > but could not identify any obvious change which would fix the code > (but I am not quite familiar with the wxGUI internals). > >

[GRASS-user] grass6.4.6 on debian 8

Hi, Trying to install grass-6.4.6svn on a fresh debian jessie, I have no errors during compilation/installation. But when I launch grass64, no gui opens up, and I get the following error message on the terminal : Traceback (most recent call last):

[GRASS-user] exporting map display

Hello, is there a way to invoke d.out.file in order to export the current wx map display ? I would like to be able to generate a georeferenced view on the fly, i.e. a map composition containing vector overlay with transparency over a raster background. The button "save display to graphic file"

Re: [GRASS-user] exporting map display

Thanks you Anna, unfortunately I understand d.to.rast cannot handle the content of the gui default display frame, which is the only display that allows me to tweak transparency. My temporary fix was to : -"set computational region from display extent" ; -press the button "save display to graphic

Re: [GRASS-user] exporting map display

ng. > > On Wed, Sep 9, 2015 at 9:52 AM, Vincent Bain <b...@toraval.fr> wrote: > Thanks you Anna, > > unfortunately I understand d.to.rast cannot handle the content > of the > gui default display frame, which is the only display t

Re: [GRASS-user] workspace file issue

Hello Anna, this happens on a quite old 7.8 debian wheezy. I tested it on a 8.2 jessie, and the problem is the same. No matter which driver from png or cairo is used. Would the problem rather be located on the wxpython layer ? Don't know if it can help : wx-config --version 3.0.2 python

[GRASS-user] workspace file issue

Hello, setting up a workspace file on a fresh grass-7.1.svn, I noticed a display issue when loading it: the map display does not show the entire map, it is like cropped to the upper left 2/3, see this snapshot : http://www.toraval.fr/telec/snap.jpg Whatever I do (panning, zooming, refreshing)

Re: [GRASS-user] GRASS GIS on gis.stackexchange.com

Le mercredi 20 janvier 2016 à 21:57 +0100, Markus Neteler a écrit : > > You may upvote the logo now :-) > > http://meta.gis.stackexchange.com/a/4145/687 Hi, the sticker for stackexechange community promotion ads was updated with a "grassy world" background. Vincent

Re: [GRASS-user] Help with DEM, Raster and Vector export to VTK / Paraview

Hi David, (besides your latest private message, I post a reply on the mailing list) If I understand correctly, your concern is about extracting vector and raster data from GRASS in order to add them to a Google Earth 3d view (I'm not familiar with the latter, sorry). I guess my very rough addon

Re: [GRASS-user] Exporting RGB Composite Images to GeoTIFF

Le jeudi 21 juillet 2016 à 16:27 +0200, Markus Neteler a écrit : > The result is an image with distorted colors when opened in > QGIS. Water has turned a reddish brown color. > [...] > Please try to create the group in order B G R, not R G B: > > i.group

Re: [GRASS-user] Exporting RGB Composite Images to GeoTIFF

Le lundi 01 août 2016 à 14:45 +0200, Markus Neteler a écrit : > What options should I be selecting to export the image? Is there a > simpler method to exporting the image that I am not aware of? > > Maybe other users have a suggestion here. Michele, maybe it does not make sense but did you try

[GRASS-user] digitizer weird behaviour

Hi, on a recent GRASS build (70476) I noticed the boundary digitizing tool produces by default closed loops. Is it a deliberate change ? or has it been a default option for long and I didn't notice it ? Vincent. ___ grass-user mailing list

Re: [GRASS-user] damaged vector

the zero-length line, then everything runs fine again for your map. Hope this can help people puzzled by this rather frequent issue (at least for me ;-)). Vincent. Le mercredi 01 mars 2017 à 13:40 +0100, Vincent Bain a écrit : > Dear Grass users/devs, > > while moving/deleting

Re: [GRASS-user] damaged vector

OK, slight rectification on my previous post: v.clean works well and truly, my mistake. V. Le mercredi 01 mars 2017 à 17:23 +0100, Martin Landa a écrit : > 2017-03-01 17:19 GMT+01:00 Vincent Bain <b...@toraval.fr>: > > There might be something wrong with the digiti

[GRASS-user] damaged vector

Dear Grass users/devs, while moving/deleting vertices on a line vector map, I was kicked out of my wxdigit session. As often in this case the map is damaged, with the warning : "Coor files of vector map is larger than it should be (7762 bytes excess)" I don't really know how

Re: [GRASS-user] v.edit tool=merge

Le vendredi 23 septembre 2016 à 23:11 +0200, Markus Metz a écrit : > Maybe it is a zero-length line issue. You can remove these zero-length > lines with v.clean tool=rmline and check if editing the cleaned vector > still causes these GUI crashes. You're right : cleaning the map prior to editing

Re: [GRASS-user] v.edit tool=merge

Le lundi 26 septembre 2016 à 09:38 +0200, Markus Metz a écrit : > Maybe coordinates changed slightly during export, this could explain > why we get different results. Line heights for the same contour are > not exactly equal, e.g. 1239.39 for one line and 1240 for the next > line. Yes

Re: [GRASS-user] v.edit tool=merge

digitizer, it fails too. Later I noticed that when applying twice the command, the result is finally correct (199 lines). Vincent. Le vendredi 23 septembre 2016 à 15:00 +0200, Markus Metz a écrit : > On Tue, Sep 20, 2016 at 3:06 PM, Vincent Bain <b...@toraval.fr> wrote: > > Hi, > &g

Re: [GRASS-user] v.edit tool=merge

Le vendredi 23 septembre 2016 à 22:17 +0200, Markus Metz a écrit : > At least you got a working solution. Yes, thanks ! working with the same dataset, I ran into several GUI crashes (no time/no way to get an error message cause the window shuts up immediately, perhaps there's a log file but I

[GRASS-user] v.edit tool=merge

Hi, on a fresh (r69498) trunk version of grass, I have a problem running a v.edit command on a map. Given a vector map composed of 200 contour lines splitted in roughly 17000 line segments (adjacent nodes perfectly overlapping), I need to "unsplit" these contours. If I try to run the following

Re: [GRASS-user] v.edit tool=merge

Le samedi 24 septembre 2016 à 22:31 +0200, Markus Metz a écrit : > These zero-length lines should not cause an infinite loop, fixed in > all G7 branches with r69569-71. With these changes, you also need only > one run of v.edit in order to merge all selected lines. Yep' perfect! > > With G64,

Re: [GRASS-user] map display query and layers

Hello Dave, am I wrong or is your map connected to two distinct tables with the same key (cat) ? then the behavior you describe may be related to a confusion on the type of features holding 'cat' values. For exemple in the case of a polygon map, you need to define which type of object handles

Re: [GRASS-user] RasterLite output

otherwise "srid" is set to 0: rasterlite_load -d test.sqlite -T my_raster -e 2154 -i png -f my_raster.tif Thanks for your advice, Vincent Le lundi 17 octobre 2016 à 08:06 +0200, Moritz Lennert a écrit : > > Le 16 octobre 2016 17:27:48 GMT+02:00, Vincent Bain

[GRASS-user] vector digitizer

Hi, trying to use the wxGUI digitizer with GRASS 7.3 I am quite puzzled with a default behavior I would like to change : Usually when I have to digitize large polygon maps, I try to do a bulk definition of attribute, i.e. after drawing the whole boundaries, I digitize a hundred of centroids

Re: [GRASS-user] vector digitizer

Hello Moritz, thank you for your reply, Le jeudi 13 octobre 2016 à 16:54 +0200, Moritz Lennert a écrit : > This exists: go into Settings->Attributs->Category mode and chose "No > category". Which I completely missed, Sorry for the stupid question... Vincent.

[GRASS-user] RasterLite output

Hi, could anyone help me with exporting a raster map to an existing spatialite database ? Running r.out.gdal with Rasterlite on a newly created spatialite db works fine, but I would like to export multiple rasters to a single database. I see there are no creation options allowing to specify an

Re: [GRASS-user] Renaming many files with one command

Hi Rich, my one-liner 2-cents solution : for i in `g.list type=vector pattern=open_h_*`;do g.rename vect=$i,`echo $i | sed s/open_h_/blocked_h_/g`;done Hope this helps ! Vincent. Le samedi 18 mars 2017 à 07:42 -0700, Rich Shepard a écrit : >I inadvertently overwrote a set of 25 output

Re: [GRASS-user] Renaming many files with one command

Le samedi 18 mars 2017 à 09:13 -0700, Rich Shepard a écrit : > On Sat, 18 Mar 2017, Vincent Bain wrote: > > for i in `g.list type=vector pattern=open_h_*`;do g.rename vect=$i,`echo > > $i | sed s/open_h_/blocked_h_/g`;done >It's close, but not complete: Rich, this sho

Re: [GRASS-user] Renaming many files with one command

s that could be hurting sed ? could you provide a g.list rast output ? Anyone else may suggest an explanation? Bye, Vincent. Le samedi 18 mars 2017 à 10:45 -0700, Rich Shepard a écrit : > On Sat, 18 Mar 2017, Vincent Bain wrote: > > > Rich, this should work indeed (I just teste

Re: [GRASS-user] Renaming many files with one command

Le samedi 18 mars 2017 à 10:45 -0700, Rich Shepard a écrit : >Here's the verbatim command: > > for i in `g.list type=raster pattern=open_h_*`; do g.rename rast=$i,`echo > $i | sed /open_h_/blocked_h_/g`; done > Lastly, I would suggest you to try the same command with no space after the

Re: [GRASS-user] Change SQLite DB Column Width?

Le vendredi 04 août 2017 à 01:32 -0600, Jeshua Lacock a écrit : > Will I have to use SQLite to do it? I’ve never actually used it directly > before, so any examples would be greatly appreciated! you can either operate from an sqlite3 session, or use the grass builtin command db.execute. In

Re: [GRASS-user] Change SQLite DB Column Width?

Hello Jeshua, to my knowledge, no way to alter a column in sqlite3 : https://www.sqlite.org/lang_altertable.html .width only affects the output width of columns within sqlite3 prompt. I would suggest you to simply add a new column (with the right width), then copy the content of the previous to

Re: [GRASS-user] Experience with extracting a DTM from a DSM ?

Hello Moritz, if you mean trying to filter a point cloud which is not especially produced by a lidar (e.g. 3d reconstruction tools such as Micmac), I would suggest you to have a look at Canupo : http://nicolas.brodu.net/en/recherche/canupo/index.html Vincent. Le mardi 08 mai 2018 à 12:58

Re: [GRASS-user] Break lines in vector A at locations of points in vector B

Hello Eric, did you try v.split on vector A, with the vertices argument set to 2? (or maybe does vector B contain only a subset of A vertices) Vincent. Le mardi 06 mars 2018 à 16:50 +, Patton, Eric (NRCan/RNCan) a écrit : > Hi, > > I have two vector maps, vector A is a line vector

[GRASS-user] Compiling GRASS GIS on Debian Buster

Hi, since I upgraded my Debian system to version 10 (buster), I'm not able to get GRASS working. I pulled the latest version from Git main source code repository. The usual compilation process runs apparently fine. When launching grass77 from a terminal, the startup screen appears, and lets me

Re: [GRASS-user] Compiling GRASS GIS on Debian Buster

2.7.16 doc) Then GRASS starts and runs like a charm! Hope this helps folks who meet the same issue. Bye, Vincent. Le jeudi 25 juillet 2019 à 09:26 +0200, Vincent Bain a écrit : > Hi, > since I upgraded my Debian system to version 10 (buster), I'm not > able > to get GRASS working. &g

[GRASS-user] grass startup slowness

Dear GRASS users/devs, working with a weekly compiled GRASS GIS (against Git repository), for a couple of days now, I am experiencing a distinct drop in grass GUI startup speed, without any noticeable error, nor any change in my build configuration. The splash screen remains visible for nearly 1

Re: [GRASS-user] grass startup slowness

ent, > > On Tue, Oct 8, 2019 at 11:48 AM Vincent Bain wrote: > > Dear GRASS users/devs, > > > > working with a weekly compiled GRASS GIS (against Git repository), > > for > > a couple of days now, I am experiencing a distinct drop in grass > > GUI > > s

Re: [GRASS-user] g.findfile

Ok Stefan, I'll file a bug. V. Le jeudi 10 octobre 2019 à 08:47 +, Stefan Blumentrath a écrit : > I would say it is a bug. > > -Original Message- > From: grass-user On Behalf Of > Vincent Bain > Sent: torsdag 10. oktober 2019 10:41 > To: GRASS user list &

[GRASS-user] g.findfile

Trying to test the existence of maps with g.findfile I see there is something wrong with the command and its manual. It says the -l option provides a list of "elements" keywords. In my case it gives the following: raster(raster map(s)) raster_3d (3D raster map(s)) vector

Re: [GRASS-user] r.param.scale issue

Sun, Oct 11, 2020 at 8:08 PM Vincent Bain wrote: > > Dear Grass users, > > has anyone ever experienced such issue with r.param.scale? > > > > Here's the point: > > I use to invoke r.param.scale instead of r.slope.aspect to > > calculate > > topographical sl

Re: [GRASS-user] r.param.scale issue

t affect > outcome > in this case (I'll try to commit fix tomorrow). > > Happy hunting, > Māris. > > ceturtd., 2020. g. 15. okt., plkst. 09:18 — lietotājs Vincent Bain > () rakstīja: > > Hi Markus, > > thank you for your reply and investigation! > > >

Re: [GRASS-user] r.param.scale issue

AM Vincent Bain > wrote: > > Markus, > > my configuration cmd : > > > > ./configure > ... > > --with-openmp=yes > ... > > --with-openmp > > You may drop "openmp" and recompile (after "make distc

Re: [GRASS-user] r.param.scale issue

a écrit : > Hi Vincent, > > On Thu, Oct 15, 2020 at 10:13 AM Vincent Bain > wrote: > > Thanks Māris for your advice, > > > > it sounds dreadful to me to have to deal with these hardware > > issues... > > I installed valgrind and ran r.param.scale. > &

Re: [GRASS-user] r.param.scale issue

a écrit : > Hi Vincent, > > On Thu, Oct 15, 2020 at 10:13 AM Vincent Bain > wrote: > > Thanks Māris for your advice, > > > > it sounds dreadful to me to have to deal with these hardware > > issues... > > I installed valgrind and ran r.param.scale. > &

Re: [GRASS-user] r.param.scale issue

deals with openMP. Besides GRASS GIS I use OpenMP directives from within Clawpack fortran code, safely. Vincent. Le jeudi 15 octobre 2020 à 11:09 +0200, Markus Neteler a écrit : > On Thu, Oct 15, 2020 at 10:58 AM Vincent Bain > wrote: > > Markus, > > my configuration cmd : &g

Re: [GRASS-user] r.param.scale issue

y problems with Intel(R) Xeon(R) CPU E3-1241 v3 and > gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04). > > Māris. > > ceturtd., 2020. g. 15. okt., plkst. 11:13 — lietotājs Vincent Bain > () rakstīja: > > Thanks Māris for your advice, > > > > it sounds drea

[GRASS-user] r.param.scale issue

Dear Grass users, has anyone ever experienced such issue with r.param.scale? Here's the point: I use to invoke r.param.scale instead of r.slope.aspect to calculate topographical slopes in various situations. I especially appreciate to have a hand on the size of processing window. I rencently had

Re: [GRASS-user] unstable results with r.param.scale ?

Hello Vincent, in case it could be related to my recent issue with r.param.scale: https://lists.osgeo.org/pipermail/grass-user/2020-October/081788.html In my case there was most probably something wrong with my OpenMP configuration. HTH, Vincent. Le mercredi 09 décembre 2020 à 13:59 +0100,

[GRASS-user] Add-Ons and batch job with the --exec interface

Hi dear Grass users, I'm wondering how/if one can run an Add-On command while invoking grass from the --exec interface. As an example, if I run : grass79 /path/to/my/location/mapset --exec g.list rast I succeed. As well as checking my GRASS_ADDON_PATH : echo $GRASS_ADDON_PATH

Re: [GRASS-user] Add-Ons and batch job with the --exec interface [Solved]

Sorry for it: I just figured out there was a mess with a wrong symlink in my addons directory. Now it's humming! V. Le dimanche 20 décembre 2020 à 12:01 +0100, Vincent Bain a écrit : > Hi dear Grass users, > > I'm wondering how/if one can run an Add-On command while invoking >

Re: [GRASS-user] Add-Ons and batch job with the --exec interface

: > On 12/20/20 1:01 PM, Vincent Bain wrote: > > Hi dear Grass users, > > > > I'm wondering how/if one can run an Add-On command while invoking > > grass > > from the --exec interface. > > > > As an example, if I run : > > > >

[GRASS-user] grass gis, docker, postgresql

Dear GRASS users, Sorry in advance if my question is clearly not straightly related to grass, but any suggestions are welcome from those who are used to run grass in docker containers. Once in a while I need to run a rather old version of GRASS, especially for a compatibility issue with old

Re: [GRASS-user] rasterize 3d line

Hi Franck, I would suggest you to do sth as follows : - if necessary add vertice along your 3d lines (v.split ?) so their "density" is roughly equivalent to (or better smaller than) your target raster resolution ; - turn your vector lines to points using v.to.points (with use=vertex argument) ;

Re: [GRASS-user] [GRASS-dev] vector patching frustration

Hello Michael, do you mean that you cannot assign a different cat number to the specific area you added, i.e. it has a cat number assigned ? I guess you tried the "sum" option of v.category. But are you sure that the new area actually has a category attached to ? (else you could achieve it with

Re: [GRASS-user] [GRASS-dev] [EXTERNAL] vector patching frustration

Michael, Huidae thats's what I was just about to post... you need to care cats intervals don't overlap before patching. With the attached set of 2 vector maps you can have a try, typing : v.in.ogr input=/your/path/to/map1.gpkg output=map1 v.in.ogr input=/your/path/to/map2.gpkg output=map2

Re: [GRASS-user] [GRASS-dev] [EXTERNAL] vector patching frustration

Hello Michael, sorry if I misunderstand your issue, but before patching these two maps are you sure that each has a set of cat values strictly distinct from the other? If a vector feature in map A shares the same cat value as another feature in map B then after patching these features will be

<    1   2   3