There may be a problem with the space in the path of the
GRASS mapset ("C:\Program Files\..."). Spaces in mapset
or installation dir paths have always been problematic
for GRASS. Try putting the mapset into a more simple path,
like: "C:\grass-db\mapset".Ben ----- Original Message ----- From: "Pedro Venâncio" <pedrongvenan...@yahoo.com> To: "Benjamin Ducke" <benjamin.du...@oxfordarch.co.uk> Cc: sextante-users@lists.forge.osor.eu Sent: Tuesday, April 27, 2010 1:21:35 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: [Sextante-users] Integration with GRASS GIS Hello Ben, You are right, GRASS also crashes with v.net.alloc.net, I don't know why. However, I erased the v.net.alloc.exe and v.net.alloc.exe.manifest (.dll) from ..\grass-6.4.0svn\bin, returned trying to load GRASS in Sextante, everything runs without errors but in the end nothing happens, GRASS menu does not appear in Sextante. I've tried everything, even bringing the mapset that I have working well in Ubuntu, but without success... Have reinstalled everything on another PC with Windows XP and the result was the same... I am using GRASS folder: C:\OSGeo4W\apps\grass\grass-6.4.0svn and GRASS mapset: C:\Program Files\gvSIG-oade-2010-1.0.0\GRASS_Mapset\Pinhel\sextant (created directly in GRASS). I don't know what to do anymore... On Ubuntu was very easy, the only problem is just I can't put the help files (sextante_help) working. Thank you! Pedro --- On Mon, 4/26/10, Benjamin Ducke <benjamin.du...@oxfordarch.co.uk> wrote: Do you need v.net.alloc.exe for your work or could you just delete it from your GRASS installation? Of course, it's not supposed to just crash like that. I googled a little but could find no hint that there are problems with v.net.alloc.exe and Windows. Can you start GRASS via the Osgeo4W launcher and test if you can run v.net.alloc.exe OK? Cheers, Ben ----- Original Message ----- From: "Pedro Venâncio" < pedrongvenan...@yahoo.com > To: "Benjamin Ducke" < benjamin.du...@oxfordarch.co.uk > Sent: Monday, April 26, 2010 1:48:25 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: [Sextante-users] Integration with GRASS GIS Hello Ben, I send you the error message in the picture attached. Thank you! Pedro --- On Mon, 4/26/10, Benjamin Ducke < benjamin.du...@oxfordarch.co.uk > wrote: From: Benjamin Ducke < benjamin.du...@oxfordarch.co.uk > Subject: Re: [Sextante-users] Integration with GRASS GIS To: "Pedro Venâncio" < pedrongvenan...@yahoo.com > Cc: sextante-users@lists.forge.osor.eu , "Antonio Falciano" < afalci...@yahoo.it > Date: Monday, April 26, 2010, 12:35 PM What is the error message? Ben ----- Original Message ----- From: "Pedro Venâncio" < pedrongvenan...@yahoo.com > To: "Antonio Falciano" < afalci...@yahoo.it > Cc: sextante-users@lists.forge.osor.eu Sent: Monday, April 26, 2010 1:29:50 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: [Sextante-users] Integration with GRASS GIS Hello Antonio I managed to activate the GRASS modules in Ubuntu 9.10 but in Windows XP, when the modules are loading, it gives me an error with v.net.alloc.exe and then GRASS modules do not appear. I tried with gvsig official version and version OADE 2010. What is happening? GRASS (6.4.0svn) was installed with Osgeo4w. Thanks! Pedro Venâncio --- On Sat, 4/24/10, Antonio Falciano < afalci...@yahoo.it > wrote: Il 22/04/2010 19.18, Antonio Falciano ha scritto: > Hi all, > are there news about integration with GRASS? I have tested a bit the > latest SEXTANTE nightly build on Ubuntu 9.10 and win OSs, however it > seems that the GRASS script hardcoded in SEXTANTE is only able to import > layers into GRASS mapset (sometimes!), while the result layer(s) is(are) > not imported in gvSIG, maybe due to filepaths. See also tickets 11467 > and 14114. Am I wrong or is it a working progress yet? Hi all, integration with GRASS GIS finally starts to work now (nigthly build 20100423 AKA 1st SEXTANTE 0.6 SNAPSHOT)! :) For instance, I have executed v.delaunay on a point layer and this is what happens: a) the input layer is imported correctly into the mapset; b) the result layer is computed correctly by GRASS GIS; c) the result layer is exported correctly to gvSIG temporary folder (tmp-andami); d) the result layer is not loaded automatically in gvSIG, but manually (gvSIG shows a dialog asking for the shapefile to load from its temporary folder); e) the result layer (output) in the mapset is removed correctly, while the input layer not (it has to be removed directly from GRASS). In reference to point d), it seems that SEXTANTE request of loading output layer is faster than its computation in GRASS GIS because, when gvSIG shows the open dialog (see point d)), the sextante_batch_job.bat is still running. I used GRASS 6.4 SVN on a win XP machine. > Then, two cosmetic remarks... Firstly, I have noticed that > grass_logo.png and grassdocs.css are missing in sextante/grass folder > and so I have to copy and paste them manually in order to obtain the > GRASS help in its typical style. This issue is fixed now. Thanks. > Secondly, if I use the buffer SEXTANTE alg and a buffer WPS process (for > instance, that of 52N, which is the same) in the modeler, it's not > possible to distinguish one from the other, because they are represented > in the same way. So, a simple differentiation of GRASS modules from > SEXTANTE algs (and WPS processes) in the modeler could consist in > changing the icons of the graphical representation of procedures. It > would be more scenic too! ;) This minor (cosmetic) issue still remains. The integration with GRASS GIS is great enhancement of SEXTANTE capabilities. Great job, Victor! Cheers, Antonio -- Antonio Falciano http://www.linkedin.com/in/antoniofalciano _______________________________________________ Sextante-users mailing list Sextante-users@lists.forge.osor.eu https://lists.forge.osor.eu/listinfo/sextante-users _______________________________________________ Sextante-users mailing list Sextante-users@lists.forge.osor.eu https://lists.forge.osor.eu/listinfo/sextante-users ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. _______________________________________________ Sextante-users mailing list Sextante-users@lists.forge.osor.eu https://lists.forge.osor.eu/listinfo/sextante-users ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. _______________________________________________ Sextante-users mailing list Sextante-users@lists.forge.osor.eu https://lists.forge.osor.eu/listinfo/sextante-users
