-
Notifications
You must be signed in to change notification settings - Fork 0
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
Required changes to CABLE model output #1
Comments
Shouldn't iLAMB be fixed to properly support CF conventions? That could be a lot easier than forcing all data to comply with an arbitrary "standard". |
@aidanheerdegen I agree. There is currently ongoing development of a new version of ILAMB which uses xarray as its backend but it is yet to be released. It looks like they are taking a CF compliant approach in the new version (e.g. see here). It might be worth submitting a patch to (current) ILAMB to support |
Seems promising, but have they heard of https://github.com/xarray-contrib/cf-xarray? I'd be using that in a heartbeat for CF compliance and making data access as agnostic as possible.
Agreed. From a cursory appraisal it looks like the code would be relatively easy to change to support this. |
Judging from this comment, I think the developer is aware of cf-xarray |
Hah hah! Good catch, actually reading the code. Well they have their reasons, but I'd standardise on the good thing and treat the outlier as the exception. |
Here is the patch to allow for flexible NetCDF dimension names: rubisco-sfa/ILAMB#105 |
This doesn't implement CF conventions (examining units, standard_name or axis attribute). I thought the CABLE data had some of the correct attributions, but perhaps I got confused? |
@aidanheerdegen I see. I agree that examining the attributes on the coordinate variables for either Here are the NetCDF coordinate variables currently in the CABLE model output along with their attributes:
They all have a |
Agreed. I don't think you should do this, but note for completeness you also have the option to add an |
Here is the revised patch: rubisco-sfa/ILAMB#106 |
This issue thread documents the changes needed for CABLE model output to be used directly with ILAMB.
Albedo
units are not CF compliant: change from-
to1
or removeunits
attribute.Rename netCDF dimensions and coordinate variables:x -> lon
,y -> lat
. Note: this is not required by CF conventions.lat
,lon
andtime
respectively.Note: ILAMB is tested with CABLE model output from the latest trunk (CABLE3).
The text was updated successfully, but these errors were encountered: