I extracted the sensitivity of a multitude of flights we conducted with an eBee X and one Parrot Sequoia sensor. The results can be seen in the attached image. I’m a bit worried about the large range of sensitivities (that are used as absolute values for correction of final reflection?).
Might this be a hint for some problems in our acquisition process that lead to substantial error in results?
Best regards,
Till
Example for sensitivity from log file:
“[2021.10.12 15:42:54][ 13%RAM][ 83%CPU][Info]: Mean corrected pixel value 0.468, std dev 0.0134712, sensitivity [ 0.86191 ]”
Thanks for the article but what does it mean in the context of my question? Do you recommend not to use a calibration target? Is it true, that the plotted sensitivity should not vary in this rang or do I miss something during processing?
First of all, it is very important to verify that the illumination conditions during the capture of the reflectance targets are representative of the illumination during the flight. Make sure that there are no shadows on the reflectance target nor on the sunshine sensor, and neither reflections onto the reflectance target from adjacent objects or yourself, and that the general illumination didn’t change (for example due to clouds forming). Make sure to hold the camera horizontal, and align the target horizontally and facing North.
Secondly, if you are using PIX4Dmapper, remember that as mentioned in the knowledge base, the sun angle correction assumes clear sky. If you have overcast conditions, please select “Camera and Sun Irradiance”. In PIX4Dmapper, selecting sun angle corrections in cloudy conditions leads to biases. In PIX4Dfields, you select the weather conditions in the settings.
For further investigations, I would suggest to plot the reflectance target derived sensitivity as a function of the weather condition. For those cases where the sensitivity is quite different across bands for the same flight, I would suggest to check if you selected images from the same capture for the different bands. If you mix two different captures that were acquired in different illumination conditions, you get biases. In general, I would suggest to always note down the weather conditions during a flight and take a few pictures of the sky with your mobile phone to visualise the in-situ conditions to refer to them later.
Thanks a lot for your detailed reply. First of al I have to admit, that we must be more thoroughly during the capture of the calibration images. It would be great, if you can additional answer following questions:
When the sensor additionally measures sun irradiance, in my understanding sensitivities should be stable across illumination conditions. Am I wrong?
When sun angle correction is activated, the irradiance of the calibration image is corrected, too?
It would be great to analyze the measured irradiance for the calibration images for some analyses, but these are not exported to the sun_angle.csv. Is there any other way to get them.
When using the sunshine sensor, the sensitivities should be stable across illumination conditions if (1) the illumination conditions of the sunshine sensor are the same as the illumination conditions of the reflectance target, (2) the proper corrections are done, i.e. the right correction type for the conditions is chosen, and (3) the orientation of the camera is correct.
When sun angle correction is enabled, it is also applied to the reflectance target image. However, since photogrammetry doesn’t apply to a single image as the one of the reflectance target, we need to make some assumptions regarding the orientation of the camera, therefore the sun angle correction will be wrong if the camera is not oriented correctly.
Thanks a lot for your detailed technical insight and sorry for responding so late. Just on more small request. What do you mean by “the orientation of the camera is correct” in this context?
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.