-
Notifications
You must be signed in to change notification settings - Fork 15
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
Problem generating weights with DAYMET data #16
Comments
@ks905383: Could it be that The DAYMET data has 1D |
Yeah - it's currently only tested / written for rectangular grids. Expanding processing to work with non-rectangular grids should not be the most complicated thing in the world, and might be achievable mainly through expanding the functionality of In the meantime, I'll see about putting in a helpful error message if a non-rectangular grid is detected, or one where the coordinates aren't the dimensions etc. |
@ks905383, okay, it's not just user error. Good! 😄 |
Here is an example of how I generated cells for Daymet grids. It might be of some help. https://github.com/nhm-usgs/onhm-fetcher-parser/blob/master/pkg/CalcDaymetWeights.py |
hm... it might. I personally haven't used |
oh nice, thanks for that - I'll take a look |
@ks905383 would be interested in helping add capability for processing structured non-uniform grids to xagg Kevin. I've got code to generate lat_bnds and lon_bnds. Wondering if you would have time and interest to meet and discuss how it would make sense to you to add that capability? Cheers Kevin. |
Hey @rmcd-mscb , apologies for the long radio silence here. That actually sounds great - we could chat later this week or next week and see about integrating it? |
Thanks @ks905383 - I sent a calendar invite. |
Hopefully, all major processing changes would only have to be in The remaining issues beyond that are largely semantic, in particular related to hardcoded calls to In
In
|
I was thinking about using xagg with DAYMET again, and thinking, "okay, it doesn't have 1D lon,lat coordinates, but it does have 1D x,y, coordinates" (lambert conformal projection, see this notebook), so I'm wondering if I could just:
I'm thinking the real limitation is the algorithm that needs 1D coordinates.... What would be the problems with this approach? |
DAYMET data has lat and long that is 2 dimensional and x and y that are 1 dimensional. I dropped lat and long, and when running pixel overlap I get the following error:
ValueError: cannot reindex or align along dimension 'lon' because the index has duplicate values
Any suggestions or help is appreciated.
Mike
The text was updated successfully, but these errors were encountered: