-
Notifications
You must be signed in to change notification settings - Fork 1
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
Switch from stackstc to odc-stac? #12
Comments
IMO the community is still unsure of which (if either) is The One™. If you do integrate/switch, I would love to hear your thoughts on the comparison between the two w.r.t. ease of integration, ease of use, etc. |
Yeah I read through opendatacube/odc-stac#54 and came out the other end thinking that odc-stac probably has more of a future. I'll see if I can com e up with any ideas around how to make odc-stac more ergonomic. |
Maybe have both? Currently, With In addition, you could register |
Oh that is an interesting idea. I wonder if that would feel surprising to the user. |
I just stumbled upon this discussion and wanted to add to @weiji14's comment, that a major difference is also the parsing of STAC metadata to Xarray, which in my opinion is an important difference to consider. Quoting from opendatacube/odc-stac#54 (comment) :
Here is an example of how it can look like in practice with a dataset created from https://github.com/SAR-ARD/S1_NRB : Users can then easily filter the array based on the parsed STAC Item properties: ds_filtered = ds.where((ds['sat:relative_orbit'] == 44), drop=True) I am working a lot with local, static STAC Catalogs without using an API or database to do the querying beforehand. |
It seems like there is a shift towards using odc-stac rather than stackstac. I'm wondering if that needs to be configurable somehow or if this library should just pick one.
The text was updated successfully, but these errors were encountered: