jgrass-users — mailinglist for support to JGrass users

[JGrass-users] SVN cleanup - for developers - remember Monday

[Andrea A. <and...@gm...>]

Hi all,
since JGrass is heavily working towards the 3 version merging with
udig, also the SVN structure will change, reflecting a bit more the
professional behavior of udig. The future structure will be:

jgrass3.0
 |-- branches   # for future branches and parallel projects
 |-- docs	# for documentation
 |-- tags	# versions
 |-- trunk	# the development version
 |-- community	# a folder for community playground
        |-- moovida	# moovida's plugins until they are not ready
to go trunk

By this weekend everything else apart of the last jgrass version
(jgrassrevolutions) will be history, in fact SVN history and will always
be available, but will be removed from the main svn view in order to
gain a bit more order and less scatteredness.
After the release of JGrass 3.0 in February (hopefully), also
jgrassrevolution will disappear. So please for those interested in some
of the older versions of JGrass, act now to get your stuff. Monday the
repository will look much more clean.
Developers of the new JGrass, on Monday take some time to find the
modules you are working on. They won't be all on trunk, which should
get the version that will first be part of the udig updating mechanism
and therefore compile properly and have no problems (apart obviously
of some nasty bugs that can't miss).

After working with the udig community at foss4g2007 I'm really sure that
joining them has been one of the best moves for JGrass
ever. I ask the users to be patient and wait for the next release to
come. It will be worth it.

Have a great day
Andrea

[JGrass-users] some mixed questions

[andrea a. <and...@gm...>]

>> 1) When I create the workspace (new location) and I choose the
>> projection and the georeference, the program changes the original
>> eastern, so I have to cut and paste the original data in the
>> DEFAULT_WIND and WIND files of the PERMANENT folder of the workspace.

What do you mean by chose the georeference? What do you mean by
changes the original eastern? We need examples that can be reproduced.

>> 2) The JGrass did not allow me to create a new folder (new
>> mapset) with the data inside the new location or workspace, so I had
>> to work in the PERMANENT location. Is this normal? Maybe later I have
>> to cut and paste the folder in a new place, but I do not open the new
>> map set as an available option. In few works the program does not let
>> to create a folder outside the PERMANENT directory.

Never had that problem before. We always suggest to create a new
mapset and work just in that.
What is the error message?


>> 3) Working with the Faln DTM example, which Erica gave me the
>> first time for beginning practicing with JGrass, I did not have
>> problems while I was working on it. Although, when I load the
>> workspace the raster map displays moved from the working area, this
>> problem is corrected used the rebuilt button, but I do not understand
>> why this happens.

That is an old bug which we will not solve, since we are working on
the jgrass-udig version. However the manual states that the refresh is
needed to solve distortions that can occur in certain cases.

>> 4) When I work with more than one workspace loaded, and then I
>> close one of them, I have problems in viewing the property window or
>> with the Menu bar, because the GIS, Raster, Vector, and and the other
>> menu bars disappear.

The multiple workspace support never came to full functionality.
Please browse also through the archives of the mailinglists, most of
the problems you see, were discussed already.

>> 5) Also when I am working with various workspaces, some buttons
>> do not work and I can not visualize a map because a legend appears
>> saying: "Map is completely outside the visible area". In the Faln
>> study case I could solve the problem using the Region tool manager
>> button, but with the Brenta basin I could not do that, because the
>> program remained processing the order and never ended.
>> 6) The diameter and Euclidean distance are measured on planar
>> projection or taking into account the topography?

I suppose on planar, but that has to be asked to who wrote the module
(which from today will b on vacation for two weeks). Probably someone
else will answer.

>> 7) Is not possible to visualize many legends?

No

>> 8) I see that the Horton Machine Menu is the main tools on the
>> fluvial, hydrologic and geomorphological analysis, but the tutorial
>> manual for applying the Horton analysis on the DEM, I see that it is
>> disorganized between the manual and the button order. For me and
>> ordinary users, it would be easier to have the buttons in the
>> corresponded and successive order of the analysis.

I don't think there is one and only way of doing things. That is why
they are logically separated. You have to know what you do before you
do :)

>> 9) In the properties sheet it would be very useful to know the
>> /dependences/ of the created maps.

What do you mean by that?

>> 10) When somebody asks a particular task to the program, this
>> develops the procedure and generates the map, but the process finishes
>> and then you have to search the map using the display raster map
>> button. It would be easier for the users that when the program
>> finishes one procession, then gives the opportunity (with an appearing
>> window) to choose either display the new map or not.

JGrass has always been founded for the more scientific part and misses
some of the needed user interaction. Contributers are very welcome.


Andrea

Re: [JGrass-users] [JGrass-Utenti] Fwd: Ciao. Here some questions related to JGrass

[Andrea A. <and...@gm...>]

Please post on this list in Italian. This is not the English list, I'll
forward it to jgr...@li....

Andrea



Riccardo Rigon probaly wrote:
> 
> 
> Begin forwarded message:
> 
>> *From: *"Jose Busnelli" <jos...@gm...
>> <mailto:jos...@gm...>>
>> *Date: *July 23, 2007 11:54:44 AM GMT+02:00
>> *To: *"Rigon Riccardo" <ric...@in...
>> <mailto:ric...@in...>>,  "Riccardo Rigon"
>> <ric...@fa... <mailto:ric...@fa...>>
>> *Subject: **Ciao. Here some questions related to JGrass*
>>
>> Lunedi' 23 Luglio 2007.
>>
>>  
>>
>> Summary of the main problems and doubts working with the softwares:
>>
>>  
>>
>> I) JGrass (on windows XP):
>>
>>  
>>
>> 1)      When I create the workspace (new location) and I choose the
>> projection and the georeference, the program changes the original
>> eastern, so I have to cut and paste the original data in the
>> DEFAULT_WIND and WIND files of the PERMANENT folder of the workspace.
>> 2)      The JGrass did not allow me to create a new folder (new
>> mapset) with the data inside the new location or workspace, so I had
>> to work in the PERMANENT location. Is this normal? Maybe later I have
>> to cut and paste the folder in a new place, but I do not open the new
>> map set as an available option. In few works the program does not let
>> to create a folder outside the PERMANENT directory.
>> 3)      Working with the Faln DTM example, which Erica gave me the
>> first time for beginning practicing with JGrass, I did not have
>> problems while I was working on it. Although, when I load the
>> workspace the raster map displays moved from the working area, this
>> problem is corrected used the rebuilt button, but I do not understand
>> why this happens.
>> 4)      When I work with more than one workspace loaded, and then I
>> close one of them, I have problems in viewing the property window or
>> with the Menu bar, because the GIS, Raster, Vector, and and the other
>> menu bars disappear.
>> 5)      Also when I am working with various workspaces, some buttons
>> do not work and I can not visualize a map because a legend appears
>> saying: "Map is completely outside the visible area". In the Faln
>> study case I could solve the problem using the Region tool manager
>> button, but with the Brenta basin I could not do that, because the
>> program remained processing the order and never ended.
>> 6)      The diameter and Euclidean distance are measured on planar
>> projection or taking into account the topography?
>> 7)      Is not possible to visualize many legends?
>> 8)      I see that the Horton Machine Menu is the main tools on the
>> fluvial, hydrologic and geomorphological analysis, but the tutorial
>> manual for applying the Horton analysis on the DEM, I see that it is
>> disorganized between the manual and the button order. For me and
>> ordinary users, it would be easier to have the buttons in the
>> corresponded and successive order of the analysis.
>> 9)      In the properties sheet it would be very useful to know the
>> /dependences/ of the created maps.
>> 10)  When somebody asks a particular task to the program, this
>> develops the procedure and generates the map, but the process finishes
>> and then you have to search the map using the display raster map
>> button. It would be easier for the users that when the program
>> finishes one procession, then gives the opportunity (with an appearing
>> window) to choose either display the new map or not.
>>
>>  
>>
>> These are some notes related to the JGrass that I compiled during the
>> exploration of the program using the Spearfish, Faln and Brenta DEM.
>> For sure I will have more questions related to the JGrass. I am
>> reading and exploring the other supporting softwares of the JGrass now
>> and I am taking notes about it. I am going to ask you again about the
>> new doubts as soon as possible.
>>
>>  
>>
>> Thank you.
>> Regards.
>> Jose Busnelli.
>> Argentina
>>
>>
> 
> ________________________________________________________________        
> *Universita` di Trento         Dipartimento di Ingegneria Civile  e 
> Ambientale/CUDAM*
> Via Mesiano, 77, 38050  Trento      (ITALIA)                            
> *E-mail*:  ric...@in...
> <mailto:ric...@in...>  
> *Ph*: +390461882614-10    *Fax*:+390461882672
> *Web page*: http://www.ing.unitn.it/dica/hp/?user=rigon
> *JGrass (*Open Source GIS): http://www.jgrass.org/
> *GEOtop* (Open Source distributed hydrological
> model):  http://www.geotop.org/
> _______________________________________________________________        
>                                                 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> jgrass-utenti mailing list
> jgr...@li...
> https://lists.sourceforge.net/lists/listinfo/jgrass-utenti

Re: [JGrass-users] Jgrass - problems

[Andrea A. <and...@gm...>]

Hi Aristófanes,
please in future send problems about JGrass only to the mailinglist and
not to our personal addresses. You can find them here:
http://www.jgrass.org/cgi-bin/moin.cgi/MailingList

The first problem you have, is a known problem, but the creation of a
new workspace should really work. Did you follow the steps in the manual?

Andrea


> I went to try to use Jgrass, but it gave the following mistakes in the
> execution:
> 
> a.       When load the default workspace
> 
> “jgrass.map.GrassLocationException: Error accessing GRASS location file
> file:/home/grassdata\spearfish\PERMANENT\DEFAULT_WIND”
> 
> Details:
> 
> “jgrass.map.GrassLocationException: Error accessing GRASS location file
> file:/home/grassdata\spearfish\PERMANENT\DEFAULT_WIND
> at jgrass.map.GrassLocation.<init>(GrassLocation.java:158)
> at jgrass.util.Grass.setLocation(Grass.java:296)
> at jgrass.util.Configuration.loadWorkspace(Configuration.java:938)
> at
> jgrass.handler.workspace.LoadWorkspaceHandler$1.run(LoadWorkspaceHandler.java:159)
> 
> at java.awt.event.InvocationEvent.dispatch(Unknown Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)”
> 
> b.       When create a new workspace
> 
> “the selected directory is not a valid GRASS location!”
> 
> This mistake happens in any directory
> 

> -- 
> 
> Could you help me?
> 
> Best regards,
> 
> Ari
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Aristófanes Corrêa Silva
> Universidade Federal do Maranhão - UFMA
> Departamento de Engenharia Elétrica - DEE
> Laboratório de Processamento de Análise de Imagens (LabPAI)
> E-mail: ar...@de..., ari...@gm..., ar...@pe...
> Fone: 98 2109 8832 / Fax: 98 2109 8241
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 
> 
> 

[JGrass-users] JGrass goes Udig

[Andrea A. <and...@gm...>]

Dear members of the JGrass list, dear community.

The decision has been taken to join the UDIG team with all the 
JGrass stuff that is possible to migrate to their project.

Our opinion is that the JGrass project will gain several advantages 
from this merging event, in organisation, as well as community, as 
well as vector tecnology, as well as etc. etc.

The time is mature to take this step for our community and even if 
the JGrass project will virtually stop because of the migration time, 
I'm pretty sure that this will be the last time we will suffer of 
heavy framework issues.

Acknowledgements go to the members of the UDIG team, that accepted 
our offer and to guide us with their help through the migration process. 

Also thanks to Riccardo Rigon from the C.U.D.A.M., who believes and 
trusts us and supports us also economically in this migration process.

Thanks to everyone who cared and cares. We will meet on the IRC chat 
of UDIG on 10.00 PST (this is not completely fixed, I'll keep you uptodate) 
to discuss the feasibility and steps of this migration.

Best regards,
Andrea Antonello

Re: [JGrass-users] [JGrass-Utenti] Projection and format issues

[Andrea A. <and...@gm...>]

Hi Benoit,
I redirect the mail to the English user list,
so we can be gladly write in English.

> 	and best wishes for this new year.

Thanks to you and best wishes back.
I've been on vacation, so sorry for the delay.

> 		o pentium IV, 512 Mo Ram, 'Intel 82852/82855 GM/GME Graphic controller'  
> graphic card.
> 
> 	* I have used the tutorial 'jgrass_manual_ENG' to test the main menus  
> with the spearfish dataset, but I'm actually meeting problems with few  
> points to go further.
> 
> 		o first of all, when trying to open the original spearfish location, I  
> have the following message
> 
> 			'jgrass.map.GrassLocationException: Error accessing GRASS location file  
> file:/home/grassdata\spearfish\PERMANENT\DEFAULT_WIND'

This is an annoying bug thatr was introduced in the last release. We
already fixed it but have problems with the new release. We will
probably release an unofficial version with some of the issues solved.

> 			Untill now, I have been around this issue by copying the spearfish  
> directory into a new one (c:/grassdata), and creating a new location from  
> this directory. Anyway, this problem might be in connexion with the  
> following.

This is ok, also you could simply create a new workspace mapped on your
original folder.

> 		o I have tried to create a new location to import my own DEM data and  
> manipulate them. My data are in SRTM format and WGS84 - LatLong. I meet  
> problems :
> 
> 			1/ to create a workspace in such a reference system (the process is  
> stopped from the window 'Select Grass Geographic window', although a  
> directory is created on the hard drive)
> 			2/ to import data into the workspace actually created.
> 
> 		As far as I have read, Jgrass is not very happy with the WGS 84  
> lat/long, but I cannot manage to save my DEM with a projection. I have  
> tried tu use Manifold and Landserf, but the projection is not saved, I end  
> back with lat/long data.
> 		After some tries, I have managed to create a file into the 'fcell'  
> directory, by importing an ascii grid format (.grd). Unfortunately, it  
> displays nothing by now, although it weights 1,6 Mo...
> 
> 		I guess I'm not to far from a solution, but another (and competent)  
> point of view could help me to solve the problem,

I'm very sorry, but lat/long is not supported i n JGrass at the moment.
The only workaround is (for what I remember):
- to create the destination workspace in a metric projection
- from there use r.in.gdal to import the data in lat-long, but telling
the command to create a _new location_ for that data
- at that point you have an invisible workspace in lat-long from which
you can reproject to your metric location

I know it is not so funny, but at the moment it is the only way.


Ciao
Andrea

[Jgrass-users] errore h.extractnetowork

[Lia R. <ro...@em...>]

jgr...@li...
Sono incappata in un errore nell\'estrazione del reticolo, da cui non rie=
sco
ad uscire.
Sto utilizzando (in primo tentativo) il metodo della soglia dell\'area
contribuente.
Inserisco correttamente i file che mi vengono richiesti nell\'interfaccia
grafica:
- mappa delle direzione di flusso con uscite marcate (da markoutlet)
- mappa delle aree contribuenti (da draindir)
e compilo gli altricampi sull\'area di soglia e sulla mappa di output.
Lanciato il comando, inizia la lettura dalla mappa delle dir di flusso, m=
a
poi il programma si blocca sullo 0% delle aree contribuenti. Non c\'=E8
problema di RAM. Mi appare l\'errore che copio qui sotto...
Di cosa si tratta?=20
>>>
Sourced file: inline evaluation of: \"import
bsh.commands.h.extractnetwork.*\"; h:extractnetwork.invoke(\"--usegui\", =
thi
. . .
\" : Method Invocation h_extractnetwork.invoke : at Line: 3 : in file:
inline evaluation of \"import
bsh.commands.h.extractnetwork.*; h_extractnetwork.invoke(\"--usegui\", th=
i .
. . \" : h_extractnetwork .invoke ( \"--usegui\" , thi
.interpreter , this .namespace )
Taget exception; java.lang.NullPointerException
 at bsh.BSHMethodInvocation.eval(Unknown Source)
 at bsh.BSHPrimaryExpression.eval(Unknown Source)
 at bsh.BSHPrimaryExpression.eval(Unknown Source)
 at bsh.Interpreter.eval(Unknown Source)
 at bsh.Interpreter.eval(Unknown Source)
 at jgrass.engine.GrassEngineLocal.run(GrassEngineLocal.java:418)
>>>=20
 --
 Email.it, the professional e-mail, gratis per te: http://www.email.it/f
=20
 Sponsor:
 Mai come oggi la comunicazione integrata =E8 fondamentale per la tua
attivit=E0..raggiungi i tuoi clienti in tutto il mondo affidandoti alla n=
ostra
professionalit=E0 ed esperienza. icecube communication
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=3D5875&d=3D20061=
216