Changes between Version 94 and Version 95 of doc/app/iofiles

Timestamp:

Jun 7, 2017 8:43:47 AM (8 years ago)

Author:

suehring

Comment:

--

doc/app/iofiles

@@ -823 +823 @@
 }}}
 These data must exactly match the horizontal grid. Due to the staggered grid, the topography may be displaced by -0.5 [../inipar#dx dx] in x-direction and -0.5 [../inipar#dy dy] in y-direction depending on the parameter [../inipar#topography_grid_convention topography_grid_convention]. See also the example in [source:/palm/trunk/EXAMPLES/topo_file trunk/EXAMPLES/topo_file/]. \\\\
+Alternatively, the user may add code to the user interface subroutine [../userint/int#user_init_grid user_init_grid].
+}}}
+|----------------
+{{{#!td style="vertical-align:top; width: 50px"
+90
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#TOPOGRAPHY_DATA2 TOPOGRAPHY_DATA2]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+I
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+netCDF
+}}}
+{{{#!td
+Rastered topography information. \\\\
+In case of  [../inipar#topography topography] = '' 'read_from_file' '' the subroutine {{{init_grid}}} reads the topography information. 
+Topography information can be further split-up into building and orography information (see netCDF varialbes ''buildings_0'' and ''orography_0'', respectively. 
+''orography_0(y,x)'' is an optional variable, comprising rastered orography-height information in m. 
+''buildings_0'' can be available in two general modes, distinguished by the variable's attribute ''lod''. \\
+1) If ''lod'' = 1, ''buildings_0(y,x)'' comprises rastered 2-D floating-point building / topography height information in m, or \\
+2) if ''lod'' = 2, ''buildings_0(z,y,x)'' comprises rastered 3-D integer building / topography information for each grid point. This case, ''buildings_0'' at the respective grid point is either 1 if the grid point belongs to a building, or is 0 if the grid point belongs to the atmosphere. Topography information need to be given up to the highest grid level where topography occurs. It is not required to provide topography information up to the model top. The 2) method is only required if overhanging building structures should be considered. Moreover, in this case, orography information is not considered so far. \\
+
+If both, ''orography_0'' and ''buildings_0'' are given, ''buildings_0'' is mapped on top of ''orography_0''. \\ 
+The global origin (y=0,x=0) of the data is the southwest corner of the model domain.
+
+If both, ASCII an netCDF file are present, topography information will be read only from netCDF file. 
+
+The data must exactly match the horizontal grid. Due to the staggered grid, the topography may be displaced by -0.5 [../inipar#dx dx] in x-direction and -0.5 [../inipar#dy dy] in y-direction depending on the parameter [../inipar#topography_grid_convention topography_grid_convention]. \\\\
 Alternatively, the user may add code to the user interface subroutine [../userint/int#user_init_grid user_init_grid] to allow different data formats.
 }}}