|
4 | 4 | - **Conformance Classes:** |
5 | 5 | - `STAC API - Item Search` binding: <https://api.stacspec.org/v1.0.0-rc.1/item-search#fields> |
6 | 6 | - `STAC API - Features` binding: <https://api.stacspec.org/v1.0.0-rc.1/ogcapi-features#fields> |
7 | | -- **Extension [Maturity Classification](https://github.com/radiantearth/stac-api-spec/blob/main/README.md#maturity-classification):** Candidate |
| 7 | +- **Extension [Maturity Classification](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/README.md#maturity-classification):** Candidate |
8 | 8 | - **Dependencies:** |
9 | | - - [STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/blob/main/item-search) |
10 | | - - [STAC API - Features](https://github.com/radiantearth/stac-api-spec/blob/main/ogcapi-features) |
| 9 | + - [STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/item-search) |
| 10 | + - [STAC API - Features](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/ogcapi-features) |
11 | 11 |
|
12 | 12 | STAC API by default returns every attribute in an item. However, Item objects can have hundreds of fields, or incredibly large |
13 | 13 | geometries, and even smaller Item objects can get big when millions are requested but not all information is used. This |
14 | 14 | fragment provides a mechanism for clients to request that servers to explicitly include or exclude certain fields. |
15 | 15 |
|
16 | 16 | This fragment may be bound to either or both of |
17 | | -[STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/blob/main/item-search) (`/search` endpoint) or |
18 | | -[STAC API - Features](https://github.com/radiantearth/stac-api-spec/blob/main/ogcapi-features) (`/collections/{collectionId}/items` endpoint) by |
| 17 | +[STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/item-search) (`/search` endpoint) or |
| 18 | +[STAC API - Features](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/ogcapi-features) (`/collections/{collectionId}/items` endpoint) by |
19 | 19 | advertising the relevant conformance class. |
20 | 20 |
|
21 | 21 | When used in a POST request with `Content-Type: application/json`, this adds an attribute `fields` with |
@@ -44,7 +44,7 @@ support the EO Extension, a successful HTTP response must be returned and the It |
44 | 44 | attribute. |
45 | 45 |
|
46 | 46 | If no `fields` are specified, the response is **must** be a valid |
47 | | -[ItemCollection](https://github.com/radiantearth/stac-spec/blob/main/itemcollection/README.md). If a client excludes |
| 47 | +[ItemCollection](https://github.com/radiantearth/stac-spec/tree/v1.0.0-rc.1/itemcollection/README.md). If a client excludes |
48 | 48 | attributes that are required in a STAC Item, the server may return an invalid STAC Item. For example, if `type` |
49 | 49 | and `geometry` are excluded, the entity will not even be a valid GeoJSON Feature, or if `bbox` is excluded then the entity |
50 | 50 | will not be a valid STAC Item. |
|
0 commit comments