Changes between Version 18 and Version 19 of Grass8Planning
- Timestamp:
- 11/25/17 09:37:17 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Grass8Planning
v18 v19 9 9 * Problem 2: Non-unix users confuse current working directory with "grassdata". 10 10 * Problem 3: The same things is referred to in different ways (GISDBASE, grassdata, GRASS Database Directory, dbase). 11 * Problem 4: Instructions often say "set your location and mapset" while they mean "set 'database ', then location, and then mapset."11 * Problem 4: Instructions often say "set your location and mapset" while they mean "set 'database directory', then location, and then mapset, and optionally also working directory." 12 12 * Problem 5: When setting up "GRASS session" manually, e.g. in Python, GISBASE and GISDBASE look too much alike. 13 13 * Solution: Make it clear that users are dealing with a database and while also emphasizing that the database is spatial as opposed to just attributes (as in GIS vector/spreadsheet tables).