A holistic microclimate model

You are here: Technical Model Webpage » filereference » The EDX/EDT file format

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
filereference:edx_edi [2017/11/10 09:25] – external edit 127.0.0.1filereference:edx_edi [2023/01/05 20:06] (current) – enviadmin
Line 51: Line 51:
 </code> </code>
  
-The Data Descrition section of the EDX-file contains metadata on the general structure of the Data.+The Data Description section of the EDX-file contains metadata on the general structure of the Data.
 The items are: The items are:
 === <data_type> === === <data_type> ===
Line 99: Line 99:
 The file content in ENVI-met is referenced in more than one way:  The file content in ENVI-met is referenced in more than one way: 
   - By the **folder** where it is stored. All output files are organised in different folders such as ''atmosphere'' or ''soil''  to make clear what is the content (see . This is a very unsafe identifier as files are moved around frequently.   - By the **folder** where it is stored. All output files are organised in different folders such as ''atmosphere'' or ''soil''  to make clear what is the content (see . This is a very unsafe identifier as files are moved around frequently.
-  - By the **''filename''**.  Each file produced by ENVI-met holds a unique identifier such as ''_AT_'' for atmospheric data (see above).  In versions before 4.0 this was the only identifer to make clear what actually is stored in the file as file might be moved out of their original folders.+  - By the **''filename''**.  Each file produced by ENVI-met holds a unique identifier such as ''_AT_'' for atmospheric data (see above).  In versions before 4.0 this was the only identifier to make clear what actually is stored in the file as file might be moved out of their original folders.
   - By the **''<data_content>''** tag. In Version V4 we have added a more explicit information tag about the content of the file. This replaces any file analysis for the identifier mentioned above which might be gone by renaming a file.    - By the **''<data_content>''** tag. In Version V4 we have added a more explicit information tag about the content of the file. This replaces any file analysis for the identifier mentioned above which might be gone by renaming a file. 
  
Line 156: Line 156:
  
 === <name_variables>=== === <name_variables>===
-Lists the name of the variables as a comma-seperated list. +Lists the name of the variables as a comma seperated list. 
  
 **Please note**: LEONARDO will interpret information given in "( )" as UNITS for the variable and will place it on the correct space in legends and other map layout features.  **Please note**: LEONARDO will interpret information given in "( )" as UNITS for the variable and will place it on the correct space in legends and other map layout features. 
Line 219: Line 219:
       For y:=0 to YY-1 do       For y:=0 to YY-1 do
         For x:=0 to XX-1 do         For x:=0 to XX-1 do
-          For n:=0 to D do+          For n:=0 to D-1 do
             Write Variable[i].Value[x][y][z][n];             Write Variable[i].Value[x][y][z][n];
  end;  end;
Line 226: Line 226:
 Here ''XX'',''YY'' and ''ZZ'' are the dimensions of the model domain started counting at x=0,y=0,z=0 at the **lower left corner** of the model. ''D'' is the variable dimension of the file. For most files, ''D'' is 1 (=one data value for each grid coordinate and variable), for façade files e.g. ''D'' is 3 (= 3 values for each grid for the left x-, front y- and bottom z- face. The values for the right x-, rear y- and top z-face are stored in the neighbour cells). Here ''XX'',''YY'' and ''ZZ'' are the dimensions of the model domain started counting at x=0,y=0,z=0 at the **lower left corner** of the model. ''D'' is the variable dimension of the file. For most files, ''D'' is 1 (=one data value for each grid coordinate and variable), for façade files e.g. ''D'' is 3 (= 3 values for each grid for the left x-, front y- and bottom z- face. The values for the right x-, rear y- and top z-face are stored in the neighbour cells).
  
 +In addition, the 3D files for building façades hold **one** field  of dimension 1 at the very beginning: 
 +<code Pascal>
 +
 +    For z:= 0 to ZZ-1 do
 +      For y:=0 to YY-1 do
 +        For x:=0 to XX-1 do
 +             Write ObjectData[x][y][z];
 +
 +</code>
 +This field holds the general Object information like in the atmosphere files marking the position of buildings, plants, DEM and sources.
 +
 +
 +==== No Data Flag ====
  
 +In all ENVI-met output files, the value of **-999** represents the "No Data" flag.  Why certain grids do not carry valid data depends mainly on the data itself and how it was generated, so no general explanation can be given here. In any case, data flagged with a "No Data" value should not be included in any further data analysis or visualisation.  
  
 +===== Reading EDX/EDT files =====
 +Using the information above, it should be easy to read ENVI-met output files from all programming languages.
 +A good tutorial on how to use Python with NumPy can be found here: [[|Blog: Reading ENVI-met Files]].
 +Also check out the [[apps:datastudio:start|]] page for more information.