Data Management Glossary
OSDU (Open Subsurface Data Universe)
What Is OSDU (Open Subsurface Data Universe)?
OSDU stands for Open Subsurface Data Universe. It is an open-standard data platform framework developed by The Open Group that defines how subsurface data, including seismic surveys, well logs, drilling data, and reservoir models, should be stored, tagged, discovered, and shared across the oil and gas enterprise.
Before OSDU, subsurface data lived in siloed, vendor-specific platforms. A seismic dataset in one system could not be easily discovered or correlated with well log data in another. OSDU defines a common data schema, standardized metadata tags, and an API framework that makes subsurface data vendor-neutral and interoperable across hybrid cloud and on-premises storage environments.
OSDU is maintained by The Open Group and has been adopted by major energy operators and independent software vendors as the standard framework for subsurface data management.
What is a LAS File?
A LAS file (Log ASCII Standard) is a plain-text file format used in the oil and gas industry to store well log data. Originally developed by the Canadian Well Logging Society in 1989, LAS files record measurements taken at various depths along a wellbore, including gamma ray readings, resistivity, porosity, and acoustic velocity. The format has become the industry standard for exchanging well log data between interpretation software packages, operators, and service companies.
LAS files contain two main sections:
- The header section stores metadata: well name, location, operator, date logged, and the names and units of each data curve.
- The data section stores the actual depth-indexed measurement values. A single exploration program can generate thousands of LAS files, each representing a distinct log run or well interval.
Despite being a decades-old format, LAS files remain ubiquitous. Most interpretation software still requires LAS as an input format, and energy companies carry decades of accumulated well log archives in LAS, representing irreplaceable subsurface knowledge.
LAS Files are Unstructured Data
LAS files are unstructured data. The header metadata is human-readable but not natively indexable by standard file storage systems. A NAS environment storing thousands of LAS files sees only filenames and timestamps. The well name, operator, basin, formation, log type, and depth range embedded in each file header are invisible to the storage layer without targeted extraction.
This creates a significant operational problem. IT teams managing subsurface data archives cannot answer basic questions about which wells were logged in a given basin, which files belong to a completed project, or which logs meet the depth or quality criteria for a geoscience AI workflow, without opening individual files or relying on spreadsheets maintained outside the storage system.
As OSDU adoption grows across the industry, the gap between the metadata OSDU requires and the metadata actually embedded in legacy LAS archives has become a primary data readiness challenge for oil and gas IT.
Why OSDU Metadata Management Requires Unstructured Data Management
OSDU defines what metadata should be associated with every subsurface data asset. But OSDU does not automatically extract that metadata from legacy file formats. LAS files in existing archives predate OSDU by decades. The metadata they carry in their own header format must be read, mapped to OSDU-standard fields, and loaded into an OSDU-compatible catalog or the Komprise Global Metadatabase before those assets become discoverable within an OSDU framework.
This is an unstructured data management problem, not a database problem. The challenge is not storing the metadata once it is extracted. The challenge is extracting it at scale, across petabytes of archived well log data, without manual file inspection, without disrupting active workflows, and without requiring a full data migration to a new storage platform.
The scale of this challenge is substantial. A major operator may hold decades of well log data across multiple storage generations, spanning on-premises NAS, object storage, and cloud storage. OSDU readiness requires that all of it be enriched, tagged, and made searchable, not just net-new data going forward.
How Komprise Manages LAS File Metadata and Supports OSDU Readiness
Komprise addresses OSDU and LAS file metadata management through KAPPA data services (Komprise AI Preparation and Process Automation), a serverless metadata enrichment framework that extracts embedded header attributes from LAS files at scale and loads the results directly into the Komprise Global Metadatabase.
KAPPA data services for LAS files work as follows. A KAPPA function reads the header section of each LAS file, extracts standard fields including well name, operator, location, log type, depth range, and measurement curves, and maps those fields to OSDU-standard metadata tags. Komprise executes the function across the full data estate, including on-premises NAS, object storage, and cloud, without requiring files to be moved, reformatted, or migrated. The entire operation is serverless: no infrastructure to provision, no pipelines to maintain.
Once LAS file metadata is loaded into the Global Metadatabase, subsurface data becomes searchable by OSDU-compliant criteria using Komprise Deep Analytics. Geoscience teams can query well logs by basin, formation, operator, or log type across the entire data estate. IT teams can identify and retire interim files from completed drilling projects, apply tiering policies to inactive archives, and enforce data governance without manual inventory work.
The result is OSDU readiness without a platform migration. Existing well log archives, wherever they live, become discoverable, governable, and ready to feed geoscience AI workflows.
Visit the KAPPA Data Services Library
Frequently Asked Questions
What does OSDU stand for?
OSDU stands for Open Subsurface Data Universe. It is an open standard developed by The Open Group that defines how subsurface data in the oil and gas industry should be stored, tagged, and shared across vendor platforms.
What is a LAS file used for?
LAS files (Log ASCII Standard) store well log data recorded during drilling operations, including measurements of gamma ray, resistivity, porosity, and other formation properties at various depths along a wellbore. They are the standard format for exchanging well log data between interpretation software packages.
Why are LAS files hard to manage at scale?
LAS files are unstructured data. The metadata embedded in their headers, including well name, operator, log type, and depth range, is not indexed by standard storage systems. IT teams managing large LAS archives cannot search or classify files by subsurface criteria without targeted metadata extraction.
How does OSDU relate to LAS files?
OSDU defines the metadata schema for subsurface data discovery, but it does not automatically extract metadata from legacy LAS files. Organizations pursuing OSDU readiness must extract LAS header metadata, map it to OSDU standard fields, and load it into an OSDU-compatible catalog or metadatabase.
How does Komprise support OSDU readiness?
Komprise uses KAPPA data services to extract metadata from LAS file headers at scale across NAS, object storage, and cloud environments, without moving files. Extracted metadata is mapped to OSDU-standard tags and stored in the Komprise Global Metadatabase, making well log archives searchable and governable without a platform migration.
What is the Komprise Global Metadatabase?
The Komprise Global Metadatabase is a centralized metadata index that spans an organization’s entire unstructured data estate across storage vendors, tiers, and clouds. It enables search, classification, and policy enforcement against any data the organization holds, regardless of where it lives.