-
Notifications
You must be signed in to change notification settings - Fork 280
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
Loading not possible with non-standard netcdf variable names #5171
Labels
Comments
In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity. If this issue is still important to you, then please comment on this issue and the stale label will be removed. Otherwise this issue will be automatically closed in 28 days time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A user presented some data from an online repository which has a lot of rather weird variable names (but is otherwise fairly sensible).
Probably from the PALM-4U atmospheric model
The question being : should we add some compliance to allow this?
Iris has been very strict on this since v2.3 -- see #3399, and refuses to load the file,
raising
ValueError: 'theta(0)' is not a valid NetCDF variable name.
.I think the main problem for Iris, which motivated being stricter in that change, is that we really wouldn't want to save data with these kinds of variable names
-- and maybe they could also cause other internal problems in Iris, like selecting cubes/coords by name ?
Resolution:
I personally think that is a poor reason for erroring it on load -- a tolerant adjusment would be "more ideal" IMHO.
A user comment was :
It seems a bit odd not to be able to load this, claiming that it is not "good netcdf", whereas there is nothing really wrong with the file : So, there's a difference between what netcdf say is generally valid, and what you can have in an actual HDF5-based netCDF4 file.
Needless to say, xarray has no problem with this data !
Adding the issue to the CF compliance discussion
Some Details...
Example file dump (shortened):
List of variable names, :
and all the "invalid" ones
The text was updated successfully, but these errors were encountered: