[GRASS-user] i.vpoints

GRASS GRASS user
1

Thanks to those who helped sort out my CVS install probelms. This look to be going better now, at least I have both 6.0 and 6.1 CVS versions up and running.

Time now then to revisit the i.vpoints trouble...

...we still don't see our vector point layers in the top right square. In 6.0 we get the option to show the vector layers but nothing shows after selecting (other than any hand placed GCPs we might have made). In 6.1 the program hangs (monitor turns white) when we click the "vector" button at the bottom of the screen.

How might we go about seeing our point vectors in (any version) of i.vpoints?

cheers
Dave

2

David wrote:

Thanks to those who helped sort out my CVS install probelms. This look
to be going better now, at least I have both 6.0 and 6.1 CVS versions
up and running.

Time now then to revisit the i.vpoints trouble...

...we still don't see our vector point layers in the top right square.
In 6.0 we get the option to show the vector layers but nothing shows
after selecting (other than any hand placed GCPs we might have made).
In 6.1 the program hangs (monitor turns white) when we click the
"vector" button at the bottom of the screen.

How might we go about seeing our point vectors in (any version) of
i.vpoints?

update to the latest (i.e. within the last few hours) version of
GRASS 6.1 from CVS*. i.vpoints is *much* improved in the last few
days- I think I've squashed most of the worst bugs now. This afternoon I
activated the reverse warp-overlay for vector points (access from the
analyze menu).

[*] updating i.vpoints and i.find should be enough

I haven't seen a GUI solution to force a terminal start, so I'm going to
revert the G_parser() change for i.vpoints, i.points, and r.digit.

Hamish

3

David wrote:

In 6.0 we get the option to show the vector layers but nothing shows
after selecting (other than any hand placed GCPs we might have made).

I only implemented the drawing of points in 6.1 last week.

In 6.1 the program hangs (monitor turns white) when we click the
"vector" button at the bottom of the screen.

Paul fixed this bug yesterday. i.find was failing (that's the tool which
lists available maps).

Hamish

4

On Wed, 28 Jun 2006, Hamish wrote:

I haven't seen a GUI solution to force a terminal start, so I'm going to
revert the G_parser() change for i.vpoints, i.points, and r.digit.

Not totally sure what you mean but does
GRASS_UI_TERM=1
export GRASS_UI_TERM

not do this? Stops a Tcl/Tk dialog box popping up and the old command line parser interface appears anyway.

Paul

5

Paul Kelly wrote:

> I haven't seen a GUI solution to force a terminal start, so I'm
> going to revert the G_parser() change for i.vpoints, i.points, and
> r.digit.

Not totally sure what you mean but does
GRASS_UI_TERM=1
export GRASS_UI_TERM

not do this? Stops a Tcl/Tk dialog box popping up and the old command
line parser interface appears anyway.

Yes! Exactly what I need. Thanks.

I've reworked lib/init/grass-run.src (-> $GISBASE/etc/grass-run.sh)
see below

It still doesn't work 100% (from gis.m i.group doesn't find maps*,
r.digit can't find selected monitor), but it lets us have those modules
use G_parser().

[*] I_get_group_ref() fails if @mapset is attached to group name, I
should have this fixed soon.

To prevent the GUI startup from the command line, in each term-only module
we can add:

    /* must run in a term window */
    setenv("GRASS_UI_TERM","1",TRUE);

before G_gisinit (argv[0]);

ie these ones:

g.access
g.setproj
d.font
r.digit
r.le.setup
d.rast.edit
i.points
i.vpoints
i.ortho.photo
i.class

look ok?

Hamish

==== grass-run.sh ==================================================

#!/bin/sh
# script to launch GRASS commands

# force command line startup mode
GRASS_UI_TERM=1
export GRASS_UI_TERM

# workaround for systems with xterm is setuid/setgid
# http://grass.itc.it/pipermail/grass5/2004-September/015409.html

LD_LIBRARY_PATH_VAR=$GRASS_LD_LIBRARY_PATH
export LD_LIBRARY_PATH_VAR

# run command
$@

EXIT_VAL=$?
if [ $EXIT_VAL -ne 0 ] ; then
   echo
   echo "ERROR: $1 exited abnormally. Press <enter> to continue."
   read
fi

exit $EXIT_VAL

6

Wow!! That's working great now. You know I had a PhD student telling me if it wasn't working soon she'd start using ArcView - arrrggghhh the horror. Thanks Hamish for all the work you put into that.

Warm regards
Dave

On Wed, Jun 28, 2006 at 08:46:32PM +1200, Hamish wrote:

David wrote:
> Thanks to those who helped sort out my CVS install probelms. This look
> to be going better now, at least I have both 6.0 and 6.1 CVS versions
> up and running.
>
> Time now then to revisit the i.vpoints trouble...
>
> ...we still don't see our vector point layers in the top right square.
> In 6.0 we get the option to show the vector layers but nothing shows
> after selecting (other than any hand placed GCPs we might have made).
> In 6.1 the program hangs (monitor turns white) when we click the
> "vector" button at the bottom of the screen.
>
> How might we go about seeing our point vectors in (any version) of
> i.vpoints?

update to the latest (i.e. within the last few hours) version of
GRASS 6.1 from CVS*. i.vpoints is *much* improved in the last few
days- I think I've squashed most of the worst bugs now. This afternoon I
activated the reverse warp-overlay for vector points (access from the
analyze menu).

[*] updating i.vpoints and i.find should be enough

I haven't seen a GUI solution to force a terminal start, so I'm going to
revert the G_parser() change for i.vpoints, i.points, and r.digit.

Hamish

7

Hamish wrote:

To prevent the GUI startup from the command line, in each term-only module
we can add:

    /* must run in a term window */
    setenv("GRASS_UI_TERM","1",TRUE);

before G_gisinit (argv[0]);

setenv() is a BSD-ism; please use putenv() instead.

--
Glynn Clements <glynn@gclements.plus.com>