Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make import_odim_hdf5() more generic to read in non-OPERA ODIM files #214

Open
ladc opened this issue Jul 20, 2021 · 0 comments
Open

Make import_odim_hdf5() more generic to read in non-OPERA ODIM files #214

ladc opened this issue Jul 20, 2021 · 0 comments
Projects
pysteps-v2

Comments

@ladc
Copy link
Contributor

ladc commented Jul 20, 2021 •
edited

The ODIM format is quite flexible and it would be useful to adapt the importer to take at least some of this flexibility into account (e.g. custom accumulation time). We experience some issues for the Belgian radar composite / QPE (RADQPE) which follows the ODIM 2.2 convention.
@dnerini dnerini added this to To do in pysteps-v2 Jul 24, 2021
@dnerini dnerini mentioned this issue Jul 26, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
pysteps-v2
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ladc