yaml and python options to define regions #387
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wwieder
changed the title
|
I ended up getting distracted from regions and working on #382 instead, so I'll let @megandevlan handle this. I vote for the actual YAML file though. |
|
I vote for the actual yml file as well, though I don't know that I have the bandwidth to test things out today. I can get to this early next week though! |
|
OK, I'll merge this in so you have access to the file when you're ready @megandevlan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I pulled the regions and lat-lon boundaries from the .nc file used by the current land diagnostics package to address #376 This was done:
@megandevlan & @samsrabin please see if this yaml file can be read in and used as expected in the regional subsetting you're working on.
Note: there are regions that span 0 longitude. Not sure what the best way to handle this is?
I've also provided lats -180 to 180, as I think this is what uxarray needs, but would have to be modified for xarray datasets that are 0-360.
Finally, I tried using copilot to see if the yaml file was formatted correctly to create a python dictionary and it just created the python dictionary for me! I've included that here too, but both files don't need to be merged. Dealers choice on which you prefer