A STAC API server with multiple backends.
To run a server from the command-line, use stac-cli. Any arguments will be interpreted as hrefs to STAC collections, items, and item collections, and will be loaded into the server on startup.
stacrs serve collection.json items.jsonTo use the pgstac backend:
stacrs serve --pgstac postgresql://username:password@localhost:5432/postgisIf you'd like to serve your own pgstac backend with some sample items:
docker compose up -d pgstac
scripts/load-pgstac-fixtures # This might take a while, e.g. 30 seconds or soTo use this library in another application:
[dependencies]
stac-server = "0.3"There is currently no infrastructure-as-code for deploying stac-server. We hope to provide this support in the future.
stac-server has two optional features.
The axum feature enables routing and serving using axum.
In order to use the pgstac, you need to enable the pgstac feature.
This table lists the provided backends and their supported conformance classes and extensions:
| Capability | Memory backend | Pgstac backend |
|---|---|---|
| STAC API - Core | ✅ | ✅ |
| STAC API - Features | ✅ | ✅ |
| STAC API - Item Search | ✅ | ✅ |
| Aggregation extension | ✖️ | ✖️ |
| Browseable extension | ✖️ | ✖️ |
| Children extension | ✖️ | ✖️ |
| Collection search extension | ✖️ | ✖️ |
| Collection transaction extension | ✖️ | ✖️ |
| Fields extension | ✖️ | ✖️ |
| Filter extension | ✖️ | ✅️ |
| Free-text search extension | ✖️ | ✖️ |
| Language (I18N) extension | ✖️ | ✖️ |
| Query extension | ✖️ | ✖️ |
| Sort extension | ✖️ | ✖️ |
| Transaction extension | ✖️ | ✖️ |
This crate is part of the stac-rs monorepo, see its README for contributing and license information.