Switch Locations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''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 16: | ||
# 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]] | |||
Revision as of 20:00, 16 June 2006
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:
- 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.
- 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.