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
Last revisionBoth sides next revision
filereference:fileformat [2015/03/27 17:47] – enviadminfilereference:fileformat [2021/10/19 12:18] – [The new EML fileformat] enviadmin
Line 1: Line 1:
-====== The new EML fileformat ======+====== The EML fileformat ======
  
 ===== Why is there a new format? ===== ===== Why is there a new format? =====
Line 53: Line 53:
 <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 128:
  
 === ''bitmap'' Tags === === ''bitmap'' Tags ===
-TODO: Store Format? (-> JPG Stream)+Including bitmaps is not foressen for the moment.
  
 === ''collections'' Tag === === ''collections'' Tag ===
Line 136: Line 136:
 </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.