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
@sharkinsspatial made a valid point that for best practices we should use fsspec in our python examples so that various cloud sources and local file paths all just work interchangeably.
@wildintellect I should clarify here that if we are using rasterio with a known source location, it is fine to use vsi patterns as well (this might often be preferable in some benchmarking scenarios as it is easier for us to view the behavior of the underlying vsicurl calls).
My comment in the call was more related to stactools-packages where we would like to make the package data source location agnostic without having to maintain multiple code paths.
@sharkinsspatial what would you tell ordinary science users of cloud optimized formats to do?
For me that's the primary audience, secondary we can add notes about the alternatives traditional methods and when they are more useful.
@sharkinsspatial made a valid point that for best practices we should use
fsspec
in our python examples so that various cloud sources and local file paths all just work interchangeably.Oddly https://developmentseed.org/cloud-optimized-geospatial-formats-guide/cloud-optimized-geotiffs/cogs-examples.html doesn't even show how to read a COG subset but rather uses earthaccess to download a whole file...
The text was updated successfully, but these errors were encountered: