Changes between Version 4 and Version 5 of doc/app/iofiles/pids/vm


Ignore:
Timestamp:
Feb 11, 2020 6:18:53 PM (5 years ago)
Author:
suehring
Comment:

--

Legend:

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

    v4 v5  
    6767
    6868\\\\
    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'''.
     69In the following, the required dimensions/variables will be listed. Please note, NetCDF dimensions of the coordinate variables ''E_UTM'', ''N_UTM'', ''z'', and ''station_h'' 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, i.e. for each site there can be several stations) 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'''.
    7070
    7171||='''Variables'''  =||='''Type''' =||='''Explanation / Remarks'''  =||