EVS Data Input & Output Formats
EVS Data Input & Output Formats Input EVS conducts most of its analysis using input data contained in a number of ASCII files. These files can generally be created using the Data Transformation Tools, which are on the Tools tab of EVS. These tools will create C Tech’s formats from from Microsoft Excel files.
Handling Non-Detects It is important to understand how to properly handle samples that are classified as non-detects. A non-detect is an analytical sample where the concentration is deemed to be lower than could be detected using the method employed by the laboratory. Non-detects are accommodated in EVS for analysis and visualization using a few very important parameters that should be well understood and carefully considered. These parameters control the clipping non-detect handling in all of the EVS modules that read chemistry (.apdv, or .aidv) files. The affected modules are 3d estimation, krig_2d, post_samples, and file_statistics.
Consistent Coordinate Systems C Tech’s software is designed to work with many types of data. However, because you are creating objects in a three-dimensional domain (x, y, and z extents) you must have all objects defined in a consistent coordinate system. Any coordinate projection may be used, but it is essential that all of your data files (including world files to georeference images) be in the same coordinate system.
Projecting File Coordinates Discussion of File Coordinate Projection Each file contains horizontal and vertical coordinates, which can be projected from one coordinate system to another given that the user knows which coordinates systems to project from and to. This is accomplished by adding the REPROJECT tag to the file. This tag is used in place of the coordinate unit definition and causes the file reader to look at the end of the file for a block of text describing the projection definitions. The definitions are a series of flags that listed below. NOTE: GMF files do not need the REPROJECT tag, the projection definitions can occur in a continuous block anywhere in the file.
All analytical data can be represented in one of two formats:
APDV: Analyte Point Data File Format
APDV: Analyte Point Data File Format Discussion of analyte (e.g. chemistry) or Property Files Analyte (e.g. chemistry) or property files contain horizontal and vertical coordinates, which describe the 3-D locations and values of properties of a system. For simplicity, these files will generally be referred to in this manual as analyte (e.g. chemistry) files, although they can actually contain any scalar property value of interest. Analyte (e.g. chemistry) files must be in ASCII format and can be delimited by commas, spaces, or tabs. They must have a .apdv suffix to be selected in the file browsers of EVS modules .The content and format of analyte (e.g. chemistry) files are the same, except that fence diagram files require some special subsetting and ordering. Each line of the analyte (e.g. chemistry) file contains the coordinate data for one sampling location and any number of (columns of) analyte (e.g. chemistry) or property values. There are no computational restrictions on the number of borings and/or samples that can be included in a analyte (e.g. chemistry) file, except that run times for execution of kriging do increase with the number of samples in the file.
AIDV: Analyte Interval Data File Format
AIDV: Analyte Interval Data File Format This format allows you to specify the top and bottom elevations of well screens and one or more concentrations that were measured over that interval. This new format (.aidv) will allow you to quickly visualize well screens in post_samples and automatically convert well screens to intelligently spaced samples along the screen interval for 3D (and 2D) kriging.
Analyte Time Files Format Discussion of Analyte Time Files Analyte time files contain 3-D coordinates (x, y, z) describing the locations of samples and values of one or more analytes or properties taken over a series of different times. Time files must conform to the ASCII formats described below and individual entries (coordinates or measurements) can be delimited by commas, spaces, or tabs. They must have either a .sct (Soil Chemistry Time) or .gwt (Ground Water Time) suffix to be selected in the file browsers of EVS modules. Each line of the file contains the coordinate data for one sampling location, or well screen, and any number of chemistry or property values. There are no limits on the number of borings and/or samples that can be included in these files, except that run times for execution of kriging do increase with a greater number of samples in the file.
PGF: Pre Geology File Lithology
Pre Geology File: Lithology The ASCII pregeology file name must have a .pgf suffix to be selected in the module’s file browser. This file type represents raw (uninterpreted) 3D boring logs representing lithology. This format is used by: create stratigraphic hierarchy post_samples gridding and horizons (to extract a top and bottom surface to build a single layer)
LPDV Lithology Point Data Value File Format
LPDV Lithology Point Data Value File Format The LPDV lithology file format is the most general, free-form format to represent lithology information. To understand the rationale for its existence, you must understand that when creating lithologic models (smooth or block) with lithologic modeling, the internal kriging operations require lithologic data in point format. Therefore all other lithology file formats (.PGF and .LSDV) are converted to points based on the PGF Refine Distance. LPDV files are not refined since we use the point data directly.
LSDV Lithology Screen Data Value File Format
LSDV Lithology Screen Data Value File Format The LSDV lithology file format can be used as a more feature rich replacement for the older PGF format. It has the following advantages: Fully supports non-vertical borings Supports missing intervals and lithology data which does not begin at ground surface Provides an Explicit definition of each lithologic interval An explanation of the file format follows:
GEO: Borehole Geology Stratigraphy
GEO: Borehole Geology Stratigraphy Geology data files basically contain horizontal and vertical coordinates, which describe the geometry of geologic features of the region being modeled. The files must be in ASCII format and can be delimited by commas, spaces, or tabs. Borehole Geology files must have a .geo suffix to be selected in the file browsers of EVS modules. The z values in .geo files can represent either elevation or depth, although elevation is generally the easiest to work with. When chemistry or property data is to be utilized along with geologic data for a 3-D visualization, a consistent coordinate system must be used in both sets of data.
Geology Multi-File Geology Multi-Files: Unlike the .geo file format, the .gmf format is not based on boring observations with common x,y coordinates. The multi-file format allows for description of individual geologic surfaces by defining a set of x,y,z coordinates (separated by spaces, tabs, and/or commas). Geologic hierarchy still applies for definition of complex geologic structures. This file format allows for creation of geologic models when the data available for the top surface and one or more of the subsurface layers are uncorrelated (in number or x,y location). For example, a gmf file may contain 1000 x,y,z measurements for the ground surface, but only 12 x,y,z measurements for other lithologic surfaces. This format also allows for specification of the geologic material color (layer material number).
.PT File Format The .PT (Place-Text) format is used to place 3D text (labels) with user adjustable font and alignment. The format is: Lines beginning with “#” are comments Lines beginning with “LINEFONT” are font specification lines specifically associated with single line text. LINEFONT, height, justification, azimuth, inclination, roll, red, green, blue, curve tolerance, font flags (bold is ignored) NOTE: There is no specification of the Font to be used, because EVS includes its own Unicode Line Font which supports most worldwide languages. Lines beginning with “TRUETYPE” are font specification lines specifically associated with TrueType Fonts.
This legacy format has been deprecated and replaced by the .PT File Format.