|
3 | 3 | - **Title:** Storage |
4 | 4 | - **Identifier:** <https://stac-extensions.github.io/storage/v1.0.0/schema.json> |
5 | 5 | - **Field Name Prefix:** storage |
6 | | -- **Scope:** Item, Asset |
| 6 | +- **Scope:** Item, Collection |
7 | 7 | - **Extension [Maturity Classification](https://github.com/radiantearth/stac-spec/tree/master/extensions/README.md#extension-maturity):** Pilot |
8 | 8 | - **Owner**: @davidraleigh @matthewhanson |
9 | 9 |
|
10 | 10 | This document explains the Storage Extension to the [SpatioTemporal Asset Catalog](https://github.com/radiantearth/stac-spec) (STAC) specification. |
11 | | -This extension adds fields to STAC Item and Asset objects, allowing for details related to cloud storage access and costs to be associated |
12 | | -with a STAC Item. This extension does not cover NFS solutions provided by PaaS cloud companies. |
| 11 | +It allows adding details related to cloud storage access and costs to be associated with STAC Assets. |
| 12 | +This extension does not cover NFS solutions provided by PaaS cloud companies. |
13 | 13 |
|
14 | 14 | - Examples: |
15 | 15 | - [Item example 1](examples/item-naip.json): Shows the basic usage of the extension in a STAC Item. |
16 | 16 | - [Item example 2](examples/item-nsl.json): Another example of basic usage. |
17 | 17 | - [JSON Schema](json-schema/schema.json) |
18 | 18 | - [Changelog](./CHANGELOG.md) |
19 | 19 |
|
20 | | -## Item Fields |
| 20 | +## Fields |
21 | 21 |
|
22 | | -| Field Name | Type | Description | |
23 | | -| ----------- | ------ | ----------- | |
24 | | -| storage:platform | string | The [cloud provider](#providers) where data is stored | |
25 | | -| storage:region | string | The region where the data is stored. Relevant to speed of access and inter region egress costs (as defined by PaaS provider) | |
26 | | -| storage:requester_pays | bool | Is the data requester pays or is it data manager/cloud provider pays. *Defaults to false* | |
27 | | -| storage:tier | string | The title for the tier type (as defined by PaaS provider) | |
| 22 | +The fields in the table below can be used in these parts of STAC documents: |
| 23 | + |
| 24 | +- [ ] Catalogs |
| 25 | +- [ ] Collections |
| 26 | +- [x] Item Properties (incl. Summaries in Collections) |
| 27 | +- [x] Assets (for both Collections and Items, incl. Item Asset Definitions in Collections) |
| 28 | +- [ ] Links |
| 29 | + |
| 30 | +| Field Name | Type | Description | |
| 31 | +| ---------------------- | --------- | ----------- | |
| 32 | +| storage:platform | string | The [cloud provider](#providers) where data is stored | |
| 33 | +| storage:region | string | The region where the data is stored. Relevant to speed of access and inter region egress costs (as defined by PaaS provider) | |
| 34 | +| storage:requester_pays | boolean | Is the data requester pays or is it data manager/cloud provider pays. *Defaults to false* | |
| 35 | +| storage:tier | string | The title for the tier type (as defined by PaaS provider) | |
28 | 36 |
|
29 | 37 | While these are all valid properties on an Item, they will typically be defined per-asset. If a field applies equally |
30 | 38 | to all assets (e.g., storage:platform=AWS if all assets are on AWS), then it should be specified in Item properties. |
|
0 commit comments