Switch Locations: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{OutDated}}{{NeedsExpansion}}


'''Q:''' Is is possible to switch one LOCATION to another while running GRASS. If yes please suggest.
'''Q:''' Is is possible to switch one LOCATION to another while running GRASS. If yes please suggest.
Line 17: Line 18:
# Existing NVIZ and tcltkgrass sessions won't recognise the change of location; they will continue to use the old location.
# Existing NVIZ and tcltkgrass sessions won't recognise the change of location; they will continue to use the old location.
# The shell history (.bash_history) will be saved in the original mapset directory.
# The shell history (.bash_history) will be saved in the original mapset directory.
[[Category:FAQ]]

Latest revision as of 09:59, 5 February 2013

Template:NeedsExpansion

Q: Is is possible to switch one LOCATION to another while running GRASS. If yes please suggest.

A: Partially. With pre4 and later, using any of:

g.gisenv set="GISDBASE=newdbase"
g.gisenv set="LOCATION_NAME=newlocation"
g.gisenv set="MAPSET=newmapset"

will mostly work.

Things which won't work correctly include:

  1. Monitor state (resizing, d.save, d.redraw etc). You may as well run "d.erase" when changing location, as the stored state is no longer usable.
  2. Existing NVIZ and tcltkgrass sessions won't recognise the change of location; they will continue to use the old location.
  3. The shell history (.bash_history) will be saved in the original mapset directory.