We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the stactools-datacube package we extend an Item like this:
stactools-datacube
asset = item.get_assets()[asset_name] datacube = extend_asset(item, asset, rtol)
This used to work, but with pystac==1.8.3 this results in an empty asset. When explicitly re-adding the asset it works again:
pystac==1.8.3
asset = item.get_assets()[asset_name] datacube = extend_asset(item, asset) item.add_asset(asset_name, asset)
Is it now required to re-add the asset to the item to trigger the update?
The text was updated successfully, but these errors were encountered:
I'd access the assets dictionary directly if you want to modify it:
asset = item.assets[asset_name]
The behavior of get_assets was intentionally changed in #1087.
get_assets
Sorry, something went wrong.
Thanks @gadomski, will fix this in stactools-datacube
No branches or pull requests
In the
stactools-datacube
package we extend an Item like this:This used to work, but with
pystac==1.8.3
this results in an empty asset. When explicitly re-adding the asset it works again:Is it now required to re-add the asset to the item to trigger the update?
The text was updated successfully, but these errors were encountered: