Custom Query (419 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 419)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#2 fixed Support: 15/May/2007, Rachel Gaulton, GB06/05 mggr mggr
Description

Two issues:

  • Amer checking on LIDAR.
  • Use of bsq with azgcorr
    • mggr suspects perhaps the missing scans are throwing off the navigation?

Rachel's initial contact email:

I am trying to process ATM and CASI data flown last summer over my two
sites in Wales (GB06/05, PI - Tim Malthus). Unfortunately we are
having a few problems with AZGCORR and I wanted to check whether you
had encountered them before and had any idea what might be wrong (or
who else might have).

As we are carrying out atmospheric correction before geometrically
correcting the swaths in AZGCORR, so we are using the resulting .bsq
image in conjunction with the original .hdf (and a DTM) as inputs to
AZGCORR, as recommended in the user guide. With the CASI data and most
of the ATM swaths this appears to work ok (at least as far as can be
determined by visual inspection of the results), however with certain
swaths the geometric correction is not successful. These seem to be
swaths with considerable numbers of missing pixels / scan lines.  When
the raw .hdf data is geometrically corrected directly, the problems do
not appear and AZGCORR  works correctly (attached jpeg1), but when the
image is first converted to .bsq and atmospherically corrected the
image seems to be corrected up until the point of the missing scan
lines, but after that appears to be just 'stretched' to fit the
correct outline (jpeg2). The same problem is also being encountered by
John Dowens in correcting strips from GB06/07.

Do you have any ideas what may be causing this problem? Any
suggestions very much appreciated.  I was also wondering if you know
when I might be likely to receive the remaining LIDAR data from this
acquisition (I have the lidar from my Glasfynydd site but not from
Clocaenog)?

jpeg1 from Rachel's initial email

jpeg2 from Rachel's initial email

#4 fixed 154 wm06-04-Madrid-3/6/2006 amro amro
Description

Casi line 1 have alot of chequers and nav problems as in below image. project 154 is ready for delivery -:)

#5 fixed 144-WM06-11 Rio Tinto mggr amro
Description

CASI line 6 has not been processed due to Segmentation fault. the massage appeared on the output file can be seen below

azexhdf  -- ver: 3.1.8 May 10 2007   (C) Azimuth Systems UK 1996, 2007

Input file: ./lev1/c144061b.hdf
processing level: 1B
Scanner type: CASI  image data item: CAimage

read hdf  bands: 48 pixels: 511 lines: 4923
Image (CAimage) : (pix) 511, (lines) 4923, (bands) 48 type 23
Output BIL file details...
 pixels per line: 511  start line: 0 lines: 4923  bits per pixel: 16
 bytes per line: 1022
 band(s): 1  to  48
line:      0
line:   1000
line:   2000
line:   3000
line:   4000
last line output: 4922
output file complete
./runc/c14406.sh: line 183:  4425 Segmentation fault      azgcorr ${V} -hs ${HGTOFF} ${PROJ} ${BANDL} -p ${PIXSIZE} ${PIXSIZE} -1 ${P_HDF1} -3 ${P_HDF3} ${DoDEM}
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.