Xee
Xee copied to clipboard
google
An Xarray extension for Google Earth Engine
Avoids the expensive call to toList unless the ImageCollection contains more than 5000 images and we are slicing past the 5000th image. Fixes https://github.com/google/Xee/issues/88 where xee wasn't recognizing new bands...
I have a script ingesting ~200 GB of landsat imagery with the current multi-threaded implementation (no Dataflow). Eventually, I always get an exception like: ``` requests.exceptions.ChunkedEncodingError: ('Connection broken: IncompleteRead(9186238 bytes...
This is definitely a nice-to-have, but I am wondering if there is a reliable way to estimate the number of eecu-hours. Considering we pay for these hours, it would be...
``` ResourceWarning: Enable tracemalloc to get the object allocation traceback xee/ext.py:432: ResourceWarning: unclosed ``` This is caused by #9.
There are some differences between how Xee opens data and "what users expect" (thanks for your feedback, @shoyer).
This should defer all metadata RPCs to the data access time.
Description TBD
This is a really common use case for climate and weather data. For example, for surface forecasts we will want to read 4d data (time, lat, lon, init_time, valid_time). Atmospheric...
This is related to #29. There is a single costly EE RPC call that we make that may not be essential. Right now, we need to access all the `system:time_start`...
I've noticed a regression in performance of Xee from the time we've introduced micro benchmarks. Before: ``` open_dataset():avg=11.89,std=3.99,best=6.71,worst=22.73 open_and_chunk():avg=11.44,std=3.40,best=7.46,worst=20.65 open_and_write():avg=58.49,std=12.15,best=48.75,worst=84.94 ``` Today: ``` open_dataset():avg=58.46,std=11.26,best=44.83,worst=76.46 open_and_chunk():avg=51.79,std=8.26,best=39.26,worst=69.36 open_and_write():avg=102.41,std=11.80,best=90.74,worst=129.80 ```