[GRASS-dev] [GRASS GIS] #2683: grass 7 doesn't start in text mode on CentOS 7

GRASS GIS trac at osgeo.org
Tue Jun 21 06:55:00 PDT 2016

#2683: grass 7 doesn't start in text mode on CentOS 7
  Reporter:  morenocomelli  |      Owner:  grass-dev@…
      Type:  defect         |     Status:  new
  Priority:  normal         |  Milestone:  7.0.5
 Component:  Startup        |    Version:  7.0.0
Resolution:                 |   Keywords:  centos
       CPU:  Unspecified    |   Platform:  Unspecified

Comment (by mlennert):

 Replying to [comment:14 neteler]:
 > Replying to [comment:13 rbarnes]:
 > > I'm running GRASS on a headless machine, so it wasn't possible for me
 to use a GUI on it.
 > Right.
 > On headless machines, use
 > grass70 /path/to/location/mapset
 > and the rc file will be generated.

 If you have no existing GRASS DATABASE, yet, on the machine, I would
 recommend starting by creating one:


 Then, if you have no existing GRASS GIS data, you have to create a
 location and mapset first. Locations are defined by their projection
 system. Two options exist to define this projection: either you use an
 existing georeferenced file, or you use an EPSG code (see grass70 --help
 for details).

 grass70 -c EPSG:32630 /home/myuser/GRASSDATA/mylocation

 will create the location 'mylocation' (using WGS 84 / UTM zone 30N
 projection) and the mapset PERMANENT.

 If you want to enter the same location, but in a newly created mapset:

 grass70 -c /home/myuser/GRASSDATA/mylocation/mymapset

 If you want to create a new location (which always needs a PERMANENT
 mapset) and immediately enter another newly created mapset, you can
 combine these two steps

 grass70 -e -c EPSG:32630 /home/mlennert/gg/mylocation
 grass70 -c /home/myuser/GRASSDATA/mylocation/mymapset

 The '-e' flag tells GRASS to just create the new location (with its
 PERMANENT mapset), and then exit. The second call then creates and enters
 the new mapset mymapset.

Ticket URL: <https://trac.osgeo.org/grass/ticket/2683#comment:16>
GRASS GIS <https://grass.osgeo.org>

More information about the grass-dev mailing list