Changes between Version 3 and Version 4 of doc/app/iofiles/pids/vm
- Timestamp:
- Feb 11, 2020 6:16:36 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/app/iofiles/pids/vm
v3 v4 2 2 3 3 The virtual measurement input file comprises all information required to setup virtual sites within the model domain. Therefore, different global attributes as well as variables are mandatory. Please note, each attribute and variable name is in the format ''name<id>'', where id is an integer number running from 1 to [#num_vm number of stations]. 4 The following global attributes must be present in the virtual setup file. 4 5 5 6 ||='''Global attributes''' =||='''Type''' =||='''Explanation / Remarks''' =|| … … 56 57 |---------------- 57 58 {{{#!td style="vertical-align:top;width: 150px" 58 [=#filename '''filename<id>''']59 }}}60 {{{#!td style="vertical-align:top;width: 50px"61 NC_CHAR62 }}}63 {{{#!td64 Name of the file where the original observational data is stored.65 }}}66 |----------------67 {{{#!td style="vertical-align:top;width: 150px"68 59 [=#soilsample '''soil_sample<id>'''] 69 60 }}} … … 76 67 77 68 \\\\ 78 In the following, the required variables will be listed. Please note, NetCDF dimensions of the coordinate variables ''E_UTM'', ''N_UTM'', and ''height_above_origin'' depend on the [#featuretype type] of the measurement. For ''timeseries'', the observation is a stationary one, with only 1 value necessary for sufficient description of the coordinates. For ''timeSeriesProfile'' or ''trajectory'', however, the coordinate variables depend on the dimensions ''tray<id>'' and ''ntime<id>'', being the number of trajectories and the maximum number of timesteps measured for a trajectory, according to the '''[UC]2 data standard'''.69 In the following, the required dimensions/variables will be listed. Please note, NetCDF dimensions of the coordinate variables ''E_UTM'', ''N_UTM'', and ''height_above_origin'' depend on the [#featuretype type] of the measurement. For ''timeseries'', the observation is a stationary one with a fixed number of locations. The number of fixed coordinates (e.g. several sensors at a mast) is stored in the dimension station<id>. For ''timeSeriesProfile'' or ''trajectory'', however, the coordinate variables depend on the dimensions ''tray<id>'' and ''ntime<id>'', being the number of trajectories and the maximum number of timesteps measured for a trajectory, according to the '''[UC]2 data standard'''. 79 70 80 71 ||='''Variables''' =||='''Type''' =||='''Explanation / Remarks''' =|| 81 72 |---------------- 82 73 {{{#!td style="vertical-align:top;width: 150px" 83 [=#eutm '''E_UTM<id>''' ( 1) or (tray<id>,ntime<id>)]74 [=#eutm '''E_UTM<id>''' (station<id>) or (tray<id>,ntime<id>)] 84 75 }}} 85 76 {{{#!td style="vertical-align:top;width: 50px" … … 91 82 |---------------- 92 83 {{{#!td style="vertical-align:top;width: 150px" 93 [=#nutm '''N_UTM<id>''' ( 1) or (tray<id>,ntime<id>)]84 [=#nutm '''N_UTM<id>''' (station<id>) or (tray<id>,ntime<id>)] 94 85 }}} 95 86 {{{#!td style="vertical-align:top;width: 50px" … … 101 92 |---------------- 102 93 {{{#!td style="vertical-align:top;width: 150px" 103 [=#zag ''' height_above_origin<id>''' (1) or (tray<id>,ntime<id>)]94 [=#zag '''z<id>''' (station<id>) or (tray<id>,ntime<id>)] 104 95 }}} 105 96 {{{#!td style="vertical-align:top;width: 50px" … … 107 98 }}} 108 99 {{{#!td 109 Height above the surface. 100 Sensor height above sea level. The relative measurement height calculates from {{{z-station_h}}}. 101 }}} 102 |---------------- 103 {{{#!td style="vertical-align:top;width: 150px" 104 [=#station_h '''station_h<id>''' (station<id>) or (tray<id>,ntime<id>)] 105 }}} 106 {{{#!td style="vertical-align:top;width: 50px" 107 NC_FLOAT 108 }}} 109 {{{#!td 110 Surface altitude with respect to sea level. 110 111 }}} 111 112 |----------------