[GRASS-user] modify feature's values interactively

GRASS GRASS user
1

Dear list,

is it possible within GRASS to modify feature’s values (of the feature attribute table) interactively (e.g. like in ArcGIS, where I can select an object within the view which then can be modified/removed…)?

Regards

Christian

Get news, entertainment and everything you care about at Live.com. Check it out!

2

Hi,

2008/3/26, christian Brandt <chrisbrandt74@hotmail.com>:

is it possible within GRASS to modify feature's values (of the feature
attribute table) interactively (e.g. like in ArcGIS, where I can select an
object within the view which then can be modified/removed...)?

you mean to modify attribute data of vector objects? If so, yes, you
can use v.digit or digitizer in wxPython GUI (experimental).

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

3

On 26/03/08 16:17, Martin Landa wrote:

Hi,

2008/3/26, christian Brandt <chrisbrandt74@hotmail.com>:

is it possible within GRASS to modify feature's values (of the feature
attribute table) interactively (e.g. like in ArcGIS, where I can select an
object within the view which then can be modified/removed...)?

you mean to modify attribute data of vector objects? If so, yes, you
can use v.digit or digitizer in wxPython GUI (experimental).

IMHO there should be a solution outside of the digitizer (i.e. without risking any alteration of the actual map), something along the lines of "d.what.vect -e".

Christian, if this is what you need, you will have to use it with the "old-style" x-monitors from the command line, i.e.:

d.mon x0
d.vect YourMap
d.what.vect -e YourMap

This is typically one element which would be GUI-only as I don't think it would make much sense to program an interactive command line version...

So maybe something to think about for wxgrass.

Moritz

4

Hi

2008/3/26, Moritz Lennert <mlennert@club.worldonline.be>:

>> is it possible within GRASS to modify feature's values (of the feature
>> attribute table) interactively (e.g. like in ArcGIS, where I can select an
>> object within the view which then can be modified/removed...)?
>
> you mean to modify attribute data of vector objects? If so, yes, you
> can use v.digit or digitizer in wxPython GUI (experimental).

Moritz:

IMHO there should be a solution outside of the digitizer (i.e. without
risking any alteration of the actual map), something along the lines of
"d.what.vect -e".

Christian, if this is what you need, you will have to use it with the
"old-style" x-monitors from the command line, i.e.:

d.mon x0
d.vect YourMap
d.what.vect -e YourMap

This is typically one element which would be GUI-only as I don't think
it would make much sense to program an interactive command line version...

So maybe something to think about for wxgrass.

hm, it wouldn't be so difficult to implement, sorry, back to the
reality;-) Basic implementation is here

http://trac.osgeo.org/grass/changeset/30745

see

http://grass.gdf-hannover.de/wiki/Image:Wxgui-vector-querying-gnulinux.png

Regards, Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

5

On 26/03/08 19:46, Martin Landa wrote:

Hi

2008/3/26, Moritz Lennert <mlennert@club.worldonline.be>:

>> is it possible within GRASS to modify feature's values (of the feature
>> attribute table) interactively (e.g. like in ArcGIS, where I can select an
>> object within the view which then can be modified/removed...)?
>
> you mean to modify attribute data of vector objects? If so, yes, you
> can use v.digit or digitizer in wxPython GUI (experimental).

Moritz:

IMHO there should be a solution outside of the digitizer (i.e. without
risking any alteration of the actual map), something along the lines of
"d.what.vect -e".

Christian, if this is what you need, you will have to use it with the
"old-style" x-monitors from the command line, i.e.:

d.mon x0
d.vect YourMap
d.what.vect -e YourMap

This is typically one element which would be GUI-only as I don't think
it would make much sense to program an interactive command line version...

So maybe something to think about for wxgrass.

hm, it wouldn't be so difficult to implement, sorry, back to the
reality;-) Basic implementation is here

http://trac.osgeo.org/grass/changeset/30745

see

http://grass.gdf-hannover.de/wiki/Image:Wxgui-vector-querying-gnulinux.png

Cool !

However, I just can't get it to work:

I have

GRASS 6.3.svn (spearfish60):~ > v.db.connect -p roads
Vector map <roads@PERMANENT> is connected by:
layer <1> table <roads> in database </home/mlennert/GRASS/DATA/spearfish60/PERMANENT/dbf/> through driver <dbf> with key <cat>

Querying in display mode works as expected:

East: 596271.961722
North: 4924483.851675

Map: roads
Mapset: PERMANENT
Type: Line
Line: 51
Longueur: 1416.211362
couche: 1
catégorie: 3

Driver: dbf
Database: /home/mlennert/GRASS/DATA/spearfish60/PERMANENT/dbf/
Table: roads
Key column: cat
cat : 3
label : secondary highway, hard surface

But when I try to query it in edit mode, I get:

"No database record available"

Also: probably the button's properties should be changed so that you can click on it again directly to change from one mode to the other. Currently you have to click on another button and then back on the query button to change mode.

Moritz

6

Hi,

2008/3/27, Moritz Lennert <mlennert@club.worldonline.be>:
[snip]

However, I just can't get it to work:

I have

GRASS 6.3.svn (spearfish60):~ > v.db.connect -p roads
Vector map <roads@PERMANENT> is connected by:
layer <1> table <roads> in database
</home/mlennert/GRASS/DATA/spearfish60/PERMANENT/dbf/> through driver
<dbf> with key <cat>

Querying in display mode works as expected:

East: 596271.961722
North: 4924483.851675

Map: roads
Mapset: PERMANENT
Type: Line
Line: 51
Longueur: 1416.211362
couche: 1
catégorie: 3

Driver: dbf
Database: /home/mlennert/GRASS/DATA/spearfish60/PERMANENT/dbf/
Table: roads
Key column: cat
cat : 3
label : secondary highway, hard surface

But when I try to query it in edit mode, I get:

"No database record available"

strange, I used for testing also 'roads' from spearfish60, seems to work.

Also: probably the button's properties should be changed so that you can
click on it again directly to change from one mode to the other.
Currently you have to click on another button and then back on the query
button to change mode.

You don't need to change a tool, double-click on 'query' should show menu again.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

7

Martin:
http://grass.gdf-hannover.de/wiki/Image:Wxgui-vector-querying-gnulinux.png

Moritz:

Cool !
However, I just can't get it to work:
I have

GRASS 6.3.svn (spearfish60):~ > v.db.connect -p roads
Vector map <roads@PERMANENT> is connected by:

...

Querying in display mode works as expected:

...

label : secondary highway, hard surface

But when I try to query it in edit mode, I get:

"No database record available"

just a guess: you were not in the PERMANENT mapset when you tried this
test? You can only edit maps in the current mapset (or at least that
should be the case) -- and the same is true for DBs.

If that is the problem here, I guess we need to add some more tests and
more appropriate error messages.

Hamish

      ____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs

8

On 28/03/08 16:48, christian Brandt wrote:

Dear Moritz,

after implementation of wxPython GUI I started with a new grass
session with the command grass63 -wxpython. Then the following
message came up:

grass63 -wxpython Cleaning up temporary files..... Starting GRASS ...
Traceback (most recent call last): File
"/usr/local/grass-6.3.0RC5/etc/wxpython/gis_set.py", line 28, in from
gui_modules import utils File
"/usr/local/grass-6.3.0RC5/etc/wxpython/gui_modules/utils.py", line 1

There must be more to the traceback, and the interesting part is always at the end...

Also: it would be helpful if you could give the following info when reporting issues with wxgrass:

- OS
- python version
- wxpython version

Moritz

Date: Thu, 27 Mar 2008 10:18:22 +0100

From: mlennert@club.worldonline.be To: landa.martin@gmail.com CC:
chrisbrandt74@hotmail.com; grass-user@lists.osgeo.org Subject: Re:
[GRASS-user] modify feature's values interactively

On 26/03/08 19:46, Martin Landa wrote:

Hi

2008/3/26, Moritz Lennert :

is it possible within GRASS to modify feature's values (of
the feature attribute table) interactively (e.g. like in
ArcGIS, where I can select an object within the view which
then can be modified/removed...)?

you mean to modify attribute data of vector objects? If so,
yes, you can use v.digit or digitizer in wxPython GUI
(experimental).

Moritz:

IMHO there should be a solution outside of the digitizer (i.e.
without risking any alteration of the actual map), something
along the lines of "d.what.vect -e".

Christian, if this is what you need, you will have to use it
with the "old-style" x-monitors from the command line, i.e.:

d.mon x0 d.vect YourMap d.what.vect -e YourMap

This is typically one element which would be GUI-only as I
don't think it would make much sense to program an interactive
command line version...

So maybe something to think about for wxgrass.

hm, it wouldn't be so difficult to implement, sorry, back to the reality;-) Basic implementation is here

http://trac.osgeo.org/grass/changeset/30745

see

http://grass.gdf-hannover.de/wiki/Image:Wxgui-vector-querying-gnulinux.png

Cool !

However, I just can't get it to work:

I have

GRASS 6.3.svn (spearfish60):~> v.db.connect -p roads Vector map is
connected by: layer table in database through driver with key

Querying in display mode works as expected:

East: 596271.961722 North: 4924483.851675

Map: roads Mapset: PERMANENT Type: Line Line: 51 Longueur:
1416.211362 couche: 1 catégorie: 3

Driver: dbf Database:
/home/mlennert/GRASS/DATA/spearfish60/PERMANENT/dbf/ Table: roads Key column: cat cat : 3 label : secondary highway, hard surface

But when I try to query it in edit mode, I get:

"No database record available"

Also: probably the button's properties should be changed so that
you can click on it again directly to change from one mode to the
other. Currently you have to click on another button and then back
on the query button to change mode.

Moritz

_________________________________________________________________ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline