[GRASS-windows] Large file support?

[Jonathan Greenberg]

Nope!  It was ENVI format, and imported flawlessly on a *nix compile.

--j

Roland Duhaime wrote:
> Hi Jonathan,
>  
> Is it possible that the file is a tif file?  I understand that tif and 
> geotiff files have a 2 gb limit.  As a result, it may be a limitation of 
> the file type, and not the software.  Just a thought.
>  
> Thanks,
> Roland
> 
>  
> 
> ----- Original Message ----
> From: Jonathan Greenberg <greenberg at ucdavis.edu>
> Cc: grass-windows at lists.osgeo.org
> Sent: Monday, July 28, 2008 4:24:32 PM
> Subject: Re: [GRASS-windows] Large file support?
> 
> Marco (and GRASS'ers):
> 
>     Has anyone *successfully* imported a file > 4gb via r.in 
> <http://r.in.gd/>.gdal into
> GRASS for Windows (including looking at the file and do a v.what in the
> lower portions of that image)?  Enabling the lfs flag I don't think is
> the issue -- I think *grass* can deal with big files, but the GDAL
> compile it is relying on probably isn't configured correctly.  I have
> confirmed this on two different computers, importing two different files
> (both are > 7gb) -- the import absolutely finished -- it failed on both
> computers in the same place.  I gave it PLENTY of time (> 12 hours, it
> imported in about 2 hours on a comparable unix box) and the r.in.gdal
> "run" button returned to black (usually a good back-up indication that a
> process is finished, if the progress bar isn't working).
> 
> --j
> 
> Marco Pasetti wrote:
>  > Hi Johnathan,
>  >
>  >> I seem to be running up against a file size limitation in the latest
>  >> version of grass for windows
>  >
>  > I made nothing different about that in the latest binary release fo
>  > Windows; I suppose it's a generic problem, not strictly related to the
>  > latest release
>  >
>  >> I'm trying to import a 7gb file and it seems to have imported only
>  >> about the first 2gb or so of the file, and the rest is just
>  >> empty/errored (when I do a v.what it gets a "can't read" in the lower
>  >> 2/3 or so of the image, but returns correct values in the upper 1/3 or
>  >> so of the image).  I used r.in.gdal to import the file (it was an ENVI
>  >> image file).  Ideas?
>  >
>  > Actually no, afraid.
>  > If you read here
>  > 
> http://grass.osgeo.org/grass63/binary/mswindows/native/README.html#Release%20Notes 
> 
>  > you can actually see that LFS is enabled.
>  > Are you sure that the command worked fine or finished to process data?
>  > sometimes the progress bar fails
>  > Please, try again launching the command within the text command line
>  > (msys or dos, as you prefer)
>  >
>  > Please report me the results.
>  >
>  > Regards,
>  >
>  > Marco
>  >
> 
> -- 
> 
> Jonathan A. Greenberg, PhD
> Postdoctoral Scholar
> Center for Spatial Technologies and Remote Sensing (CSTARS)
> University of California, Davis
> One Shields Avenue
> The Barn, Room 250N
> Davis, CA 95616
> Cell: 415-794-5043
> AIM: jgrn307, MSN: jgrn307 at hotmail.com <mailto:jgrn307 at hotmail.com>, 
> Gchat: jgrn307
> _______________________________________________
> grass-windows mailing list
> grass-windows at lists.osgeo.org <mailto:grass-windows at lists.osgeo.org>
> http://lists.osgeo.org/mailman/listinfo/grass-windows
> 

-- 

Jonathan A. Greenberg, PhD
Postdoctoral Scholar
Center for Spatial Technologies and Remote Sensing (CSTARS)
University of California, Davis
One Shields Avenue
The Barn, Room 250N
Davis, CA 95616
Cell: 415-794-5043
AIM: jgrn307, MSN: jgrn307 at hotmail.com, Gchat: jgrn307