Difference between revisions of "Wx.stream GSoC 2011"
|Line 75:||Line 75:|
== Documentation ==
== Documentation ==
== Timeline ==
*23 May - 5 Jun : design interface based on other similar software
* 23 May - 5 Jun : design interface based on other similar software
*6 Jun - 15 Jul : midterm goal: get a
* 6 Jun - 15 Jul : midterm goal: get a widget
*16 Jul - 31 Jul: add functionality and documentation
* 16 Jul - 31 Jul: add functionality and documentation
*1 Aug - 15 Aug : testing
* 1 Aug - 15 Aug : testing
* goal: working GUI for grass7
== Weekly Reports, from SoC mailing list ==
== Weekly Reports, from SoC mailing list ==
Revision as of 11:49, 24 June 2011
Student: Margherita (Madi) Di Leo
Mentor: Jarek Jasiewicz
Organization: OSGeo - Open Source Geospatial Foundation
Title: Graphical User Interface for the hydrological tools r.stream* in GRASS GIS
Aim of the project
In GRASS GIS new modules suitable for hydrological analysis have been developed, r.stream*. My idea is to develop a wxpython GUI for r.stream* that allows to see the preview of the hydrological analysis over a part of a map and then decide if apply the analysis or not. It will include "multiple previews". Every result can be saved as an image and set of parameters for future use in additional "preview windows", next choose from group of possible parameters that which is most suitable.
- First draft of main r.stream GUI
I thought to add in Map display a button that allows to select a point on the DEM that will be the center of the preview. So the region is determined by the script and not by the user. This can avoid the warning message for the user if the region selected is too big.
Selecting the point on DEM raises a window with different tabs. Each tab corresponds to a r.stream command. In each tab there are text boxes in which user inserts parameters required to run the command. Below them, there are the following buttons:
- "Preview" Button : it generates the preview. The previews are visible on the right side of the panel. Passing the mouse over the previews shows the command line and so the parameters' values, just like menu items in main GUI.
- "Change Point" Button : it switches on the map display and allows the user to change the center of the preview window.
- "Apply" Button : it applies the analysis over the map on basis of the selected preview. If no preview is selected it applies the last generated. If no preview has been generated it simply applies the command as it is.
- "Close" Button : it closes the window.
Please feel free to discuss and comment my idea.
- Previous design
I thought hydrological analysis by GUI has to be organized in two steps:
- In the first step, a simple GUI pops up, asking for the main maps that user should provide. First of all, DEM on which analysis should be carried out. Also, it asks for flow direction and flow accumulation, that are the basis of further hydrological analysis. In fact user can either provide them already done by for instance another software, or create them using GRASS. In the latter case, user should indicate the name of new maps to be created and also he can choose the flow routing algorithm (default is MFD i.e. multiple flow direction). It is also possible to add Mask map (optional). This latter is useful to weight accumulation map in order to improve stream extraction.
IMHO this previous step is necessary in order to generate the preview fastly and also because stream extraction preview needs the accumulation map generated on the whole area and not only on the small region selected (stream network may vary). The "hello world" of this first step GUI is available on my brand new github repository 
- Once the user has provided these information, the elaboration starts if user asked to calculate flow direction and flow accumulation and the main GUI pops up, asking for further detailed analysis, for which the preview tool should be available. (see above "Draft of main r.stream GUI")
- Design updated Friday 17 June
There will be probably no need of first time step window. GUI is designed to be divided into tabs. Analysis starts in tab 1, that is stream network extraction. Also, in the first tab should run r.stream.order (result is ordered network. This should be optional, it's required only if user wants to run further analysis in tab 2) and r.stream.basin (resulting map is the basin delineation. This should be optional, it's required only if user wants to run further analysis in tab 2).
Inputs of the first tab are:
- DEM (required) - mask (optional) - closing section (required if user wants to run r.stream.basin) - accumulation map -> three possibilities: 1 Accumulation map can be previously generated by another software (custom); 2 To be generated by r.watershed using SFD algorithm; 3 To be generated by r.watershed using MFD algorithm.
If user chooses "custom", the name of the map in accum field is the name of existing map which will be used. If map is generated, the name in the field is the name of the new map which will be created. The choice will be done by a dropdown list. The field could be labeled as "Use existing accum map or create a new one using r.watershed". Of course, there will be fields to write the names of results maps. There will be checkboxes to choose which layers will be generated, let's say: network, ordered network, ecc.
About preview area: user should select a point on the DEM and push the "update" button. A preview is generated according to parameters inserted by user. The extents of the small area are pre-established (I will establish them on the basis of the computing time, after testing)
Second tab uses results of tab 1 if user wants to continue his/her work on segmentation on the basis of results of network modeling.
- 23 May - 5 Jun : design interface based on other similar software
- 6 Jun - 15 Jul : midterm goal: get a interface widget for r.stream.extract, r.stream.order
- 16 Jul - 31 Jul: add preview widget, functionality and documentation
- 1 Aug - 15 Aug : testing
- Final goal: working GUI for grass7
Weekly Reports, from SoC mailing list
- Week 1 Report (27 May) http://lists.osgeo.org/pipermail/soc/2011-May/001330.html
- Week 2 Report (3 Jun) http://lists.osgeo.org/pipermail/soc/2011-June/001341.html
- Week 3 Report (10 Jun) http://lists.osgeo.org/pipermail/soc/2011-June/001369.html
- Week 4 Report (17 Jun) http://lists.osgeo.org/pipermail/soc/2011-June/001392.html
- Week 5 Report (24 Jun) http://lists.osgeo.org/pipermail/soc/2011-June/001414.html