Re: [GRASS-user] Multiple errors building Grass 7.7svn

2019-05-22 Thread Patton, Eric (NRCan/RNCan) 
Thanks for the help, Markus N. and Markus M. – Grass compiles and builds 
successfully with proj 5.2.0.

Cheers,

~ Eric.

From: Markus Metz 
Sent: May 22, 2019 13:16
To: Patton, Eric (NRCan/RNCan) 
Cc: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Multiple errors building Grass 7.7svn

Hi Eric,

On Wed, May 22, 2019 at 6:01 PM Patton, Eric (NRCan/RNCan) 
mailto:eric.pat...@canada.ca>> wrote:
>
> Thanks for that info. So would a suitable strategy be to try re-synching  
> Grass from git,

yes, with "git pull"

then compiling and building with proj 6.1, and if that fails, try the proj 
5.9.3 release?

As I wrote earlier, GRASS should now build with proj 6, but coordinate 
operations can produce wrong results.

proj-5.2.0 is the latest proj 5 release, GRASS is working with proj-5.2.0

Markus M

> ~ Eric.
>
>
>
> From: Markus Metz 
> mailto:markus.metz.gisw...@gmail.com>>
> Sent: May 22, 2019 12:57
> To: Patton, Eric (NRCan/RNCan) 
> mailto:eric.pat...@canada.ca>>
> Cc: grass-user@lists.osgeo.org<mailto:grass-user@lists.osgeo.org>
> Subject: Re: [GRASS-user] Multiple errors building Grass 7.7svn
>
>
>
>
>
> On Wed, May 22, 2019 at 5:33 PM Patton, Eric (NRCan/RNCan) 
> mailto:eric.pat...@canada.ca>> wrote:
> >
> > Markus -
> >
> > Yes, I am using proj 6.0.0 – built with no errors.
>
>
>
> be aware that GRASS might compile with PROJ 6, but it is not working, too 
> much has changed from PROJ 5 and all those changes are not yet considered in 
> GRASS. Most importantly, coordinate transformations might produce wrong 
> results.
>
>
>
> Furthermore, GRASS will most likely not support PROJ 6.0, only PROJ 6.1+, 
> because of bug fixes and important new functionality.
>
> >
> > I believe I checked out master with ‘git clone 
> > https://github.com/OSGeo/grass.git’ – so shouldn’t that fix already be 
> > present in my source tree?
>
>
>
> It depends when you updated master the last time. If in doubt, git pull again.
>
>
>
> Markus M
>
>
>
> >
>
> >
> >
> > ~ Eric.
> >
> >
> >
> > From: Markus Metz 
> > mailto:markus.metz.gisw...@gmail.com>>
> > Sent: May 22, 2019 12:25
> > To: Markus Neteler mailto:nete...@osgeo.org>>
> > Cc: Patton, Eric (NRCan/RNCan) 
> > mailto:eric.pat...@canada.ca>>; 
> > grass-user@lists.osgeo.org<mailto:grass-user@lists.osgeo.org>
> > Subject: Re: [GRASS-user] Multiple errors building Grass 7.7svn
> >
> >
> >
> >
> >
> > On Wed, May 22, 2019 at 4:39 PM Markus Neteler 
> > mailto:nete...@osgeo.org>> wrote:
> > >
> > > Hi Eric,
> > >
> > > On Wed, May 22, 2019 at 3:32 PM Patton, Eric (NRCan/RNCan)
> > > mailto:eric.pat...@canada.ca>> wrote:
> > > >
> > > > Hi Markus,
> > > >
> > > > I noted your new installation instructions for the git repo and have 
> > > > used those.
> > > >
> > > > The first error in error.log occurs in /usr/local/grass/lib/proj:
> > > >
> > > > test -d OBJ.x86_64-pc-linux-gnu || mkdir -p OBJ.x86_64-pc-linux-gnu
> > > > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include
> > > > -I/usr/local/include -DPACKAGE=\""grasslibs"\"   
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -DRELDIR=\"lib/proj\" -o OBJ.x86_64-pc-linux-gnu/convert.o -c convert.c
> > > > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include
> > > > -I/usr/local/include -DPACKAGE=\""grasslibs"\"   
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -DRELDIR=\"lib/proj\" -o OBJ.x86_64-pc-linux-gnu/datum.o -c datum.c
> > > > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include
> > > > -I/usr/local/include -DPACKAGE=\""grasslibs"\"   
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > > -DRELDIR=\"lib/proj\" -o OBJ.x86_64-pc-linux-gnu/do_proj.o -c do_proj.c
> > > > gcc  -

Re: [GRASS-user] Multiple errors building Grass 7.7svn

2019-05-22 Thread Patton, Eric (NRCan/RNCan) 
Thanks for that info. So would a suitable strategy be to try re-synching  Grass 
from git, then compiling and building with proj 6.1, and if that fails, try the 
proj 5.9.3 release?

~ Eric.

From: Markus Metz 
Sent: May 22, 2019 12:57
To: Patton, Eric (NRCan/RNCan) 
Cc: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Multiple errors building Grass 7.7svn



On Wed, May 22, 2019 at 5:33 PM Patton, Eric (NRCan/RNCan) 
mailto:eric.pat...@canada.ca>> wrote:
>
> Markus -
>
> Yes, I am using proj 6.0.0 – built with no errors.

be aware that GRASS might compile with PROJ 6, but it is not working, too much 
has changed from PROJ 5 and all those changes are not yet considered in GRASS. 
Most importantly, coordinate transformations might produce wrong results.

Furthermore, GRASS will most likely not support PROJ 6.0, only PROJ 6.1+, 
because of bug fixes and important new functionality.
>
> I believe I checked out master with ‘git clone 
> https://github.com/OSGeo/grass.git’ – so shouldn’t that fix already be 
> present in my source tree?

It depends when you updated master the last time. If in doubt, git pull again.

Markus M

>
>
>
> ~ Eric.
>
>
>
> From: Markus Metz 
> mailto:markus.metz.gisw...@gmail.com>>
> Sent: May 22, 2019 12:25
> To: Markus Neteler mailto:nete...@osgeo.org>>
> Cc: Patton, Eric (NRCan/RNCan) 
> mailto:eric.pat...@canada.ca>>; 
> grass-user@lists.osgeo.org<mailto:grass-user@lists.osgeo.org>
> Subject: Re: [GRASS-user] Multiple errors building Grass 7.7svn
>
>
>
>
>
> On Wed, May 22, 2019 at 4:39 PM Markus Neteler 
> mailto:nete...@osgeo.org>> wrote:
> >
> > Hi Eric,
> >
> > On Wed, May 22, 2019 at 3:32 PM Patton, Eric (NRCan/RNCan)
> > mailto:eric.pat...@canada.ca>> wrote:
> > >
> > > Hi Markus,
> > >
> > > I noted your new installation instructions for the git repo and have used 
> > > those.
> > >
> > > The first error in error.log occurs in /usr/local/grass/lib/proj:
> > >
> > > test -d OBJ.x86_64-pc-linux-gnu || mkdir -p OBJ.x86_64-pc-linux-gnu
> > > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include
> > > -I/usr/local/include -DPACKAGE=\""grasslibs"\"   
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > > -o OBJ.x86_64-pc-linux-gnu/convert.o -c convert.c
> > > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include
> > > -I/usr/local/include -DPACKAGE=\""grasslibs"\"   
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > > -o OBJ.x86_64-pc-linux-gnu/datum.o -c datum.c
> > > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include
> > > -I/usr/local/include -DPACKAGE=\""grasslibs"\"   
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > > -o OBJ.x86_64-pc-linux-gnu/do_proj.o -c do_proj.c
> > > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include
> > > -I/usr/local/include -DPACKAGE=\""grasslibs"\"   
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > > -o OBJ.x86_64-pc-linux-gnu/ellipse.o -c ellipse.c
> > > do_proj.c: In function ‘GPJ_init_transform’:
> > > do_proj.c:136:6: error: expected ‘}’ before ‘else’
> > >   else {
> > >   ^~~~
> > > do_proj.c: At top level:
> > > do_proj.c:160:5: error: expected identifier or ‘(’ before ‘if’
> > >  if (info_trans->pj == NULL)
> > >  ^~
> > > do_proj.c:162:5: error: expected identifier or ‘(’ before ‘if’
> > >  if (info_trans->pj == NULL) {
> > >  ^~
> > > do_proj.c:167:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
> > > before ‘->’ token
> > >  info_trans->meters = 1.;
> > >^~
> > > do_proj.c:168:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
> > > before ‘-

Re: [GRASS-user] Multiple errors building Grass 7.7svn

2019-05-22 Thread Patton, Eric (NRCan/RNCan) 
Markus -

Yes, I am using proj 6.0.0 – built with no errors.

I believe I checked out master with ‘git clone 
https://github.com/OSGeo/grass.git’ – so shouldn’t that fix already be present 
in my source tree?

~ Eric.

From: Markus Metz 
Sent: May 22, 2019 12:25
To: Markus Neteler 
Cc: Patton, Eric (NRCan/RNCan) ; 
grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Multiple errors building Grass 7.7svn



On Wed, May 22, 2019 at 4:39 PM Markus Neteler 
mailto:nete...@osgeo.org>> wrote:
>
> Hi Eric,
>
> On Wed, May 22, 2019 at 3:32 PM Patton, Eric (NRCan/RNCan)
> mailto:eric.pat...@canada.ca>> wrote:
> >
> > Hi Markus,
> >
> > I noted your new installation instructions for the git repo and have used 
> > those.
> >
> > The first error in error.log occurs in /usr/local/grass/lib/proj:
> >
> > test -d OBJ.x86_64-pc-linux-gnu || mkdir -p OBJ.x86_64-pc-linux-gnu
> > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
> > -DPACKAGE=\""grasslibs"\"   
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > -o OBJ.x86_64-pc-linux-gnu/convert.o -c convert.c
> > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
> > -DPACKAGE=\""grasslibs"\"   
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > -o OBJ.x86_64-pc-linux-gnu/datum.o -c datum.c
> > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
> > -DPACKAGE=\""grasslibs"\"   
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > -o OBJ.x86_64-pc-linux-gnu/do_proj.o -c do_proj.c
> > gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
> > -DPACKAGE=\""grasslibs"\"   
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
> > -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" 
> > -o OBJ.x86_64-pc-linux-gnu/ellipse.o -c ellipse.c
> > do_proj.c: In function ‘GPJ_init_transform’:
> > do_proj.c:136:6: error: expected ‘}’ before ‘else’
> >   else {
> >   ^~~~
> > do_proj.c: At top level:
> > do_proj.c:160:5: error: expected identifier or ‘(’ before ‘if’
> >  if (info_trans->pj == NULL)
> >  ^~
> > do_proj.c:162:5: error: expected identifier or ‘(’ before ‘if’
> >  if (info_trans->pj == NULL) {
> >  ^~
> > do_proj.c:167:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
> > before ‘->’ token
> >  info_trans->meters = 1.;
> >^~
> > do_proj.c:168:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
> > before ‘->’ token
> >  info_trans->zone = 0;
> >^~
> > do_proj.c:169:23: error: expected ‘)’ before ‘->’ token
> >  sprintf(info_trans->proj, "pipeline");
> >^~
> > do_proj.c:180:5: error: expected identifier or ‘(’ before ‘return’
> >  return 1;
> >  ^~
> > do_proj.c:181:1: error: expected identifier or ‘(’ before ‘}’ token
> >  }
> >  ^
> > ../../include/Make/Compile.make:32: recipe for target 
> > 'OBJ.x86_64-pc-linux-gnu/do_proj.o' failed
> > make: *** [OBJ.x86_64-pc-linux-gnu/do_proj.o] Error 1
> > make: *** Waiting for unfinished jobs
>
> ok, there seems to be a problem with the PROJ installation.

No, it's a problem with the #ifdef's in do_proj.c accounting for different 
versions of PROJ
>
> Which proj version do you use? Please post the names of the related
> packages here which you have installed (so that we see the precise
> version names).

This must be PROJ 6.

do_proj.c should be fixed in master 7c3e8de:
https://github.com/OSGeo/grass/commit/7c3e8de11b877f7c6240b5f94868ec27464d6c9f

Markus M

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

Re: [GRASS-user] Multiple errors building Grass 7.7svn

2019-05-22 Thread Patton, Eric (NRCan/RNCan) 
Hi Markus,

I noted your new installation instructions for the git repo and have used 
those. 

The first error in error.log occurs in /usr/local/grass/lib/proj:
 
test -d OBJ.x86_64-pc-linux-gnu || mkdir -p OBJ.x86_64-pc-linux-gnu
gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
-DPACKAGE=\""grasslibs"\"   -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" -o 
OBJ.x86_64-pc-linux-gnu/convert.o -c convert.c
gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
-DPACKAGE=\""grasslibs"\"   -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" -o 
OBJ.x86_64-pc-linux-gnu/datum.o -c datum.c
gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
-DPACKAGE=\""grasslibs"\"   -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" -o 
OBJ.x86_64-pc-linux-gnu/do_proj.o -c do_proj.c
gcc  -g -O2  -fPIC  -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include-I/usr/local/include 
-DPACKAGE=\""grasslibs"\"   -I/usr/local/grass/dist.x86_64-pc-linux-gnu/include 
-I/usr/local/grass/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/proj\" -o 
OBJ.x86_64-pc-linux-gnu/ellipse.o -c ellipse.c
do_proj.c: In function ‘GPJ_init_transform’:
do_proj.c:136:6: error: expected ‘}’ before ‘else’
  else {
  ^~~~
do_proj.c: At top level:
do_proj.c:160:5: error: expected identifier or ‘(’ before ‘if’
 if (info_trans->pj == NULL)
 ^~
do_proj.c:162:5: error: expected identifier or ‘(’ before ‘if’
 if (info_trans->pj == NULL) {
 ^~
do_proj.c:167:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘->’ token
 info_trans->meters = 1.;
   ^~
do_proj.c:168:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘->’ token
 info_trans->zone = 0;
   ^~
do_proj.c:169:23: error: expected ‘)’ before ‘->’ token
 sprintf(info_trans->proj, "pipeline");
   ^~
do_proj.c:180:5: error: expected identifier or ‘(’ before ‘return’
 return 1;
 ^~
do_proj.c:181:1: error: expected identifier or ‘(’ before ‘}’ token
 }
 ^
../../include/Make/Compile.make:32: recipe for target 
'OBJ.x86_64-pc-linux-gnu/do_proj.o' failed
make: *** [OBJ.x86_64-pc-linux-gnu/do_proj.o] Error 1
make: *** Waiting for unfinished jobs

Thanks,

~ Eric.




-Original Message-
From: Markus Neteler  
Sent: May 21, 2019 16:49
To: Patton, Eric (NRCan/RNCan) 
Cc: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Multiple errors building Grass 7.7svn

Hi Eric,

On Tue, May 21, 2019 at 6:00 PM Patton, Eric (NRCan/RNCan) 
 wrote:
...
> I was running Grass 7.7svn (trunk) fine last week, and updated to v74509 
> today on Linux Mint 19.1.

We just moved to GitHub:

git clone https://github.com/OSGeo/grass.git

However, a question:

> No errors during configure, but make showed many errors of the type:
>
> Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/xmmintrin.h:120: Syntax error 
> at '{'

I guess that these error messages appear in the ctypes part which is
(unfortunately) "normal" and apparently not an issue.
...

> There’s far too many errors to list here, but the result of it is that 221 
> grass modules fail to build.

Which is the first one listed in
error.log
?

Can you then cd into that directory, run "make" therein and report the error?

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

[GRASS-user] Multiple errors building Grass 7.7svn

2019-05-21 Thread Patton, Eric (NRCan/RNCan) 
Hi,

I was running Grass 7.7svn (trunk) fine last week, and updated to v74509 today 
on Linux Mint 19.1. No errors during configure, but make showed many errors of 
the type:

Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/xmmintrin.h:120: Syntax error at 
'{'
Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/xmmintrin.h:887: Syntax error at 
'{'
Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/xmmintrin.h:894: Syntax error at 
'{'
...
Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/emmintrin.h:68: Syntax error at 
'{'
...
Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/avx512fintrin.h:13330: Syntax 
error at '__v8si'
...
Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/avx512fintrin.h:13414: Syntax 
error at '__m256i'
...
Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/avx512fintrin.h:13632: Syntax 
error at '__m512i'
..
Error: /usr/lib/gcc/x86_64-linux-gnu/7/include/sgxintrin.h:96: Syntax error at 
'__volatile__'

...and many other similar errors in other header files.

There's far too many errors to list here, but the result of it is that 221 
grass modules fail to build. Hopefully this class of error messages will be 
familiar to experts.

As I mentioned, I have all dependencies satisfied and no problems building 
grass last week (last time was around Wednesday, I think.)

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

Re: [GRASS-user] Unable to modify PS1 variable

2019-02-28 Thread Patton, Eric (NRCan/RNCan) 
Micha, I don't have a bashrc file in ~.grass7. And copying ~/.grass.bashrc to 
~/.grass7/bashrc and restarting Grass doesn't change anything (PS1 remains the 
same). It seems the grass77 startup is clobbering all other places where $PS1 
is set.

~ Eric.

From: Micha Silver 
Sent: February 28, 2019 11:49
To: Patton, Eric (NRCan/RNCan) ; 
grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Unable to modify PS1 variable


On 28/02/2019 16:10, Patton, Eric (NRCan/RNCan) wrote:
Hi, I am having trouble changing my PS1 bash prompt in Grass 7.7svn. I have PS1 
set to "\W >" in ~/.grass.bashrc, but instead my prompt consistently prints

"GRASS 7.7.svn ($LOCATION_NAME):\w > "  (with LOCATION_NAME and \W expanded to 
current Grass location and full directory path, respectively). The result is my 
prompt is eating almost the full width of my shell window.

Just wondering what other resource files need to be changed?

On my system (Debian, GRASS 7.6) it's ~/.grass7/bashrc



Thanks,

~ Eric.



___

grass-user mailing list

grass-user@lists.osgeo.org<mailto:grass-user@lists.osgeo.org>

https://lists.osgeo.org/mailman/listinfo/grass-user

--

Micha Silver

Ben Gurion Univ.

Sde Boker, Remote Sensing Lab

cell: +972-523-665918
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Unable to modify PS1 variable

2019-02-28 Thread Patton, Eric (NRCan/RNCan) 
Thanks for that, Markus, that works.

~ Eric.

From: Markus Metz 
Sent: February 28, 2019 12:08
To: Patton, Eric (NRCan/RNCan) 
Cc: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Unable to modify PS1 variable



On Thu, Feb 28, 2019 at 3:21 PM Patton, Eric (NRCan/RNCan) 
mailto:eric.pat...@canada.ca>> wrote:
>
> Hi, I am having trouble changing my PS1 bash prompt in Grass 7.7svn. I have 
> PS1 set to “\W >” in ~/.grass.bashrc, but instead my prompt consistently 
> prints
>
> “GRASS 7.7.svn ($LOCATION_NAME):\w > “  (with LOCATION_NAME and \W expanded 
> to current Grass location and full directory path, respectively). The result 
> is my prompt is eating almost the full width of my shell window.
>
> Just wondering what other resource files need to be changed?

You could directly hack the GRASS startup script grass77, there in the fn 
bash_startup() the line that defines PS1, around L1772.

HTH,

Markus M

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

Re: [GRASS-user] Unable to modify PS1 variable

2019-02-28 Thread Patton, Eric (NRCan/RNCan) 
On Thu, Feb 28, 2019 at 3:20 PM Patton, Eric (NRCan/RNCan) 
 wrote:
>>
>> Hi, I am having trouble changing my PS1 bash prompt in Grass 7.7svn. I 
>>have
>> PS1 set to “\W >” in ~/.grass.bashrc, but instead my prompt 
>> consistently prints
>>
>> “GRASS 7.7.svn ($LOCATION_NAME):\w > “  (with LOCATION_NAME and \W 
>> expanded to current Grass location and full directory path, 
>> respectively). The result is my prompt is eating almost the full width of my 
>> shell window.
>
>Just to be sure: what is $SHELL set to? What is the output of:
>
>
>echo $SHELL
>
> and
>
>ls -la $(which $SHELL)

Markus, 

Here is the output:

echo $SHELL
/bin/bash

ls -al $(which $SHELL)
-rwxr-xr-x 1 root root 1037440 May 26  2017 /bin/bash

~ Eric.

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

[GRASS-user] Unable to modify PS1 variable

2019-02-28 Thread Patton, Eric (NRCan/RNCan) 
Hi, I am having trouble changing my PS1 bash prompt in Grass 7.7svn. I have PS1 
set to "\W >" in ~/.grass.bashrc, but instead my prompt consistently prints

"GRASS 7.7.svn ($LOCATION_NAME):\w > "  (with LOCATION_NAME and \W expanded to 
current Grass location and full directory path, respectively). The result is my 
prompt is eating almost the full width of my shell window.

Just wondering what other resource files need to be changed?


Thanks,

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

Re: [GRASS-user] Joining attributes of points to spatially-coincident line vertices

2018-03-06 Thread Patton, Eric (NRCan/RNCan) 
>Not sure what your overall goal is here. (Won't the slopes along the coastline 
>all be about 0?). If there are >two adjacent points with different slopes from 
>the raster, which value would you want to attach to the line >segment between 
>those points?

I am trying to assign a general raster slope to a segment of coastline that is 
representative of the steepness of that roughly 100m2 raster pixel. Yes, 
technically the slope is 0 at the waterline, but what we are trying to assign 
to the vector shoreline is a slope value that is more representative of the 
backshore, to give an idea of how sensitive the coastline might be to sea-level 
inundation and erosion. I was able to assign the raster slope to the vector 
points using v.distance, but getting the slopes onto the coastline line vector 
with a spatial join seems to be very difficult if not impossible in Grass.
As for the problem of which of two points to assign to a vector line segment, I 
thought there might be a function to choose the median value of the two points, 
or some other statistic – ArcGIS provides a way to do this through their 
spatial join module.
>But you could approach the task in a different, more straightforward way:
>Run the module v.split on your original coastline line vector and split to 
>segments at whatever max distance >you choose, Then run v.rast.stats with that 
>split line as input and use your slope raster to derive slopes. The >result 
>will be an attribute table attached to the coastline vector with min,max,mean, 
>etc raster values for >each line segment.

Your method is interesting, I would like to try that on a sample section and 
see how the processing time compares to the v.distance method. Since I am 
working with the entire coastline of Canada, I don’t think I will have time to 
rerun the process with v.rast.stats. I might take several weeks just to 
complete the v.split portion.
Thanks for the ideas though,
~ Eric.

On 03/06/2018 06:02 PM, thepatton...@gmail.com 
wrote:



I have a high-resolution vector coastline, and I extracted the vertices of this 
coastline to points using 'v.to.points use=vertex'. I am trying to find the 
nearest raster slope value from another map to these points, and then upload 
this slope to the attribute table of the vector points coastline. To do this, I 
converted the raster slope map to points with r.to.vect, and successfully 
uploaded the nearest slope value from the now vector slope map to the vector 
points coastline with v.distance, using a dmax=200.



Ok, now to my problem: I want to get the vector coastline points back onto the 
original vector *lines* coastline, with all the point attributes as well. Since 
the vector coastline points were derived from the vertices of the coastline map 
in the first place, they are spatially  coincident, but I can't find a 
processing method that does this. Ideally, I suppose the coastline points map 
could act as breakpoints to the coastline polyline map, and the attributes 
would be transferred based on a buffer of something like one metre or less.



Any ideas on how I might do this?



Thanks,



--

Eric

___

grass-user mailing list

grass-user@lists.osgeo.org

https://lists.osgeo.org/mailman/listinfo/grass-user



--

Micha Silver

Ben Gurion Univ.

Sde Boker, Remote Sensing Lab

cell: +972-523-665918
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-03-06 Thread Patton, Eric (NRCan/RNCan) 
Hi,

I have two vector maps, vector A is a line vector representing coastline, and 
vector B is vector points which are the vertices of vector A. Is there a way to 
split vector A into line segments using vector B as breakpoints? 

v.edit tool=break kind of does this, but seems to want coordinates given one at 
a time. I have hundreds of thousands of points, and this doesn't seem an 
efficient way of doing it. 

Thanks,

~ Eric. 

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

Re: [GRASS-user] problem creating secant Lambert Conformal Conic projection

2016-11-15 Thread Patton, Eric (NRCan/RNCan) 
Markus,

Responding to a months-old post (sorry!)

Upgrading to proj 4.9.2 and gdal 2.1.2 seemed to fix the problem.

Both secant parallels in my Lambert Conformal projection are now being reported:

> g.proj -we
PROJCS["Lambert_Conformal_Conic",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137,298.257223563]],
PRIMEM["Greenwich",0],
UNIT["Degree",0.017453292519943295]],
PROJECTION["Lambert_Conformal_Conic"],
PARAMETER["standard_parallel_1",65],
PARAMETER["standard_parallel_2",75],
PARAMETER["latitude_of_origin",65],
PARAMETER["central_meridian",-60],
PARAMETER["false_easting",0],
PARAMETER["false_northing",0],
UNIT["Meter",1]]

Sorry for the noise!

--
Eric 


From: neteler.os...@gmail.com <neteler.os...@gmail.com> on behalf of Markus 
Neteler <nete...@osgeo.org>
Sent: Tuesday, May 17, 2016 5:33 PM
To: Patton, Eric (NRCan/RNCan)
Cc: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] problem creating secant Lambert Conformal Conic 
projection

On Tue, May 17, 2016 at 7:28 PM, Patton, Eric (NRCan/RNCan)
<eric.pat...@canada.ca> wrote:
> Hi Markus,
>
> Sorry for the delay in responding. I am using Grass 7.0.5svn, proj 4.8.0,
> gdal 1.10.1.
>
> I really don’t understand what could be the cause of this. I tried a fresh
> checkout and install, and encountered the same behavior. I'm using the proj
> and gdal packages provided by my package manager, so there's no custom
> installations installed in parallel.

proj-4.8.0 is from roughly 13-Mar-2012

I use proj 4.9.1, 04 March 2015

Perhaps some fixes in between?

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

Re: [GRASS-user] problem creating secant Lambert Conformal Conic projection

2016-05-17 Thread Patton, Eric (NRCan/RNCan) 
??Hi Markus,

Sorry for the delay in responding. I am using Grass 7.0.5svn, proj 4.8.0, gdal 
1.10.1.

I really don't understand what could be the cause of this. I tried a fresh 
checkout and install, and encountered the same behavior. I'm using the proj and 
gdal packages provided by my package manager, so there's no custom 
installations installed in parallel.

~ Eric.


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