Open HolgerPollyNet opened 4 years ago
you are fast gy, ok you vote for an offline routine ;-)
I think it's best to deal with EARLINET data format issues here.
I don't have any doubt that EARLINET data format is great for many applications. But we still have products of Pollynet_Processing_Chain that are not in the scope of EARLINET, i.e., water vapor products. That could make it unsuitable for incorporating EARLINET data foramt into Picasso, right now.
In addition to the avergaed profiles we store for the whole altitude range, there wa a request to store "quality screened data" additionally. Meaning cutting out overlap regions and provide extinction and intensive properties only when a certain aerosol load is existent (i.e. backscatter exeeds a certain threshold). I think we can start to store such data in our Picasso netcdf format but preferable would be to switchalready to EARLINET standard format. What do you think? Shall we do this a a complete independent module in post-processing? Then we coudl base it on your pythoin script for converison to EARLINET DB format. Or better implement in the Picasso complete routine?