| 86 | === Complete basic cartography suite in GRASS GIS wxGUI Map Display === |
| 87 | |
| 88 | * 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. |
| 89 | * first phase: |
| 90 | * store legend, scale bar, north arrow and text (and others if added) in workspace |
| 91 | * add units to legend (optionally also title) as parameter |
| 92 | * possibility to add any image (as in animation tool), use cases: logo/watermark, workaround for overview maps |
| 93 | * disable rendering when loading workspace |
| 94 | * determine map window size without the need to change map display size manually |
| 95 | * second phase: |
| 96 | * support map units in scale bar, not only meters |
| 97 | * allow user to set the length of scale bar (in map units) |
| 98 | * manual breaks for legend |
| 99 | * legend background |
| 100 | * general shapes |
| 101 | * can be implemented using `d.*` commands or wxPython or both (wxPython might be easier for interactivity, `d.*` commands for scripting) |
| 102 | * use cases: workaround missing backgroud of legend or text, manual marking special points |
| 103 | * include map-display-like object |
| 104 | * would be represented as image but the image would be dynamically generated |
| 105 | * useful for overview maps (insets) or histograms |
| 106 | * might be implemented as a standard Map Display whose saved image would be inserted as an image |
| 107 | * third phase: |
| 108 | * implement vector legend: |
| 109 | * 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). |
| 110 | * May get complicated with (enhancements of) vector thematic mapping |
| 111 | * enhance `d.vect.thematic` |
| 112 | * make `d.text` accessible from wxGUI |
| 113 | * implement module which can parametrize workspace (similarly as `g.gui.animation` is doing for 3D View) and render it with different maps |
| 114 | * if the implementation would be wxPython free (ideal option) then it would have to translate some wxPython/wxGUI specific things to plain `d.*` commands |
| 115 | * this can be also implemented as a script generator (rather than workspace renderer) |
| 116 | * it should work as a simple automatic map ("atlas") generator and should accept also time series as the input |
| 117 | * Language requirements: Python, wxPython |
| 118 | * Co-mentors: Anna Petrasova, Helena Mitasova |
| 119 | |