[GRASS-user] Re-organizing Project

Rich Shepard rshepard at appl-ecosys.com
Tue Dec 22 14:45:56 EST 2009


   Since I'm having all sorts of issues getting usable data in one place so I
can start modeling, I should step back and reorganize what I'm doing. I've
just picked up that mapsets can be used for different issues or themes as
well as different users. This leads to several questions for which I don't
find answers in the Book or Web site; they may be in there but I've missed
them.

   For the current project, all data is in Oregon. All source data files have
the same projection information, but each has different bounds. I'm thinking
that I should put all source data in a single location, called 'Oregon.' The
location's PERMANENT mapset, DEFAULT_WIND and PROJ_INFO will come from the
state boundary outline (an .e00 file). That will be placed in the 'statebnd'
mapset and should have the same WIND as the DEFAULT_WIND in PERMANENT.
County outlines will be placed in the 'cntybnd' mapset which should have the
same WIND, too.

   Then I use v.proj and r.proj to copy each vector map and the raster DEM
map to their own mapsets within the Oregon location. The projection
information should all the same, but each will have different WIND
boundaries.

   If I'm correct on the above, then it should be simpler and correct to
create a project mapset in the same location since it, too, has the same
projection, but bounds the smallest area.

   With the above scheme, do I need to run g.region to set the bounds for
each mapset/map theme? I ask because some of the maps (e.g., stream/rivers,
hydrologic units, soil mapping units) may extend past the state or county
boundaries.

   Re-learning after 5-6 years of not using GRASS at all will get me back to
speed so I can complete this project.

Thanks,

Rich




More information about the grass-user mailing list