Import PRODML
PRODML is an Energistics data-exchange standard for production and well data. g-Space reads PRODML records from JSON .json files through a dedicated import wizard that previews the content and reports the outcome before anything is written to the project.
Purpose
PRODML import is a one-way import. It brings two kinds of data into the current project: well comments, which are attached to existing wells matched from the PRODML records, and point sets, which are built from records that carry coordinates but do not match any well. Wells are never created by this import.
Launching the import
Start the Import PRODML files wizard. On the first page, use Add to choose one or more .json files and Remove to drop a selected file. Each added file is parsed immediately and listed with its per-file counts: Records, Matched wells, Comments planned, Points planned, Skipped and Errors.
[image: placeholder_The_Import_PRODML_files_wizard_first_pag.png]
Step-by-step
- Press Add and select the PRODML .json files to import. Repeat to build the list; each file is parsed as it is added.
- Review the per-file counts in the table to confirm how many records were read, how many wells were matched, and whether any files reported errors.
- Continue to open the preview. The preview lists every record with its source object type and id, the matched well (or a "no match" note), the record Kind, and the reason describing how it will be handled. A summary line totals files, records, matched wells, points and skipped records.
- Confirm the preview to apply the import. Records that match an existing well become well comments (depth-bearing when a depth is present); records with coordinates but no matching well are routed to a PRODML import point set; the rest are skipped.
- Read the import report. It groups the outcome into counters (parsed records, matched to wells, well comments created, depth-bearing well comments, point sets created, points created), issue buckets and records by kind. Use Export to text to save the report to a .txt file if needed.
[image: placeholder_The_PRODML_import_preview_dialog_showing.png]
Notes
- Wells are matched case-insensitively against existing wells using the PRODML name, UWI, API, reporting-entity name and any aliases. If no existing well matches, no well is created.
- A record that has no matching well but does carry coordinates is imported as a point instead of a comment. Point sets are created only when at least one such orphan point lands.
- A record with neither a matching well nor coordinates is skipped and listed in the report, together with any unsupported object types and parse errors.
- PRODML import is read-only; there is no PRODML export. Multiple files can be added at once and are aggregated into a single preview and report.
See Also