OpenSpirit Table Data Model

This document summarizes the OpenSpirit Table Data Model. This is the common model exposed by the OpenSpirit attribute query service. This model presents a logical view of data as a set of related tables. A table is comprised of a set of rows and each row has a set of column values. In addition to the standard primitive column types such as String, float, and integer (and arrays of these types), OpenSpirit has provided some specialized column types designed to conveniently handle Geotechnical data. This includes types such as point (a point in 3d) and pointSeq (an array of points).

Using the attribute query service via the OpenSpirit library of of your choice (Java, C++. .NET, or COM) one may read, create, update, or delete data residing in any datastore for which an OpenSpirit dataserver has been developed. The attribute query service is the preferred technique for accessing data and should be used instead of the earlier fixed object Entity APIs. The only time the Entity objects need to be used are to exploit the specialized bulk data accessors required for 2d and 3d seismic trace data access and horizon grid access. Well path, well log, well velocity, and fault polyline array data may all be accessed via the attribute query service.

In addition to providing documentation for the full OpenSpirit Table model, the table below also provides links to documentation for each specific data server. Although OpenSpirit exposes a common data model, independent of any specific datastore, a specific dataserver may not support all data types or may have specific restrictions on allowable attribute values. For example, the OpenSpirit Finder data server only implements the well related OpenSpirit tables - one may not read or write horizons or faults to or from Finder. Applications that only read data will, in general, not need to worry about variations in capabilities amongst different data server implementations.