This directory contains a number of samples and more 'real world' examples of how a STAC Item could be implemented. As of right now none of these are actual production implementations - they are more adaptations of current catalogs to the STAC specifications. In time these will evolve to be examples of truly real world implementations.
This document also contains discussion of the various examples in this folder.
sample.json is the most minimal possible compliant Item record. Most all data will include additional fields, as STAC is designed to be a minimal common subset. But it is useful for showing exactly what is required.
sample-full.json is a more realistic example, for a hypothetical analytic image acquisition from a satellite company called 'cool sat'. It includes additional fields, including some from the Earth Observation extension, as well as some vendor specific additions. It also links to a variety of assets that is typical for satellite imagery, as most providers include a number of complementary files.
DigitalGlobe The DigitalGlobe sample is taken from the proposed DigitalGlobe static catalog pull request, with minor field updates to validate against the the item specification.
Landsat8 The Landsat8 sample is meant to be an example of how an S3-based catalog like the Landsat on AWS public data set could be a STAC static catalog. It includes the 'collection' concept, which is explained more in the /extensions/examples/ folder.
Planet The Planet sample is an adaption of Planet's Data API returned JSON, with minor tweaks to have it fit in to a STAC Item.
CBERS The CBERS sample is copied from CBERS static STAC catalog.
These examples demonstrate that there is a range of potential implementations of STAC Items. Most were made by adapting the current implementations as minimally as possible. The hope is that there will emerge more consensus and best practices on the things outside of the core fields, to increase interoperability.
The Planet example is likely the least 'static' of the examples, as it was taken from Planet's Data API and just added on a few fields. DigitalGlobe's made a bit more changes to make it static, but still has that lineage. Landsat8 is primarily made thinking about how they are laid out on Amazon Web Services.
Catalog API's will tend to have more absolute links, while the static examples tend more towards relative links, representing actual files that are next to them. Planet's API shows a set of 'activation' assets that present a workflow to enable the data to be downloaded. This is not a desired end-state - ideally the data is more readily available in a Catalog API, or at least has a better workflow - but it shows how the asset field can be adapted.
Currently the additional metadata on assets is quite minimal - only a link is required. 'title' and 'type' are the only other specified fields.
The Planet example has some small bits about 'permissions'. The DigitalGlobe catalog would have similar concerns. The core idea would be that assets should provide links to the data, even if a user doesn't have permissions to actually access the data.
The Landsat example shows an idea of using 'prefixes' like eo: or l8: to help differentiate metadata fields that would be validated by different schemas. EO could be a shared earth observation schema. Using prefixes could also help point the way towards JSON-LD type validation.