| 116 | |
| 117 | '''12. Raster algebra in the core'''[[BR]] |
| 118 | |
| 119 | Raster algebra (computing rasters or other data from one or more raster) is currently possible with Python and NumPy but it would be good to have a core plugin it. There was some discussion on the list https://lists.osgeo.org/pipermail/gdal-dev/2016-January/043539.html about one way to do it. |
| 120 | |
| 121 | Skills: C++ |
| 122 | |
| 123 | Difficulty level: medium |
| 124 | |
| 125 | '''13. Header file reorganization'''[[BR]] |
| 126 | |
| 127 | GDAL header files raise some concerns from time to time (#1589, https://lists.osgeo.org/pipermail/gdal-dev/2016-January/043564.html). GDAL installs about 70 header files into plain include and they contains things that are only needed when GDAL is built, the C++ API and the C API. |
| 128 | |
| 129 | Skills: C/C++ |
| 130 | |
| 131 | Difficulty level: medium |
| 132 | |
| 133 | '''14. Swig interface reorganization'''[[BR]] |
| 134 | |
| 135 | The swig interface, which is the main (but not only) method used to add GDAL capabilities to other languages than C or C++, is riddled with ifdefs and |
| 136 | language specificities and there is a need to bring order into the chaos. |
| 137 | |
| 138 | Skills: Swig/C/C++ |
| 139 | |
| 140 | Difficulty level: high |