Hi Folks, I very much appreciate the efforts in the code sprint this week!
On Thu, Mar 27, 2014 at 8:54 AM, Helmut Kudrnovsky <[email protected]> wrote: > > > > 1) to keep r.stream.basins as an add-on, demanding the delineation of > multiple subbasins from coordinates to a user´s script looping > r.water.outlet; > 2) to include r.stream.basins and keep also r.water.outlet; > 3) to include r.stream.basins in the core and remove r.water.outlet as > obsolete. > 4) ? > > regards from Vienna > > Madi, Helmut > > [1] http://grass.osgeo.org/grass70/manuals/addons/r.stream.basins.html > [2] http://grass.osgeo.org/grass70/manuals/r.water.outlet.html > [3] http://grass.osgeo.org/grass70/manuals/r.watershed.html If r.stream.basins can replicate the functionality of r.water.outlet, I would prefer 3 . Some argument might be made for a conservative approach for option 2 for version 7.0 and drop r.water.outlet in version 7.1, but 7.0 is in development status. Why not make the change now? Doug > > > > > ----- > best regards > Helmut > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/r-stream-to-trunk-what-about-r-stream-basins-tp5131543.html > Sent from the Grass - Dev mailing list archive at Nabble.com. > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 [email protected] --------------------------------------------------------------------------------------------------------- The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
