Closed sparshgarg23 closed 8 months ago
Thanks for opening your first issue here at xarray! Be sure to follow the issue template! If you have an idea for a solution, we would really welcome a Pull Request with proposed changes. See the Contributing Guide for more. It may take us a while to respond here, but we really value your contribution. Contributors like you help make xarray better. Thank you!
is this the same error as umr-lops/xarray-safe-rcm#75? If so, let's discuss that there.
@keewis yes it's the same issue,I was able to trace the error.But I am not sure if it's because of xarray or some other library UMR-LOPS is using ,which is causing this error.
Thanks for your report. It's due to a change in xarray but has to be fixed downstream - see https://github.com/umr-lops/xarray-safe-rcm/issues/75#issuecomment-1953510785. I'll close here for now.
What happened?
UMR-LOPS has introduced XSAR a library to work with RCM dataset. when working with the following code
I am encountering the following error
As you can see from the last sections in the trace,the issue is with xarray/dataset.py when we unstack the dataframe. Any ideas why this is happening.The issue doesn't occur with radarsat 2 or any other dataset.So is this an xarray problem or should I raise the issue at umr-lops?
What did you expect to happen?
the error shouldn't be there,and I should be able to view the dataframe. as shown in below link https://cyclobs.ifremer.fr/static/sarwing_datarmor/xsar/examples/rcm.html
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
No response
Anything else we need to know?
No response
Environment