OSDU is an open subsurface data platform whose records are exchanged as JSON .json documents. g-Space reads OSDU records with a dedicated import dialog that classifies the content by record kind, lets you choose what to bring in, and maps the selected records into the project's wells.

Purpose

OSDU import is a one-way import. A single import can carry several kinds of objects at once: wells and wellbores, deviation (trajectory) data, well logs and their curves, markers and tops, and point sets. The importer groups records by kind so you can review and select exactly what to load, then a field mapper matches or creates the corresponding g-Space wells and attaches the related data.

Launching the import

Start the OSDU import and point it at the source. The reader accepts a single OSDU record file, a manifest file, or a whole folder of .json files. The Import OSDU data model dialog opens, showing the source path and the number of OSDU records detected.

[image: placeholder_The_Import_OSDU_data_model_dialog_header.png]

Step-by-step

1. Choose the source: a single OSDU JSON file, a manifest, or a folder of .json files. The dialog parses it and reports how many records were found.
2. Review the record groups. Records are laid out in collapsible groups by kind, such as Wells, Wellbores, Trajectories, Well logs, Markers and Spatial records. Each group lists its records with Name, Record id, Kind and Source file.
3. Select what to import. Use the per-record checkboxes, toggle a whole group with its header checkbox, or use Select all / Select none. The report area at the bottom summarises the detected records and any reader issues.
4. Press OK to run the import. The field mapper matches each selected record to an existing well by OSDU record id, by name, or by surface coordinates, and creates a new well when nothing matches.
5. Let the mapper attach the related data: wellbores are kept as metadata (extra wellbores under one well become sidetracks), trajectory stations populate the well path and inclinometry, well-log curves are added as a log file on the parent well, markers go to the marker set, and spatial records become point sets.

[image: placeholder_The_OSDU_import_dialog_with_per-family_r.png]

Notes

• Records whose kind is not recognised are grouped under Unsupported and are not mapped; nothing is dropped silently, so you can see them in the dialog and the report.
• Well logs that only reference an external LAS or DLIS file, and records without a resolvable parent well, are skipped and listed in the import report rather than mapped.
• Matching by surface coordinates uses a small tolerance, so a well already in the project may be reused instead of duplicated. The report lists how many wells were created, matched or added as sidetracks.
• OSDU import is read-only; there is no OSDU export from g-Space.

See Also

Import wells | Well Data Formats