OCLI documentation (9.3.0-132)

Intro document

Documentation is intended for a backend component of GolenRAM platform, internally referred to as OCLI, more specifically for the AIKP developers building, maintaining, or integrating with the platform.

Summary of the GoldenRAM Project

The GoldenRAM project is a significant, three-year initiative (2024-2026) funded by the European Commission’s Horizon Europe program. Its central objective is to develop and deploy a sophisticated Earth Observation (EO) platform to support the European Union’s critical raw materials (CRM) industry. The platform is designed to facilitate the secure and accurate exchange of information among mining companies, industry stakeholders, and the public by leveraging advanced technologies in cloud computing, artificial intelligence (AI), and data fusion.

OCLI is the platform’s core backend processing component responsible for orchestrating complex, automated workflows, including multi-source data ingestion, preprocessing, and the execution of advanced analytics through modular AI Knowledge Packs (AIKPs).

Platform roles

AIKPs can be executed by platform backend users via CLI commands one by one or via bash scripts, meaning operate interactively to receive instructions (triggered by CLI command or bash script), orchestrate complex data workflows, and return processed results for visualization. Currently there are more than 20 available AIKPs:

  • Unsupervised cluster mapping (ASTER, Landsat-8, Sentinel-2, Sentinel-1, TerraSAR-X)

  • Spectral indices calculations (ASTER, Sentinel-2, WorldView-3, Sentinel-1)

  • Generation of RGB composites (Sentinel-2, Landsat-8, Sentinel-1)

  • Radar Vegetation Index (oRVI) calculation and time series analysis (Sentinel-1)

  • Calculation of volume difference over time based on DEMs (e.g., for real-time accounting of waste materials in dumps or changes in open-pit mines)

  • Principal Component Analysis (PCA) (ASTER, Sentinel-2, WorldView-3)

  • Publishing of single band and multiband raster data, vector data, pointcloud data

A separate role is meant for AIKP developers who have access to the source code and design the workflows for backend users to use for each AIKP. Most of this web documentation is made for aIKP developers.

Frontend user interaction with the platform’s published datasets is facilitated by a separate Graphical User Interface (GUI): primary portal through which frontend users engage with the GoldenRAM platform. It is designed to be intuitive and user-friendly. A key innovation in the platform’s GUI is its NLP capability. This feature allows users to query the vast database using simple, human-like language. For example, a user could enter commands such as “show me all copper deposits near Roșia Poieni” or “show volume change in Valea Șesei tailings pond between January 2024 and June 2025”. The final outputs of the AIKPs are delivered to the user through the GUI in highly accessible, visualized formats. These include lightweight, web-friendly Cloud Optimized GeoTIFF (COG) files, which are ideal for displaying geospatial imagery. The retrieved data is organized logically, presented in formats such as a tree-like folder structure for easy navigation and a comprehensive table view for detailed examination.

Important information for AIKP developers

Development Environments

For comprehensive information about AIKP development environments, see AIKP Development Environments which covers:

  • Difference between AIKP development in DOCLI vs LOCLI

  • LOCLI: Local development environment setup and limitations

  • DOCLI: Dockerized development environment with SSH access and enhanced AIKP development options

  • Environment-specific configuration requirements

  • Development workflow recommendations

Quick Reference

  • Bash scripts

Usage: ocli-batch <path_to_file> file example test.sh

create -n bash_test -a
y
task list
roi list

Usage example: ocli-batch test.sh

  • All Python files should be encoded in UTF-8

Development

Explains step by step instructions for developing standard and custom AIKP with detailed descriptions of every file that should be present in the AIKP folder, as well as how to create local version of OCLI (LOCLI).

Contents

Explains general OCLI tooling used by multiple AIKPs that does not have to be re-made for every AIKP, but can simply be used as a tool.

AIKP

Step by step workflows for running open source AIKPs as a backend user.

UI Documents Type API

Documentation for each media type supported by ocli.