Re: [GRASS-user] Organizing data over extensive areas [RESOLVED]

[Rich Shepard]

On Wed, 11 Sep 2019, Rich Shepard wrote:


Is there a way to put a collection of locations in a single subdirectory,
e.g., /data/grassdata/fishes/ and have grass know how to find them?


Never mind, I figured it out.

I wrote a script to reproject the map from each individual location's
PERMANENT mapset to an existing location's biota mapset. When I have
projects in other locations I can reproject from this core one to that of
each individual project.

Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Organizing data over extensive areas

[Rich Shepard]

I imported an OpenFileGDB containing the distributions of 14 species and
runs of fish in the Columbia River Basin. Because one species has a
different CRS than the others each layer needed to be separately imported
into separate locations. This is inefficient and I would like to gather them
in a directory, perhaps named 'fishes.'

The issue is that collectively, the distributions cover most of Washington
and Oregon along with bits of Canada, Idaho, Wyoming, Nevada, and California
(drainage basin extents). So a projection covering all these areas will be
different from the standard projections used by each state and British
Columbia.

Is there a way to put a collection of locations in a single subdirectory,
e.g., /data/grassdata/fishes/ and have grass know how to find them?

TIA,

Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user