fix: handle already existing collection.json #532
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the
collection_from_items.py
is run with a--uri
source of an S3 path which already contains acollection.json
file which is the output of a previous run of the script, it will fail.This is because of a KeyError exception for
"collection"
, which all the item STAC files have, but which the resultingcollection.json
file does not, as the collection ID is instead stored in the"id"
key.Swapping from
item_stac["collection"]
toitem_stac.get("collection")
eliminates this KeyError exception, and allows the script to run happily with a previously existingcollection.json
file, as it will be skipped and then overwritten.