- Title: AUXIP
- Identifier: https://home.rs-python.eu/auxip-stac-extension/v1.1.0/schema.json
- Field Name Prefix: auxip
- Scope: Item
- Extension Maturity Classification: Pilot
- Owner: @vprivat-ads
This document explains the AUXIP Extension to the SpatioTemporal Asset Catalog (STAC) specification. Allows to describe Copernicus auxiliary files from ADGS as STAC items.
- Examples:
- Item example: Shows the basic usage of the extension in a STAC Item
- JSON Schema
- Changelog
The fields in the table below can be used in these parts of STAC documents:
- Catalogs
- Collections
- Item Properties (incl. Summaries in Collections)
- Assets (for both Collections and Items, incl. Item Asset Definitions in Collections)
- Links
| Field Name | Type | Description |
|---|---|---|
| auxip:id | string (uuid) | REQUIRED. UUID for the product instance within the AUXIP. |
Universally unique identifier (UUID). The Id is a local identifier for the product instance within the AUXIP, assigned by the service managing the AUXIP.
All contributions are subject to the STAC Specification Code of Conduct. For contributions, please follow the STAC specification contributing guide Instructions for running tests are copied here for convenience.
The same checks that run as checks on PR's are part of the repository and can be run locally to verify that changes are valid.
To run tests locally, you'll need npm, which is a standard part of any node.js installation.
First you'll need to install everything with npm once. Just navigate to the root of this repository and on your command line run:
npm installThen to check markdown formatting and test the examples against the JSON schema, you can run:
npm testThis will spit out the same texts that you see online, and you can then go and fix your markdown or examples.
If the tests reveal formatting problems with the examples, you can fix them with:
npm run format-examples
This project is funded by the EU and ESA.