Custom Query (419 matches)


Show under each result:

Results (109 - 111 of 419)

Ticket Resolution Summary Owner Reporter
#121 fixed Azatm -cuo option seemingly not working benj benj

If you use the -cuo option in azatm to change the values it's supposed to set overflowed and underflowed pixels to, it doesn't seem to have an effect - always sets underflowed pixels to 0 (even if told to set them to ffff) and always says:

************* radcal underflow and overflow fill values changed ********
      under : 00000  = 0     over: 00000  = 0 azatm output, regardless of what values are entered for the under/overflow (tried with 0 fffe and ffff ffff).

Arose from testing on #115

#127 fixed IPY07/08, flight day 214ef/2007, Langjökull mggr mggr

Data location: ~arsf/arsf_data/in_progress/2007/flight_data/ipy/IPY07_08-2007_214ef_Langjokull

Data arrived from ARSF via SATA disk transfer in August, with post-processed GPS arriving in December following Kidlington visit.

Scientific details: (details of IPY applications not currently available at PML)

PI: I Willis

Langjökull anglicises to Langjokull - use this for filenames just in case of problems.


  • ATM (delivered 23/May/2008)
  • CASI (delivered 6/May/2008)




#128 fixed Support: 16/Apr/2008, Jon Atherton, (no project code) mggr benj

Had a request for help from a user of existing CASI data (Jon Atherton) who was not an original PI but obtained some 2005 flight data from NEODC:


I'm a complete novice at preprocessing CASI data. I have access to the NEODC online data sets, and I would like to use CASI data from Sitia, 2005 (
I need about 15 bands worth centred at 685 nm (band 32 to 47) from images c130021b and c130041b.

Your colleague (Gary Llewellyn) kindly provided me with the FTP for AZGCORR. I had a go with the basic line of code (provided in the tutorial) which produced a blurred image on an angle, when compared with the three bands-worth of images already processed to level 3b which are available online. Any help on correcting the blurriness would be greatly appreciated.

The only code I used was (I don't have a DEM):

 "./azcor -bl 1 -1 -p 2.0 2.5 -1 c130021b.hdf -3 c130023a.hdf"

Best wishes,

Jon Atherton

PhD student
University of Edinburgh

Replied to the query (suggested he applied a correct projection, used square pixels and tried some different bands), which seems to have solved the problem.

What if any support level should we be providing to new users of existing data? On the one hand we don't want to leave ourselves open to potentially large open-ended support requests from non-PIs, on the other it's in our interests to have ARSF data as widely available and used as possible.

Note: See TracQuery for help on using queries.