Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
filereference:fileformat [2014/01/16 21:45] – [ENVI-met Markup Language EML: General concept] enviadmin | filereference:fileformat [2014/05/10 00:19] – [Why is there a new format?] enviadmin | ||
---|---|---|---|
Line 4: | Line 4: | ||
With version 4, ENVI-met has changed the format of **ALL** system files, databasefiles and input/ output files to the new EML 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. | + | 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. |
For the large files such as your Area Input files and the different databases, import and conversion options are given, so you do not need to re-built the big files. 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. | For the large files such as your Area Input files and the different databases, import and conversion options are given, so you do not need to re-built the big files. 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 69: | Line 69: | ||
</ | </ | ||
- | == Remark for '' | + | |
- | 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, | + | |
Line 79: | Line 78: | ||
=== '' | === '' | ||
- | **Modified: | ||
'' | '' | ||
Line 87: | Line 85: | ||
<code XML> | <code XML> | ||
< | < | ||
- | <z-top type=" | + | <zTop type=" |
- | | + | 0, |
- | </z-top> | + | |
+ | (...) | ||
+ | | ||
</ | </ | ||
</ | </ | ||
The '' | The '' | ||
- | * rows: Number of rows following | + | * dataI: Number of elements |
- | * 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 | + | |
+ | **Note:** | ||
+ | Valid only for PREVIEW applications: | ||
+ | A test was included in the reader routines allowing old file to be read, but only new format | ||
=== '' | === '' | ||
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 // | 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 // | ||
+ | |||
+ | |||
+ | === 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, | ||
+ | |||