Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#128 closed support (fixed)

Support: 16/Apr/2008, Jon Atherton, (no project code)

Reported by: benj Owned by: mggr
Priority: alpha 4 high Milestone:
Component: Support Keywords:
Cc: benj, sbg, gaew Other processors:


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.

Change History (2)

comment:1 Changed 16 years ago by mggr

  • Resolution set to fixed
  • Status changed from new to closed
  • Summary changed from Jon Atherton CASI query (no project code) to Support: 16/Apr/2008, Jon Atherton, (no project code)

comment:2 Changed 16 years ago by mggr

Decision on support was that we should support indirect users (ie. not the original PIs) of ARSF data, though it shouldn't be allowed to impact on processing to too great an extent.

Note: See TracTickets for help on using tickets.