Open VDS issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues2022-08-25T13:23:13Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/48Implement resumable uploads2022-08-25T13:23:13ZMorten OfstadImplement resumable uploadsWe can check if the chunk-metadata on the metadata-page is in sync with the chunk-metadata header of the objects (with HEAD requests) to quickly find where to resume an upload that was stopped part-way through. This feature will be impor...We can check if the chunk-metadata on the metadata-page is in sync with the chunk-metadata header of the objects (with HEAD requests) to quickly find where to resume an upload that was stopped part-way through. This feature will be important as we move to larger datasets that are more likely to have a problem and are more costly to retry from the beginning.Version 2.1Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/7SEG-Y importer LOD generation2022-07-21T13:15:19ZMorten OfstadSEG-Y importer LOD generationThe SEG-Y importer needs to be augmented with functionality to create LODs. Since we're writing to an object store we don't want to base the LOD generation on re-downloading all objects in order to generate LODs, so we need to implement ...The SEG-Y importer needs to be augmented with functionality to create LODs. Since we're writing to an object store we don't want to base the LOD generation on re-downloading all objects in order to generate LODs, so we need to implement an in-memory cache of partially written LOD tiles. If possible this should be implemented as a re-usable utility class that can be used by other importers with similar needs.Version 2.1https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/4Support for 2D seismic2022-01-12T13:29:20ZMorten OfstadSupport for 2D seismicThe SEG-Y import needs to be augmented with code to create the required metadata for 2D seismic (In the TraceCoordinates category, see KnownMetadata.h) and the SEG-Y export needs to be validated (it should work as-is). An additional help...The SEG-Y import needs to be augmented with code to create the required metadata for 2D seismic (In the TraceCoordinates category, see KnownMetadata.h) and the SEG-Y export needs to be validated (it should work as-is). An additional helper class is needed to do correct lookups in the metadata (similar to the IJKGridDefinition/VDSCoordinateTransformer classes).Version 2.1https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/5Support for prestack-migrated seismic2021-02-04T09:20:14ZMorten OfstadSupport for prestack-migrated seismicThe SEG-Y importer should create 4D volumes with a bin-grid for these data types.The SEG-Y importer should create 4D volumes with a bin-grid for these data types.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/6Support for unbinned prestack seismic2021-02-04T09:19:15ZMorten OfstadSupport for unbinned prestack seismicThis includes shot, receiver and CMP/CDP/CRP gathers. The axis information needs to be correct according to the KnownMetadata.h, no bingrid metadata should be added.This includes shot, receiver and CMP/CDP/CRP gathers. The axis information needs to be correct according to the KnownMetadata.h, no bingrid metadata should be added.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/58Refactor SEGY importer read strategy2020-09-01T09:10:43ZMorten OfstadRefactor SEGY importer read strategyThe SEGY importer currently reads entire inline-groups, split into multiple requests if they come from blob store. It is more efficient if we can start the import process before the entire inline-group is populated and instead read from ...The SEGY importer currently reads entire inline-groups, split into multiple requests if they come from blob store. It is more efficient if we can start the import process before the entire inline-group is populated and instead read from the input SEGY in "pages" of a fixed number of traces that are needed to make the next column of cubes.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/8File backend2020-08-07T12:37:29ZMorten OfstadFile backendA file backend based on the huebds library for manipulating data-store files should be added. This needs to have a compatibility layer so it can read files written with the commercial library (translating the serialized objects into JSON...A file backend based on the huebds library for manipulating data-store files should be added. This needs to have a compatibility layer so it can read files written with the commercial library (translating the serialized objects into JSON that is similar to the objects found in an object store version of VDS). The handling of chunk-metadata and metadata-pages is done quite differently for the file format, so there is some refactoring work to be done to make this backend possible.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/9SEGYScan and SEGYUpload tools should be merged2020-01-27T14:06:35ZMorten OfstadSEGYScan and SEGYUpload tools should be mergedThere is no need to have two separate tools for scanning and uploading SEG-Y files, the command line options of both should be available and an additional --scan-only parameter can be added to tell it to only scan the file and write the ...There is no need to have two separate tools for scanning and uploading SEG-Y files, the command line options of both should be available and an additional --scan-only parameter can be added to tell it to only scan the file and write the results of the scanning to a JSON file. The merged command-line tool should be named SEGYImport to be consistent with the naming of the SEGYExport tool.Version 1.0