|
1 | | -<img src="https://github.com/radiantearth/stac-site/raw/master/images/logo/stac-030-long.png" alt="stac-logo" width="700"/> |
2 | 1 |
|
3 | 2 | [](https://travis-ci.org/boundlessgeo/staccato) |
4 | 3 | [](https://quay.io/repository/boundlessgeo/staccato) |
5 | 4 | [](https://gitter.im/SpatioTemporal-Asset-Catalog/Lobby "Gitter chat") |
6 | 5 |
|
7 | 6 | ## About |
8 | 7 |
|
| 8 | +Staccato is a server that enables browsing and search of geospatial assets like satellite imagery. It implements the |
| 9 | +SpatioTemporal Asset Catalog (STAC) standard and is backed by [ElasticSearch](https://www.elastic.co/products/elasticsearch). |
| 10 | +In addition to the core STAC catalog browsing and search functionality, it includes support for transactions, statistics, |
| 11 | +auto-generated schemas, [gRPC](https://grpc.io/) endpoints and [Kafka](https://kafka.apache.org/) ingestion. |
| 12 | + |
| 13 | +Staccato is built using the latest versions of [Spring Boot](https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/) |
| 14 | +and [Spring WebFlux](https://docs.spring.io/spring/docs/current/spring-framework-reference/web-reactive.html). The |
| 15 | +codebase is written reactively, utilizing the [Project Reactor](https://projectreactor.io) library. |
| 16 | + |
| 17 | + |
| 18 | +## About the STAC Spec |
| 19 | + |
| 20 | +<img src="https://github.com/radiantearth/stac-site/raw/master/images/logo/stac-030-long.png" alt="stac-logo" width="300"/> |
| 21 | + |
9 | 22 | The SpatioTemporal Asset Catalog (STAC) specification aims to standardize the way geospatial assets are exposed online |
10 | 23 | and queried. A 'spatiotemporal asset' is any file that represents information about the earth captured in a certain |
11 | 24 | space and time. The initial focus is primarily remotely-sensed imagery (from satellites, but also planes, drones, |
12 | 25 | balloons, etc), but the core is designed to be extensible to SAR, full motion video, point clouds, hyperspectral, LiDAR |
13 | 26 | and derived data like NDVI, Digital Elevation Models, mosaics, etc. |
14 | 27 |
|
15 | | -The goal is for all major providers of imagery and other earth observation data to expose their data as SpatioTemporal |
16 | | -Asset Catalogs, so that new code doesn't need to be written whenever a new JSON-based REST API comes out that makes its |
17 | | -data available in a slightly different way. This will enable standard library components in many languages. STAC can |
18 | | -also be implemented in a completely 'static' manner, enabling data publishers to expose their data by simply publishing |
19 | | -linked JSON files online. |
20 | | - |
21 | | -## WARNING |
22 | | - |
23 | | -The specification is currently still an early version, with the potential for some major things to change. The core is |
24 | | -now fleshed out, so implementors are encouraged to try it out and give feedback. But the goal is to actually be able to |
25 | | -act on that feedback, which will mean changes are quite possible. |
| 28 | +**For more see the [STAC Spec github repo](https://github.com/radiantearth/stac-spec)** |
26 | 29 |
|
27 | | -But efforts will be made to maintain the core fields established in the central |
28 | | -[Item spec](https://github.com/radiantearth/stac-spec/tree/master/item-spec), |
29 | | -[Catalog spec](https://github.com/radiantearth/stac-spec/tree/master/catalog-spec) and |
30 | | -[Collection spec](https://github.com/radiantearth/stac-spec/tree/master/collection-spec). The minimal amount is |
31 | | -specified right now, but best practices should emerge with implementation and more will likely be specified. |
32 | 30 |
|
33 | 31 | ## Requirements |
34 | 32 |
|
@@ -208,7 +206,7 @@ the item's properties. |
208 | 206 |
|
209 | 207 | ### Overview |
210 | 208 |
|
211 | | -The STAC item spec only has one requirement for item properties: to provide a `datetime` field. Properties specific to |
| 209 | +The [STAC Item spec](https://github.com/radiantearth/stac-spec) only has one requirement for item properties: to provide a `datetime` field. Properties specific to |
212 | 210 | certain datasets or product types will be developed by the community as extensions and move through a series of maturity |
213 | 211 | steps as outlined [here](https://github.com/radiantearth/stac-spec/tree/master/extensions). This STAC implementation was |
214 | 212 | originally designed for internal use at Boundless Spatial and was intended to only offer only a small number of static |
|
0 commit comments