[GRASS-dev] [GRASS GIS] #2036: Failed watershed analysis on Grass

[GRASS GIS]

#2036: Failed watershed analysis on Grass
--------------------------+-------------------------------------------------
  Reporter:  mehmeto      |       Owner:  grass-dev@…              
      Type:  defect       |      Status:  closed                   
  Priority:  normal       |   Milestone:  6.4.4                    
 Component:  Raster       |     Version:  6.4.2                    
Resolution:  fixed        |    Keywords:  LFS, r.watershed         
  Platform:  MSWindows 7  |         Cpu:  x86-64                   
--------------------------+-------------------------------------------------

Comment(by hamish):

 Hi,

 I tried in 6.4.3svn on Windows7 with Spearfish's elevation.10m with
 g.region at 2m, with r.watershed run using the '-m' flag and 4 output
 maps. It seemed to work fine that way. (region size ~ 7000x9500)

 mmetz:
 > It's not so easy for Windows. You need to use the LFS API explicitely,
 i.e.
 > off64_t, fseeko64(), ftello64, lseek64(), _stati64, etc.

 so more #ifdefs are needed in G_ftell() and G_fseek(), then more modules
 in g6 need to use those functions? (right now only r.in.bin does) If so it
 doesn't seem so hard.
 As a future maintenance goal, full 64bit file support on Windows for 6.4.x
 seems to me a rather important thing to work towards. (From both the grass
 code, msys, and osgeo4w ends)


 > For trunk, the -m flag could become the default, in order to avoid
 tickets
 > like this.

 mmph, I'm not a fan of that, rather just document the memory issues in the
 man page and have it go fast in the typical cases. (how much RAM will the
 average computer have when g7 is middle aged?)


 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2036#comment:20>
GRASS GIS <http://grass.osgeo.org>