| 16 | | |
| 17 | | == Empty slots == |
| 18 | | |
| 19 | | List of major tasks to be implemented for wxGUI which are not assigned to any developer. Please don't hesitate to join the wxGUI development group. |
| 20 | | |
| 21 | | * '''[http://grass.osgeo.org/wiki/WxGUI#General_GUI_Design General GUI desing]''' (Python/wxPython required) |
| 22 | | * '''Clean up/update imagery modules and library''' (C required) and [http://grass.osgeo.org/wiki/WxGUI#Imagery_tools integrate these tools into wxGUI] - e.g. {{{i.class}}}, {{{i.ortho.photo}}} (Python/wxPython required) |
| | 18 | * [http://grass.osgeo.org/wiki/WxGUI#General_GUI_Design General GUI desing] (Python/wxPython required) |
| | 19 | * Clean up & integrate [source:grass-addons/grass6/gui/wxpython/wx.data_catalog data catalog] into wxGUI in trunk |
| | 20 | * Integration of imagery modules and wxGUI |
| | 21 | * Clean up/update imagery modules and library (C required) |
| | 22 | * [http://grass.osgeo.org/wiki/WxGUI#Imagery_tools integrate these tools into wxGUI] - e.g. {{{i.class}}}, {{{i.ortho.photo}}} (Python/wxPython required) |
| 24 | | * Clean up & integrate [http://grass.osgeo.org/wiki/WxGUI#Data_Catalog data catalog] into wxGUI in trunk |
| 25 | | * Improve '''[http://grass.osgeo.org/wiki/wxNviz 3D view mode]''' |
| 26 | | * Improve '''vector querying''' by allowing interactive queries using a line or polygon drawn by the user on the display canvas. This would be facilitated by improvements to v.what that allows it to find all vector objects within (or optionally intersecting) a line or polygon defined by a set of coordinate pairs. This could be done via v.select but it sounds like v.select might be problematic to use in this way. |
| 27 | | * Create a new python wrapper script for '''thematic mapping'''. This would include d.thematic for areas, and scripting code (possibly salvaged from d.vect.thematic) for points and lines. It also would need legend generating code. |
| 28 | | * '''Times series / voxel slices visualizer''' for GRASS7 - Given the increasing need to support extensive time series of data from simulations or remote sensing, it should combine and enhance capabilities currently available through combination of xganim, d.slide.show, !ImageMagic and various custom scripts to visually analyze series of raster and vector data using animations, frame browsing and series management. In addition to the current xganim (or its tcltk version) + d.slide.show capabilities the following would be desirable: |
| | 24 | * [http://grass.osgeo.org/wiki/wxNviz 3D view mode] |
| | 25 | * Vector querying |
| | 26 | * Allowing interactive queries using a line or polygon drawn by the user on the display canvas. This would be facilitated by improvements to v.what that allows it to find all vector objects within (or optionally intersecting) a line or polygon defined by a set of coordinate pairs. This could be done via v.select but it sounds like v.select might be problematic to use in this way. |
| | 27 | * Thematic mapping |
| | 28 | * Create a new python wrapper script for thematic mapping. This would include d.thematic for areas, and scripting code (possibly salvaged from `d.vect.thematic`) for points and lines. |
| | 29 | * It also would need legend generating code. |
| | 30 | * Times series / voxel slices visualizer |
| | 31 | * Given the increasing need to support extensive time series of data from simulations or remote sensing, it should combine and enhance capabilities currently available through combination of `xganim`, `d.slide.show`, !ImageMagic and various custom scripts to visually analyze series of raster and vector data using animations, frame browsing and series management. In addition to the current xganim (or its tcltk version) + d.slide.show capabilities the following would be desirable: |
