-
Notifications
You must be signed in to change notification settings - Fork 265
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
MFDataset not support NETCDF4 #1240
Comments
probably better to use xarray.mf_dataset anyway |
MFDataset really only requires the classic data model, so we could remove the check for the file format. The problem will be if NETCDF4 files are used that don't use the classic data model it may fail. |
I means "How to read NETCDF4 files by MFDataset ". Reading NETCDF4 files one by one is too slow!
…------------------ 原始邮件 ------------------
发件人: "Unidata/netcdf4-python" ***@***.***>;
发送时间: 2023年3月15日(星期三) 晚上10:55
***@***.***>;
***@***.******@***.***>;
主题: Re: [Unidata/netcdf4-python] MFDataset not support NETCDF4 (Issue #1240)
MFDataset really only requires the classic data model, so we could remove the check for the file format. The problem will be if NETCDF4 files are used that don't use the classic data model it may fail.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I think we understood your meaning - xarray.mf_dataset has better functionality than netCDF4.MFDataset. xarray uses netCDF4 under the hood for netCDF file I/O. |
xarray does a lot that can be useful. Nonetheless, using the netCDF4 lib directly has a lot of use cases. We are bitten a lot by this limitation -- netcdf4 is no longer rare, and is the default in most cases -- it seems we could remove this limitation pretty easily (at least for "classic" files -- and even for non-classic, probably be a bit smart about it :-) Would a PR be accepted? -CHB |
NOTE: " if NETCDF4 files are used that don't use the classic data model it may fail." what would cause it to fail? one thing I can think of is more than one unlimited dimension -- any others? groups would be problematic, too. But I think the code could check for the actual feature(s) that matter, rather than the file format, yes. e.g. we commonly get a bunch o' netcdf4 files that we can't use with MFDAtaset, but we can simply convert them to netcdf3, and it all works -- so file format is not really the issue here, it's actual data layout and features.. or am I missing something? |
Ping! I'm happy to work on a PR -- but only if someone can tell me it has a chance of being accepted .... @jswhit What do you think? |
The text was updated successfully, but these errors were encountered: