This extension is used to describe processing history of both assets and the STAC metadata. For STAC metadata, the software that was used to create the data is often public (at least in part). We could provide more guidance/structure around how to provide that information. I haven't fully thought this through, but that might look like this:
Field Name Type Description processing:software List<Software
> Software that was used to create assets or the STAC object itself, in order from the first software used to the last
And then the Software
object:
stactools-landsat
href string An href to the source code, e.g. https://github.com/stactools-packages/landsat
. This could also be the href from a package management system, e.g. https://pypi.org/project/stactools-landsat/
version string A version identifier, e.g. v1.2.3
. This could also be an SHA from a version control system, e.g. 6dcb09b5b57875f334f61aebed695e2e4193db5e
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4