Re: Call for changes in the Python library
Steven Pawley <[email protected]>
| Newsgroups | gmane.comp.gis.grass.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Vaclav, A couple of thoughts: An equivalent of a RasterRow class for 3D rasters to make it easier to read stacks of GRASS raster datasets into multidimensional arrays. Not really a Python addition as it mostly relates to the raster C library, but the ability to read windows/blocks/cubes of raster data, not just rows, IMHO would be a large improvement for raster data access into python. AFAIU, this is only currently possible by repeatedly moving the computational window, which I think was slower (when I tested this for reading chunks for r.learn.ml2) than the performance from windowed reading in other libraries (e.g. GDAL/Rasterio). Steve > On Sep 24, 2020, at 8:29 PM, Vaclav Petras <[email protected]> wrote: > > Now would be a great time to do any large or small changes in the Python library. Let's discuss these. For example, there was a talk about more clear splitting of the ctypes dependent and independent code in grass.pygrass, about moving the library to a different place, there is the new grass.grassdb subpackage, PEP8/Black/Flake8, ... Is there anything *you* see as a priority for 8.0? Is there anything you can do before 8.0? Let's coordinate here. > _______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev