[GRASS-dev] [GRASS GIS] #3772: Make the grass library importable outside of a GRASS session

GRASS GIS trac at osgeo.org
Tue Mar 5 12:48:54 PST 2019


#3772: Make the grass library importable outside of a GRASS session
--------------------------+-------------------------
  Reporter:  pmav99       |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:
 Component:  Python       |    Version:  svn-trunk
Resolution:               |   Keywords:
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------

Comment (by mmetz):

 This is a question about the general design of GRASS GIS.

 There are two requirements in order to use GRASS GIS;

 some environment variables mus be set:

 At the very least GISBASE, LD_LIBRARY_PATH must be expanded to include the
 path to GRASS libraries, and PATH must be expanded to include the path to
 both all GRASS core modules and all GRASS scripts. GISRC must point to a
 valid gisrc file.

 See also
 https://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3772#comment:4>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list