Changes between Version 1 and Version 2 of FAQ/hdfsizelimit

Timestamp:

May 18, 2012, 5:42:49 PM (13 years ago)

Author:

benj

Comment:

--

FAQ/hdfsizelimit

@@ -2 +2 @@
 
 '''A:'''[[BR]]
+This occurs normally for Eagle or Hawk data that are too large for the HDF 4 file format. This format is normal for ARSF delivered Eagle and Hawk data.
+
 For ATM and CASI, the image data is held in the HDF file along with the image metadata. You get only a single HDF data file per flightline that contains all of the relevant data and azgcorr operates on this. Unfortunately, the HDF 4 file format used has a limit of about 2GB on how big the file can be, and data files from Eagle and Hawk frequently exceed this limitation.
 
@@ -14 +16 @@
 azgcorr -mUK99 osgb02.cgrf -p 1 1 -bl 30 15 7 -1 -eh my_dem.dem -1 flight_data_l1.hdf -3 flight_data_l3.hdf
 
+For user created level-2 BIL files the options -Bi, -Bs or -Be have to be used. -Bi and -Bs require a -B parameter command to provide the image file details. -Be expects an ENVI/BIL/BSQ pair of files with at least the items on the header file: samples, lines, bands, "header offset"  ( to skip header info/data etc at the start of the binary file), "data type"  ( = 4 or 12 only ie f32 or u16 ), interleave  ( = bil or bsq ), "sensor type"  ( = atm, casi, az16 or ccd ), "default bands" = ( r g b  band numbers )
+
+See the -help command for more details.
+
+
 [wiki:FAQ Back to FAQ]