Re: Binary data in multiple adjacent files
- From: prep@xxxxxxxxxxxxxxxx
- Date: Fri, 27 Oct 2006 00:21:37 +0800
JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx> writes:
Now however, updated data comes in much smaller files, each covering
only 1° lat by 1° long. Each file has 1201 * 1201 values, each value
is 2 bytes. (basically elevation in metres for a 92 square metre
area). Each file is roughly 2.8 megs.
You can get all of oz on 2 CDs with ease. Two niggles, first is it
is bigendian INT16. Second, is that the boundary row and colum are
duplicated in each file.
I intend to read in ALL the files and build a single, or a few, files.
That would be a lot simpler, ESP as I intend to do quite a bit of number
crunching over it.
--
Paul Repacholi 1 Crescent Rd.,
+61 (08) 9257-1001 Kalamunda.
West Australia 6076
comp.os.vms,- The Older, Grumpier Slashdot
Raw, Cooked or Well-done, it's all half baked.
EPIC, The Architecture of the future, always has been, always will be.
.
- Follow-Ups:
- Re: Binary data in multiple adjacent files
- From: Dave Froble
- Re: Binary data in multiple adjacent files
- References:
- Binary data in multiple adjacent files
- From: JF Mezei
- Binary data in multiple adjacent files
- Prev by Date: Re: Banking security Was:PARSEC: SPAMMERS (not !)
- Next by Date: Spit Brook location
- Previous by thread: Re: Binary data in multiple adjacent files
- Next by thread: Re: Binary data in multiple adjacent files
- Index(es):