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
From my understanding, this repo defines an Item's primary key as only its id field, not the collection it belongs to. This restricts items with the same id from being inserted into multiple different collections. However, according to the stac spec here (https://github.com/radiantearth/stac-spec/blob/master/item-spec/item-spec.md#id), the id field only needs to be unique within their own collections, not globally.
Is this an intentional break from the stac specification? If not, can the Item implementation be changed to support the same id in different collections?
The text was updated successfully, but these errors were encountered:
From my understanding, this repo defines an Item's primary key as only its id field, not the collection it belongs to. This restricts items with the same id from being inserted into multiple different collections. However, according to the stac spec here (https://github.com/radiantearth/stac-spec/blob/master/item-spec/item-spec.md#id), the id field only needs to be unique within their own collections, not globally.
Is this an intentional break from the stac specification? If not, can the Item implementation be changed to support the same id in different collections?
The text was updated successfully, but these errors were encountered: