-
Notifications
You must be signed in to change notification settings - Fork 38
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
Accessing xarray when using goes_nearesttime loaded in memory #39
Comments
Hi @nrchade, Thanks for reporting this behavior. I admit, the in-memory processing is not well executed in goes2go (would love to see a pull request improving the behavior). I haven't worked on or tested the I'll leave this issue open and try to find time to investigate the |
Hi @blaylockbk, I ultimately did what you suggested, download the file, process, then deleted it to move to the next one. It did seem faster to load into memory when it did download which seemed odd. I think your work on this package is to be commended as you have helped to make working with this type of data easier for the layperson. I ultimately needed a small amount of info specific to a certain geography and prior attempts to solving this problem seemed overwhelming. Many thanks! |
Outstanding! |
results in this error:
raise ValueError("I/O operation on closed file.")
ValueError: I/O operation on closed file.
When download = True and return as filelist, I have no issues opening xarray.open_dataset, but these files are huge so i was hoping to load in memory, process, and then move onto the next one. Am i doing something wrong when trying to access the data once this is loaded into memory?
The text was updated successfully, but these errors were encountered: