write evs field
The write evs field module creates a file in one of several formats containing the mesh and nodal and/or cell data component information sent to the input port.
This module is useful for writing the output of modules which manipulate or interpolate data (3d estimation, 2d estimation, etc.) so that the data will not need to be processed in the future.
The saved and processed data can be read using read evs field, which is much faster than reprocessing the data.
Principal recommended format: EF2
The newest and strongly recommended format is EF2. This format is capable of containing additional field data and mesh types which are not supported in the legacy format. This is the only LOSSLESS format for current and future EVS fields. Although the files created in EF2 format are generally larger than EFBs, the further subsetting and/or processing of these updated fields can be dramatically more efficient.
- Uniform fields
- Geology (from gridding and horizons)
- Structured fields (such as irregular fields read in from read evs field)
- Unstructured Cell Data (UCD format) general grids with nodal and/or cell data
- Special fields containing spheres (which are points with radii)
- Special fields containing color data (such as LIDAR data)
Legacy formats:
- The legacy formats below were the recommended formats in software releases before 2024. With enhancements to EVS Fields, these formats must be considered LOSSY, meaning that some data and the (EF2) optimized grids will be compromised if these formats are used. We strongly recommend using the EF2 format.
- .eff ASCII format, best if you want to be able to open the file in an editor or print it. For a description of the EFF file formats click here.
- .efz GNU Zip compressed ASCII, same as .eff but in a zip archive
- .efb binary compressed format, the smallest and fastest format due to its binary form
Ports
| Direction | Name | Type | Description |
|---|---|---|---|
| Input | Input Field | Field | A field containing model to write to the EVS field file format. |
| Input | Geologic Legend Information | Geology Legend | Information required to properly label stratigraphic output or lithology within Legend. |
| Input | String 1 | String | A string to use as a variable. |
| Input | File Notes | String | Text containing the notes to be stored in the file. |
Properties
| Property | Type | Description |
|---|---|---|
| Filename | String | The output filename. Saves datasets in any of the EVS/MVS compatible file formats (EF2, EFB, EFF). |
| Check For Cell Set Data | Boolean | Causes any cell data that is constant throughout its cell set to be written as a cell set data component. |
| Translate By Origin | Boolean | Causes the output to be written in the user’s coordinate space. When turned off, the output will be written around the origin. |
Additional Information
| Property | Type | Description |
|---|---|---|
| Notes | String | The notes to include within the file. These are just comments and have no effect on the module. |
| Description | String | Sets the description stored in the output file. |
| Author | String | Sets the author name on the output file. |
| Organization | String | Sets the organization name on the output file. |
| Project | String | Sets the project displayed in the output file. |
| Status | String | Sets the status displayed in the output file. |
| Restrictions | String | Sets the restrictions displayed in the output file. |
Variables
| Property | Type | Description |
|---|---|---|
| S1 | String | A string value that can be used as the variable {S1} in the expression. |
Legacy File Options
| Property | Type | Description |
|---|---|---|
| Force Nodal Data In Output | Boolean | (Only applies to EFB/EFF) Causes the field definition to always contain Node_Data. If off and there are no node data components, a simpler Mesh-Only style field will be saved; however, when those fields are loaded into EVS or MVS, many modules will not work correctly with them. Enabling this saves the mesh as Mesh+Node_Data (with 0 data components) so that those modules will work. |
| Force Cell Data In Output | Boolean | (Only applies to EFB/EFF) Same as Force Nodal Data In Output, but for cell data. Very few modules require cell data, so this is off by default. |