WinGRASS 6 Current Status: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(+category)
(vector DB problems)
Line 17: Line 17:
** Note: also in lib/gis/popen.c and lib/gis/system.c (use those implementations?)
** Note: also in lib/gis/popen.c and lib/gis/system.c (use those implementations?)
* r.terraflow: getrusage()
* r.terraflow: getrusage()
* Vector-DB connection:
** M Lennert: I had hoped that Radim's patch for dbmi_client (http://grass.itc.it/pipermail/grass5/2006-December/028118.html) might solve the issue I've had with the db protocol errors, but apparently this is not the case. When I push the 'show the attribute columns' in a vector panel, I still get
<pre>
*******
Displaying column types/names for database connection of layer 1:
dbmi: Protocol error
Cannot open table <streams>
********
and a 'v.db.select' on the same map gives me:
********
'vector/streams' was found in more mapsets (also found in user1).
dbmi: Protocol error
Cannot open select cursor
*********
</pre>
* P Kelly:  I can confirm similar problems. I tried to import a Shapefile with v.in.ogr. I went quite deep into debugging it and got nowhere at all, although I should have taken better notes. I did confirm though that compiling the library with -mwindows as Radim suggested on the list made no difference either. I think trying with a different database, PostgreSQL perhaps is the next big step to debugging this. See if the behaviour is the same as with dbf and if not we can isolate it a bit more.


== Known problems ==
== Known problems ==

Revision as of 08:32, 7 February 2007

This page describes the current status of winGRASS development. Precompiled native winGRASS packages are available here.

What is missing?

  • Display drivers: socket
    • Use gis.m instead of monitors.
    • Make gis.m Output window more like xterm. No need to hit Run.
    • Is there any way that the Map Display in gis.m can interact with console commands? IPC? File Alteration Monitor?
  • i.class: SIGALRM, SIGTSTP (are these signals important?)
  • wait() in:
    • i.ortho.photo/photo.2image: wait()
    • i.ortho.photo/photo.2target: wait()
    • i.points: wait()
    • i.vpoints: wait()
    • Note: also in lib/gis/popen.c and lib/gis/system.c (use those implementations?)
  • r.terraflow: getrusage()
  • Vector-DB connection:
 *******
 Displaying column types/names for database connection of layer 1:
 dbmi: Protocol error
 Cannot open table <streams>
 ********

 and a 'v.db.select' on the same map gives me:

 ********
 'vector/streams' was found in more mapsets (also found in user1).
 dbmi: Protocol error

 Cannot open select cursor
 *********
  • P Kelly: I can confirm similar problems. I tried to import a Shapefile with v.in.ogr. I went quite deep into debugging it and got nowhere at all, although I should have taken better notes. I did confirm though that compiling the library with -mwindows as Radim suggested on the list made no difference either. I think trying with a different database, PostgreSQL perhaps is the next big step to debugging this. See if the behaviour is the same as with dbf and if not we can isolate it a bit more.

Known problems

  • metacharacter escape in "sh -c '$cmd'"
  • modules not working: r.proj (v.proj too?), r.surf.rst, v.neighbors, v.kernel, r.cost
  • Cannot open Help pages.
  • Have to add c:\mingw\bin to PATH on some systems.
    • You should have typed c:/mingw instead of c:\mingw when asked by the MinGW installer.
  • Have to type "exit" in the console to save ~/.grassrc file. Then, close gis.m to finish the session.
  • A previous installation of grass under cygwin is likely to cause problems with WinGrass. Follow the directions to remove cygwin at http://cygwin.com/faq/faq-nochunks.html#faq.setup.uninstall-all

The following items cannot be fixed in the near future:

TclTk issues

Other libraries

GDAL

  • lib/gis/OBJ.*/fmode.o is needed for any GRASS related modules.
  • modified ltmain.sh to install binary files from wrapper scripts.