IVAAP OSDU Data FAQ

IVAAP
OSDU Data FAQ

IVAAP 2025.1

Introduction

This document describes the OSDU data types supported by IVAAP and the required attributes for them to be visualized. OSDU requires that all records have valid legal and ACL tags. Some OSDU services enforce this requirement, while some do not. SLB recommends that vendors always add these fields. IVAAP supports the following OSDU data types:

• Well Data
• Wellbore Data
• Well Log
• Wellbore Trajectory
• Wellbore Marker Set
• Seismic Trace Data
• Seismic Acquisition Survey
• Seismic Horizon
• Fault System
• Perforation
• Tubing Set
• Wellbore Geometry
• Well Core Image

Well Data

In order to visualize well data in IVAAP, there needs to be a master-data–Well record with the following fields specified:

• data.FacilityName or data.FacilityID - used to determine the name of the well
• data.SpatialLocation.Wgs84Coordinates - used to determine the wgs84 location of the well and is used in IVAAP map search during data discovery

Listed below are optional fields in master-data–Well record that should be specified but don’t have to be:

• data.NameAliases - allows searches on UWI
• data.GeoContent - Can search on Country, BlockID, FieldID, and ProvinceID based on the ids specified
• data.FacilityOperators.FacilityOperatorOrganisationID - allows searches on organizations
• data.VerticalMeasurements - allows searches on vertical measurements
• data.FacilityStates.FacilityStateTypeID - allows searches on facility state type
• data.FacilityEvents - allows searches on spud date and drilling finish dates
• data.OperatingEvironmentID - allows searches on operating environments

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Wellbore Data

In order to visualize wellbore data in IVAAP, there needs to be a master-data–Wellbore record with the following fields specified:

• data.FacilityName or data.FacilityID - used to determine the name of the wellbore
• data.WellID - used to link a wellbore with its parent well, the data.WellID needs to match an existing well.
• data.SpatialLocation.Wgs84Coordinates - used to determine the wgs84 location of the wellbore and is used in IVAAP map search during data discovery

Listed below are optional fields in a master-data–Wellbore record that should be specified but don’t have to be:

• data.FacilityEvents - used to determine spud date and drilling finish dates of a wellbore
• data.VerticalMeasurements - used to determine tvd and elevation of a wellbore, this is needed to create a wellbore trajectory from a las file
• data.SpatialLocation.AsIngestedCoordinates - this is needed to create a wellbore trajectory from a las file

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Well Log

In order to visualize well log data in IVAAP, there needs to be a work-product-component--WellLog record with the following fields specified:

• data.Curves.Mnemonic - name of the curve
• data.Datasets - required for file-based data
• data.WellboreID - used to link a well log to its parent wellbore, the data.WellboreID needs to match an existing wellbore
• data.Curves.DepthUnit (or data.Curves.CurveUnit for the first curve) - this field is used to determine the unit of the index curve

For work-product-component--WellLog:1.0.0 the following fields need to be specified:

• data.Curves.BaseDepth
• data.Curves.TopDepth

For work-product-component--WellLog:1.1.0 and work-product-component--WellLog:1.2.0 record the following fields need to be specified:

• Either:
• data.Curves.BaseDepth
• data.Curves.TopDepth
• And/Or:
• data.SamplingStart
• data.SamplingStop
• And/Or:
• data.BottomMeasuredDepth
• data.TopMeasuredDepth

Listed below are optional fields in a work-product-component--WellLog record that should be specified but don’t have to be:

• data.Curves.CurveID - used for Wellbore DDMS to map search record to raw curve data
• data.Name - used to determine the name of the well log, if not specified, then a generic name will be used
• data.Curves.CurveUnit - used to determine the unit for each curve

IVAAP supports file-based and Wellbore DDMS curve data for well logs.
The following well log file formats are supported in IVAAP for OSDU:

• LAS
• DLIS

For DLIS files with multiple frames/logs, IVAAP will expect a work-product-component--WellLog record for each frame with a data.FrameIdentifier field identifying which frame is being referenced. IVAAP will treat the data.FrameIdentifier as a frame index that corresponds to a particular frame in the DLIS file. By default, IVAAP will assume this frame index is a 0-based index. IVAAP can be configured to support a frame index that does not start at 0. If the data.FrameIdentifier is not specified, then IVAAP will assume the work-product-component--WellLog record represents the first frame in a DLIS file.

IVAAP will attempt to match the curves specified in the work-product-component--WellLog record by name for DLIS files. If there is a discrepancy between the work-product-component--WellLog record and the DLIS file (such as curve name, units, index range, etc), IVAAP will use the information in the dlis file and log a data warning.

IVAAP will attempt to match the curves specified in the work-product-component--WellLog record by name for LAS files. IVAAP will return an error if a curve specified in work-product-component--WellLog record cannot be found in a LAS file.

For array curves, the data.Curves.NumberOfColumns field needs to be specified.

The 1.0.0, 1.1.0, and 1.2.0 schema versions have been tested and are supported by IVAAP.

For interval logs, the data.Curves.NumberOfColumns field will need to be changed to 2 for the first curve. IVAAP only supports interval logs for well logs in Wellbore DDMS.

For string curves, IVAAP requires the following field and value be specified: data.Curves.CurveSampleTypeID : "{{osdu-data-partition}}:reference-data--CurveSampleType:string:"

Wellbore Trajectory

In order to visualize wellbore trajectory data in IVAAP, there needs to be a work-product-component–WellboreTrajectory record with the following fields specified:

• data.WellboreID - used to link a wellbore trajectory to its parent wellbore, the data.WellboreID needs to match an existing wellbore
• data.Datasets - required for file-based data

For Wellbore Trajectories with Wellbore DDMS data, the following fields need to be specified in the work-product-component–WellboreTrajectory record:

• data.AvailableTrajectoryStationProperties.Name - used to determine the name of trajectory curve
• data.AvailableTrajectoryStationProperties.TrajectoryStationPropertyTypeID - used to help link trajectory stations to Wellbore DDMS curve data
• data.AvailableTrajectoryStationProperties.StationPropertyUnitID - used to determine unit of a wellbore trajectory curve. This is only required for the md curve but strongly recommended for all curves
• data.TopDepthMeasuredDepth - top depth of the wellbore trajectory
• data.BaseDepthMeasuredDepth - base depth of the wellbore trajectory

A wellbore trajectory needs to have an MD curve in order to be used in IVAAP:

• MD - the unit symbol for the md curve needs to be specified

In order to display a trajectory in the IVAAP 3D widget, one of the following sets of curves and information needs to be specified (in addition to MD):

• Either
• TVD, X, and Y curves
• Or
• TVD, Surface X, Surface Y, Inclination, and Azimuth curves in file-based data
• Or
• TVD, Inclination, and Azimuth curves and data.SpatialPoint.AsIngestedCoordinates field for Wellbore DDMS data
• Or
• TVD, dispEw, and dispNs curves and data.SpatialPoint.AsIngestedCoordinates field for Wellbore DDMS data

Ideally, the associated with the original x,y values of the Wellbore Trajectory should be specified. If the EPSG code of a trajectory cannot be found, then IVAAP will not be able to display the trajectory or its parent well in the base map widget. For file-based data the crs will be specified in the epsg_code, horizontalcrs, crs, or coord_system_cd column.

For Wellbore DDMS data, this information will be specified in the reference-data--CoordinateReferenceSystem record referenced in the data.SpatialPoint.AsIngestedCoordinates.CoordinateReferenceSystemID or the data.ProjectedCRSID field.

To determine the EPSG code quickly it is advisable that the id of the reference-data--CoordinateReferenceSystem should specify the EPSG code in the id after the string :EPSG::. An example of this is shown below:

• osdu:reference-data--CoordinateReferenceSystem:GeodeticCRS::EPSG::23031:

If the id of the reference-data--CoordinateReferenceSystem record is not specified in this way, IVAAP will try to determine the EPSG code by requesting the reference-data--CoordinateReferenceSystem record.

The following fields are used to determine the vertical shift of a trajectory:

• data.VerticalMeasurement.VerticalMeasurement - primary field used to determine the vertical shift
• data.VerticalMeasurement.VerticalMeasurementUnitOfMeasureID - primary field used to determine the vertical shift unit
• data.VerticalMeasurement.VerticalReferenceID - secondary field used to determine the vertical shift. If the data.VerticalMeasurement.VerticalMeasurement field is not specified, then the data.VerticalMeasurement.VerticalReferenceID will be used in conjunction with the data.VerticalMeasurement.VerticalReferenceEntityID field to find the vertical shift. The data.VerticalMeasurement.VerticalReferenceID field will point to a reference record (typically a well or wellbore) with a data.VerticalMeasurements section and the data.VerticalMeasurement.VerticalReferenceEntityID field will reference the data.VerticalMeasurements.VerticalMeasurementID field of the reference record.
• data.VerticalMeasurement.VerticalReferenceEntityID - see description of data.VerticalMeasurement.VerticalReferenceID

The 1.0.0 and 1.1.0 schema versions have been tested and are supported by IVAAP.

Wellbore Marker Set

In order to visualize wellbore marker set data (also referred to as top data) in IVAAP, there needs to be a work-product-component–WellboreMarkerSet record with the following fields specified:

• data.WellboreID - used to link a wellbore marker set to its parent wellbore, the data.WellboreID needs to match an existing wellbore
• data.Markers.MarkerMeasuredDepth - used to determine the depth of each marker
• data.Markers.MarkerName - used to determine the name of each marker

The unit for all markers is determined by the data.VerticalMeasurement.VerticalMeasurementUnitOfMeasureID field. If this field is not specified, then IVAAP will assume the marker units are meters.

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Seismic Trace Data

In order to visualize seismic trace data in IVAAP, there needs to be a work-product-component–SeismicTraceData record with the following fields specified:

• data.Name - used to determine the name of the seismic data
• data.Datasets - used to get data access credentials for seismic data
• data.SpatialArea.Wgs84Coordinates - used to determine the wgs84 location of the seismic data and is used in IVAAP map search during data discovery. IVAAP supports coordinates specified as a feature geometry polygon or a series of feature geometry points
• data.SpatialArea.AsIngestedCoordinates - used to determine CRS of the seismic data and help determine xy to ij transformation. These coordinates are used to display the seismic data in 3D using xy coordinates

SEG-Y data can be viewed in 3D if it is a regular volume (the number of inline traces multiplied by the number of xline traces matches the total number of traces). Timeslices cannot be viewed for SEG-Y data.

Listed below are the fields in a work-product-component–SeismicTraceData record that are required to display SEG-Y data in 3D:

• data.TraceCount - used to determine the number of traces.
• data.InlineMin - used to determine the min value of the inline range.
• data.InlineMax - used to determine the max value of the inline range
• data.InlineIncrement - needed if inline increment is not 1. IVAAP will assume inline increment is 1 if this field is not specified.
• data.CrosslineMin - used to determine the min value of the crossline (or xline) range
• data.CrosslineMax - used to determine the max value of the crossline (or xline) range
• data.CrosslineIncrement - needed if crossline (or xline) increment is not 1. IVAAP will assume crossline increment is 1 if this field is not specified

Listed below are optional fields in a work-product-component–SeismicTraceData record that should be specified but don’t have to be:

• data.SampleCount - used to determine the number of samples per trace
• data.SeismicDomainTypeID - used to determine if the seismic data is time-based or depth-based. If this field is not specified IVAAP will determine the domain type based on the data.TraceDomainUOM field.
• data.StartTime - start time for time-based seismic data
• data.EndTime - end time for time-based seismic data
• data.StartDepth - start depth for depth-based seismic data
• data.EndDepth - end depth for depth-based seismic data
• data.TraceDomainUOM - unit symbol for time-based or depth-based data. If this field is not specified then IVAAP will try to determine the z unit based on the seismic file. In the case of SEG-Y IVAAP will assume the units are in milliseconds.
• data.BinGridID - refers to a work-product-component--SeismicBinGrid that can be used to accurately create an xy to ij transformation. This helps in accurately displaying seismic data in 3D and alongside other data. IVAAP does not use bin grid in location searches at this time.
• data.GeoContent - Can search on Country, BlockID, FieldID, and ProvinceID based on the ids specified

IVAAP supports the following seismic data formats for OSDU:

• SEG-Y files stored in cloud storage
• OpenVDS data is stored in cloud storage (AWS only)
• OpenVDS data stored in Seismic DDMS
• OpenZGY data stored in Seismic DDMS

Both OpenVDS and OpenZGY data can be viewed in 3D and support displaying a timeslice section.

If a SeismicTraceData record references multiple seismic files, IVAAP displays the indexed seismic files (OpenVDS, OpenZGY) over the non-indexed seismic file (SEGY-Y).

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Seismic Acquisition Survey

The Seismic Acquisition Survey can be used as an optional parent for Seismic Trace Data in IVAAP. In order to visualize seismic trace data in IVAAP, there needs to be a work-product-component–SeismicTraceData record with the following fields specified:

• data.Name - used to determine the name of the seismic survey
• data.SpatialArea.Wgs84Coordinates - used to determine the wgs84 location of the seismic data and is used in IVAAP map search during data discovery. IVAAP supports coordinates specified as a feature geometry polygon or a series of feature geometry points

Seismic Horizon

In order to visualize horizon data in IVAAP, there needs to be a work-product-component–SeismicHorizon record with the following fields specified:

• data.Name - used to determine the name of the seismic horizon data
• data.Datasets - used to get data access credentials for seismic horizon data
• data.SpatialArea.Wgs84Coordinates - used to determine the wgs84 location of the seismic horizon data and is used in IVAAP map search during data discovery. IVAAP supports coordinates specified as a feature geometry polygon or a series of feature geometry points
• data.SpatialArea.AsIngestedCoordinates - used to determine CRS of the seismic horizon data.

Listed below are optional fields in a work-product-component–SeismicHorizon record that should be specified but don’t have to be:

• data.SeismicDomainUOM - unit symbol for seismic horizon data
• data.GeoContent - Can search on Country, BlockID, FieldID, and ProvinceID based on the ids specified
• data.SeismicDomainTypeID - used to determine if the seismic horizon is time or depth-based. This field can be searched on in the map search dialog

The following horizon file formats are supported by IVAAP:

• Volve Horizon Dat format

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Fault System

In order to visualize fault data in IVAAP, there needs to be a work-product-component–FaultSystem record with the following fields specified:

• data.Name - used to determine the name of the fault data
• data.Datasets - used to get data access credentials for fault data
• data.SpatialArea.Wgs84Coordinates - used to determine the wgs84 location of the fault data and is used in IVAAP map search during data discovery. IVAAP supports coordinates specified as a feature geometry polygon or a series of feature geometry points
• data.SpatialArea.AsIngestedCoordinates - used to determine CRS of the fault data. These coordinates are used to display the fault data in 3d using xy coordinates

Listed below are optional fields in a work-product-component–FaultSystem record that should be specified but don’t have to be:

• data.GeoContent - can search on Country, BlockID, FieldID, and ProvinceID based on the ids specified
• data.SeismicDomainUOM - unit symbol for fault data
• data.SeismicDomainTypeID - used to determine if the seismic horizon is time-based or depth-based. This field can be searched on in the map search dialog

The following horizon file formats are supported by IVAAP:

• Volve Fault Dat format

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Perforation

In order to visualize perforation data in IVAAP, a master-data--PerforationJob record and at least one master-data--PerforationInterval records are needed. The master-data--PerforationInterval records represent each perforation and the master-data--PerforationJob record will represent a collection of perforations.

The master-data--PerforationJob record needs to have the following fields specified:

• data.WellboreID - used to link a perforation job to its parent wellbore, the data.WellboreID needs to match an existing wellbore

Listed below are optional fields in a master-data--PerforationJob record that should be specified but don’t have to be:

• data.ConveyedMethodID - used to determine method for all perforations that are associated with this master-data--PerforationJob. The method identifies the type of opening the fluid entered through into the tubing.

The master-data--PerforationInterval record needs to have the following fields specified:

• data.IntervalTopMD - top depth of this perforation interval
• data.IntervalBaseMD - bottom depth of this perforation interval
• data.PerforationJobID - used to link a perforation to its perforation job, the data.PerforationJobID needs to match an existing perforation job

Listed below are optional fields in a master-data--PerforationInterval record that should be specified but don’t have to be:

• data.Name - used to determine the name of the perforation data, if not specified then a generic name will be used
• data.SequenceNumber - sequence number for perforation data
• data.IntervalTypeID - perforated interval type
• data.ShotDensity - the density of this perforation. This is the number of perforations used in combination with the perorations per unit. For example 8.5 shots per meter with 17 shots every 2 meters.
• data.EntranceHoleDiameter - the size of the diameter of the perforation
• data.Source - source for perforation data
• data.GunCarrierPhasing - the phase of the perforation. The phase is the angle separating perforations

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Tubing Set

In order to visualize tubing set data in IVAAP, a work-product-component--TubularAssembly record and at least one work-product-component--TubularComponent records are needed. The work-product-component--TubularComponent records represent each tubular component and the work-product-component--TubularAssembly record will represent a collection of tubular components.

The work-product-component--TubularAssembly record needs to have the following fields specified:

• data.WellboreID - used to link a tubular assembly to its parent wellbore, the data.WellboreID needs to match an existing wellbore

Listed below are optional fields in a work-product-component--TubularAssembly record that should be specified but don’t have to be:

• data.Name - used to determine the name of the tubular assembly, if not specified then a generic name will be used
• data.AssemblyBaseMD - depth of this tubular assembly

The work-product-component--TubularComponent needs to have the following fields specified:

• data.DriftDiameter - outer diameter of this tubular component
• data.TubularComponentTopMD - top depth of this tubular component
• data.TubularComponentBaseMD - base depth of this tubular component
• data.TubularComponentTypeID - use to determine what symbol to use when visualizing this tubular component
• data.ParentAssemblyID - used to link a tubular component to a parent tubular assembly

Listed below are optional fields in a work-product-component--TubularAssembly record that should be specified but don’t have to be:

• data.TubularComponentLength - total length of this tubular component
• data.Description - description of this tubular component
• data.MaximumOuterDiameter - max outer diameter of this tubular component
• data.InnerDiameter - inner diameter of this tubular component
• data.TubularComponentSequence - sequence number assigned to the wellbore that this tubular component is used for

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Wellbore Geometry

In order to visualize wellbore geometry data in IVAAP, at least one master-data–HoleSection record is needed. The master-data–HoleSection records represent each section of a wellbore geometry data. There can be only one wellbore geometry data per wellbore.

The master-data–HoleSection record needs to have the following fields specified:

• data.WellboreID - used to link a hole section to its parent wellbore, the data.WellboreID needs to match an existing wellbore
• data.Size - diameter of a hole section

Listed below are optional fields in a master-data--HoleSection record that should be specified but don’t have to be:

• data.Name - used to determine the name of the hole section, if not specified then a generic name will be used
• data.MeasuredDepthTop - top measured depth of this hole section
• data.MeasuredDepthBase - bottom measured depth this hole section

The 1.0.0 schema version has been tested and is supported by IVAAP. Newer schema versions have not been tested but may be supported by IVAAP.

Well Core Image

In order to visualize rubbing set data in IVAAP, at least one work-product-component--RockImage record is needed. A work-product-component--RockImage record will represent one well core image. Well core images can be grouped by a master-data--RockSamle record, a master-data--Coring record, or a master-data--Wellbore record. Well core images will only be grouped by a master-data--Wellbore record if they can’t be grouped by a master-data--RockSample record or master-data--Coring record.

The work-product-component--RockImage record needs to have the following fields specified:

• data.WellboreID - used to link a well core image to its parent wellbore, the data.WellboreID needs to match an existing wellbore
• data.Datasets - used to get data access credentials for well core image data

Listed below are optional fields in a work-product-component--RockImage record that should be specified but don’t have to be:

• data.Name - used to determine the name of the hole section, if not specified then a generic name will be used.
• data.RockSampleIDs - used to link a well core image to a set of parent master-data--RockSample records.
• data.CoringID - use to link a well core image to a parent master-data--Coring record.
• data.TopDepthMeasuredDepth - depth corresponding to the top of this well core image.
• data.BaseDepthMeasuredDepth - depth corresponding to the bottom of this well core image.

Reference Data and Miscellaneous Master Data

It is strongly recommended to populate any reference-data or master-data that is referenced in the above-mentioned data type that IVAAP supports. The reference data allows for searches by reference names and will allow for more information to be available for each data type.

OSDU Seismic Support by IVAAP

In OSDU, you can ingest the data as cloud storage (blob storage, AWS S3, etc.) or through Seismic DDMS. Seismic DDMS is a cloud agnostic storage mechanism that overcomes the object size limitations imposed by a cloud provider, by managing generic datasets as multi independent objects and, therefore, provides a generic, reliable and a better performed solution to handle data on a cloud storage.

Seismic formats supported by OSDU are SEG-Y, OpenVDS and OpenZGY. All of them are also supported through the Seismic DDMS. For OpenVDS, OpenZGY, and SEG-Y there is a fully supported client API for the Seismic DDMS storage.

IVAAP has full support for OpenVDS and OpenZGY (cloud storage and Seismic DDMS) for 3D regular and irregular volumes including access for Inlines, cross-lines, time slices and arbitrary lines.

For SEG-Y, there is no indexing mechanism supported by OSDU and no support for displaying time slices due to the limitations of the format. If the SEG-Y volume is regular then IVAAP can display it in a 2D or 3D viewer. If the volume is irregular, it can only be displayed in 2D with no sorting on Inline or Xlines. Irregular SEG-Y files can be indexed with the INT Indexer to produce xgy and igx files that can be ingested into OSDU. These indexed files can be used to visualize the SEG-Y seismic data in a 3D view.

For SEG-Y files specified in a SEG-Y File Collection Dataset Record, IVAAP will try to match the SEG-Y file based on the following criteria:

• data.Name
• data.DatasetProperties.FileSourceInfos.Name
• data.DatasetProperties.FileSourceInfos.FileSource
• data.DatasetProperties.FileSourceInfos.PreloadFilePath
• If the folder only contains 1 SEG-Y file, then IVAAP will use that file
• If the folder only contains 1 file, then IVAAP will assume it is a SEG-Y file and use it

If multiple data.DatasetProperties.FileSourceInfos entries are specified, IVAAP will use the first one to try to find the SEG-Y file.

OpenVDS and OpenZGY also support 2D seismic lines with some limitations. IVAAP will support the 2D seismic lines display, including 2D and 3D views and full cursor tracking.

IVAAP also supports displaying 2D SEG-Y seismic lines in the 2D viewer. However because there is no indexing, 2D SEG-Y lines cannot be displayed in 3D nor will it support cursor tracking between a map and the 2D seismic viewer.

We don’t recommend using the Seismic DDMS for versions less than M13. M15 should support all supported formats on AWS and Azure. At this time, we have not done full testing of the Seismic DDMS on GCP.

For AWS, when Seismic DDMS data or OpenVDS data in S3 is referenced, the AWS_REGION environment variable must be set. This variable must be set in the docker container that is running the IVAAP OSDU Node.

Example Map Search Queries

Below are some example map search queries that are used by IVAAP for data discovery.

Well Map Search Query

{  
    "kind": "osdu:wks:master-data--Well:*",  
    "spatialFilter": {  
        "field": "data.SpatialLocation.Wgs84Coordinates",  
        "byGeoPolygon": {  
            "points": [  
                {"longitude": -180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": -90.0}  
            ]  
        }  
    },  
    "returnedFields": [ "id","kind","data.FacilityID","data.FacilityName","data.SpatialLocation.Wgs84Coordinates"],  
    "sort": { "field": ["id"],"order": ["ASC"]},  
    "limit": 1000,  
    "offset": 0  
}

Seismic Trace Data Map Search Query

{  
    "kind": "osdu:wks:work-product-component--SeismicTraceData:*",  
    "spatialFilter": {  
        "field": "data.SpatialArea.Wgs84Coordinates",  
        "byGeoPolygon": {  
            "points": [  
                {"longitude": -180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": -90.0}  
            ]  
        }  
    },  
    "returnedFields": [ "id","kind","data.Name","data.SpatialArea.Wgs84Coordinates" ],  
    "sort": { "field": ["id"], "order": ["ASC"] },  
    "limit": 1000,  
    "offset": 0  
}

Seismic Horizon Map Search Query

{  
    "kind": "osdu:wks:work-product-component--SeismicHorizon:*",  
    "spatialFilter": {  
        "field": "data.SpatialArea.Wgs84Coordinates",  
        "byGeoPolygon": {  
            "points": [  
                {"longitude": -180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": -90.0}  
            ]  
        }  
    },  
    "returnedFields": ["id","kind","data.Name","data.SpatialArea.Wgs84Coordinates"],  
    "sort": {"field": ["id"],"order": ["ASC"]},  
    "limit": 1000,  
    "offset": 0  
}

Fault System Map Search Query

{  
    "kind": "osdu:wks:work-product-component--FaultSystem:*",  
    "spatialFilter": {  
        "field": "data.SpatialArea.Wgs84Coordinates",  
        "byGeoPolygon": {  
            "points": [  
                {"longitude": -180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": -90.0},  
                {"longitude": 180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": 90.0},  
                {"longitude": -180.0,"latitude": -90.0}  
            ]  
        }  
    },  
    "returnedFields": ["id","kind","data.Name","data.SpatialArea.Wgs84Coordinates"],  
    "sort": {"field": ["id"],"order": ["ASC"]},  
    "limit": 1000,  
    "offset": 0  
}

@2026 SLB Inc. Last Updated February 13, 2026