Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
xr.open_dataset user experience on S1-SLC
See original GitHub issueIssue to analyse the possible behaviour when calling xr.open_dataset on Sentinel 1 SLC data.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Option 4 looks nice, but AFAIK it has a main drawback: the accessor will be present on every dataset, independetly on whether it has been opened with
sentinel_xarrayor not, which looks pretty odd.Current agreement with @aurghs is to map the data to
open_datasetgroupoption and leave it as similar as possible to the original structure. The structure is described in https://github.com/bopen/xarray-sentinel/blob/main/docs/DATATREE.mdOnce xarray solves https://github.com/pydata/xarray/issues/4118 we may reassess (tracked by #60).
I would propose to close this issue.