You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2
Original file line number
Diff line number
Diff line change
@@ -11,10 +11,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
11
11
- Added recommendation to enable CORS for public APIs
12
12
13
13
### Changed
14
+
- Added Filter extension to integrate OAFeat Part 3 CQL
14
15
- Passing the `ids` parameter to an item search does not deactivate other query parameters [#125](https://github.com/radiantearth/stac-api-spec/pull/125)
15
16
- The first extent in a Collection is always the overall extent, followed by more specific extents. [opengeospatial/ogcapi-features#520](https://github.com/opengeospatial/ogcapi-features/pull/520)
16
17
17
18
### Deprecated
19
+
- Query extension is now deprecated. Replaced by the Filter extension using OGC CQL
Copy file name to clipboardExpand all lines: core/README.md
+11-9
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,8 @@
10
10
-**Extension [Maturity Classification](../extensions.md#extension-maturity):** Pilot
11
11
-**Dependencies**: None
12
12
13
-
The base of a STAC API is its landing page. This resource is the starting point to discover what behaviors the API supports via the `conformsTo` values and link relations.
13
+
The base of a STAC API is its landing page. This resource is the starting point to discover what behaviors
14
+
the API supports via the `conformsTo` values and link relations.
14
15
This behavior in a RESTful API is known as
15
16
[Hypermedia as the Engine of Application State (HATEOAS)](https://en.wikipedia.org/wiki/HATEOAS).
16
17
STAC API relies heavily on hypermedia for API resource navigation.
@@ -29,7 +30,8 @@ client must inspect the the `rel` (relationship) to understand what capabilities
29
30
Note the `conformsTo` JSON object follows exactly the structure of OGC API - Features [declaration of conformance
30
31
classes](http://docs.opengeospatial.org/is/17-069r3/17-069r3.html#_declaration_of_conformance_classes), except is available directly under
31
32
the landing page. This is a slight break from how OGC API does things, as STAC feels it is important for clients to be able to understand
32
-
conformance in a single request. Implementers choosing to also implement the OGC API - Features and/or STAC API - Features conformance classes must also implment the `/conformance` endpoint.
33
+
conformance in a single request. Implementers choosing to also implement the OGC API - Features and/or
34
+
STAC API - Features conformance classes must also implment the `/conformance` endpoint.
33
35
34
36
This particular catalog provides the ability to browse down to child STAC Collection objects through its `child` links, and also provides the search
35
37
endpoint to be able to search across items in its collections. Note though that none of those links are required, other servers may provide
@@ -47,13 +49,13 @@ API endpoints from OAFeat or STAC API to be implemented, so the following links
47
49
48
50
When implementing the STAC API Core conformance class, it it recommended to implement these Link relations.
|`root`| The root URI | STAC Core | Reference to self URI|
53
-
|`self`| The root URI | OAFeat | Reference to self URI|
54
-
|`service-desc`| The OpenAPI service description | OAFeat OpenAPI | Uses the `application/vnd.oai.openapi+json;version=3.0` media type to refer to the OpenAPI 3.0 document that defines the service's API |
55
-
|`service-doc`| An HTML service description | OAFeat OpenAPI | Uses the `text/html` media type to refer to a human-consumable description of the service |
56
-
|`child`| The child STAC Catalogs & Collections | STAC Core | Provides curated paths to get to STAC Collection and Item objects |
|`root`| The root URI | STAC Core| Reference to self URI|
55
+
|`self`| The root URI | OAFeat| Reference to self URI|
56
+
|`service-desc`| The OpenAPI service description | OAFeat OpenAPI | Uses the `application/vnd.oai.openapi+json;version=3.0` media type to refer to the OpenAPI 3.0 document that defines the service's API |
57
+
|`service-doc`| An HTML service description | OAFeat OpenAPI | Uses the `text/html` media type to refer to a human-consumable description of the service|
58
+
|`child`| The child STAC Catalogs & Collections | STAC Core | Provides curated paths to get to STAC Collection and Item objects|
57
59
58
60
It is also valid to have `item` links from the landing page, but most STAC API services are used to
59
61
serve up a large number of features, so they typically
|[Fields](item-search/README.md#fields)|[Item Search](item-search/) request | Adds parameter to control which fields are returned in the response. |*Pilot*|
56
-
|[Query](item-search/README.md#query)|[Item Search](item-search/)request | Adds parameter to search Item and Collection properties. |*Pilot*|
53
+
| Extension Name | Scope*| Description | Maturity |
|[Fields](item-search/README.md#fields)|[Item Search](item-search/) request | Adds parameter to control which fields are returned in the response. |*Pilot*|
56
+
|[Filter](item-search/README.md#filter)|[Item Search](item-search/)and [STAC - Features API](ogcapi-features)`/items` requests | Adds parameter to search Item and Collection properties. |*Pilot*|
57
57
|[Context](item-search/README.md#context)|[Item Search](item-search/) response ([ItemCollection](fragments/itemcollection/README.md)) | Adds search related metadata (context) to ItemCollection. |*Proposal*|
58
58
|[Sort](item-search/README.md#sort)|[Item Search](item-search/) request | Adds Parameter to control sorting of returns results. |*Pilot*|
59
59
|[Transaction](ogcapi-features/extensions/transaction/README.md)|[STAC - Features API](ogcapi-features) POST on `/items` endpoint, DELETE/PUT on `/items/{itemId}` endpoint | Adds PUT and DELETE endpoints for the creation, editing, and deleting of Item objects. |*Pilot*|
60
60
|[Items and Collections API Version](ogcapi-features/extensions/version/README.md)|[STAC - Features API](ogcapi-features) on `/items` endpoint | Adds GET versions resource to Collection and Item endpoints and provides semantics for a versioning scheme for Collection and Item objects. |*Proposal*|
61
+
|[Query](item-search/README.md#query)|[Item Search](item-search/) request | Adds parameter to search Item and Collection properties. |*Deprecated*|
61
62
62
63
### Conformance classes of extensions
63
64
64
65
Each extension has its own conformance URI, which is used in the `conformsTo` response of the landing page to let clients know what capabilities
65
66
the service supports. This are listed at the top of each extension description, but the full table is given here for ease of reference.
|[Items and Collections API Version](ogcapi-features/extensions/version/README.md)|<https://api.stacspec.org/v1.0.0-beta.1/ogcapi-features/extensions/version>|
|[Items and Collections API Version](ogcapi-features/extensions/version/README.md)|<https://api.stacspec.org/v1.0.0-beta.1/ogcapi-features/extensions/version>|
0 commit comments