Skip to content


eoAPI combines several state-of-the-art projects to create an entire Earth Observation API. Each service can be used and deployed independently, but eoAPI creates the interconnections between each service:


The STAC database is at the heart of eoAPI and is the only mandatory service. We use PgSTAC Postgres schema and functions, which provides functionality for STAC Filters, CQL2 search, and utilities to help manage the indexing and partitioning of STAC Collections and Items.

PgSTAC is used in production to scale to hundreds of millions of STAC items. PgSTAC implements core data models and functions to provide a STAC API from a PostgreSQL database. PgSTAC is entirely within the database and does not provide an HTTP-facing API. The Stac FastAPI PgSTAC backend and Franklin can be used to expose a PgSTAC catalog. Integrating PgSTAC with any other language with PostgreSQL drivers is also possible.

PgSTAC Documentation:

pyPgSTAC Documentation:


The Metadata service deployed in eoAPI is built on stac-fastapi.pgstac application.

By default, the STAC metadata service will have a set of endpoints to search and list STAC collections and items.




The Raster service deployed in eoAPI is built on top of titiler-pgstac.

It enables Raster visualization for a single STAC Item and large-scale (multi collections/items) mosaic based on STAC search queries.



Items endpoints

Mosaic endpoints


The OGC Features and (Mapbox Vector) Tiles API service deployed in eoAPI is built on top of tipg).

It enables vector Features/Features Collection exploration and visualization for Tables stored in the Postgres database (in the public schema).



OGC Features

OGC Tiles

Browsing UI

The browsing UI deployed in eoAPI is built on the radiant earth STAC browser, and provides a configurable, user-friendly interface to search across and within collections and quickly visualize single items assets.