Changes between Version 5 and Version 6 of GSoC/2015

Timestamp:

Feb 10, 2015, 8:00:15 PM (9 years ago)

Author:

wenzeslaus

Comment:

more info to the cartography idea

GSoC/2015

@@ -86 +86 @@
 === Complete basic cartography suite in GRASS GIS wxGUI Map Display ===
 
- * With few additions the wxGUI Map Display could cover large number of cartography needs so that users wouldn't be forced to switch to [http://grasswiki.osgeo.org/wiki/WxGUI_Cartographic_Composer WxGUI Cartographic Composer] or different software (Inkscape, QGIS) to create fully-featured map usable, e.g. for scientific publications.
+ * With few additions the wxGUI Map Display could cover large number of cartography needs so that users wouldn't be forced to switch to [http://grasswiki.osgeo.org/wiki/WxGUI_Cartographic_Composer WxGUI Cartographic Composer] or different software (Inkscape, QGIS) to create fully-featured map usable, e.g. for scientific publications. The development can happen in phases so that the easy-to-implement things, which gives greatest gain, are done first.
  * first phase:
   * store legend, scale bar, north arrow and text (and others if added) in workspace
@@ -99 +99 @@
   * legend background
   * general shapes
-   * can be implemented using `d.*` commands or wxPython or both (wxPython might be easier for interactivity, `d.*` commands for scripting)
+   * can be implemented using `d.*` commands (e.g. `d.graph`) or wxPython or both (wxPython might be easier for interactivity, `d.*` commands for scripting)
    * use cases: workaround missing backgroud of legend or text, manual marking special points 
   * include map-display-like object
    * would be represented as image but the image would be dynamically generated
    * useful for overview maps (insets) or histograms
-   * might be implemented as a standard Map Display whose saved image would be inserted as an image
+   * might be implemented as a standard Map Display whose saved image would be inserted as an image, perhaps image from other Map Display can be used
+   * the important feature is the user does not have to create an intermediate file
  * third phase:
   * implement vector legend:
-   * Perhaps we can find some workaround and wrap it into a module, e.g. vector legend drawn as vector with attribute table (enables even line with border thanks to different vector layers).
+   * Perhaps we can find some workaround (i.e. some easy implementation) and wrap it into a module, e.g. vector legend drawn as vector with attribute table (enables even line with border thanks to different vector layers).
    * May get complicated with (enhancements of) vector thematic mapping
   * enhance `d.vect.thematic`
-  * make `d.text` accessible from wxGUI
+  * make `d.text`, `d.graph`, `d.erase` and perhaps other existing `d.*` modules accessible from wxGUI
   * implement module which can parametrize workspace (similarly as `g.gui.animation` is doing for 3D View) and render it with different maps
    * if the implementation would be wxPython free (ideal option) then it would have to translate some wxPython/wxGUI specific things to plain `d.*` commands
    * this can be also implemented as a script generator (rather than workspace renderer)
    * it should work as a simple automatic map ("atlas") generator and should accept also time series as the input
- * Language requirements: Python, wxPython
+ * It would be great to make as much things as possible to work also in 3D Views (wxNVIZ).
+ * Thorough (manual) testing on different platforms is needed (by student or mentors).
+ * 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]
+ * Language requirements: Python, wxPython, (perhaps a little bit of C and OpenGL)
  * Co-mentors: Anna Petrasova, Helena Mitasova
-
-
 == Tips for students ==