| | 63 | |
| | 64 | === Improved color management === |
| | 65 | |
| | 66 | Current color management of raster and vector maps has several issues: |
| | 67 | * Interactive editing of colors is rather limited: #3370 |
| | 68 | * We can't easily specify discrete color intervals (e.g. [http://soliton.vm.bytemark.co.uk/pub/cpt-city/cb/seq/tn/BuPu_09.png.index.html this ramp]) for floating point data unless we reclass first, legend does not display that correctly |
| | 69 | * [https://trac.osgeo.org/grass/query?status=!closed&keywords=~colors and others...] |
| | 70 | |
| | 71 | A new color editing widget could be developed that would be integrated in r.colors, r3.colors, v.colors, t.rast.colors. It would allow simple editing of breaks (manual and automatic). Better support for discrete color tables for floating point data needs to be developed. |
| | 72 | |
| | 73 | * Requirements: Python, wxPython, possibly some C |
| | 74 | * Mentor: Anna Petrasova, Vaclav Petras |
| | 75 | * Proposed by: Anna Petrasova |
| | 76 | * Rating: medium |
| | 77 | * Expected Outcomes: More user-friendly color management |
| | 78 | * Test of skills: [https://trac.osgeo.org/grass/query?status=!closed&keywords=~colors and others...] |
