Thanks guys for putting that into perspective. On Mon, Apr 5, 2010 at 6:38 PM, <[email protected]> wrote:
> Jordan, > I've dealt with ERDAS Imagine files larger than 10 GB on a regular basis. > I have occasionally tried to reproject and merge all of the 1 m NAIP > imagery tiles for North Carolina into 1 BigTIFF > 500GB with gdal. Any > parallelizaion work for open source geospatial tools would be welcome :-). > So you "tried" to do that? Does that mean you failed or is the system still processing it? :-P I kid, but that is a very large file... it's bigger than my current desktop's hard drive. > > Doug > > 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. > > [email protected] wrote: ----- > > To: Jordan Neumeyer <[email protected]> > From: Markus Neteler <[email protected]> > Sent by: [email protected] > Date: 04/05/2010 04:06AM > cc: GRASS developers list <[email protected]> > Subject: Re: [GRASS-dev] [SoC] Parallelization of Raster and Vector modules > > On Sun, Apr 4, 2010 at 3:22 AM, Jordan Neumeyer > <[email protected]> wrote: > > I didn't realize how big the data set could be. What's > > biggest map you've seen? > > Our provincial DEM is a 3.5GB Geotiff which is of 48800x58000 size. > Another file which I recently had to import was a 4GB Geotiff with > 21550 bands. Finally, in remote sensing, you can quickly generate > quickly files in the multi-GB range. > > Markus > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > ~Jordan
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
