Simon Cox writes:
I want to get a bit more structured in the way my data is stored. I
thought that using a set of mapsets for different themes would be the way
to go. However, in order to be able to hop around without starting a new
GRASS session, it would be desirable to EITHER
i) be able to write to mapsets other than the "current" one,
OR (preferably)
ii) be able to change the "current" mapset during a session,
(OR BOTH).
I guess it would not be difficult to write a script, or maybe a program to
modify the appropriate environment variables, etc, but has anyone already
done this?ALSO - how about a g.move or a more powerful g.rename that does a g.copy
followed by a g.remove?
You might consider leaving the GRASS file-management tools behind, as
they behave like modified versions of the well known cp and mv commands. I
don't think you will have much trouble writing some shell scripts that do
things like mv $LOCATION/*/<file-name> <some other place>, but you'll
have to set some variables like the mapset-paths and the data-type
directories. Good luck!
Philip Verhagen
--
S t i c h t i n g R A A P
Regionaal Archeologisch Archiverings Projekt
adress: Plantage Muidergracht 14
1018 TV Amsterdam
THE NETHERLANDS
phone/fax: (31) 20 525 5834
e-mail: motte@hacktic.nl