Skip to content

Merge remote-tracking branch 'origin/master' into dev #573

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
m-mohr merged 2 commits into from
Aug 23, 2019
Merged

Merge remote-tracking branch 'origin/master' into dev #573

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
936af54
Merge remote-tracking branch 'origin/master' into dev
m-mohr Aug 23, 2019
7398077
Fixed merge.
m-mohr Aug 23, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
**Related Issue(s):** #


**Proposed Changes:**

1.
2.

**PR Checklist:**

- [ ] This PR has **no** breaking changes.
- [ ] I have added my changes to the [CHANGELOG](https://github.com/radiantearth/stac-spec/blob/dev/CHANGELOG.md) **or** a CHANGELOG entry is not required.
- [ ] API only: I have run `npm run generate-all` to update the [generated OpenAPI files](https://github.com/radiantearth/stac-spec/blob/dev/api-spec/README.md#openapi-definitions).
13 changes: 9 additions & 4 deletions api-spec/examples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,17 @@
# STAC API Examples

A typical WFS will have multiple collections, and each will just offer simple search for its particular collection at `/collections/{collectionId}/items`.
For advanced queries across collections use the STAC API at `/stac/search`.
The filtering is made to be compatible with the STAC API whenever feasible, and the two specs seek to share the general query and filtering patterns.
The key difference is that a STAC search endpoint will do cross collection search.
A typical WFS will have multiple collections, and each will just offer simple search for its particular collection at `GET /collections/{collectionId}/items`.
Due to the limited parameter support in WFS3, it is recommended to use the STAC API endpoint `POST /stac/search` for advanced queries.
The filtering is made to be compatible between STAC API and WFS3 whenever feasible, and the two specs seek to share the general query and filtering patterns.
The key difference is that the STAC API search endpoints will do cross collection search.

Implementations may **optionally** provide support for the full superset of STAC API query parameters to the `/collections/{collectionId}/items` endpoint,
where the collection ID in the path is equivalent to providing that single value in the `collections` query parameter in STAC API.

## WFS

Note that the WFS endpoints _only_ supports HTTP GET. HTTP POST requests are not supported.

Request all the data in `mycollection` that is in New Zealand:

```
Expand Down