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
filereference:fileformat [2015/03/27 17:47] – enviadminfilereference:fileformat [2021/10/19 12:18] (current) – [Why is there a new format?] enviadmin
Line 1: Line 1:
-====== The new EML fileformat ====== +====== The EML fileformat ======
- +
-===== Why is there a new format? ===== +
- +
-With version 4, ENVI-met has changed the format of **ALL** system files, databasefiles and input/ output files to the new EML format.  +
-There are several reasons for that: First, with V4 a huge amount of new features have been introduced in ENVI-met. In any case, this required a complete redesign of the data structure and the contents of all input and output files.  Moreover, the old format lacked versioning information and was very unflexible concering the data sequenzes and the way the data was stored (fixed sign intervalls, all information in a fixed order). Hence, there was no way but to break with the old format and design a new one. +
- +
-For the Area Input files, import and conversion options are given through the editor, so you do not need to re-built them. For the smaller files (e.g. the files formerly known as Configuration Files .CF), you will need to re-compose them. That makes also sense as the new files also reflect the new model options in ENVI-met.+
  
  
Line 53: Line 46:
 <code XML> <code XML>
 <SOIL> <SOIL>
-     <ID> AK </ID>+     <ID> 00MM00AK </ID>
      <Description> Asphalt (with Gravel </Description>      <Description> Asphalt (with Gravel </Description>
      <versiegelung> 1 </versiegelung>      <versiegelung> 1 </versiegelung>
Line 128: Line 121:
  
 === ''bitmap'' Tags === === ''bitmap'' Tags ===
-TODO: Store Format? (-> JPG Stream)+Including bitmaps is not foressen for the moment.
  
 === ''collections'' Tag === === ''collections'' Tag ===
Line 136: Line 129:
 </code> </code>
  
-''Collections'' are Multi-Item tags stored as normal item tags. In the example above, the item ''<soilprofil>'' holds a series of 19 individual values (sub-items) which are stored in a comma-sepearated list.+''Collections'' are Multi-Item tags stored as normal item tags. In the example above, the item ''<soilprofil>'' holds a series of 19 individual values (sub-items) which are stored in a comma-sepearated list (to keep it readable we used only 2 instead of 6 chars for the IDs).
  
 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.