h5geo 0.4.0
C++17 and python API to work with geo-data (seismic, wells, maps, other in process) based on HDF5. Aimed at geoscientists and developers.
|
Class for creating H5Map. More...
#include <h5base.h>
Public Attributes | |
double | X0 |
X-coordinate of origin (upper-left corner of column-major Eigen matrix) | |
double | Y0 |
Y-coordinate of origin (upper-left corner of column-major Eigen matrix) | |
double | X1 |
X-coordinate of first point (upper-right corner of column-major Eigen matrix) | |
double | Y1 |
Y-coordinate of first point (upper-right corner of column-major Eigen matrix) | |
double | X2 |
X-coordinate of second point (lower-left corner of column-major Eigen matrix) | |
double | Y2 |
Y-coordinate of second point (lower-left corner of column-major Eigen matrix) | |
size_t | nX |
number of columns in column-major Eigen matrix | |
size_t | nY |
number of rows in column-major Eigen matrix | |
h5geo::Domain | domain |
time or depth (TWT, TVD etc) | |
hsize_t | xChunkSize = 10 |
see HDF5 chunking | |
hsize_t | yChunkSize = 10 |
see HDF5 chunking | |
Public Attributes inherited from H5BaseObjectParam | |
std::string | spatialReference |
usually in the form authName:code given by 'proj.db' (probably using name will also work) | |
std::string | lengthUnits |
all geo-object's lengthUnits data must follow it (if any) | |
std::string | temporalUnits |
all geo-object's temporalUnits data must follow it (if any) | |
std::string | angularUnits |
all geo-object's angularUnits data must follow it (if any) | |
std::string | dataUnits |
all geo-object's dataUnits data must follow it (if any) | |
double | nullValue = std::nan("nan") |
usually used for missed values | |
Class for creating H5Map.
Map parameters are needed when creating any Map geo-object.