I think you mix up the purpose of location and mapsets- what
you ask for is exactly what mapsets are do.
It seemed to. And yes, this may come from experiences with other GIS
programs, too.
Note that not only ArcGIS works this way but also QGIS or gvSIG, for
instance.
Throw together data from
I don't understand what you want to do here.
Image the following use case:
You have project location.
Then you would like to test out some new processing workflows or
developed a new methodology.
In order not to pollute the project location with a lot of test rasters,
you start a new location to
I don't understand what you want to do here.
Image the following use case:
You have project location.
Then you would like to test out some new processing workflows or
developed a new methodology.
In order not to pollute the project location with a lot of test rasters,
you start a new location to
Tim wrote:
In order not to pollute the project location with a lot of
test rasters, you start a new location to do the testing.
It would be nice to have the save region settings available
for /all/ locations with the same projection.
I think you mix up the purpose of location and mapsets-
startup screen:
LOCATION: This is the name of a geographic location. It is
defined by a co-ordinate system and a rectangular boundary.
The REGION defaults to the entire area of the chosen
LOCATION. You may change it later with the command: g.region
- - - - - - - - - - - - - - - - - -
I don't understand what you want to do here. AFAICT, the only reason
for saving a GRASS region is to use the region in GRASS. The same goes
for a workspace file. As others have pointed out g.region and g.proj
will export the details of any projection used by GRASS.
If you are trying to use
