A holistic microclimate model

You are here: Technical Model Webpage » filereference » The EML fileformat

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:fileformat [2014/01/16 21:44] – [ENVI-met Markup Language: General concept] enviadminfilereference:fileformat [2014/03/28 23:11] – enviadmin
Line 9: Line 9:
  
  
-===== ENVI-met Markup Language EML: General concept =====+===== ENVI-met Markup Language EML format: General concept =====
    
-The new ENVI-met EML (ENVI-met Markup Languge)  format is an XML-based self-describing file format. It can handle missing information by automatically adding default settings where possible. Therefore there will be almost no (or very few) version conflicts with old, recent and future files and the information they (not) provide.+The new ENVI-met EML (ENVI-met Markup Language)  format is an XML-based self-describing file format. It can handle missing information by automatically adding default settings where possible. Therefore there will be almost no (or very few) version conflicts with old, recent and future files and the information they (not) provide.
  
 As the term "XML-based" suggests, it uses the concept of XML, but only supports a limited sub-set of XML features and file options. In addition, EML introduces a number of extra features (e.g. matrix tags) which are not defined in general XML. As the term "XML-based" suggests, it uses the concept of XML, but only supports a limited sub-set of XML features and file options. In addition, EML introduces a number of extra features (e.g. matrix tags) which are not defined in general XML.
Line 69: Line 69:
 </code> </code>
  
-== Remark for ''color'' codes == +
-Color codes like in this example are always stored in RGB data. To understand the concept, the decimal value needs to be converted into a hexadecimal value. In hexadecimal, the colors are coded ''$RRGGBB'' where ''RR'', ''GG'' and ''BB'' are the intensities for the red, green and blue component of the color. Each intensity ranges from ''$00'' (not present) to ''$FF'' (full presence). For example ''$00FF00'' is a full red and in decimal this would be '#65280' like in the example above which gives no clue which color this might be. +
  
  
Line 79: Line 78:
  
 === ''matrix-data'' Tags === === ''matrix-data'' Tags ===
-**Modified:** 
  
 ''Matrix-data'' tags hold a comma-seperated set of 2D data. It is similar to the original ENVI-met Matrix-Format but has some important changes: ''Matrix-data'' tags hold a comma-seperated set of 2D data. It is similar to the original ENVI-met Matrix-Format but has some important changes:
Line 87: Line 85:
 <code XML> <code XML>
 <buildings> <buildings>
-<z-top type="matrix-data" X="40" Y="40"> + <zTop type="matrix-data" dataI="15" dataJ="15"> 
-         (Example missing) +     0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 
-</z-top>+     0,20,20,0,0,0,0,0,0,0,0,0,20,20,0 
 +     (...) 
 +     </zTop>
 </buildings> </buildings>
 </code> </code>
  
 The ''matrix-data'' tag allows the definition of a 2D element matrix in the EML file. The attribute required are: The ''matrix-data'' tag allows the definition of a 2D element matrix in the EML file. The attribute required are:
-  * rows: Number of rows following in the matrix +  * dataI: Number of elements in each row (=one x-row) 
-  * colums: Number of columns in the matrix+  * dataJ: Number of rows to come (=number of y-elements)
  
 +No line-breaks are alowed within one row of data. 
  
-No line-breaks are alowed within one row of data.+ 
 +**Note:**  
 +Valid only for PREVIEW applications: This item has been changed. Previous, the dimensions tags have been "columns" ans "rows" but due to missleading interpretation hve been changed.  
 +A test  was included in the reader routines allowing old file to be read, but only new format are written.
  
 === ''spare-matrix-3D'' Tags === === ''spare-matrix-3D'' Tags ===
Line 139: Line 143:
  
 These kind of tags only work with items that have explicit defined number of subitems to follow. They will only be interpeted correctly with programs understanding the meaning of such a comma-seperated list. In standard XML, this //collection// would have been splitted into 19 sub-items, one for each soil layer. Each of these sub-items would have its own opening and closing tag. For ENVI-met this was considered as an overkill. Therefor the Multi-Item tags have been introduced.  These kind of tags only work with items that have explicit defined number of subitems to follow. They will only be interpeted correctly with programs understanding the meaning of such a comma-seperated list. In standard XML, this //collection// would have been splitted into 19 sub-items, one for each soil layer. Each of these sub-items would have its own opening and closing tag. For ENVI-met this was considered as an overkill. Therefor the Multi-Item tags have been introduced. 
 +
 +
 +=== Color encoding ===
 +Color codes like in the example above are always stored in plain RGB data. To understand the concept, the decimal value needs to be converted into a hexadecimal value. In hexadecimal, the colors are coded ''$RRGGBB'' where ''RR'', ''GG'' and ''BB'' are the intensities for the red, green and blue component of the color. Each intensity ranges from ''$00'' (not present) to ''$FF'' (full presence). For example ''$00FF00'' is a full red and in decimal this would be '#65280' like in the example above which gives no clue which color this might be. 
 +