Implement cloud filtering on EARLINET reader
lewisblake opened this issue · 0 comments
lewisblake commented
Describe the bug
Different EARLINET stations describe cloud interference in different ways. Some stations such as Warsaw (WAW) have a variable cloud_mask_type
byte cloud_mask_type ;
cloud_mask_type:long_name = "cloud mask type" ;
cloud_mask_type:_FillValue = -127b ;
cloud_mask_type:valid_range = 0b, 3b ;
cloud_mask_type:flag_values = 0b, 1b, 2b ;
cloud_mask_type:flag_meanings = "no_cloudmask_available manual_cloudmask automatic_cloudmask" ;
whereas Cork (UCC) has a variable cirrus_contamination
byte cirrus_contamination ;
cirrus_contamination:long_name = "do the profiles contain cirrus layers?" ;
cirrus_contamination:_FillValue = -127b ;
cirrus_contamination:valid_range = 0b, 3b ;
cirrus_contamination:flag_values = 0b, 1b, 2b ;
cirrus_contamination:flag_meanings = "not_available no_cirrus cirrus_detected" ;
We would like to include as many stations as possible, but implement the strategy of getting the cleanest data possible. This means the EARLINET reader will have to check for these quality-control related variables, and filter using the correct one for each file.
- Pyaerocom version: >= 0.22.0.dev0
- Computing platform: all
- Configuration file (if applicable): NA
- Error message (if applicable): NA
To Reproduce
Steps to reproduce the behavior:
- Run an experiment with EARLINET data
Expected behavior
A clear and concise description of what you expected to happen.