[GRASS-user] geotagging of sound recordings for dialect project

TclTk NVIZ is still on the menu in 6.4. Look under the file menu for 3D.

Michael Barton

On Aug 26, 2009, at 9:00 AM, grass-user-request@lists.osgeo.org wrote:

Date: Wed, 26 Aug 2009 08:04:47 -0700 (PDT)
From: Hamish <hamish_b@yahoo.com>
Subject: Re: [GRASS-user] geotagging of sound recordings for dialect
  project
To: Bov <dialectproject@trans-mania.com>
Cc: grass-user@lists.osgeo.org
Message-ID: <54321.36113.qm@web110003.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=us-ascii

Bov wrote:

I installed Grass 6.4.0RC5 Windows and try to find my way.
I couldn't start the vector digitizer yet:

"Vector digitizer is not available (No module named
grass6_wxvdigit)"

we have not yet figured out to build that on Windows yet, as
we use an existing copy of Python from Python.org, but their
package doesn't provide all the details we need to link our
programs into theirs. Usually it isn't a problem but the vector
digitizer and wxGUI 3D viewer are partly written in C++ which
need exact addresses for things.

for now you'll have to use the old Tcl/Tk v.digit tool, to
start it type "v.digit" at the Cmd> prompt. It's not as slick
but it is well tested and gets the job done.

for the 3D visualization you need to start with the MSys prompt
and type "nviz" at the terminal prompt.

good luck,
Hamish

Hamish

> you need to start with the MSys prompt and type "nviz" at the terminal
> prompt.

Michael wrote:

TclTk NVIZ is still on the menu in 6.4. Look under the file menu for 3D.

yeah, but unfortunately on WinGrass that menu item doesn't work from the
wxGUI. Same result if you type "nviz" at the Cmd> prompt. It just silently
exits, the command output tab gives a completion time, 0 sec elapsed.
I've got no idea why. From the menu at least you get the parser GUI
showing up, but then nothing when you hit [Run].

The only way I've found to start it when using the wxGUI is from the Msys
prompt.

see https://trac.osgeo.org/grass/report/13
"WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run"

Hamish