Re: [GRASS-dev] [GRASS GIS] #3462: Allow setting environment variables in grass startup script

[GRASS GIS]

#3462: Allow setting environment variables in grass startup script
--+-
  Reporter:  mankoff  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:
 Component:  Default  |Version:  7.2.2
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  MacOSX
--+-

Comment (by martinl):

 Replying to [comment:8 mankoff]:
 > I'm not clear how the comment in `grass.py` pointing to this ticket
 helps. Certain critical environment variables that are **required** for
 GRASS to work correctly cannot be set in either `~/.grass.bashrc` or
 `~/.grass7/bashrc`, as long as the line ignoring `export` statements
 remains. Why can't I `export` variables from these scripts?

 As I mentioned earlier, the environment variables should be loaded by
 `load_env()`. I tested your config file and it's working on my Linux
 machine. So probably something related to MAC? Try to put more debug
 message around `load_env()`.

 {{{
 cat ~/.grass7/bashrc
 export BAR=42
 export DYLD_LIBRARY_PATH=/opt/local/share/grass-7.2.2/lib

 GRASS_DEBUG=ON ./bin.x86_64-pc-linux-gnu/grass75 -text
 ...
 DEBUG: Environmental variable set BAR=42
 DEBUG: Environmental variable set
 DYLD_LIBRARY_PATH=/opt/local/share/grass-7.2.2/lib
 ...

 GRASS> env | grep BAR
 BAR=42

 GRASS> env | grep DY
 DYLD_LIBRARY_PATH=/opt/local/share/grass-7.2.2/lib
 }}}

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] pip install grass-session - No matching distribution found for grass-session

[Pietro]

Hi Markus,

On Sun, Dec 17, 2017 at 5:11 PM, Markus Neteler  wrote:

> [...]
> > No matching distribution found for grass-session
>
> Ah, just discovered the trick:
>
> https://grasswiki.osgeo.org/w/index.php?title=Working_with_
> GRASS_without_starting_it_explicitly=0=24906
>
> Now it works fine.


Sorry if I didn't replied to you, but I thought that the "best" reply was
fix the missing information on the wikipage.
Thank you to pointing out the missing information, it is still under
testing on my side.
I'm going to test and use for an analyses in the next weeks, after this I
would like to publish it on pypi, and therefore should be installable with
"pip install grass-session".
Hopefully for the beginning of the next year.

Today, I found out: https://github.com/perrygeo/mower that it seems
similar, my approach should be more flexible for multiprocessing (this is
my impression).

If it works well for my use case, I will publish it on pypi, and I will
write to grass-user.

Thank you for your interest.

Have a nice night.

All the best.

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

Re: [GRASS-dev] [GRASS GIS] #3462: Allow setting environment variables in grass startup script

[GRASS GIS]

#3462: Allow setting environment variables in grass startup script
--+-
  Reporter:  mankoff  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:
 Component:  Default  |Version:  7.2.2
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  MacOSX
--+-

Comment (by mankoff):

 I'm not clear how the comment in `grass.py` pointing to this ticket helps.
 Certain critical environment variables that are **required** for GRASS to
 work correctly cannot be set in either `~/.grass.bashrc` or
 `~/.grass7/bashrc`, as long as the line ignoring `export` statements
 remains. Why can't I `export` variables from these scripts?

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] List of tutorials

[Paulo van Breugel]

Thanks Doug,

Yes, you are right. We could use that (or make a separate page for
tutorials and courses only). I think the list can use some clean up, at the
very least separating out the tutorials for grass 7 and 6.4 (giving
preference to the former). I'll have a look at it later this week.

Cheers,

Paulo

On Mon, Dec 18, 2017 at 2:07 PM, Newcomb, Doug  wrote:

> There is also the list here:
> https://grasswiki.osgeo.org/wiki/GRASS_Documents#GRASS_tutorials
>
> Doug
>
> On Sun, Dec 17, 2017 at 10:59 AM, Paulo van Breugel <
> p.vanbreu...@gmail.com> wrote:
>
>>
>> On 12/17/17 4:57 PM, Markus Neteler wrote:
>>
>>> On Sun, Dec 17, 2017 at 10:19 AM, Paulo van Breugel
>>>  wrote:
>>>
 Hi devs,

 I think it is important to have a good and curated list of tutorials on
 the
 main grass gis website. The current list with tutorials on
 https://grass.osgeo.org/documentation/tutorials/ is not very complete,
 and
 does include old tutorials. What about adding a form to the page, where
 people can fill in tutorials and courses? Then there would still be
 somebody
 that needs to add (or remove) them to the list (I wouldn't mind doing
 that).
 An alternative would be to link directly to a dedicated page on the
 GRASS
 GIS wiki?

>>> I'd suggest to make it a Wiki page to which we then link from the Web
>>> site.
>>>
>>> Paulo, would  you be willing to start that?
>>>
>>
>> Yes, sure. Will make something in the coming week
>>
>>
>>
>>> thanks,
>>> Markus
>>>
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
>
> --
> Doug Newcomb
> USFWS
> 551F Pylon Dr
> 
> Raleigh, NC
> 
> 919-856-4520 ext. 14 doug_newc...@fws.gov
> 
> -
> The opinions I express are my own and are not representative of the
> official policy of the U.S.Fish and Wildlife Service or Dept. of the
> Interior.   Life is too short for undocumented, proprietary data formats.
> *NOTE: This email correspondence and any attachments to and from this
> sender is subject to the Freedom of Information Act (FOIA) and may be
> disclosed to third parties.*​
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] List of tutorials

[Newcomb, Doug]

There is also the list here:
https://grasswiki.osgeo.org/wiki/GRASS_Documents#GRASS_tutorials

Doug

On Sun, Dec 17, 2017 at 10:59 AM, Paulo van Breugel 
wrote:

>
> On 12/17/17 4:57 PM, Markus Neteler wrote:
>
>> On Sun, Dec 17, 2017 at 10:19 AM, Paulo van Breugel
>>  wrote:
>>
>>> Hi devs,
>>>
>>> I think it is important to have a good and curated list of tutorials on
>>> the
>>> main grass gis website. The current list with tutorials on
>>> https://grass.osgeo.org/documentation/tutorials/ is not very complete,
>>> and
>>> does include old tutorials. What about adding a form to the page, where
>>> people can fill in tutorials and courses? Then there would still be
>>> somebody
>>> that needs to add (or remove) them to the list (I wouldn't mind doing
>>> that).
>>> An alternative would be to link directly to a dedicated page on the GRASS
>>> GIS wiki?
>>>
>> I'd suggest to make it a Wiki page to which we then link from the Web
>> site.
>>
>> Paulo, would  you be willing to start that?
>>
>
> Yes, sure. Will make something in the coming week
>
>
>
>> thanks,
>> Markus
>>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>



-- 
Doug Newcomb
USFWS
551F Pylon Dr
Raleigh, NC
919-856-4520 ext. 14 doug_newc...@fws.gov
-
The opinions I express are my own and are not representative of the
official policy of the U.S.Fish and Wildlife Service or Dept. of the
Interior.   Life is too short for undocumented, proprietary data formats.
*NOTE: This email correspondence and any attachments to and from this
sender is subject to the Freedom of Information Act (FOIA) and may be
disclosed to third parties.*​
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] GRASS add-on sharing and write access

[Moritz Lennert]

[CC'ing grass-dev where such discussion should be happening]

On 17/12/17 22:37, Markus Neteler wrote:

On Sun, Dec 17, 2017 at 9:14 PM, Markus Metz
 wrote:
...

Right now, r.drain is somewhat overloaded: it creates directions for a DEM
same way r.fill.dir does it, or it uses supplied directions, then the module
extracts least costly paths. I suggest to have a new module r.path that
extracts extract least costly paths from input directions and start points
and mark r.drain as deprecated.


Sounds interesting! At time it is a bit confusing.


+1

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