|
OpenZGY/C++ Public API (ALPHA)
Access seismic data stored in ZGY format.
|
Concrete implementation of IZgyUtils. More...
Public Member Functions | |
| ZgyUtils (const std::string &prefix, const IOContext *iocontext) | |
| Create a new concrete instance of IZgyUtils. More... | |
| void | deletefile (const std::string &filename, bool missing_ok) |
| Delete a file. Works both for local and cloud files. More... | |
Additional Inherited Members | |
Static Public Member Functions inherited from OpenZGY::IZgyUtils | |
| static std::shared_ptr< IZgyUtils > | utils (const std::string &prefix, const IOContext *iocontext) |
| Create a new concrete instance of IZgyUtils. More... | |
Concrete implementation of IZgyUtils.
| OpenZGY::Impl::ZgyUtils::ZgyUtils | ( | const std::string & | prefix, |
| const IOContext * | iocontext | ||
| ) |
Create a new concrete instance of IZgyUtils.
| prefix | File name or file name prefix. |
| iocontext | Credentials and other configuration. |
The reason you need to supply a file name or a file name prefix is that you need to provide enough information to identify the back-end that this instance will be bound to. So both "sd://some/bogus/file.zgy" and just "sd://" will produce an instance that works for the seismic store.
For performance reasons you should consider caching one IZgyUtils instance for each back end you will be using. Instead of just creating a new one each time you want to invoke a method. Just remember that most operations need an instance created with the same prefix.
|
virtual |
Delete a file. Works both for local and cloud files.
Note that the instance must be of the correct (local or cloud) type.
Implements OpenZGY::IZgyUtils.
1.8.17