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

A better way to caculate and handle cml coverage maps #13

Open
cchwala opened this issue Aug 24, 2017 · 0 comments
Open

A better way to caculate and handle cml coverage maps #13

cchwala opened this issue Aug 24, 2017 · 0 comments

Comments

@cchwala
Copy link
Contributor

cchwala commented Aug 24, 2017

Idea:

  • Calculate the covered pixels for a given grid for each cml
  • Store this info along with the Comlink data
  • Maybe store everything in a xarray dataset:
    • cml rainfall series (all with a common time index) indexed by cml_id
    • cml rainfall grid (lat, lon, time)
    • cml coverage (lat, lon, cml_id)
    • or maybe cml coverage (list_of_covered_x_y_indices, cml_id)

This way, once all coverage maps for the individual cml have been calculate, it would be easy to get the coverage for a given point in time, taking into account the varying NaNs of the CML rainfall time series.

Open questions:

  • speed of calculating coverage for each CML, instead of building a convex hull for all of them in geopandas/shapely? (but, could be parallelized)
  • size impact of coverage matrices?
    • matrices would only be of dtype bool
    • however, for large grids and a thousands of CMLs, that would still be a lot of bits...
    • maybe storing only the covered indices is better, just include a simple way to project these onto the grid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant