Optical calibration on a Pleiades image : SpotImageMetadataInterface is complaining
Mantis Issue 992, reported by sdinot, assigned to jmichel, created: 2014-12-12
Tried to perform an optical calibration of a xs pleiades image to TOC level, through monteverdi 2 (0.8, 32bits). Received an error message from SpotImageMetadataInterface, specifying that the image is not a Spot one.
On the dashboard, Raoul (Win7-vc10-x86-RelWithDebInfo-Static), didn't find anything involving PHR products and metadatainterface errors.
Also tried to launch equivalent command under an Ubuntu12.04-64bits. Didn't not get any error.
Screenshot attached.
1418377448 - grizonnetmI confirm that I've got the same problem on Windows7 last week.
With which version of OTB was produce the phr_xs_melbourne.tif?
1418662125 - cpalmannphr_xs_melbourne.tif was produced from an OTB trunk build. Today, I could reproduce the bug with revision #17166.
1418915764 - cpalmannThere are several points related to this issue.
-
Part of the problem is related to the fact that MVD2 quietly enables some parameters whereas they are not mandatory. This is the case for the Relative Spectral Response File parameter (atmo.rsr) for instance, whose field is left empty. So contrary to what it has been said above, the issue can be reproduced on any platform from the gui version of the OpticalCalibration app : just enable atmo.rsr parameter, and don't feed the corresponding field.
-
Now the fundamental problem.
When atmo.rsr is enabled, the method LoadFilterFunctionValue from the class otbImageMetadataCorrectionParameters is called, and takes an SR file as input (con