[GRASS-user] Linux Journal features GRASS GIS

GRASS GRASS user
1

Dear All,

This month's edition of the Amerian Linux Journal
(www.linuxjournal.com) features an article on GRASS.

Overall, I would say the article does a good job
of introducing potential new users to GRASS.

However, while reading it, I realised that two
conceptual problems remain that new users might
struggle with:

1. The role of the PERMAMENT mapset remains
hard to grasp (the article wrongly suggests that
this should be the default mapset to log into).

2. The GUI does not speak the same language as
the CLI when it comes to the use of the terms
"map", "layer" and "monitor".

The first issue could be addressed by displaying
a warning of the kind "Do you really want to work
in the PERMANENT mapset" when a first-time login
attempt is made.

The second issue requires some consideration of
how "map" and "layer" are used in different ways
at the moment. Traditionally, a "map" is a GRASS
raster or vector dataset. In the GUI, what used to
be a "monitor" is now called "Map Display", whereas
what used to be "maps" is now called "Map layers"
(and the associated window title is "Layer Manager").
Novice users might stumble over this when they
discover the vector modules' "layer=" option and/or
any single-input module's "map=" option.

Also:
- The window title "Layer Manager" is somewhat
of a misnomer, since this is really the main window
and does a lot more than just managing a layer list.

- Using the location name as right-hand part of the
"Map Display" window title suggests that there could be
multiple locations per GRASS session (as there can be
multiple "Map Display" windows), which is misleading
(at least for languages that use left-to-right writing).

To bring back consistency, some review of terminology
across CLI and GUI seems in order. Since it seems to
me that it is easiest to change some strings in the
GUI, I would suggest something like this:

"Layer Manager" = "GRASS GIS - location (filename.gxw)"

"Map Display x" = "GRASS GIS - location (Monitor x)"

"Map layers" = "Maps"

"Display x" = "Monitor x"

Best,

Ben

--
Dr. Benjamin Ducke, M.A.
{*} Geospatial Consultant
{*} GIS Developer

   benducke@fastmail.fm

2

On Wednesday 05 of June 2013 09:08:24 Benjamin Ducke wrote:

Dear All,

This month's edition of the Amerian Linux Journal
(www.linuxjournal.com) features an article on GRASS.

That's great!

Overall, I would say the article does a good job
of introducing potential new users to GRASS.

However, while reading it, I realised that two
conceptual problems remain that new users might
struggle with:

1. The role of the PERMAMENT mapset remains
hard to grasp (the article wrongly suggests that
this should be the default mapset to log into).

At some extent it's unavoidable I think without engaging in some process of
understanding GRASS' basic concepts.

2. The GUI does not speak the same language as
the CLI when it comes to the use of the terms
"map", "layer" and "monitor".

The first issue could be addressed by displaying
a warning of the kind "Do you really want to work
in the PERMANENT mapset" when a first-time login
attempt is made.

Why not even more extended/interfering something among the lines:

Do you really want to work in the PERMANENT mapset? Consider the PERMANENT
Mapset as an import container from which to draw raw material. Unless you know
what you are doing, you are better off using another mapset for real
processing.

The second issue requires some consideration of
how "map" and "layer" are used in different ways
at the moment. Traditionally, a "map" is a GRASS
raster or vector dataset. In the GUI, what used to
be a "monitor" is now called "Map Display", whereas
what used to be "maps" is now called "Map layers"
(and the associated window title is "Layer Manager").
Novice users might stumble over this when they
discover the vector modules' "layer=" option and/or
any single-input module's "map=" option.

Also:
- The window title "Layer Manager" is somewhat
of a misnomer, since this is really the main window
and does a lot more than just managing a layer list.

Good point! What about "Map Manager?"

- Using the location name as right-hand part of the
"Map Display" window title suggests that there could be
multiple locations per GRASS session (as there can be
multiple "Map Display" windows), which is misleading
(at least for languages that use left-to-right writing).

To bring back consistency, some review of terminology
across CLI and GUI seems in order. Since it seems to
me that it is easiest to change some strings in the
GUI, I would suggest something like this:

"Layer Manager" = "GRASS GIS - location (filename.gxw)"

"Map Manager"?

"Map Display x" = "GRASS GIS - location (Monitor x)"

"Map layers" = "Maps"

+1

"Display x" = "Monitor x"

Best,

Ben

Cheers, Nikos

3

Hi,

what about moving PERMANENT to .PERMANENT (hidden configuration mapset)

People, who want to know, can use it

People who don't care, don't see it

GRASS would move little bit to new users.

However, some of it's essence would be gone.

J

Dne 5.6.2013 09:08, Benjamin Ducke napsal(a):

Dear All,

This month's edition of the Amerian Linux Journal
(www.linuxjournal.com) features an article on GRASS.

Overall, I would say the article does a good job
of introducing potential new users to GRASS.

However, while reading it, I realised that two
conceptual problems remain that new users might
struggle with:

1. The role of the PERMAMENT mapset remains
hard to grasp (the article wrongly suggests that
this should be the default mapset to log into).

2. The GUI does not speak the same language as
the CLI when it comes to the use of the terms
"map", "layer" and "monitor".

The first issue could be addressed by displaying
a warning of the kind "Do you really want to work
in the PERMANENT mapset" when a first-time login
attempt is made.

The second issue requires some consideration of
how "map" and "layer" are used in different ways
at the moment. Traditionally, a "map" is a GRASS
raster or vector dataset. In the GUI, what used to
be a "monitor" is now called "Map Display", whereas
what used to be "maps" is now called "Map layers"
(and the associated window title is "Layer Manager").
Novice users might stumble over this when they
discover the vector modules' "layer=" option and/or
any single-input module's "map=" option.

Also:
- The window title "Layer Manager" is somewhat
of a misnomer, since this is really the main window
and does a lot more than just managing a layer list.

- Using the location name as right-hand part of the
"Map Display" window title suggests that there could be
multiple locations per GRASS session (as there can be
multiple "Map Display" windows), which is misleading
(at least for languages that use left-to-right writing).

To bring back consistency, some review of terminology
across CLI and GUI seems in order. Since it seems to
me that it is easiest to change some strings in the
GUI, I would suggest something like this:

"Layer Manager" = "GRASS GIS - location (filename.gxw)"

"Map Display x" = "GRASS GIS - location (Monitor x)"

"Map layers" = "Maps"

"Display x" = "Monitor x"

Best,

Ben

--
Jachym Cepicky
Help Service - Remote Sensing s.r.o.
jachym.cepicky@gmail.com
HS-RS: jachym@hsrs.cz http://bnhelp.cz
http://les-ejk.cz

4

Hi,

last month or so we changed the location wizard to offer to
create a user mapset, which should gently nudge people in the
direction of not using the PERMANENT mapset for everyday work,
and exploring the concept of MAPSETS. as long as your user name
starts with a letter before "p" your one is the first offered.
even if not, you are more likely to click on your own name.

I see a funny thing where on linux wx organizes the [cancel][ok]
so the [cancel] is right under your mouse when you get to the
pop up for workspace mapset creation, but on windows the [ok]
is pre-selected.

so I think the problem is already partially addressed.

moving PERMANENT to .PERMANENT would break backwards compatibility
too much I think, and it is useful when you want to share e.g.
country coastline maps.

wrt "maps" wording I don't think there is too much confusion about
what they are.

"layer" is certainly used in two ways. Originally the vector
DB link ones were called "fields" (and still are in bits of the
vector API fns internally), but Radim decided to change that
after a long while. I can't quite remember, you'll have to dig in
the archives to see the logic in it. Anyway it was before the new
GUIs arrived so before the overlap.

wrt "display" vs "monitor" I don't think there is too much
confusion. at least new users not using 'd.mon x0' will not
have to worry about "monitors" since they will never see them.
and if they get it wrong it's still sort of the same thing
to them so they shouldn't notice the difference.
(ps, I just noticed the d.rast3d.py module description is a
bit fuzzy in what it will render to [nothing?] [note also in
grass 5 there was a d.3d module like m.nviz.image now does])

but probably "Layer manager" -> "GRASS GIS manager" makes more sense seeing it is both the layer manager and the GUI menus, and the python console, and the output window ... the trouble
with "layers" is that people coming from other GIS software
will naturally thing in the foreign terminology that they are
used to, and that was the GUI map kind.

(btw, maybe pack the Help menu to the far right side, and make
the "layer manager" window wider/bigger by default)

Hamish

5

On 06/05/2013 11:33 AM, Hamish wrote:

Hi,

last month or so we changed the location wizard to offer to create a
user mapset, which should gently nudge people in the direction of not
using the PERMANENT mapset for everyday work, and exploring the
concept of MAPSETS. as long as your user name starts with a letter
before "p" your one is the first offered. even if not, you are more
likely to click on your own name.

Perhaps the dialog that offers to create a new mapset
should also advise that there will always be a
PERMANENT mapset for common static base data.

I see a funny thing where on linux wx organizes the [cancel][ok] so
the [cancel] is right under your mouse when you get to the pop up for
workspace mapset creation, but on windows the [ok] is pre-selected.

That's probably because wxWidgets delegates the
management of the actual widgets to the OS' own
class library. And for some reason the Windows
designers thought it would be wise to have "OK"
selected by default. On Mac OS and Linux (GTK+),
different standard behaviour is used.

so I think the problem is already partially addressed.

I would still favour a warning message when
a user attempts to log into PERMANENT for the
first time (perhaps with a little "Do not show this
hint again" toggle button).

moving PERMANENT to .PERMANENT would break backwards compatibility
too much I think, and it is useful when you want to share e.g.
country coastline maps.

Yes, attempting to completely hide the PERMANENT
folder would be counter-productive. It is actually
a very useful thing -- if used properly.

Best,

Ben

wrt "maps" wording I don't think there is too much confusion about
what they are.

"layer" is certainly used in two ways. Originally the vector DB link
ones were called "fields" (and still are in bits of the vector API
fns internally), but Radim decided to change that after a long while.
I can't quite remember, you'll have to dig in the archives to see the
logic in it. Anyway it was before the new GUIs arrived so before the
overlap.

wrt "display" vs "monitor" I don't think there is too much confusion.
at least new users not using 'd.mon x0' will not have to worry about
"monitors" since they will never see them. and if they get it wrong
it's still sort of the same thing to them so they shouldn't notice
the difference. (ps, I just noticed the d.rast3d.py module
description is a bit fuzzy in what it will render to [nothing?]
[note also in grass 5 there was a d.3d module like m.nviz.image now
does])

but probably "Layer manager" -> "GRASS GIS manager" makes more sense
seeing it is both the layer manager and the GUI menus, and the python
console, and the output window ... the trouble with "layers" is that
people coming from other GIS software will naturally thing in the
foreign terminology that they are used to, and that was the GUI map
kind.

(btw, maybe pack the Help menu to the far right side, and make the
"layer manager" window wider/bigger by default)

Hamish

--
Dr. Benjamin Ducke, M.A.
{*} Geospatial Consultant
{*} GIS Developer

   benducke@fastmail.fm

6

Ben wrote:

Perhaps the dialog that offers to create a new mapset
should also advise that there will always be a
PERMANENT mapset for common static base data.

it offers a Help button which leads to the quickstart page
which explains all about that. Since there is a lot of
material to learn quickly, it's hard to say which feature
should be explained first. (need to explain what a mapset is
before you teach the nuances of using them)

I think the general solution is to add multi-sentence
tooltips all over the place - blanket the gui with them!
Perhaps if it gets too much a popup-delay or on/off switch
could go into the GUI preferences.

For the startup screen and location wizard mapset creation,
probably the explanatory text already in the esc-enter text
startup screen could be recycled directly for those.

it's a good discussion to have, since the learning curve is
real.

Hamish