Skip to content
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

Audit: Are we always using fsspec in python examples? #47

Open
wildintellect opened this issue Aug 31, 2023 · 2 comments
Open

Audit: Are we always using fsspec in python examples? #47

wildintellect opened this issue Aug 31, 2023 · 2 comments

Comments

@wildintellect
Copy link
Contributor

@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...

@sharkinsspatial
Copy link

@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.

@wildintellect
Copy link
Contributor Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants