All projects

Project inventory · November 2026

Bulk Petrel Projects Data Extraction

A read-only Petrel portfolio audit turns scattered project metadata into a coverage report, showing available metadata, stored coordinate-system declarations and missing information.

Case study · project metadata inventory

Understanding a project portfolio

Before reusing a collection of Petrel projects, a reviewer needs to know what each project contains and which information is accessible. This workflow brings project and companion metadata into one inventory without launching Petrel.

The report combines registry and Model metadata, identifies stored CRS declarations, and distinguishes readable information from missing, unsupported or unprobed items.

Metadata coverage for 98 selected project entries: 81 Registry plus Model, 4 Registry only and 13 unavailable
Aggregate metadata coverage from the recorded November 2026 inventory. Counts refer to selected project entries, not unique fields or recovered datasets. Open full-size image.
Recorded metadata availability
CoverageProject entriesMeaning
Registry + Model81Registry and Model metadata available
Registry only4Registry metadata available; Model metadata unavailable
Unavailable13Registry and Model metadata unavailable

Results and interpretation

Of 98 selected project entries, 81 provided both Registry and Model metadata, four provided Registry metadata only, and 13 had neither available for the inventory.

These counts describe metadata coverage. Dataset extraction and coordinate validation are separate tasks: a stored CRS declaration or seismic reference alone does not confirm usable coordinates or a readable seismic volume.