#2301: unifying all of the different "segment" libraries -------------------------+-------------------------------------------------- Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.1.0 Component: Raster | Version: svn-trunk Keywords: | Platform: All Cpu: All | -------------------------+-------------------------------------------------- quoting here comment 1 in ticket #2296 ([http://trac.osgeo.org/grass/ticket/2296#comment:1 unifying segment libraries])
{{{ While we're at it, maybe we should look into unifying all of the different "segment" libraries. They all do essentially the same thing: provide a 2-dimensional array which may be too large to fit into RAM (or, more accurately, into the process' address space; if RAM was the issue, mmap() etc would suffice), and which can be accessed (more or less) randomly. Apart from the "official" segment library (lib/segment), r.proj has its own, r.stream.* each have their own, r.grow.distance has something simpler (the temporary file is read row-by-row but in reverse). }}} -- Ticket URL: <http://trac.osgeo.org/grass/ticket/2301> GRASS GIS <http://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev