A holistic microclimate model

You are here: Technical Model Webpage » filereference » ENVI-met Output Files

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
filereference:output:start [2019/08/29 11:10] – enviadminfilereference:output:start [2021/07/26 18:11] – [Sumary on File Identifiers] enviadmin
Line 4: Line 4:
 Each ENVI-met simulation creates a huge amount of data which is organized in different files and folders.  Each ENVI-met simulation creates a huge amount of data which is organized in different files and folders. 
 In general, there are two different types of output files regardless their content: In general, there are two different types of output files regardless their content:
-  * **Simple Text Files**: Files which contain data in pure ASCII text format. Usually, the content of the file are described in the first row of the file. These file can be read and visiualized with any software that can read text files (which should be about every piece of software that can visiualize data).+  * **Simple Text Files**: Files which contain data in pure ASCII text format. Usually, the content of the file are described in the first row of the file. These file can be read and visiualized with any software that can read text files.  From Version 5 on, ENVI-met provides different options to analyse data using Python e.g. the DataStudio inside LEONARDO. With respect to Python, the format of the text output files have been changed in V5 to allow a seamless use with Python and Pandas.
   * **Binary Files (EDX/EDT)**: The main ENVI-met output files are stored in a binary format and require special software to be read. The [[leonardo:start|LEONARDO]] software included in the ENVI-met system offers a comfortable and visual access to all data and give various options for 2D and 3D visualisation. In addition, with the help of the reference for the [[filereference:edx_edi|EDX/EDT file format]], own reader routines can easily be developed.  Moreover, ENVI-met provides the option to convert EDX/EDT data to the [[wp>NetCDF|NetCDF format]]  via the **NetCDF application** found in the Headquarter.    * **Binary Files (EDX/EDT)**: The main ENVI-met output files are stored in a binary format and require special software to be read. The [[leonardo:start|LEONARDO]] software included in the ENVI-met system offers a comfortable and visual access to all data and give various options for 2D and 3D visualisation. In addition, with the help of the reference for the [[filereference:edx_edi|EDX/EDT file format]], own reader routines can easily be developed.  Moreover, ENVI-met provides the option to convert EDX/EDT data to the [[wp>NetCDF|NetCDF format]]  via the **NetCDF application** found in the Headquarter. 
 +
 +**In order to use advanced analysis functions like Time Series in LEONARDO, it is strongly recommended to store only one simulation run in the same folder and not to mix different model runs.**
  
 ===== Name and storage logic ===== ===== Name and storage logic =====
Line 13: Line 15:
   * Level 2: Classification by filename   * Level 2: Classification by filename
   * Level 3: Metadata information in the [[filereference:edx_edi|. EDX File]]   * Level 3: Metadata information in the [[filereference:edx_edi|. EDX File]]
 +
 +For simple Text files, Level 3 data are not available, so that the filename and filename extension provide information about the content of the files.
  
 ==== Level 1: Storage by folder name ==== ==== Level 1: Storage by folder name ====
Line 51: Line 55:
  
  
-==== Sumary on File Identifiers ====+==== File Name Identifiers: Overview ==== 
 + 
 +Especially for pure text files it is not possible to store metadata in the file itself. So we must use the filename and filename extension to identify the contend of the files.  
 +The list below provides a summary on the different file IDs thatare used all through ENVI-met at different occasions to identify the content of a file. 
 +The IDs can be part of the filename or can be used as file extensions. 
 + 
  
 <WRAP box left 80%> <WRAP box left 80%>
 ^ ID ^ Content ^ Remark ^ ^ ID ^ Content ^ Remark ^
-| _AT_ | Atmospheric data  |  | +| AT | Atmospheric data  |  | 
-| _BLDG_ | Building data  | Both STATIC and DYNAMIC   | +| FX | Surface data and surface fluxes  |  | 
-| _POLU_ | Pollutants  |  | +| SO | Soil data  |  | 
-| _SO_ | Soil data  |  | +| VEG | Vegetation data  | Main 3D Model, Observed plants are text files | 
-| _SA_ | Solar Access  | Main 3D Model | +| BLDG | Building data Facade  | Static building data like material properties  | 
-| _SAFAC_ | Solar Accerss   | Facade and Single Wall data  | +| FAC | Building data Facade  | Dynamic building data like wall temperatures  | 
-| _FX_ | Surface data and surface fluxes  |  | +| POLU | Pollutants  |  | 
-| _VEG_ | Vegetation data  | Main 3D Model, Observed plants are text files |+| BIO | Biomet Data  |  | 
 +| SA | Solar Access  | Main 3D Model | 
 +| SAFAC | Solar Accerss   | Facade and Single Wall data  | 
 +| VEG | Vegetation data  | Main 3D Model, Observed plants are text files | 
 +| IVS| Indexed View Sphere | Data on the Index View Sphere if used | 
 </WRAP> </WRAP>