Explore projects

The Notification service allows interested consumers to subscribe to data and metadata changes using a publish/subscriber pattern.

Docs: https://osdu.pages.opengroup.org/platform/system/notification

The Schema Service enables schema management in the OSDU and offers an implementation of the schema standard.

Docs: https://osdu.pages.opengroup.org/platform/system/schema-service

The Unit Service provides dimension/measurement and unit definitions. Given two unit definitions, the service also offers conversion parameters in two different parameterizations.

The CRS Conversion Service provides spatial reference conversions for coordinates. Coordinates are represented by an array of 3D points.

The Storage Service handles metadata ingestion in OSDU.

Docs: https://osdu.pages.opengroup.org/platform/system/storage

The Dataset Service provides internal and external APIs to allow fetching storage/retrieval instructions for various types of datasets.

Docs: https://osdu.pages.opengroup.org/platform/system/dataset

The Indexer Service indexes the metadata store to support the Search Service.

Docs: https://osdu.pages.opengroup.org/platform/system/indexer-service

Airflow DAG for transformation from SEGY to MDIO

Typescript client for open-etp-server, including REST API

Core-owned CI for the Venus backing environment: create, refresh, status, and teardown of the cimpl stack on the persistent OpenShift cluster.

Source of truth for the Core Services wiki. Edited via merge request; CI publishes to the group wiki on merge to the default branch.

The Geospatial Consumption Zone (GCZ) is a project spawned by the OSDU Geomatics Workstream to streamline the management and consumption of geospatial data in OSDU by client applications.

The Time-series Management Service allows users to ingest time-series bulk data as a array of data points. The data can be written for set of entities, properties and source. User access is restricted through entitlements. The data ingested supports bi-temporality.

The Time-series Storage Core (or internal) Service is a final step in time-series ingestion pipeline. Processes published ingestion messages and stores data to the Time-series Storage.

Time-series Query Core (or internal) Service provides low level APIs for fetching data streams from Time-series Store.

The Time-series Publisher Core (or internal) Service is a part of time-series ingestion pipeline. Processes ingestion messaging queue and prepares data for Time-series Storage Core Service.

The Stream Storage Core (or internal) Service is a set of low level APIs for time-series data streams management.

The Time-series Service provides functionality for fetching stored time-series by entity, property, source and date-time span. The time-series are handled in a bi-temporal approach, where the version time is the time where the fact has been stored and the physical time where the transaction has happened.