Opened 18 years ago
Closed 17 years ago
#9 closed bug (fixed)
BSEQ dump produces incorrect ENVI header
Reported by: | mggr | Owned by: | mggr |
---|---|---|---|
Priority: | whenever | Milestone: | |
Component: | azexhdf | Keywords: | bug |
Cc: | Other processors: |
Description
azexhdf -h a195041b.hdf -BSe a195041b_test.raw
Should produce an envi .hdr for a bseq file (azexhdf help states:
-B fn : convert image data to BIL binary file -BS fn : convert image data to BSEQ binary file -Be fn : -BSe fn : : B and BS may be followed by e to request an ENVI : compatible header to be output with extension fn.hdr : For ENVI compatibility fn should be given as fn.raw or fn.bil : fn = output filename
Actual header file produced claims it's a BIL, not a BSEQ:
arsf@pmpc889:~/support/20070515-GB06_05-195a-RachelGaulton<1040>cat a195041b_test.hdr
ENVI description = { File output by azexhdf } file type = ENVI interleave = bil samples = 938 lines = 3802 bands = 11 header offset = 0 data type = 12 byte order = 0
Correcting the interleave line to read "bseq" results in a correct load into ENVI.
Change History (4)
comment:1 Changed 18 years ago by mggr
- Keywords bug added
- Status changed from new to assigned
comment:2 Changed 18 years ago by mggr
comment:3 Changed 17 years ago by mggr
Tested, it works.
comment:4 Changed 17 years ago by mggr
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
Reported to Bill 11/June/2007.
Fix arrived 12/June with rel108, axexhdf.319.
Not tested yet.