[GRASS-user] Getting Started with GRASS Python Scripts
mlacayo at stanford.edu
Thu May 23 14:55:31 PDT 2013
Thank you. Yes, that does help. I hadn't realized that in this case
database was essentially synonymous with user directory. Several
things have now clicked into place.
On Thu, May 23, 2013 at 2:06 PM, Rich Shepard <rshepard at appl-ecosys.com> wrote:
> On Thu, 23 May 2013, Martin Lacayo wrote:
>> Have I understood correctly that a database can only contain one
>> projection, which is set when it is first created, and that besides
>> importing and exporting data all processing has to happen with data that
>> is in the database?
> You seem to confuse database, location, and mapset. There is only one
> database (here, it's in /home/rshepard/grassdata/) where everything is
> The database can contain multiple locations, each one with a specific
> projection. For example, I have a number of projects in Washington state so
> I have (among others) Washington-Counties/, Washington-HUC/,
> Washington-Hydro/, Washington-LL/, Washington-NED/, and Washington-NHD/.
> Notice that Washington-LL is in long/lat; others might be in SPCS, UTM, or
> whatever other projection is used by the data source.
> I also have project-specific locations. Each of these has a basic
> PERMANENT/ map se and multiple other map sets that might have different
> themes, and so on.
> Richard B. Shepard, Ph.D. | Have knowledge, will travel.
> Applied Ecosystem Services, Inc. |
> <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
> grass-user mailing list
> grass-user at lists.osgeo.org
More information about the grass-user