DATACONVERT.DAT: Difference between revisions

Revision as of 15:05, 15 February 2011

Basic Information

File-Type

dataconvert.dat

File-Form

FORMATTED

Version

8.x / February 2011

Description-Date

February 2011

Significance of the File

Contains various input steering data for the postprocessor DATACONVERT

File-Contents (in Catchwords)

Contains various input steering data, which are required during

mode 1 , conversion of computational results for the integrated modelling system Delft3D. Original data are stored in NetCDF data files and are going to be converted and written to BAW-specific BDF data files, or,
mode 2 , conversion of (DWD) NetCDF files to BAW-specific BDF data files, or,
mode 3 , merge of several (DWD) NetCDF files to a single NetCDF data file (times for input data must be identical in all input files), or
neu: mode 6: conversion of meteorological data in BDF-Format into Delft3D format METEO_DLFT

informations related to output files (block Output_Information)

mode 1
- file to store converted depth averaged (2D-) computational results (filetype dirz.bin.r, dirz.bin.i and dirz.bin).
  Notice: data for multiple computational domains are going to be gathered and stored in this file.
- file to store the converted computational grid (filetype untrim_grid.dat).
  Notice: computational grid data for multiple computational domains are going to be gathered and stored in this grid file.
- (optional) file to store converted depth dependent (3D-) computational results (filetype dirz.bin.r, dirz.bin.i and dirz.bin).
  Notice: data for multiple computational domains are going to be gathered and stored in this file.
- (optional) file with description of the vertical layer structure (z-layers), to be used for the converted computational results (filetype vertical.dat).
  Notice: this file must be always specified in situations when three-dimensional data are going to be generated by conversion.
- (optional) threshold depth for drying and wetting.
  Notice: the value prescribed shall be not smaller than the one used during the Delft3D simulation.
- (optional) start time for data conversion.
  Notice: if not specified the first date contained in the input data will be used.
- (optional) end time for data conversion.
  Notice: if not specified the last date contained in the input data will be used.
- (optional) time step for data conversion.
  Notice: if not specified all dates contained in the input data will be converted.
- (optional) maximum increase of depth during a morphodynamic simulation. Depth at all grid points is increased by this amount to cover depth variation due to morphodynamics within a z-layered (vertical) grid. Exception: depths at (protected) structures will not be altered.
  Notice: if this parameter is not prescribed all depth values will remain unchanged.
- (optional) steering parameter for the method chosen to compute initial depth values at grid points. Depths can be computed from values prescribed in grid files or in computational result files.
  Notice: if this parameter is not prescribed, depth values are derived from grid data only.
- (optional) steering parameter for type of method used to compute depth values for new edges inserted during the grid refinement process. Method can be either MEAN, MAX or MIN.
  Notice: if this parameter is missing, method MEAN will be used.
- (optional) steering parameter for rounding of time and date information (digits for nanoseconds). The number of digits for nanoseconds (0 - 9) has to be prescribed. In case 0 (zero) is prescribed, no digits for nanoseconds are taken into account and all internal time and date items are rounded to seconds.
  Notice: if this parameter is not specified, no time and date item will be subject to rounding (full accuracy).
mode 2
- file to store converted data (filetype dirz.bin.r, dirz.bin.i and dirz.bin).
  Notice: file is not generated, only the filetype is used.
- file to store the converted computational grid (filetype gitter05.dat or gitter05.bin).
  Notice: file is not generated, only filetype is used.
- (optional) start time for data conversion.
  Notice: if not specified the first date contained in the input data will be used.
- (optional) end time for data conversion.
  Notice: if not specified the last date contained in the input data will be used.
- (optional) time step for data conversion.
  Notice: if not specified all dates contained in the input data will be converted.
- (optional) steering parameter for rounding of time and date information (digits for nanoseconds). The number of digits for nanoseconds (0 - 9) has to be prescribed. In case 0 (zero) is prescribed, no digits for nanoseconds are taken into account and all internal time and date items are rounded to seconds.
  Notice: if this parameter is not specified, no time and date item will be subject to rounding (full accuracy).
- EPSG code for coordinates of resulting grid file (see EPSG Geodetic Parameter Registry).
mode 3
- file to store merged data (filetype netcdf.cdf).
- (optional) start time for data conversion.
  Notice: if not specified the first date contained in the input data will be used.
- (optional) end time for data conversion.
  Notice: if not specified the last date contained in the input data will be used.
- (optional) time step for data conversion.
  Notice: if not specified all dates contained in the input data will be converted.
- (optional) steering parameter for rounding of time and date information (digits for nanoseconds). The number of digits for nanoseconds (0 - 9) has to be prescribed. In case 0 (zero) is prescribed, no digits for nanoseconds are taken into account and all internal time and date items are rounded to seconds.
  Notice: if this parameter is not specified, no time and date item will be subject to rounding (full accuracy).
mode 6
- file to store converted data (filetype METEO_DLFT
- (optional) start time for data conversion.
  Notice: if not specified the first date contained in the input data will be used.
- (optional) end time for data conversion.
  Notice: if not specified the last date contained in the input data will be used.
- (optional) time step for data conversion.
  Notice: if not specified all dates contained in the input data will be converted.
- (optional) EPSG code for coordinates of resulting grid file (see EPSG Geodetic Parameter Registry).
  Notice: There will be be no mapping, but the code will be written as a comment into the METEO_DELFT file.
- (optional) No_Data_Value for invalid data.
- (optional) Timezone for the time string of the output file (Default: UTC)

informations related to input files (block Input_Files) - block can be specified several times

mode 1
- name of NetCDF-file which contains the computational results from Delft3D going to be converted (filetype netcdf.cdf);
  Notice: has to be specified only once per computational domain), plus (optional) code numbers for the converted physical quantities (Notice: in case code numbers are not specified, all quantities which are feasible for conversion are going to be converted automatically).
- name of file which contains the computational grid going to be converted (filetype delft3d.grd).
- Additionally the following files of type delft3d.dep and delft3d.enc must be present in the working directory.
- Optionally files of type delft3d.dry, delft3d.thd, delft3d.lwl, delft3d.ext as well as delft3d.bnd may be present in the working directory.
  Remark 1: Only one file with extension grd per computational domain can be specified. The other (related) files are only allowed to differ with respect to their extension.
  
  Remark 2: For each computational domain the converted computational grid as well as the converted computational results are stored in files of type untrim_grid.dat, dirz.bin.r, dirz.bin.i and dirz.bin.
mode 2
- name of NetCDF-file with data to be converted (filetype netcdf.cdf);
  Remark 1: For each input file a grid file of type gitter05.dat or gitter05.bin as well as data files of type dirz.bin.r, dirz.bin.i and dirz.bin will be generated.
- EPSG code for coordinates in input data file (see EPSG Geodetic Parameter Registry).
mode 3
- file name with type netcdf.cdf, contents will be merged into the output file.
mode 6
- data files of type dirz.bin.r, dirz.bin.i and dirz.bin
- alle grid formats connectable with BDF files, e.g. GITTER05

dictionary-file hyd_untrim_dico.dat, normally present in directory $PROGHOME/dic/, will be automatically read by the application program in addition to the user-specified input file.

Programs using this Type of File

DATACONVERT

Example-File

please refer to $PROGHOME/examples/dataconvert/

back to: File Descriptions

Overview

@@ Line 2: / Line 2: @@
 |name_de=DATACONVERT.DAT
 |filetype=dataconvert.dat
-|version=7.x / August 2010
+|version=8.x / February 2011
-|version_descr=August 2010
+|version_descr=February 2011
 |significance=Contains various input steering data for the postprocessor DATACONVERT
 |filecontents=
@@ Line 9: / Line 9: @@
 * '''mode 1''' , conversion of computational results for the integrated modelling system [[Mathematical Model DELFT3D|Delft3D]]. Original data are stored in NetCDF data files and are going to be converted and written to BAW-specific BDF data files, or,
 * '''mode 2''' , conversion of (DWD) NetCDF files to BAW-specific BDF data files, or,
-* '''mode 3''' , merge of several (DWD) NetCDF files to a single NetCDF data file (times for input data must be identical in all input files).
+* '''mode 3''' , merge of several (DWD) NetCDF files to a single NetCDF data file (times for input data must be identical in all input files), or
+* '''<font color=Green>neu: mode 6</font>''': conversion of meteorological data in BDF-Format into Delft3D format METEO_DLFT<br />
 '''informations related to output files''' (block '''Output_Information''')
@@ Line 61: / Line 62: @@
 ** (optional) steering parameter for rounding of time and date information (digits for nanoseconds). The number of digits for nanoseconds (0 - 9) has to be prescribed. In case 0 (zero) is prescribed, no digits for nanoseconds are taken into account and all internal time and date items are rounded to seconds.
 **: Notice: if this parameter is not specified, no time and date item will be subject to rounding (full accuracy).
+* '''mode 6'''
+** file to store converted data (filetype [[METEO_DLFT]]
+** (optional) start time for data conversion.
+**: Notice: if not specified the first date contained in the input data will be used.
+** (optional) end time for data conversion.
+**: Notice: if not specified the last date contained in the input data will be used.
+** (optional) time step for data conversion.
+**: Notice: if not specified all dates contained in the input data will be converted.
+** (optional) EPSG code for coordinates of resulting grid file (see [http://www.epsg-registry.org/ EPSG Geodetic Parameter Registry]).
+**: Notice: There will be be no mapping, but the code will be written as a comment into the METEO_DELFT file.
+** (optional) No_Data_Value for invalid data.
+** (optional) Timezone for the time string of the output file (Default: UTC)
 '''informations related to input files''' (block '''Input_Files''') - block can be specified several times
@@ Line 77: / Line 90: @@
 * '''mode 3'''
 ** file name with type [[NETCDF.CDF|netcdf.cdf]], contents will be merged into the output file.
+* '''mode 6'''
+** data files of type [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]]
+** alle grid formats connectable with BDF files, e.g. [[GITTER05.DAT_and_GITTER05.BIN|GITTER05]]
 dictionary-file '''hyd_untrim_dico.dat''', normally present in directory '''$PROGHOME/dic/''', will be automatically read by the application program in addition to the user-specified input file.