You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's code for Sentinel 5p data reading (mostly tested for the variable tcolno2) in pyaerocom here and here that are the product of Michael Gauss's Sentinel 5p project (finished last year).
The data reading is based on stcorp's coda package. At the time of writing coda was only available at scorp's own conda channel and not entirely installable within a standard pyaerocom distribution.
A lot has changed since then and it's now available via conda-forge, but not via pip.
The code in general is not according to our general pyaerocom style, but went through black and isort as othe other code as well. But at least the doc strings need to be adjusted and also some test need to be added.
It's also using the geopy library. At the moment this is just used for the Earth's radius. Because I did not use great circle distances or real distances (provided e.g. via a Google web API by geopy, but not feasible for more than just a few hundred points), the geopy dependency can in principle removed. I just need to go through the code.
The interesting part is the gridding functionality
"""simple gridding algorithm that only takes the pixel middle points into account
All the data points in data are considered!
"""
Due to RAM needs (~64GB per day if I remember correctly), the code can only work on a single day and will therefore never be used in a normal pyaerocom run. It was used to produce daily gridded files the were then put together to a yearly file using nco. The netcdf writing method is here:
There's code for Sentinel 5p data reading (mostly tested for the variable tcolno2) in pyaerocom
here and here that are the product of Michael Gauss's Sentinel 5p project (finished last year).
The data reading is based on stcorp's coda package. At the time of writing coda was only available at scorp's own conda channel and not entirely installable within a standard pyaerocom distribution.
A lot has changed since then and it's now available via conda-forge, but not via pip.
The code in general is not according to our general pyaerocom style, but went through black and isort as othe other code as well. But at least the doc strings need to be adjusted and also some test need to be added.
It's also using the geopy library. At the moment this is just used for the Earth's radius. Because I did not use great circle distances or real distances (provided e.g. via a Google web API by geopy, but not feasible for more than just a few hundred points), the geopy dependency can in principle removed. I just need to go through the code.
The interesting part is the gridding functionality
pyaerocom/pyaerocom/io/readsatellitel2base.py
Lines 686 to 693 in 3e80488
Due to RAM needs (~64GB per day if I remember correctly), the code can only work on a single day and will therefore never be used in a normal pyaerocom run. It was used to produce daily gridded files the were then put together to a yearly file using nco. The netcdf writing method is here:
pyaerocom/pyaerocom/io/readsatellitel2base.py
Lines 521 to 537 in 3e80488
Another issue is that the CLI is included in the class file, but @avaldebe addressed that already in PR #540
The text was updated successfully, but these errors were encountered: