New lat-lon variables recognized #196
Closed
Conversation
This file contains 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
…uses error when dy is ~ to dx (i.e. non-zero)
… can be created as long as latlon coordinates are recognized by name in Datasets
|
Hi @anthony-ds , thank you very much for your contribution! This proposed change looks very similar to the case proposed in Issue #171 ; please take a look. Even though we understand the convenience of adding the non-WRF variable naming options into the tool, we believe the tool should be kept specific to the WRF model variable naming conventions. As you will see from Issue #171 though, you'd be able to make your dataset variables compatible with WRF-Python very easily with something like the following:
then execute WRF-Python functions. Would this help? |
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 am using WRF-Python to create vertical cross-sections (using vertcross) on non-wrfout files. However, these files use "lat" or "lon" as coordinate names, not "XLAT" or "XLONG". I've added these in, in the file util.py.
Also, I commented "dy = 0.0" in latlonutils.py, as this produces an error when trying to create a projection from metadata instead of a file.