Abstract: Implementations described and claimed herein provide a system and methods for managing a flow of and access to proprietary data in a cloud storage array. In one implementation, a plurality of uploads of the proprietary data is received. An association of the proprietary data is maintained across the plurality of uploads. A role is assigned to a party with an interest in the proprietary data. The role is defined by a set of access permissions. The access of the party to the proprietary data is controlled based on the assigned role. The proprietary data may be multi-dimensional data sets, such as raw, processed, and/or interpreted seismic data sets.

Abstract: A transaction service whereby a first party, such as the owner of a data set, may make data sets available for some form of transaction, such as to transform the data for the owner, a license to a second party for the data, or an acquisition of the data by a second party. The service may be deployed in conjunction with a system that provides efficient mechanism to partition the data set and store it into nodes, as well as to retrieve portions of the data set. As part of the service, the owner can register the data set for a transaction and second parties, such as contractors or partners, can be notified of such registrations such as through some form of electronic notification or through having the data set listed or otherwise provided on a viewable page or pages provided by the service.

Abstract: A cloud based storage system and methods for uploading and accessing 3-D data partitioned across distributed storage nodes of the system. The data cube is processed to identify discrete partitions thereof, which partitions may be organized according to the x (e.g., inline), y (e.g., crossline) and/ or z (e.g., time) aspects of the cube. The partitions are stored in unique storage nodes associated with unique keys. Sub-keys may also be used as indexes to specific data values or collections of values (e.g., traces) within a partition. Upon receiving a request, the proper partitions and values within the partitions are accessed, and the response may be passed to a renderer that converts the values into an image displayable at a client device. The request may also facilitate data or image access at a local cache, a remote cache, or the storage partitions using location, data, retrieval, and/or rendering parameters.