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
The item spec says that STAC ids are only unique within a collection. But the best practices page says "...existing providers can easily use their same ID when they translate their data into STAC - they just need to be sure it is globally unique, so may need a prefix." Do STAC ids need to be globally unique or only within a collection?
I think I might have found the source of the apparent discrepancy. In the collection spec it says:
"It is important that Collection identifiers are unique across the provider. And providers should strive as much as possible to make their Collection ids 'globally' unique, prefixing any common information with a unique string. This could be the provider's name if it is a fairly unique name, or their name combined with the domain they operate in."
So in the best practices, maybe there is some conflation of the recommendation that collection ids be globally unique, while item ids have no such requirement or even recommendation?
The text was updated successfully, but these errors were encountered:
I think we decided on a change in one the the RCs: Collection IDs should be globally unique, Item IDs should be unique per collection. I'm pretty sure we just did not manage to update all occurances properly, so we should update the best practices.
@gsf-sellis wrote on Gitter:
The text was updated successfully, but these errors were encountered: