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:edx_edi [2014/01/16 21:27] – [The EDX Metadata file] enviadmin | filereference:edx_edi [2014/07/15 16:27] – enviadmin | ||
---|---|---|---|
Line 15: | Line 15: | ||
**Note:** All data stored withing the EDX files by ENVI-met are consistent. Several sections contain repeating (=redundant) information. While normally redundant information are seen as a design failure, here they serve a clear target: They allow a quick access on the raw data without interpreting the thematic content of the file and its implication on the file format. | **Note:** All data stored withing the EDX files by ENVI-met are consistent. Several sections contain repeating (=redundant) information. While normally redundant information are seen as a design failure, here they serve a clear target: They allow a quick access on the raw data without interpreting the thematic content of the file and its implication on the file format. | ||
- | Example: A surface flux file is always just 2-dimensional, | + | Example: A surface flux file is always just 2-dimensional, |
Line 70: | Line 70: | ||
* 3D facade files with 3 data for each grid point corresponding to the x-, y- and z-cell faces of the cell | * 3D facade files with 3 data for each grid point corresponding to the x-, y- and z-cell faces of the cell | ||
- | In the example | + | In the example |
**Note: More type are up to come** | **Note: More type are up to come** | ||
Line 78: | Line 78: | ||
type | type | ||
tSimFileContent = ( | tSimFileContent = ( | ||
- | fcUnknown = 0, // undef | + | fcUnknown = 0, // undefined format |
- | fcAtmosphere = 1, // 3d atmosphere data _AT_ | + | fcAtmosphere = 1, // 3D atmosphere data _AT_ |
fcSurface = 2, // surface data _FX_ | fcSurface = 2, // surface data _FX_ | ||
fcSoil = 3, // soil data _SO_ | fcSoil = 3, // soil data _SO_ | ||
Line 85: | Line 85: | ||
fcBiomet = 5, // biomet _BIO_ | fcBiomet = 5, // biomet _BIO_ | ||
fcVegetation = 6, // vegetation _VEG_ | fcVegetation = 6, // vegetation _VEG_ | ||
- | fcFacade = 7, // building data _BLDG_ | + | fcFacade = 7, // building |
- | fcSolarAccess = 8, // solar access _SA_ | + | fcSolarAccess = 8, // 2D solar access _SA_ |
fcFacadeStatic = 9, // constant building data _BLDG_ | fcFacadeStatic = 9, // constant building data _BLDG_ | ||
- | fcFacadeSolarAccess = 10 // facade solar access data _SAFAC_ | + | fcFacadeSolarAccess = 10, // facade solar access data _SAFAC_ |
+ | fcRadiation = 11, // radiation data _RD_ | ||
+ | fcViewScape = 12, // view projections | ||
+ | fcPhotocat = 13 // photocatalytic data _PHX_ | ||
); | ); | ||
- | | + | |
The ''< | The ''< | ||
Line 122: | Line 125: | ||
The ''< | The ''< | ||
- | === Dimensions | + | === Dimensions: < |
Defines the matrix layout of the binary files. It is again, to some extent, a repetition to the infomrmation store before. | Defines the matrix layout of the binary files. It is again, to some extent, a repetition to the infomrmation store before. | ||
- | === Grid spacing | + | === Grid spacing: < |
Defines the size of the individual grids in x-, y- and z- dimension. For each grid as given by the '' | Defines the size of the individual grids in x-, y- and z- dimension. For each grid as given by the '' | ||
Line 141: | Line 144: | ||
</ | </ | ||
- | The **variables** section defines the different information | + | The **variables** section defines the different information |
While the preceeding section were used to interpret the format of the file, this section defines the information stored for each grid. | While the preceeding section were used to interpret the format of the file, this section defines the information stored for each grid. | ||
=== < | === < | ||
- | The ''< | + | The ''< |
- | In most of the cases, there is just one data set for each gird pont. But for the 3D data of buildings coded with '' | + | In most of the cases, there is just one data set for each grid point. But for the 3D data of buildings coded with '' |
=== < | === < | ||
Line 155: | Line 158: | ||
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 "( )" |
==== Model Description ==== | ==== Model Description ==== | ||
Line 174: | Line 177: | ||
</ | </ | ||
| | ||
- | The **< | + | The **< |
- | Software like LEONADO | + | Software like LEONARDO |
| | ||
| | ||
Line 184: | Line 187: | ||
< | < | ||
< | < | ||
+ | < | ||
</ | </ | ||
</ | </ | ||
- | The ENVI-met reference is added to kep track on which version the simulation was actually executed. | + | The ENVI-met reference is added to keep track on which version the simulation was actually executed. |
- | In addition, the ''< | + | In addition, the ''< |
+ | The ''< | ||
- | === Additional Info === | + | ==== Additional Info ==== |
<code XML> | <code XML> |