Re: [GRASS-user] Missing information in the GRASS 7 NewFeatures/OptionChanges web page

On Sat, Apr 30, 2016 at 9:59 AM, Bartolomei.Chris wrote: > Sorry to keep at this but here's a few more (and I'm sure more to follow as I > debug my scripts): These comments are most welcome. Feel free to just send them to me. > For v.to.rast: > option rows= has been

Re: [GRASS-user] where is MSYS in GRASS 7?

Hi Martin, On Sat, 30. Apr 2016 at 13:49:20 +0200, Martin Landa wrote: > AFAIU this must be defined in the GRASS env file (so the file which is > loaded when GRASS is started - by bat file). Ma grass70.bat calls o4w_env.bat which in turn calls all batch files in etc/ini Jürgen -- Jürgen E.

Re: [GRASS-user] PostgreSQL not in v.out.ogr format options

[Please keep discussions on the list] On 29/04/16 19:35, Peter Tittmann wrote: Thx for your reply! -> "PostgreSQL" (read/write) And v.in.ogr -f | grep PostgreSQL ? If that doesn't show success, then it would seem to me that there might be an issue in your installation with GRASS not

Re: [GRASS-user] where is MSYS in GRASS 7?

Hi, 2016-04-30 12:04 GMT+02:00 Jürgen E. : >> > REM set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe >> > >> > -> > set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe > > This could be added to etc/ini/msys.bat in the msys package. AFAIU this must be defined in the GRASS env file

Re: [GRASS-user] where is MSYS in GRASS 7?

Hi, 2016-04-29 18:46 GMT+02:00 Bartolomei.Chris : > Just a couple notes: the C:\OSGeo4W/apps/grassX/etc/env.bat file did not have > the GRASS_SH line in it so I just added it as you typed out and it works. right, I re-added this line recently, will be included in

Re: [GRASS-user] where is MSYS in GRASS 7?

Hi Markus, On Fri, 29. Apr 2016 at 11:38:29 +0200, Markus Neteler wrote: > > it's easy to switch to msys. Install grass and msys from OSGeo4W. Edit > > C:\OSGeo4W/apps/grassX/etc/env.bat. > > > > REM set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe > > > > -> > set

Re: [GRASS-user] why is v.build.all (and many others) a windows batch file and not an executable?

>They modules should all be compiled executables so legacy shell >scripts users have can run them ... AFAIK there were always a distinction in GRASS between compiled code and scripts since the beginning. the motivation of the switch to python scripts from grass6 to grass7 was cross platform

Re: [GRASS-user] why is v.build.all (and many others) a windows batch file and not an executable?

Ok (I guess) but this causes severe problems running shell scripts that call out the GRASS modules ... there is no way of knowing which modules are compiled executables (which run fine from the shell script) and which ones are Windows Batch files (which DON'T run when called from a script) ...

Re: [GRASS-user] Missing information in the GRASS 7 NewFeatures/OptionChanges web page

Sorry to keep at this but here's a few more (and I'm sure more to follow as I debug my scripts): For v.to.rast: option rows= has been removed option memory= has been added In the Renamed Modules section: Add v.db.addcol -> v.db.addcolumn and why on earth are a bunch of the modules Windows

Re: [GRASS-user] Missing information in the GRASS 7 NewFeatures/OptionChanges web page

I found another issue ... I'm using 7.0.3 and the change list I was correcting (https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Optionschanges) indicated for g.region: n -> north s -> south e -> east w -> west t -> top b -> bottom This is all incorrect ... the