Hi,
I wonder what is the reason for existence of `llayer` parameter in
`d.vect` module. I would guess that it's not reasonable to display
features (shapes) from `layer` 1 and cats/attributes from `llayer` 2
at the same time? You can display features from all layers
(`layer=-1`) and to display only labels for features from eg. layer 2
(`llayer=2`). I just wonder if it's not too big price, probably it can
be source of the user confusion. Why `d.vect map=map layer=2
display=cat` still displays categories for layer 1? And so on.
My suggestion is to remove `llayer` parameter from `d.vect` module.
The paremeter `layer` would be used to select all display types -
shapes, cats, attributes.
What do you think? Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
On 03/01/13 20:51, Martin Landa wrote:
Hi,
I wonder what is the reason for existence of `llayer` parameter in
`d.vect` module. I would guess that it's not reasonable to display
features (shapes) from `layer` 1 and cats/attributes from `llayer` 2
at the same time? You can display features from all layers
(`layer=-1`) and to display only labels for features from eg. layer 2
(`llayer=2`). I just wonder if it's not too big price, probably it can
be source of the user confusion. Why `d.vect map=map layer=2
display=cat` still displays categories for layer 1? And so on.
My suggestion is to remove `llayer` parameter from `d.vect` module.
The paremeter `layer` would be used to select all display types -
shapes, cats, attributes.
What do you think? Martin
-1
Two examples of where I find llayer useful:
- checking for results of automatic cleaning in v.in.ogr: you might to see the features and the cat on layer two indicating how many overlapping features were at the origin
- for all the v.net.* modules where by default arcs are in layer 1 and nodes in layer 2: I often display everything with layer=-1 and then display the node categories.
Moritz
It seems that setting the region extent from the cli (in current grass_trunk)
does not have any effect on a wx monitor.
Is it so?
Thanks, Nikos
On 08/01/13 11:37, Nikos Alexandris wrote:
It seems that setting the region extent from the cli (in current grass_trunk)
does not have any effect on a wx monitor.
What do you mean with "effect" ? If you chose to zoom tu current region extent, it zooms to the region you set on cli, or ?
Moritz
Nikos:
> It seems that setting the region extent from the cli (in current
> grass_trunk) does not have any effect on a wx monitor.
Moritz:
What do you mean with "effect" ? If you chose to zoom tu current region
extent, it zooms to the region you set on cli, or ?
Yes, it does.
I was expecting that the following would also work:
# launch grass70 in some LOCATION
# region was/is set to Raster_1
d.rast Raster
d.erase
# so far, so good
g.region rast=Raster_2
d.rast Raster_2 # shows nothing
#as stated by Moritz, it takes to zoom to the comp-region
Thanks, Nikos
On Tue, Jan 8, 2013 at 11:26 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
On 03/01/13 20:51, Martin Landa wrote:
Hi,
I wonder what is the reason for existence of `llayer` parameter in
`d.vect` module. I would guess that it's not reasonable to display
features (shapes) from `layer` 1 and cats/attributes from `llayer` 2
at the same time? You can display features from all layers
(`layer=-1`) and to display only labels for features from eg. layer 2
(`llayer=2`). I just wonder if it's not too big price, probably it can
be source of the user confusion. Why `d.vect map=map layer=2
display=cat` still displays categories for layer 1? And so on.
My suggestion is to remove `llayer` parameter from `d.vect` module.
The paremeter `layer` would be used to select all display types -
shapes, cats, attributes.
What do you think? Martin
-1
Two examples of where I find llayer useful:
- checking for results of automatic cleaning in v.in.ogr: you might to see
the features and the cat on layer two indicating how many overlapping
features were at the origin
- for all the v.net.* modules where by default arcs are in layer 1 and nodes
in layer 2: I often display everything with layer=-1 and then display the
node categories.
The arguments of Moritz make sense to me.
Anyway, I would prefer to get wxGUI vector display fixed before
changing d.vect: the layer option is silently reset by the GUI to the
default when you open the properties dialog, don't change anything,
just click ok.
Markus M