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.

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

Create coverage_vpfiles() function #181

Closed
peterdesmet opened this issue Dec 13, 2018 · 2 comments
Closed

Create coverage_vpfiles() function #181

peterdesmet opened this issue Dec 13, 2018 · 2 comments
Labels
duplicate VPTS CSV Related to VPTS CSV format
Milestone

Comments

@peterdesmet
Copy link
Collaborator

From #176 (comment), create a function to check the vp files coverage (over time and radars), so the user has an idea about the coverage before analysis:

I would suggest to bundle this at some point in a separate function coverage_vpfiles() that could provide such information for remote or even downloaded vp files. @CeciliaNilsson709 has already created some nice charts to express the coverage. 👌 And the returned information (list of vp files that are available) could optionally be passed to the download_vpfiles() for more targeted download. So something for a separate enhancement issue I would say.

This function could be based on checking files directly or build upon the coverage.csv that is generated by the ENRAM data repository pipeline.

@peterdesmet peterdesmet modified the milestones: 0.5.0, 1.0.0 Dec 13, 2018
@peterdesmet peterdesmet added the VPTS CSV Related to VPTS CSV format label Mar 10, 2023
@peterdesmet
Copy link
Collaborator Author

The new bucket also has a coverage.csv, with an updated structure.

@peterdesmet
Copy link
Collaborator Author

The functionality described in this issue is covered by #556

@adokter adokter modified the milestones: 1.0.0, 0.7.0 May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate VPTS CSV Related to VPTS CSV format
Projects
None yet
Development

No branches or pull requests

2 participants