Wishes

[GoogleCodeExporter]

We are using JGrass in the Hydrology class at Politecnico di Torino since last 
year. There are some features we think could be very useful if they can be 
implemented into JGrass.
In the following our wish list is reported.
1)  Hypsographic curve:
a.  Representation with elevation on the x-axis;
b.  Representation starting with the minimum basin elevation instead of 0 m asl;
c.  Representation of the hypsometric curve.
2)  River network:
a.  Extraction of the main channel. To identify the main channel we apply the 
function hackstream, and then we use its output to mask the DTM in order to be 
able to represent the longitudinal profile of the main channel. However, if 
this could be done automatically it would be great;
b.  Determination of the topological width function for the river network;
c.  Determination of the informative entropy
3)  Raster profile tool: there is a way to make it scalable with the zoom?
4)  Raster summary tool: It is not working with the output of hacklength

Original issue reported on code.google.com by elisabar...@gmail.com on 3 Feb 2011 at 8:33

[GoogleCodeExporter]

Thanks for the feedback, we will consider the wishlist for sure!

Original comment by andrea.a...@gmail.com on 3 Feb 2011 at 9:50

• Changed state: Accepted

[GoogleCodeExporter]

These should be moved to the jgrasstools project.
Is there someone still around to talk about those wishes?

Original comment by andrea.a...@gmail.com on 23 Apr 2012 at 6:34

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

These wishes are intended for making Grass products more appealing for the 
average hydrology professional, who is willing to produce graphic results in 
some customary forms. Some of them are very practical in that they can be used 
in a printed form to obtain graphically a glimpse of some important basin 
parameters (i.e. the compensation line of the hypsographic curve for the 
average basin elevation)  

Original comment by pierluig...@gmail.com on 2 May 2012 at 9:37

[GoogleCodeExporter]

I agree with what you write. Which is also why I didn't want to loose this 
contribution to enhance the tools. 
The reason why I opened temporarily this issue, is because we finally finished 
the merging of JGrass into uDig and the whole processing power in the 
jgrasstools project [0]. There we have a whole pile of automated tests to keep 
the quality of the modules monitored.
JGrasstools can be both used in a gui in uDig [1] or in a serverside scripting 
environment.

We would be happy to discuss each of the above points in the jgrasstools 
mailinglist [2] if you would care to join and open a thread.

I will soon close the issue here in the JGrass tracker, since JGrass as such 
has been discontinued, while uDig + jgrasstools is highly supported.

[0] http://jgrasstools.org
[1] 
http://udig.refractions.net/confluence/display/EN/Introduction+to+the+Spatial+To
olbox
[2] http://groups.google.com/group/jgrasstools

Original comment by andrea.a...@gmail.com on 3 May 2012 at 7:26