Changes between Initial Version and Version 1 of doc/app/iofiles/pids/static


Ignore:
Timestamp:
Jul 2, 2019 1:24:05 PM (6 years ago)
Author:
scharf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/iofiles/pids/static

    v1 v1  
     1== [=#static_input '''Static input file'''] ==
     2
     3The static input file encompasses topography information as well as all necessary information file to initialize all land- and urban-type surfaces in the model, such as heat capacities, roughness, albedo, emissivity, etc..
     4The initialization procedure for the surfaces follows a multi-step approach, depending on the given level of detail of each variable as provided in the static input file.
     5In a first step, surfaces are initialized horizontally homogeneous with a bulk classification for each type (e.g. vegetation or soil), either set by a default value or set by a namelist-provided value, while the bulk classification provides standard values for a variety of parameters.
     6In a second step, surfaces are initialized individually by providing the bulk classification at each grid point individually.
     7In case more detailed information is available, all or even single parameters can be initialized individually at each grid point.
     8
     9The provided input data is used to classify each surface element according to its treatment, i.e. default-, natural- or urban-type, in order to treat each surface element accordingly.
     10In case no land-surface or urban-surface scheme is applied, all surfaces are classified as default-type.
     11If a surface element has vegetation, pavement or water, it will be classified as natural-type and is treated by the land-surface scheme, while building surfaces will be treated by the urban-surface scheme.
     12
     13\\\\
     14=== [=#attr '''Global attributes:] ===
     15
     16'''Following list of mandatory attributes is expected by PALM when reading input data from the static input file.'''
     17
     18||='''Attribute'''  =||='''Type'''  =||='''Explanation / Remarks'''  =||
     19|----------------
     20{{{#!td style="vertical-align:top;width: 150px"
     21[=#origin_lat '''origin_lat''']
     22}}}
     23{{{#!td style="vertical-align:top;width: 50px"
     24NC_FLOAT
     25}}}
     26{{{#!td
     27Geographical latitude in degrees north. This attribute defines the south boundary of the model domain and overwrites the namelist parameter [../../inipar#latitude latitude], which is used e.g. for the Coriolis parameters as well as for the radiation. 
     28Please note, in case of a nested run, values of [../../inipar#latitude latitude] will be synchronized internally to the respective value of the root parent domain.
     29}}}
     30|----------------
     31{{{#!td style="vertical-align:top;width: 150px"
     32[=#origin_lon '''origin_lon''']
     33}}}
     34{{{#!td style="vertical-align:top;width: 50px"
     35NC_FLOAT
     36}}}
     37{{{#!td
     38Geographical longitude in degrees east. This attribute defines the left boundary of the model domain and overwrites the namelist parameter [../../inipar#longitude longitude], which is used e.g. for the radiation. 
     39Please note, in case of a nested run, values of [../../inipar#longitude longitude] will be synchronized internally to the respective value of the root parent domain.
     40}}}
     41|----------------
     42{{{#!td style="vertical-align:top;width: 150px"
     43[=#origin_time '''origin_time''']
     44}}}
     45{{{#!td style="vertical-align:top;width: 50px"
     46NC_CHAR
     47}}}
     48{{{#!td
     49Reference point in time (UTC) {{{YYYY­-MM­-DD hh:mm:ss +00}}}.
     50}}}
     51|----------------
     52{{{#!td style="vertical-align:top;width: 150px"
     53[=#origin_x '''origin_x''']
     54}}}
     55{{{#!td style="vertical-align:top;width: 50px"
     56NC_FLOAT
     57}}}
     58{{{#!td
     59Reference x-location in m (UTM) of left model boundary.
     60}}}
     61|----------------
     62{{{#!td style="vertical-align:top;width: 150px"
     63[=#origin_y '''origin_y''']
     64}}}
     65{{{#!td style="vertical-align:top;width: 50px"
     66NC_FLOAT
     67}}}
     68{{{#!td
     69Reference y-location in m (UTM) of south model boundary.
     70}}}
     71|----------------
     72{{{#!td style="vertical-align:top;width: 150px"
     73[=#origin_z '''origin_z''']
     74}}}
     75{{{#!td style="vertical-align:top;width: 50px"
     76NC_FLOAT
     77}}}
     78{{{#!td
     79Reference height in m above sea level after DHHN2016.
     80}}}
     81|----------------
     82{{{#!td style="vertical-align:top;width: 150px"
     83[=#rotation_angle '''rotation_angle''']
     84}}}
     85{{{#!td style="vertical-align:top;width: 50px"
     86NC_FLOAT
     87}}}
     88{{{#!td
     89Clockwise angle of rotation in degrees between North positive y axis and the y axis in the data, e.g. ''0.0''.
     90}}}
     91\\\\
     92=== [=#topo '''Topography:] ===
     93
     94In order to prescribe topography from the static input file, [../../inipar#topography topography] = 'read_from_file' is required.
     95
     96||='''Input variable'''  =||='''Type'''  =||='''LOD''' =||='''Explanation / Remarks'''  =||
     97|----------------
     98{{{#!td style="vertical-align:top;width: 150px"
     99[=#zt '''zt(y,x)''']
     100}}}
     101{{{#!td style="vertical-align:top;width: 50px"
     102NC_FLOAT
     103}}}
     104{{{#!td style="vertical-align:top;width: 50px"
     105none
     106}}}
     107{{{#!td
     108Terrain height in m relative to [#origin_z origin_z].
     109If not provided, the relative terrain height will be set to 0 all over the model domain.
     110Please note, '''zt''' must not contain any {{{_FillValues}}}.
     111}}}
     112|----------------
     113{{{#!td style="vertical-align:top;width: 150px"
     114[=#buildings_2d '''buildings_2d(y,x)''']
     115}}}
     116{{{#!td style="vertical-align:top;width: 50px"
     117NC_FLOAT
     118}}}
     119{{{#!td style="vertical-align:top;width: 50px"
     1201
     121}}}
     122{{{#!td
     1232-dimensional building height in m relative to the underlying terrain. No holes or overhanging structures are possible. '''buildings_2d''' will be mounted on top of the maximum local terrain height occupied by the respective building. Please note, '''buildings_2d''' will not be used if [#buildings_3d buildings_3d] is present on file. If '''buildings_2d''' are prescribed, [#building_id building_id] is required. 
     124}}}
     125|----------------
     126{{{#!td style="vertical-align:top;width: 150px"
     127[=#buildings_3d '''buildings_3d(z,y,x)''']
     128}}}
     129{{{#!td style="vertical-align:top;width: 50px"
     130NC_BYTE
     131}}}
     132{{{#!td style="vertical-align:top;width: 50px"
     1332
     134}}}
     135{{{#!td
     1363-dimensional building topology relative to the underlying terrain. '''buildings_3d''' will be mapped on top of the maximum local terrain height occupied by the respective building. Note, '''buildings_3d''' do not need to be prescribed beyond the top level of the highest buildings. If '''buildings_3d''' are prescribed, [#building_id building_id] is required. 
     137}}}
     138|----------------
     139{{{#!td style="vertical-align:top;width: 150px"
     140[=#building_id '''building_id(y,x)''']
     141}}}
     142{{{#!td style="vertical-align:top;width: 50px"
     143NC_INT
     144}}}
     145{{{#!td style="vertical-align:top;width: 50px"
     146none
     147}}}
     148{{{#!td
     149Building ID is used to identify single building envelopes, which is used for correct mapping of buildings on top of the underlying terrain, as well as for the [#indoor_model indoor_model]. Please note, '''building_id''' must not contain any {{{_FillValue}}} at grid points where buildings_2d/3d is defined.
     150}}}
     151
     152\\\\
     153
     154=== [=#surf '''Surface variables''':] ===
     155
     156For a proper classification of natural land and water surfaces, [#pavement_type pavement_type], [#soil_type soil_type], [#vegetation_type vegetation_type] and [#water_type water_type] are required, which define bulk parameters for albedo, soil, root distribution, leaf-area density, etc. To enable initialization of the land-surface model with input-file-provided variables, the namelist parameter [../../lsmpar#surface_type surface_type] needs to be set to 'netcdf'. 
     157In case more than one of the surface types (vegetation, pavement, water) is given at an (x,y) location, the relative fraction of each of the types must be provided by [#surface_fraction surface_fraction].
     158Further, if the [../../usmpar urban-surface model] is applied, also [#building_type building_type] is required, which defines bulk parameters to run the urban-surface model. Please note, for the sake of consistency, at least one of the variables  [#pavement_type pavement_type], [#vegetation_type vegetation_type], [#water_type water_type] or [#building_type building_type] needs to be defined at each (x,y) location if the land- and urban-surface model is applied.
     159If only the land-surface model is applied but no urban-surface model, one of [#pavement_type pavement_type], [#vegetation_type vegetation_type] or [#water_type water_type] needs to be defined at each (x,y) location.
     160Further, in case data is taken from the static input file, both, the land- and urban-surface model need to be either switched on or off. Applying only one of the energy-balance models is not sufficient and will lead to a controlled termination.  \\
     161
     162||='''Input variable'''  =||='''Type'''  =||='''LOD''' =||='''Explanation / Remarks'''  =||
     163|----------------
     164{{{#!td style="vertical-align:top;width: 150px"
     165[=#albedo_pars '''albedo_pars'''] //
     166'''(nalbedo_pars,y,x)'''
     167}}}
     168{{{#!td style="vertical-align:top;width: 50px"
     169NC_FLOAT
     170}}}
     171{{{#!td style="vertical-align:top;width: 50px"
     172none
     173}}}
     174{{{#!td
     175Spectral and broadband albedo for natural and urban surfaces for ''(y,x)''-locations.
     176When [#albedo_type albedo_type] = 0, all parameters must be set. Otherwise, single parameters for a given [#albedo_type albedo_type] can be overwritten, while the remaining parameters must be set to {{{_FillValue}}}.
     177}}}
     178|----------------
     179{{{#!td style="vertical-align:top;width: 150px"
     180[=#albedo_type '''albedo_type(y,x)''']
     181}}}
     182{{{#!td style="vertical-align:top;width: 50px"
     183NC_BYTE
     184}}}
     185{{{#!td style="vertical-align:top;width: 50px"
     186none
     187}}}
     188{{{#!td
     189Optional classification of albedo. Default values for '''albedo_type''' are already set in the bulk parametrization of [#buiding_type building_type], [#pavement_type pavement_type], [#vegetation_type vegetation_type], [#water_type water_type], but will be overwritten in case '''albedo_type''' is defined. The value of '''albedo_type''' will also overwrite the prescribed values in [#vegetation_pars vegetation_pars], [#water_pars water_pars], or [#pavement_pars pavement_pars].
     190An overview of the different albedo types can be found  [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     191}}}
     192|----------------
     193{{{#!td style="vertical-align:top;width: 150px"
     194[=#building_pars '''building_pars'''] //
     195'''(nbuilding_pars,y,x)'''
     196}}}
     197{{{#!td style="vertical-align:top;width: 50px"
     198NC_FLOAT
     199}}}
     200{{{#!td style="vertical-align:top;width: 50px"
     201none
     202}}}
     203{{{#!td
     204Parameters for the building parameterization. When [#building_type building_type] = 0, all parameters must be set. Otherwise, single parameters for a given [#building_type building_type] can be overwritten, while the remaining parameters must be set to {{{_FillValue}}}. '''building_pars''' becomes only effective if the [../../usmpar urban-surface model] or the [#indoor_model indoor_model] are applied.
     205Building parameters can be distinguished between ground-floor and upper level. For more information, please see [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     206}}}
     207|----------------
     208{{{#!td style="vertical-align:top;width: 150px"
     209[=#building_surface_pars '''building_surface_pars'''] //
     210'''(nbuilding_surface_pars,s,\\
     211y,x)'''
     212}}}
     213{{{#!td style="vertical-align:top;width: 50px"
     214NC_FLOAT
     215}}}
     216{{{#!td style="vertical-align:top;width: 50px"
     217none
     218}}}
     219{{{#!td
     220Detailed information for specific building surfaces. This variable
     221can contain data for the entire domain or for selected areas where
     222detailed data is available.
     223Setting of '''building_surface_pars''' will replace parameter settings made by [#building_type building_type] and [#building_pars building_pars].
     224'''building_surface_pars''' becomes only effective if the [../../usmpar urban-surface model] is applied.
     225For more information, please see [[attachment:PALM_input_data_standard_v1.9.pdf|here]]. \\\\
     226'''Please note: this input variable is currently not implemented.'''
     227}}}
     228|----------------
     229{{{#!td style="vertical-align:top;width: 150px"
     230[=#building_type '''building_type(y,x)''']
     231}}}
     232{{{#!td style="vertical-align:top;width: 50px"
     233NC_BYTE
     234}}}
     235{{{#!td style="vertical-align:top;width: 50px"
     236none
     237}}}
     238{{{#!td
     239Building type used to select bulk parameters. '''building_type''' is required if the [../../usmpar urban-surface model] or the [#indoor_model indoor_model]  are applied.
     240Please note, '''building_type''' must not contain any {{{_FillValue}}} at grid points where buildings_2d/3d is defined.
     241An overview of the different building types can be found [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     242}}}
     243|----------------
     244{{{#!td style="vertical-align:top;width: 150px"
     245[=#pavement_pars '''pavement_pars'''] //
     246'''(npavement_pars,y,x)'''
     247}}}
     248{{{#!td style="vertical-align:top;width: 50px"
     249NC_FLOAT
     250}}}
     251{{{#!td style="vertical-align:top;width: 50px"
     252none
     253}}}
     254{{{#!td
     255Parameters required for the bulk pavement parameterization in the
     256land surface scheme.
     257When [#pavement_type pavement_type] = 0, all parameters must be set. Otherwise, single parameters for a given [#pavement_type pavement_type] can be overwritten, while the remaining parameters must be set to {{{_FillValue}}}.
     258}}}
     259|----------------
     260{{{#!td style="vertical-align:top;width: 150px"
     261[=#pavement_subsurface_pars '''pavement_subsurface_pars'''] //
     262'''(npavement_subsurface_pars,  \\
     263zsoil,y,x)'''
     264}}}
     265{{{#!td style="vertical-align:top;width: 50px"
     266NC_FLOAT
     267}}}
     268{{{#!td style="vertical-align:top;width: 50px"
     269none
     270}}}
     271{{{#!td
     272Parameters required for the bulk pavement parameterization.
     273For all zsoil levels where '''pavement_subsurface_pars''' is not missing, the settings of the soil model are overwritten, i.e. thermal conductivity and heat capacities are set, and the layers are impermeable for water.
     274When [#pavement_type pavement_type] = 0, all parameters must be set.
     275}}}
     276|----------------
     277{{{#!td style="vertical-align:top;width: 150px"
     278[=#pavement_type '''pavement_type(y,x)''']
     279}}}
     280{{{#!td style="vertical-align:top;width: 50px"
     281NC_BYTE
     282}}}
     283{{{#!td style="vertical-align:top;width: 50px"
     284none
     285}}}
     286{{{#!td
     287Bulk classification of pavements on soil. At locations where '''pavement_type''' is defined, [#soil_type soil_type] must not contain any {{{_FillValues}}}. '''pavement_type''' overwrites the homogeneously prescribed setting via the namelist parameter [../../lsmpar#pavement_type pavement_type]. An overview of the different pavement types can be found  [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     288}}}
     289|----------------
     290{{{#!td style="vertical-align:top;width: 150px"
     291[=#soil_pars '''soil_pars'''] //
     292'''(nsoil_pars,(zsoil),y,x)'''
     293}}}
     294{{{#!td style="vertical-align:top;width: 50px"
     295NC_FLOAT
     296}}}
     297{{{#!td style="vertical-align:top;width: 50px"
     2981, 2
     299}}}
     300{{{#!td
     301Parameters for soil parametrization.
     302When [#soil_type soil_type] = 0, all parameters must be set. Otherwise,
     303single parameters for a given [#soil_type soil_type] can be overwritten, while the remaining parameters must be set to {{{_FillValue}}}.
     304In case {{{lod = 1}}}, prescribed parameters are vertically uniform,
     305while in case {{{lod = 2}}} parameters can be set for each layer individually. An overview of the different soil parameters can be found  [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     306}}}
     307|----------------
     308{{{#!td style="vertical-align:top;width: 150px"
     309[=#soil_type '''soil_type((zsoil),y,x)''']
     310}}}
     311{{{#!td style="vertical-align:top;width: 50px"
     312NC_BYTE
     313}}}
     314{{{#!td style="vertical-align:top;width: 50px"
     3151, 2
     316}}}
     317{{{#!td
     318Bulk classification of soil in terms of porosity. '''soil_type''' overwrites the homogeneously prescribed setting via the namelist parameter [../../lsmpar#soil_type soil_type].
     319In case {{{lod = 1}}}, a 2-dimensional vertically uniform soil texture is prescribed, while in case {{{lod = 2}}} the 3-dimensional soil_type is set for each layer individually. An overview of the different soil types can be found  [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     320}}}
     321|----------------
     322{{{#!td style="vertical-align:top;width: 150px"
     323[=#surface_fraction '''surface_fraction'''] //
     324'''(nsurface_fraction,y,x)'''
     325}}}
     326{{{#!td style="vertical-align:top;width: 50px"
     327NC_FLOAT
     328}}}
     329{{{#!td style="vertical-align:top;width: 50px"
     330none
     331}}}
     332{{{#!td
     333Relative fraction of the respective surface type given via [#vegetation vegetation_type] (nsurface_fraction = 0), [#pavement_type pavement_type] (nsurface_fraction = 1) and [#water_type water_type] (nsurface_fraction = 2). The sum over all relative fractions must be equal to one for each location. This parameter is only needed at
     334locations (y,x) where more than one surface type (vegetation,
     335pavement, water) is defined. Moreover, if more than one surface type is defined at a location, the relative fractions of the respective surface types must not be 0. Also, if '''surface_fraction''' is given for one of the above mentioned surface types, this type need to be defined at this location.
     336}}}
     337|----------------
     338{{{#!td style="vertical-align:top;width: 150px"
     339[=#vegetation_pars '''vegetation_pars'''] //
     340'''(nvegetation_pars,y,x)'''
     341}}}
     342{{{#!td style="vertical-align:top;width: 50px"
     343NC_FLOAT
     344}}}
     345{{{#!td style="vertical-align:top;width: 50px"
     346none
     347}}}
     348{{{#!td
     349Parameters for the bulk parametrization of non-resolved vegetation in the land-surface model for each ''(y,x)''-location. 
     350All/single parameters of vegetation_pars for a given [#vegetation_type vegetation_type] can be overwritten for given ''(y,x)''-location. If only single parameters shall be overwritten, all other parameters must be set to {{{_FillValue}}}. Please note, if [#vegetation_type vegetation_type] = 0, all parameters must be set.
     351An overview of the different vegetation parameters can be found  [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     352}}}
     353|----------------
     354{{{#!td style="vertical-align:top;width: 150px"
     355[=#vegetation_type '''vegetation_type(y,x)''']
     356}}}
     357{{{#!td style="vertical-align:top;width: 50px"
     358NC_BYTE
     359}}}
     360{{{#!td style="vertical-align:top;width: 50px"
     361none
     362}}}
     363{{{#!td
     364Bulk classification of non-resolved vegetation surfaces at natural land surface types. At locations where '''vegetation_type''' is defined, [#soil_type soil_type] must not contain any {{{_FillValues}}}. '''vegetation_type''' overwrites the homogeneously prescribed setting via the namelist parameter [../../lsmpar#vegetation_type vegetation_type]. An overview of the different vegetation types can be found  [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     365}}}
     366|----------------
     367{{{#!td style="vertical-align:top;width: 150px"
     368[=#water_pars '''water_pars'''] //
     369'''(nalbedo_pars,y,x)'''
     370}}}
     371{{{#!td style="vertical-align:top;width: 50px"
     372NC_FLOAT
     373}}}
     374{{{#!td style="vertical-align:top;width: 50px"
     375none
     376}}}
     377{{{#!td
     378Parameters used for the parameterization of water surfaces.
     379When [#water_type water_type] = 0, all parameters must be set. Otherwise, single parameters for a given [#water_type water_type] can be overwritten, while the remaining parameters must be set to {{{_FillValue}}}.
     380}}}
     381|----------------
     382{{{#!td style="vertical-align:top;width: 150px"
     383[=#water_type '''water_type(y,x)''']
     384}}}
     385{{{#!td style="vertical-align:top;width: 50px"
     386NC_BYTE
     387}}}
     388{{{#!td style="vertical-align:top;width: 50px"
     389none
     390}}}
     391{{{#!td
     392Bulk classification of water bodies. '''water_type''' overwrites the homogeneously prescribed setting via the namelist parameter [../../lsmpar#water_type water_type]. An overview of the different water types can be found  [[attachment:PALM_input_data_standard_v1.9.pdf|here]].
     393}}}
     394
     395\\\\
     396
     397=== [=#plant '''Resolved plant canopy:] ===
     398
     399In order to consider resolved plant canopy, the [../../canpar plant-canopy model] need to be switched on and setting of [#canopy_mode canopy_mode] = 'read_from_file_3d' is required.
     400
     401||='''Input variable'''  =||='''Type'''  =||='''LOD''' =||='''Explanation / Remarks'''  =||
     402|----------------
     403{{{#!td style="vertical-align:top;width: 150px"
     404[=#lad '''lad'''] //
     405'''(zlad,y,x)'''
     406}}}
     407{{{#!td style="vertical-align:top;width: 50px"
     408NC_FLOAT
     409}}}
     410{{{#!td style="vertical-align:top;width: 50px"
     411none
     412}}}
     413{{{#!td
     414Vegetation resolved by the plant-canopy model in terms of a three­
     415dimensional leaf area density (LAD).
     416Please note, plant canopy is prescribed relative to the underlying topography and will be mounted on top of the terrain.
     417A preprocessor tool is available to convert arbitrary vegetation information to an LAD field. If '''lad''' is set, all settings of LAD-related parameters made in the namelist [../../canpar &plant_canopy_parameters] will be ignored.
     418Please note, unresolved vegetation is already treated via the land-surface model considered by [#vegetation_type vegetation_type]. Please check for possible double counting of similar vegetation in case [#vegetation_type vegetation_type] and '''lad''' is set at ''(y,x)''-location.
     419}}}
     420|----------------
     421{{{#!td style="vertical-align:top;width: 150px"
     422[=#bad '''bad'''] //
     423'''(zlad,y,x)'''
     424}}}
     425{{{#!td style="vertical-align:top;width: 50px"
     426NC_FLOAT
     427}}}
     428{{{#!td style="vertical-align:top;width: 50px"
     429none
     430}}}
     431{{{#!td
     432Basal area in m2 (i.e. trunk area) per grid volume. A preprocessor
     433tool is available to convert arbritrary vegetation information to an
     434basal area density field. The dimension of the field must be equal
     435to that of the leaf area density. Please note, basal area is prescribed relative to the underlying topography.
     436}}}
     437|----------------
     438{{{#!td style="vertical-align:top;width: 150px"
     439[=#root_area_dens_r '''root_area_dens_r''']//
     440'''(zsoil,y,x)'''
     441}}}
     442{{{#!td style="vertical-align:top;width: 50px"
     443NC_FLOAT
     444}}}
     445{{{#!td style="vertical-align:top;width: 50px"
     446none
     447}}}
     448{{{#!td
     449Root area of the resolved vegetation in the soil.
     450}}}
     451|----------------
     452{{{#!td style="vertical-align:top;width: 150px"
     453[=#root_area_dens_s '''root_area_dens_s''']//
     454'''(zsoil,y,x)'''
     455}}}
     456{{{#!td style="vertical-align:top;width: 50px"
     457NC_FLOAT
     458}}}
     459{{{#!td style="vertical-align:top;width: 50px"
     460none
     461}}}
     462{{{#!td
     463Root area of the parameterized vegetation in the soil that is set via
     464[#vegetation_type vegetation_type]. When [#vegetation_type vegetation_type] = 0, the '''root_area_density_s''' must be set.
     465}}}
     466\\\\\\