8000
Use computePixels endpoint to extract data without going through an export · Issue #17 · water3d/eedl · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earth Engine now has a computePixels endpoint, which supports parallel requests via, e.g. threads and Dask, and where we could obtain image data directly into something like an XArray DataArray. This saves the need to configure exports, and we could write tiles directly to our location of choice rather than a formal export through someone's account. We'd need to do some work to make the requests and tile them, most likely (they'd need to give an ROI, I think), and for small requests, tile in memory and larger ones, tile with GDAL.
This would be an advanced feature, but something pretty awesome to have. We may just want a feature that makes retrieval over this endpoint more generic and easier to use and include that either as a separate simple library or as a feature within this one, then we can work on integrating it for actual downloads later. We'd likely want to make the class-based downloads backend happen first
The text was updated successfully, but these errors were encountered:
Earth Engine now has a computePixels endpoint, which supports parallel requests via, e.g. threads and Dask, and where we could obtain image data directly into something like an XArray DataArray. This saves the need to configure exports, and we could write tiles directly to our location of choice rather than a formal export through someone's account. We'd need to do some work to make the requests and tile them, most likely (they'd need to give an ROI, I think), and for small requests, tile in memory and larger ones, tile with GDAL.
See this page for docs: https://developers.google.com/earth-engine/guides/data_extraction#getting-image-data-from-computed-images
This would be an advanced feature, but something pretty awesome to have. We may just want a feature that makes retrieval over this endpoint more generic and easier to use and include that either as a separate simple library or as a feature within this one, then we can work on integrating it for actual downloads later. We'd likely want to make the class-based downloads backend happen first
The text was updated successfully, but these errors were encountered: