Skip to content
/ resto Public
forked from jjrom/resto

A metadata catalog and search engine for geospatialized data

License

Notifications You must be signed in to change notification settings

nitreb/resto

This branch is 234 commits behind jjrom/resto:master.

Folders and files

NameName
Last commit message
Last commit date
Nov 28, 2023
Jun 24, 2024
Jun 21, 2024
Jun 12, 2024
Jun 24, 2024
Jun 24, 2024
Jan 17, 2023
Jun 7, 2024
Jan 23, 2023
May 5, 2019
Dec 7, 2023
Feb 16, 2023
Jan 12, 2023
Jun 29, 2022
Apr 11, 2024
Jun 12, 2024
Jun 12, 2024
Mar 27, 2023
Apr 18, 2024
Apr 18, 2024
Apr 18, 2024
Jan 30, 2023

Repository files navigation

About

Build Average time to resolve an issue Percentage of issues still open

resto is a metadata catalog and a search engine dedicated to geospatialized data. Originally, it’s main purpose it to handle Earth Observation satellite imagery but it can be used to store any kind of metadata localized in time and space.

resto search API conforms to the SpatioTemporal Asset Catalog (STAC) specification v1.0.0 and to the CEOS OpenSearch Best Practice Document.

It is mentioned in ESA's "Exploitation Platform Common Core Components" as the closest implementation of a catalogue component according to the requirements specified in ESA's "Exploitation Platform Open Architecture"

Demo

The [https://tamn.snapplanet.io] resto server provides up to date access to Landsat-8 and Sentinel-2 images.

You can browse it with the rocket web client

Or test the API :

Installation

TL;DR

The INSTALLATION.md file provides additional information on the installation process.

Deploy the service

To launch a default pre-configured resto instance, just type :

./deploy

This will build locally the jjrom/resto image and launch a resto container exposing the resto API service at http://localhost:5252

[IMPORTANT] Docker on Mac M1

If you're using docker on Mac with apple Silicon M1 chip, be sure to turn off "Use Rosetta for x86/amd64 emulation on Apple Silicon" in Docker Desktop > Settings > General.

When this option is turned on, every calls to PHP preg_match function (which is used by resto) leads to a segmentation fault within php fpm and an HTTP 502 Bad Gateway error in nginx. Why ? I just don't know !

Users, groups and rights

See ./USERS.md

Collection and catalogs

See .COLLECTIONS_AND_CATALOGS.md

References

Here are some projects that use resto.

If you plan to use resto and would like to have your project added to this list, feel free to contact support

Support

resto is developped and maintained by jeobrowser.

For questions, support or anything related to resto feel free to contact jerome[dot]gasperi[at]gmail[dot]com

About

A metadata catalog and search engine for geospatialized data

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • PHP 93.7%
  • PLpgSQL 4.2%
  • Shell 2.0%
  • Dockerfile 0.1%