Changes between Version 8 and Version 9 of GSoC/2015
- Timestamp:
- Feb 10, 2015, 9:03:13 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSoC/2015
v8 v9 119 119 * It would be great to make as much things as possible to work also in 3D Views (wxNVIZ). 120 120 * Thorough (manual) testing on different platforms is needed (by student or mentors). 121 * See also: [wiki:GSoC/2014#GRASSGISMapdisplaydecorationsenhancements related last year idea], #2582, [http://lists.osgeo.org/pipermail/grass-dev/2015-January/072918.html grass-dev future of thematic mapping in GRASS], [http://lists.osgeo.org/pipermail/grass-dev/2010-March/049414.html grass-dev future thematic cartography in GRASS] 121 * See also: 122 * [wiki:GSoC/2014#GRASSGISMapdisplaydecorationsenhancements map decorations idea from last year] 123 * [wiki:GSoC/2014#VectorlegendforGRASSGIS vector legend idea from last year] 124 * #2582 (implement `d.vect.thematic2` addon module features in `d.vect.thematic` core module) 125 * [http://lists.osgeo.org/pipermail/grass-dev/2015-January/072918.html grass-dev future of thematic mapping in GRASS] 126 * [http://lists.osgeo.org/pipermail/grass-dev/2010-March/049414.html grass-dev future thematic cartography in GRASS] 127 * [wiki:GSoC/2014#ColortablemanagementGRASSGISwxGUI slightly related color tables idea from last year] 122 128 * Language requirements: Python, wxPython, (perhaps a little bit of C and OpenGL) 123 129 * Co-mentors: Anna Petrasova, Helena Mitasova … … 125 131 === GRASS GIS 3D viewer NVIZ module independent of the main GUI === 126 132 127 * GRASS GIS 6 has a Tcl/Tk interface to NVIZ, a GRASS GIS 3D visualization library, and the interface is a standalone application in GRASS GIS environment. This has its disadvantages and thus wxGUI in GRASS GIS 6 and GRASS GIS 7 contains in fully integrated 3D view which is using NVIZ library as a backend. However, this also has its disadvantages and ideal solution is to have both.133 * GRASS GIS 6 has a !Tcl/Tk interface to NVIZ, a GRASS GIS 3D visualization library, and the interface is a standalone application in GRASS GIS environment. This has its disadvantages and thus wxGUI in GRASS GIS 6 and GRASS GIS 7 contains in fully integrated 3D view which is using NVIZ library as a backend. However, this also has its disadvantages and ideal solution is to have both. 128 134 * The existing examples are `g.gui.iclass`, `g.gui.animation` and `g.gui.vdigit` which is closest to proposed `g.gui.nviz` because it is also integrated into wxGUI Map Display. 129 135 * The implementation should use/reuse/refactor the existing code and all current functionality should be preserved (comparisons with the original version should be done throughout the whole development period). … … 133 139 * usage in `g.gui.animation` could be considered too 134 140 * having a Python API might be quite advantageous for scripting (although `m.nviz.image` solves most of the problems) 135 * This would bring benefit to QGIS Processing which is using the standalone Tcl/Tk NVIZ with GRASS GIS 6, so this project should be (co-)mentored by mentors from both GRASS GIS and QGIS projects.141 * This would bring benefit to QGIS Processing which is using the standalone !Tcl/Tk NVIZ with GRASS GIS 6, so this project should be (co-)mentored by mentors from both GRASS GIS and QGIS projects. 136 142 * Language requirements: Python, wxPython, (C and OpenGL shouldn't be necessary) 137 143 * Other requirements: basic software design patterns and GUI programming experience