BAWiki - User contributions [en]

FILELIST TO GEOM

2025-09-02T11:38:23Z

Ak3gseis: Version geändert

{{ProgramDescription
|name_de=FILELIST_TO_GEOM
|name=FILELIST_TO_GEOM
|version=December 2024
|version_descr=May 2022
|catchwords=
preprozessor 
collect geopositions 
visualize coordinates 
GPX format 
|shortdescription=
The program FILELIST_TO_GEOM exports the coordinates of many single files into one file to make them readable by visualisation programs.
|inputfiles=
# list of files [[DATEILISTE.DAT|dateiliste.dat]] (created with "ls -1", eventually manipulated with a textfile editor ).
# The files listed of type [[GEOPOS.DAT|geopos.dat]] or
# The files listed of type [[BOEWRT.DAT|boewrt.dat]])
|outputfiles=
# file of type [[GEOM.DAT|geom.dat]] : contains the positions of the files listed as a table (x,y,z) or
# file of type [[INSEL.DAT|insel.dat]] : contains the positions of the files listed as GTEXT objekt
# Datei imi GUQRLP-Kommentaren zur Verwendung in GVIEW2D-Log-Dateien zur präzisen Auswahl von bestimmten Geopositionen, die sehr dicht zusammen liegen oder
# CSV file with coordinates and further und weiteren attributes useful for generating ESRI shapes with GISMO.
# [https://en.wikipedia.org/wiki/GPS_Exchange_Format GPX file] with waypoints. Only the information "depth", "name of station" and "source file" are saved.
|methodology=
The file list will be worked on sequentially. The coordinate of the Location will be extracted for each file, eventually transformed into the coordinate reference System which is given by BAWCRS and exported into the output file. '''If BAWCRS is undefined''', the standard coordinate reference system for the German Northsea coast, '''UTM/ETRS89, Zone 32''' (EPSG-Code 25832) '''is implicitely assumed to be wished by the user'''.

|preprocessor=
LINUX command "ls -1", textfile editor, [[FRQWF]], [[FRQ2ZEITR]], [[ZEITRIO]]
|postprocessor=
DAVIT, [[FDGITTER05]], GISMO, [[HVIEW2D]], [[JANET]]
|language=Fortran2003
|add_software= libgeodesy
|contact_original=G. Seiß
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation= self explainig program. Examples are in $PROGHOME/examples/filelist_to_geom.
}}

ZEITRIO

2025-03-19T16:03:14Z

Ak3gseis:

{{ProgramDescription
|name_de=ZEITRIO
|name=ZEITRIO
|version=March 2025
|version_descr=March 2025
|catchwords=preprocessor 
time series 
concatenation
|shortdescription=The program ZEITRIO reads and writes data files, that contain time series in different formats. It is possible to read the file-types listed below. They can be wrote as boewrt.dat, as ASCII columns or CSV format afterwards. Concatenation of multible files is supported. A BOEWRT status flag is eventually be generated or transported.
|inputfiles=
# data file(s) with time series of type [[BOEWRT.DAT|boewrt.dat]]. A list of several files can be concatenated by the command line argument ''-srclist=<file>''.
# data file(s) with time series of type [[SOLWRT.DAT|solwrt.dat]].
# data file(s) with time series of type 6dph.dat.
# data file(s) with time series of type trbnk.dat.
# data file(s) with time series of type aander.dat.
# data file(s) with time series of type dwdwin.dat.
# data file(s) with time series of type WSA Bremen.
# data file(s) with time series of type peg.dat.
# data file(s) with time series of type pegel.his.
# data file(s) with time series of type extab.dat (Excel table with separators Blanks, Tabs, comma, semicolon).
# data file(s) with time series of type WSA Emden.
# data file(s) with time series of type column oriented MATLAB matrix.
# data file(s) with time series of type ZRX.
# data file(s) with time series of type WOCE gauge data.
# data file(s) with time series of type [[KNOERG.BIN|knoerg.bin]].
# data file(s) with time series of type CSV of the BfG "Pegel-Online" Service.
# data file(s) with time series of type CSV provided by ftp://ftp-cdc.dwd.de/pub/CDC/
# data file(s) with time series of type ALL (Kisters export of WISKI database)
# netCDF files with timeseries from http://www.marineinsitu.eu/dashboard/
# generic CSV file interface allowing free choice of columns .
# optional input data of type [[ZEITRIO.DAT|zeitrio.dat]]. This file defines time intervals in case that the output ([[BOEWRT.DAT|boewrt.dat]] only) should be devided into several seperate files of a certain length.
|outputfiles=
The number of output file types was limited to really useful standard formats.
# data file with time series of type [[BOEWRT.DAT|boewrt.dat]] (output modes 1 and 2)..
# data file with time series as ASCII-columns and a separate header file (a format which can be used with MATLAB, SCILAB or Mathematica)
# data file with time series of type CSV with an one line header of type (Zeitpunkt; property 1; property 2; ....) for [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS] (output mode 4).
# printer protocol file (zeitrio.sdr).
# (optional) terminal input protocol of type gkslog.dat.
|methodology=After defining a reference date, which is important when reading or writing a file with relative time information (e.g. solwrt.dat) a time series file is read. Please note, that only one time series at one knot can be read and processed at the same time. Optionally further time series files can be concatenated then. The file type can be switched for each file to read. After reading process has finished, the time series will be ordered chronologically and double as well as unvalid times are rejected.

The time series are wrote to a file using the format defined by the user. If writing [[BOEWRT.DAT|boewrt.dat]] there is the additional option to write defined time intervals (e.g. days) into separate files. The date of the day is part of the file name. Measured values additionally get the BOEWRT status flag 2 ("untested") where the flag data are not read from the input file. Calculated values ("knoerg.bin") get the status "good" (1).

Optionally the time series will be interpolated to equidistant time steps. Larger time gaps can optionally filled with a dummy value (fill value, output mode 1) or eliminated (output mode 2) on output. The user defines a minmal value for time gaps to be recognized large. The printer protocol file provides information about significant gaps in time axis. Interpolation of smaller gaps is be done alternatively by spline or linear interpolation. The BOEWRT status flag indicates whether the values are interpolated. Those values get the flags "untested", "interpolated" and eventually "good" or "suspicious".

The output time period is determined by the interactive user input. If several input files are read during one cycle, the first start time and last end time determine the output period. If output mode 1 is chosen, eventually fill values are added during equidistant interpolation before the first valid measurement time and after the last valid measurement time. Unlike Versions before February 2020, the program doesent stop with an error, if the time period, specified by the user is not completely covered.
Check output files and standard output for warnings!

'''Attention:''' Versions before February 2020 were not able to correctly deal with fill values during interpolation of more than one physical quantity at once. Now this functionality is implemented. But still check your results! BOEWRT timeseries for input can start with empty data records ("fill_values") since version 2020_10_15 to be processed anyway.

Time series of type MATLAB matrix, ZRX or "exctab.dat" can be filtered and recalculated with an offset and scaling for the data values. Absolute date and time will always be calculated by special operators with high accuracy.

During reading and interpolation, eventually a BOEWRT status flag is created. Check correctness of those flags befor further processing the files.

Since Version June 2020 interpolation of BOEWRT status flags takes the neighbouring flag values into account. If both neighbours are "good", the interpolated value becomes "good" too. If one of them is "suspicious", the interpolated flag becomes "suspicious". Interpolated values are always "untested"!

The number of interactiv dialogs can be reduced by giving command line arguments. This feature is available since version 2020_10_15. The command '''''zeitrio[.i21] -h''''' helps in using this feature.

Files of type BOEWRT.DAT are allowed to contain datetime stamps in so called "Gesetzlicher Zeit" from March 2025 onward. Then, this fact is indicated with timezone "GZ" in the file header. At the autumn day of timezone switch datetime stamps between 2:00 AM und 3:00 AM DST must have the specific timezone (e.g. "CEST").

An executable is available for LINUX as well as WINDOWS platforms.

|preprocessor=spreadsheet software (e.g. [https://en.wikipedia.org/wiki/Microsoft_Excel MS Office EXCEL], [https://en.wikipedia.org/wiki/LibreOffice_Calc LibreOffice Calc] ),[[FFT]], [[FRQ2ZEITR]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [http://www.scilab.org/ SCILAB], [[TSCALC]], [[TRIM-2D]], [[TRIM-3D]], [[XTRDATA]]
|postprocessor=[[BOERND]], [[DATACONVERT]], [[EXCELENZ]], [[FFT]], [[FRQWF]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [[ROSE]], [http://www.scilab.org/ SCILAB], [[TIDKEN]], [[TSCALC]], [[UTRRND]], [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS]
|language=Fortran2003
|add_software= libgeodesy, NTv2 mesh files for coordinate transformation (see also [[GEOTRANSFORMER]]).
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/zeitrio
}}

ZEITRIO

2025-03-19T16:01:57Z

Ak3gseis:

{{ProgramDescription
|name_de=ZEITRIO
|name=ZEITRIO
|version=March 2025
|version_descr=March 2025
|catchwords=preprocessor 
time series 
concatenation
|shortdescription=The program ZEITRIO reads and writes data files, that contain time series in different formats. It is possible to read the file-types listed below. They can be wrote as boewrt.dat, as ASCII columns or CSV format afterwards. Concatenation of multible files is supported. A BOEWRT status flag is eventually be generated or transported.
|inputfiles=
# data file(s) with time series of type [[BOEWRT.DAT|boewrt.dat]]. A list of several files can be concatenated by the command line argument ''-srclist=<file>''.
# data file(s) with time series of type [[SOLWRT.DAT|solwrt.dat]].
# data file(s) with time series of type 6dph.dat.
# data file(s) with time series of type trbnk.dat.
# data file(s) with time series of type aander.dat.
# data file(s) with time series of type dwdwin.dat.
# data file(s) with time series of type WSA Bremen.
# data file(s) with time series of type peg.dat.
# data file(s) with time series of type pegel.his.
# data file(s) with time series of type extab.dat (Excel table with separators Blanks, Tabs, comma, semicolon).
# data file(s) with time series of type WSA Emden.
# data file(s) with time series of type column oriented MATLAB matrix.
# data file(s) with time series of type ZRX.
# data file(s) with time series of type WOCE gauge data.
# data file(s) with time series of type [[KNOERG.BIN|knoerg.bin]].
# data file(s) with time series of type CSV of the BfG "Pegel-Online" Service.
# data file(s) with time series of type CSV provided by ftp://ftp-cdc.dwd.de/pub/CDC/
# data file(s) with time series of type ALL (Kisters export of WISKI database)
# netCDF files with timeseries from http://www.marineinsitu.eu/dashboard/
# generic CSV file interface allowing free choice of columns .
# optional input data of type [[ZEITRIO.DAT|zeitrio.dat]]. This file defines time intervals in case that the output ([[BOEWRT.DAT|boewrt.dat]] only) should be devided into several seperate files of a certain length.
|outputfiles=
The number of output file types was limited to really useful standard formats.
# data file with time series of type [[BOEWRT.DAT|boewrt.dat]] (output modes 1 and 2)..
# data file with time series as ASCII-columns and a separate header file (a format which can be used with MATLAB, SCILAB or Mathematica)
# data file with time series of type CSV with an one line header of type (Zeitpunkt; property 1; property 2; ....) for [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS] (output mode 4).
# printer protocol file (zeitrio.sdr).
# (optional) terminal input protocol of type gkslog.dat.
|methodology=After defining a reference date, which is important when reading or writing a file with relative time information (e.g. solwrt.dat) a time series file is read. Please note, that only one time series at one knot can be read and processed at the same time. Optionally further time series files can be concatenated then. The file type can be switched for each file to read. After reading process has finished, the time series will be ordered chronologically and double as well as unvalid times are rejected.

The time series are wrote to a file using the format defined by the user. If writing [[BOEWRT.DAT|boewrt.dat]] there is the additional option to write defined time intervals (e.g. days) into separate files. The date of the day is part of the file name. Measured values additionally get the BOEWRT status flag 2 ("untested") where the flag data are not read from the input file. Calculated values ("knoerg.bin") get the status "good" (1).

Optionally the time series will be interpolated to equidistant time steps. Larger time gaps can optionally filled with a dummy value (fill value, output mode 1) or eliminated (output mode 2) on output. The user defines a minmal value for time gaps to be recognized large. The printer protocol file provides information about significant gaps in time axis. Interpolation of smaller gaps is be done alternatively by spline or linear interpolation. The BOEWRT status flag indicates whether the values are interpolated. Those values get the flags "untested", "interpolated" and eventually "good" or "suspicious".

The output time period is determined by the interactive user input. If several input files are read during one cycle, the first start time and last end time determine the output period. If output mode 1 is chosen, eventually fill values are added during equidistant interpolation before the first valid measurement time and after the last valid measurement time. Unlike Versions before February 2020, the program doesent stop with an error, if the time period, specified by the user is not completely covered.
Check output files and standard output for warnings!

'''Attention:''' Versions before February 2020 were not able to correctly deal with fill values during interpolation of more than one physical quantity at once. Now this functionality is implemented. But still check your results! BOEWRT timeseries for input can start with empty data records ("fill_values") since version 2020_10_15 to be processed anyway.

Time series of type MATLAB matrix, ZRX or "exctab.dat" can be filtered and recalculated with an offset and scaling for the data values. Absolute date and time will always be calculated by special operators with high accuracy.

During reading and interpolation, eventually a BOEWRT status flag is created. Check correctness of those flags befor further processing the files.

Since Version June 2020 interpolation of BOEWRT status flags takes the neighbouring flag values into account. If both neighbours are "good", the interpolated value becomes "good" too. If one of them is "suspicious", the interpolated flag becomes "suspicious". Interpolated values are always "untested"!

The number of interactiv dialogs can be reduced by giving command line arguments. This feature is available since version 2020_10_15. The command '''''zeitrio[.i18] -h''''' helps in using this feature.

Files of type BOEWRT.DAT are allowed to contain datetime stamps in so called "Gesetzlicher Zeit" from March 2025 onward. Then, this fact is indicated with timezone "GZ" in the file header. At the autumn day of timezone switch datetime stamps between 2:00 AM und 3:00 AM DST must have the specific timezone (e.g. "CEST").

An executable is available for LINUX as well as WINDOWS platforms.

|preprocessor=spreadsheet software (e.g. [https://en.wikipedia.org/wiki/Microsoft_Excel MS Office EXCEL], [https://en.wikipedia.org/wiki/LibreOffice_Calc LibreOffice Calc] ),[[FFT]], [[FRQ2ZEITR]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [http://www.scilab.org/ SCILAB], [[TSCALC]], [[TRIM-2D]], [[TRIM-3D]], [[XTRDATA]]
|postprocessor=[[BOERND]], [[DATACONVERT]], [[EXCELENZ]], [[FFT]], [[FRQWF]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [[ROSE]], [http://www.scilab.org/ SCILAB], [[TIDKEN]], [[TSCALC]], [[UTRRND]], [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS]
|language=Fortran2003
|add_software= libgeodesy, NTv2 mesh files for coordinate transformation (see also [[GEOTRANSFORMER]]).
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/zeitrio
}}

ZEITRIO

2025-03-19T16:01:17Z

Ak3gseis:

{{ProgramDescription
|name_de=ZEITRIO
|name=ZEITRIO
|version=April 2021
|version_descr=April 2021
|catchwords=preprocessor 
time series 
concatenation
|shortdescription=The program ZEITRIO reads and writes data files, that contain time series in different formats. It is possible to read the file-types listed below. They can be wrote as boewrt.dat, as ASCII columns or CSV format afterwards. Concatenation of multible files is supported. A BOEWRT status flag is eventually be generated or transported.
|inputfiles=
# data file(s) with time series of type [[BOEWRT.DAT|boewrt.dat]]. A list of several files can be concatenated by the command line argument ''-srclist=<file>''.
# data file(s) with time series of type [[SOLWRT.DAT|solwrt.dat]].
# data file(s) with time series of type 6dph.dat.
# data file(s) with time series of type trbnk.dat.
# data file(s) with time series of type aander.dat.
# data file(s) with time series of type dwdwin.dat.
# data file(s) with time series of type WSA Bremen.
# data file(s) with time series of type peg.dat.
# data file(s) with time series of type pegel.his.
# data file(s) with time series of type extab.dat (Excel table with separators Blanks, Tabs, comma, semicolon).
# data file(s) with time series of type WSA Emden.
# data file(s) with time series of type column oriented MATLAB matrix.
# data file(s) with time series of type ZRX.
# data file(s) with time series of type WOCE gauge data.
# data file(s) with time series of type [[KNOERG.BIN|knoerg.bin]].
# data file(s) with time series of type CSV of the BfG "Pegel-Online" Service.
# data file(s) with time series of type CSV provided by ftp://ftp-cdc.dwd.de/pub/CDC/
# data file(s) with time series of type ALL (Kisters export of WISKI database)
# netCDF files with timeseries from http://www.marineinsitu.eu/dashboard/
# generic CSV file interface allowing free choice of columns .
# optional input data of type [[ZEITRIO.DAT|zeitrio.dat]]. This file defines time intervals in case that the output ([[BOEWRT.DAT|boewrt.dat]] only) should be devided into several seperate files of a certain length.
|outputfiles=
The number of output file types was limited to really useful standard formats.
# data file with time series of type [[BOEWRT.DAT|boewrt.dat]] (output modes 1 and 2)..
# data file with time series as ASCII-columns and a separate header file (a format which can be used with MATLAB, SCILAB or Mathematica)
# data file with time series of type CSV with an one line header of type (Zeitpunkt; property 1; property 2; ....) for [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS] (output mode 4).
# printer protocol file (zeitrio.sdr).
# (optional) terminal input protocol of type gkslog.dat.
|methodology=After defining a reference date, which is important when reading or writing a file with relative time information (e.g. solwrt.dat) a time series file is read. Please note, that only one time series at one knot can be read and processed at the same time. Optionally further time series files can be concatenated then. The file type can be switched for each file to read. After reading process has finished, the time series will be ordered chronologically and double as well as unvalid times are rejected.

The time series are wrote to a file using the format defined by the user. If writing [[BOEWRT.DAT|boewrt.dat]] there is the additional option to write defined time intervals (e.g. days) into separate files. The date of the day is part of the file name. Measured values additionally get the BOEWRT status flag 2 ("untested") where the flag data are not read from the input file. Calculated values ("knoerg.bin") get the status "good" (1).

Optionally the time series will be interpolated to equidistant time steps. Larger time gaps can optionally filled with a dummy value (fill value, output mode 1) or eliminated (output mode 2) on output. The user defines a minmal value for time gaps to be recognized large. The printer protocol file provides information about significant gaps in time axis. Interpolation of smaller gaps is be done alternatively by spline or linear interpolation. The BOEWRT status flag indicates whether the values are interpolated. Those values get the flags "untested", "interpolated" and eventually "good" or "suspicious".

The output time period is determined by the interactive user input. If several input files are read during one cycle, the first start time and last end time determine the output period. If output mode 1 is chosen, eventually fill values are added during equidistant interpolation before the first valid measurement time and after the last valid measurement time. Unlike Versions before February 2020, the program doesent stop with an error, if the time period, specified by the user is not completely covered.
Check output files and standard output for warnings!

'''Attention:''' Versions before February 2020 were not able to correctly deal with fill values during interpolation of more than one physical quantity at once. Now this functionality is implemented. But still check your results! BOEWRT timeseries for input can start with empty data records ("fill_values") since version 2020_10_15 to be processed anyway.

Time series of type MATLAB matrix, ZRX or "exctab.dat" can be filtered and recalculated with an offset and scaling for the data values. Absolute date and time will always be calculated by special operators with high accuracy.

During reading and interpolation, eventually a BOEWRT status flag is created. Check correctness of those flags befor further processing the files.

Since Version June 2020 interpolation of BOEWRT status flags takes the neighbouring flag values into account. If both neighbours are "good", the interpolated value becomes "good" too. If one of them is "suspicious", the interpolated flag becomes "suspicious". Interpolated values are always "untested"!

The number of interactiv dialogs can be reduced by giving command line arguments. This feature is available since version 2020_10_15. The command '''''zeitrio[.i18] -h''''' helps in using this feature.

Files of type BOEWRT.DAT are allowed to contain datetime stamps in so called "Gesetzlicher Zeit" from March 2025 onward. Then, this fact is indicated with timezone "GZ" in the file header. At the autumn day of timezone switch datetime stamps between 2:00 AM und 3:00 AM DST must have the specific timezone (e.g. "CEST").

An executable is available for LINUX as well as WINDOWS platforms.

|preprocessor=spreadsheet software (e.g. [https://en.wikipedia.org/wiki/Microsoft_Excel MS Office EXCEL], [https://en.wikipedia.org/wiki/LibreOffice_Calc LibreOffice Calc] ),[[FFT]], [[FRQ2ZEITR]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [http://www.scilab.org/ SCILAB], [[TSCALC]], [[TRIM-2D]], [[TRIM-3D]], [[XTRDATA]]
|postprocessor=[[BOERND]], [[DATACONVERT]], [[EXCELENZ]], [[FFT]], [[FRQWF]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [[ROSE]], [http://www.scilab.org/ SCILAB], [[TIDKEN]], [[TSCALC]], [[UTRRND]], [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS]
|language=Fortran2003
|add_software= libgeodesy, NTv2 mesh files for coordinate transformation (see also [[GEOTRANSFORMER]]).
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/zeitrio
}}

GRIDCONVERT

2024-05-29T11:48:23Z

Ak3gseis:

{{ProgramDescription
|name_de=GRIDCONVERT
|name=GRIDCONVERT
|version=April 2019
|version_descr=September 2022
|catchwords=
conversion of computational grids 
read and write computational grids in different file formats 

Acknowledgment: ''This project took advantage of netCDF software developed by UCAR/Unidata ([http://www.unidata.ucar.edu/software/netcdf/ www.unidata.ucar.edu/software/netcdf/]).''

|shortdescription=
The program GRIDCONVERT can be used to convert computational grids for different mathematical methods:

* between different file formats but identical structure of the computational grid,
* between different grid types and different file formats,
* refinement (factor 4) of an UNTRIM grid, as well as
* flattening of all sub grid scale bathymetry variations within all grid cells and along all edges and
* conversion of constructions in insel.dat files.

In addition to that also the following functionality is available:
* compute some statistical data for a grid,
* find some differences between two grids, and
* compare initial bathymetry used with [[UNTRIM]] between cases one-grid simulation versus two-grid simulation.

Due to some specific properties of computational grids for mathematical methods the number of possible conversions remains naturally very limited. The grid will not be optimized automatically with respect to the specific requirements of the different mathematical models.

The program is '''also available for WINDOWS platform'''.

|inputfiles=
# '''computational grid (input formats)'''
:: The following file formats are currently supported:
::* [[DELFT3D.GRD|delft3d.grd]], [[DELFT3D.DEP|delft3d.dep]], [[DELFT3D.ENC|delft3d.enc]], [[DELFT3D.DRY|delft3d.dry]],
::* [[DELFT3D.THD|delft3d.thd]], [[DELFT3D.LWL|delft3d.lwl]], [[DELFT3D.EXT|delft3d.ext]] as well as [[DELFT3D.BND|delft3d.bnd]],
::* [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]],
::* [[SELAFIN|selafin]],
::* [[UNTRIM_GRID.DAT|untrim_grid.dat]],
::* [[UTRSUB_GRID.DAT|utrsub_grid.dat]],
::* [[PLTSUB_GRID.UPI|pltsub_grid.upi]],
::* [[LOCATION_GRID.DAT|location_grid.dat]],
::* [[PROFIL05.BIN|profil05.bin]] and
::* [[INSEL.DAT|insel.dat]] (which does not contain a computational grid but structures as groynes or islands).
# '''(optional) global metadata'''
::* [[NC_META.DAT|nc_meta.dat]].
In case file ''nc_meta.dat'' is present in the current working directory, this file will be read by the application. Otherwise the respective file from $PROGHOME/cfg will be read.
|outputfiles=
# '''computational grid (output formats)'''
:: The following file formats are currently supported:
::* [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]],
::* [[UNTRIM_GRID.DAT|untrim_grid.dat]],
::* [[UTRSUB_GRID.DAT|utrsub_grid.dat]],
::* [[PLTSUB_GRID.UPI|pltsub_grid.upi]],
::* [[INSEL.DAT|insel.dat]] and
::* [[CF-NETCDF.NC|cf-netcdf.nc]] (actual only [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]], [[INSEL.DAT|insel.dat]], [[UNTRIM_GRID.DAT|untrim_grid.dat]], [[UTRSUB_GRID.DAT|utrsub_grid.dat]], [[PLTSUB_GRID.UPI|pltsub_grid.upi]], [[LOCATION_GRID.DAT|location_grid.dat]] and [[PROFIL05.BIN|profil05.bin]]).

Remark: In case the files [[UTRSUB_GRID.DAT|utrsub_grid.dat]] and [[PLTSUB_GRID.UPI|pltsub_grid.upi]] are both present in the working directory, all data related to the so called plot subgrid will be transferred to the NetCDF file. If the latter file is missing, no data related to the plot subgrid will be stored in the NetCDF file.

|methodology=The computational grid informations are converted using various methods from the software package '''H_GRID''' as well as written to file in different formats.
Files with information concerning locations are converted by the software package called '''L_GRID'''.
The software package '''P_GRID''' converts files with profile grid data.: 
The software package '''IO_INSEL''' converts construction data of insel.dat files. GRIDCONVERT enables the user to select the construction types, e.g. "DAMM", which should be converted.


''Notice'': You can add some optional information blocks to the input file (except: profil05.bin). This is the way to put additional meta data, e.g. of the CF-convention, into the CF-NetCDF file.
To add CF informations to a file of type [[PROFIL05.BIN|profil05.bin]] put the meta data in an ASCII-file with the same name and the extension '.dat'. 
See example file: 
''$PROGHOME/examples/gridconvert/data/loc/lg.allCFinfo.dat'' or 
''$PROGHOME/examples/lib/h_grid/h_grid_test_g05_plus_CF_Info_input.dat'' or 
''$PROGHOME/examples/lib/h_grid/h_grid_test_utr_plus_CF_Info_input.dat'' or 
''$PROGHOME/examples/lib/h_grid/h_grid_test_sub_plus_CF_Info_input.dat'' or 
''$PROGHOME/examples/lib/p_grid/profil05.CF_Test.dat'' or 
''$PROGHOME/examples/gridconvert/data/ins/insel.all.dat''

|preprocessor=[[DAVIT]], [[Mathematical_Model_DELFT3D|DELFT3D]], [[JANET]], [[TELEMAC-2D]], [[UNTRIM]]
|postprocessor=[[DATACONVERT]], [[DAVIT]], [[HVIEW2D]], [[JANET]], [[NCANALYSE]], [[NCAUTO]], [[NCCHUNKIE]], [[NCPLOT]], [[NC2TABLE]], [[UNTRIM]], [[UTRPRE]] and diverse NetCDF-Tools, e.g. NCPLOT, QUICKPLOT
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de Working group PRE]
|documentation=example files: 
$PROGHOME/examples/gridconvert/, 
$PROGHOME/examples/gridconvert/data/loc/, 
$PROGHOME/examples/gridconvert/data/ins/ ([[INSEL.DAT|insel.dat]]). 

Further informations: 
All NetCDF conventions, which are relevant to store the typical BAW-specific data, are documented in the [[NetCDF|NetCDF-Pages of BAW-Wiki]].
}}

F77 TO F90

2023-05-03T06:52:25Z

Ak3gseis:

{{ProgramDescription
|name_de=F77_TO_F90
|name=F77_TO_F90
|version=May 2023
|version_descr=March 2023
|catchwords=
FORTRAN source code 
FORTRAN 90 syntax 
conversion of F77 sources 
|shortdescription=
The program F77_TO_F90 converts FORTRAN sources which have been written in FORTRAN77 standard syntax into correct FORTRAN90 source code. For sources, which include other sources, also the latter have to be converted.

Obsolescent language elements are prserved and should be substituted by the programmer after conversion.

Remark: The program can also be used with command line arguments since 2023. Help can be found by typing:
f77_to_f90 -h

|inputfiles=
# one or more files with FORTRAN77 code
# If more then one file shall be processed (optional) a list of the files (type [[DATEILISTE.DAT|dateiliste.dat]])
|outputfiles=
# one or more files with FORTRAN90 code
# printer output f77_to_f90.sdr
# (optional) file with test output
|methodology=
For every file a version written in F90 syntax will be created. The following changes will be done in comparison with the original code:
* comment lines wich start with '''C''', '''c''' or '''*''' change their first character to '''!'''.
* for continuation lines (the 6th column is not a blank) the preceeding line will end with a '''&'''. The 6th column is changed to blank normally. If a '''CHARACTER''' constant is distributed over the two lines, the 6th column is changed to '''&'''.
All changes are documented by the printer output file.
|preprocessor=
-
|postprocessor=
FORTRAN compiler, e.g. ifort, gfortran, nagfor
|language=Fortran 2003
|add_software= -
|contact_original=G. Seiß
|contact_maintenance=[mailto:guntram.seiss@baw.de G. Seiß]
|documentation=self-explanatory
}}

F77 TO F90

2023-05-03T06:48:42Z

Ak3gseis: some corrections

{{ProgramDescription
|name_de=F77_TO_F90
|name=F77_TO_F90
|version=May 2023
|version_descr=March 2023
|catchwords=
FORTRAN source code 
FORTRAN 90 syntax 
conversion of F77 sources 
|shortdescription=
The program F77_TO_F90 converts FORTRAN sources which have been written in FORTRAN77 standard syntax into correct FORTRAN90 source code. For sources, which include other sources, also the latter have to be converted.

Obsolescent language elements are prserved and should be substituted by the programmer after conversion.

Remark: The program can also be used with command line arguments since 2023. Help can be found by typing:
f77_to_f90 -h

|inputfiles=
# one or more files with FORTRAN77 code
# If more then one file shall be processed (optional) a list of the files (type [[DATEILISTE.DAT|dateiliste.dat]])
|outputfiles=
# one or more files with FORTRAN90 code
# printer output f77_to_f90.sdr
# (optional) file with test output
|methodology=
For every file a version written in F90 syntax will be created. The following changes will be done in comparison with the original code:
* comment lines wich start with '''C''', '''c''' or '''*''' change their first character to '''!'''.
* for continuation lines (the 6th column is not a blank) the preceeding line will end with a '''&'''. The 6th column is changed to blank normally. If a '''CHARACTER''' constant is distributed over the two lines, the 6th column is changed to '''&'''.
All changes are documented by the printer output file.
|preprocessor=
-
|postprocessor=
FORTRAN compiler, e.g. ifort, gfortran, nagfor
|language=Fortran 2003
|add_software= -
|contact_original=[mailto:guntram.seiss@baw.de G. Seiß]
|contact_maintenance=[mailto:guntram.seiss@baw.de G. Seiß]
|documentation=self-explanatory
}}

F77 TO F90

2023-05-03T06:43:29Z

Ak3gseis: program version updated

{{ProgramDescription
|name_de=F77_TO_F90
|name=F77_TO_F90
|version=May 2023
|version_descr=March 2023
|catchwords=
FORTRAN source code 
FORTRAN 90 syntax 
conversion of F77 sources 
|shortdescription=
The program F77_TO_F90 converts FORTRAN sources which have been written in FORTRAN77 standard syntax into correct FORTRAN90 source code. For sources, which include other sources, also the latter have to be converted.

Obsolescent language elements are prserved and should be substituted by the programmer after conversion.

Remark: The program can also be used with command line arguments since 2023. Help can be found by typing:
f77_to_f90 -h

|inputfiles=
# one or more files with FORTRAN77 code
# If more then one file shall be processed (optional) a list of the files (type [[DATEILISTE.DAT|dateiliste.dat]])
|outputfiles=
# one or more files with FORTRAN90 code
# printer output f77_to_f90.sdr
# (optional) file with test output
|methodology=
For every file a version written in F90 syntax will be created. The following changes will be done in comparison with the original code:
* comment lines wich start with '''C''', '''c''' or '''*''' change their first character to '''!'''.
* for continuation lines (the 6th column is not a blank) the preceeding line will end with a '''&'''. The 6th column is changed to blank normally. If a '''CHARACTER''' constant is distributed over the two lines, the 6th column is changed to '''&'''.
All changes are documented by the printer output file.
|preprocessor=
-
|postprocessor=
F90 compiler
|language=Fortran90
|add_software= -
|contact_original=[mailto:guntram.seiß@baw.de G. Seiß]
|contact_maintenance=[mailto:guntram.seiß@baw.de G. Seiß]
|documentation=self-explanatory
}}

F77 TO F90

2023-03-24T15:46:17Z

Ak3gseis: commandline arguments and other remarks

{{ProgramDescription
|name_de=F77_TO_F90
|name=F77_TO_F90
|version=March 2023
|version_descr=March 2023
|catchwords=
FORTRAN source code 
FORTRAN 90 syntax 
conversion of F77 sources 
|shortdescription=
The program F77_TO_F90 converts FORTRAN sources which have been written in FORTRAN77 standard syntax into correct FORTRAN90 source code. For sources, which include other sources, also the latter have to be converted.

Obsolescent language elements are prserved and should be substituted by the programmer after conversion.

Remark: The program can also be used with command line arguments since 2023. Help can be found by typing:
f77_to_f90 -h

|inputfiles=
# one or more files with FORTRAN77 code
# If more then one file shall be processed (optional) a list of the files (type [[DATEILISTE.DAT|dateiliste.dat]])
|outputfiles=
# one or more files with FORTRAN90 code
# printer output f77_to_f90.sdr
# (optional) file with test output
|methodology=
For every file a version written in F90 syntax will be created. The following changes will be done in comparison with the original code:
* comment lines wich start with '''C''', '''c''' or '''*''' change their first character to '''!'''.
* for continuation lines (the 6th column is not a blank) the preceeding line will end with a '''&'''. The 6th column is changed to blank normally. If a '''CHARACTER''' constant is distributed over the two lines, the 6th column is changed to '''&'''.
All changes are documented by the printer output file.
|preprocessor=
-
|postprocessor=
F90 compiler
|language=Fortran90
|add_software= -
|contact_original=[mailto:guntram.seiß@baw.de G. Seiß]
|contact_maintenance=[mailto:guntram.seiß@baw.de G. Seiß]
|documentation=self-explanatory
}}

GEOTRANSFORMER

2023-02-27T14:19:32Z

Ak3gseis: EPSG for UTM coordinates with 8 digits easting

{{ProgramDescription
|name_de=GEOTRANSFORMER
|name=GEOTRANSFORMER
|version=February 2023
|version_descr=February 2023
|catchwords=coordinate transformation 
coordinate system 
Gauss-Krueger 
Universal Transverse Mercator (UTM) 
Universal Polar Stereographic 
Country Hamburg "Lagestatus 320" 
European Terrestrial Reference System 1989 (ETRS89) 
world geodetic system 1984 (WGS84) 
european datum 1950 (ED50) 
Potsdam datum (Bessel 1841) 
Krassovski ellipsoid 
NTv2 method 
GNTRANS-WSV 
BETA2007 
Rijksdriehoeksmeting (RD, coordinate system of the netherlands) 
BAW file formats 
European petrol service group (EPSG)
|shortdescription=This program transforms coordinates between different coordinate systems.
Currently implemented map projections are:

* Gauß-Krüger (stripe 2 to 5)
* spherical coordinates (longitude, latitude)
* Universal Transverse Mercator (UTM)
* Rijksdatum (Netherlands)
* local metric central projection
* British National Grid

Currently implemented geodetic 7-parameter transformations:

* European Terrestrial Reference System 1989 (ETRS89)
* World Geodetic System 1984 (WGS84)
* European Datum 1950 (ED50)
* Federal Intstitute for cartography und geodesy, standard parameter
* Federal Intstitute for cartography und geodesy, latitudes >52,3 degrees N
* BAW C. Maushake,
* Krassovsky standard ([http://de.wikipedia.org/wiki/7-Parameter-Transformation Wikipedia])
* Krassovsky (WSA Stralsund)
* Federal Intstitute for cartography und geodesy, latitudes between 50,3 degrees N and 52,3 degrees N
* Federal Intstitute for cartography und geodesy, latitudes <50,3 Grad N
* Amsterdam Datum
* OSGB36 (based on Airy 1830)
* NTv2 grid shift methods GNTRANS-WSV (DHDN/STN -> ETRS89) and BETA2007 (DHDN -> ETRS89)

You can run the software in batch mode. There is no memory limit in amount of data to work with, because files are processed sequentially. To process 25 Mio. pairs of coordinates (Gauß-Krüger/DHDN <-> UTM/ETRS89) the software uses 280.68 minutes on a common INTEL CPU including Input/Output.

Since November 2018 the application is able to get the user input via command line arguments. This mode of input is documented by the online help, which is called by typing '''''geotransformer -h'''''.

Since May 2016 the software GEOTRANSFORMER is available without limits to its functionality on '''LINUX''' and '''WINDOWS''' driven INTEL based computers. It was validated on official test coordinates of the addressed systems. There exists a short "User Manual" for first time users.

The library '''libgeodesy''', which is used by this application, is used also in other applications to transform coordinates "on the fly". An "Application Programmer Interface" (API) called '''libgeodesyCAPI''' was supplied, to realize a port of the transformation functionality for MATLAB.

|inputfiles=
# triangulated mesh (file type TICAD,[[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# digitized polylines (file type [[DIGI.GKK|digi.gkk]]) or
# digitized polylines (file type [[INSEL.DAT|insel.dat]]) or
# polygon file (file type [[POLY.DAT|poly.dat]]) or
# polygone file to protect edges of a grid (file type [[NODES.SAVE|nodes.save]]) oder
# plot frames (file type [[FRAMES.DAT|frames.dat]], center and size, or
# description of boundary cells (file type [[RGZ.DAT|rgz.dat]]) or
# ASCII triple data, file with soundings (file type [[GEOM.DAT|geom.dat]]) or
# time series at single station (file type [[BOEWRT.DAT|boewrt.dat]]) or
# position description (file type [[GEOPOS.DAT|geopos.dat]]) or
# triangulated UNTRIM-VC mesh (file type [[UNTRIM_GRID.DAT|untrim_grid.dat]], version Vincenzo Casulli) or
# grid of the numerical method DELFT3D (file type [[DELFT3D.GRD|delft3d.grd]]) or
# triangulated UNTRIM-BAW mesh (file type [[UNTRIM_GRID.DAT|untrim_grid.dat]], BAW version) or
# system file for specific locations (file type [[LOCATION_GRID.DAT|location_grid.dat]]) or
# file IPDS to initialize models area wide (file type [[IPDS.DAT|ipds.dat]]) or
# world files which describe the georeference of an Image (typical file extensions are ''.pngw, .jpgw, .gifw'') or
# mesh of profiles (file type [[PROFIL05.BIN|profil05.bin]]) or
# CSV table ("comma seperated values") where columns are seperated by semicolon ( ; )
# indexed point data (index, x/longitude, y/latitude, z).

|outputfiles=
# triangulated mesh (file type TICAD,[[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]]) and (optionally) files of type [[GEOPOS.DAT|geopos.dat]] or
# digitized polylines (file type [[DIGI.GKK|digi.gkk]]) and (optionally) files of type [[GEOPOS.DAT|geopos.dat]] or
# digitized polylines (file type [[INSEL.DAT|insel.dat]]) and (optionally) files of type [[GEOPOS.DAT|geopos.dat]] or
# polygon file (file type [[POLY.DAT|poly.dat]]) and (optionally) files of type [[GEOPOS.DAT|geopos.dat]] or
# polygone file to protect edges of a grid (file type [[NODES.SAVE|nodes.save]]) and (optionally) files of type [[GEOPOS.DAT|geopos.dat]] oder
# plot frames (file type [[FRAMES.DAT|frames.dat]], center and size, or
# description of boundary cells (file type [[RGZ.DAT|rgz.dat]]) or
# ASCII triple data, file with soundings (file type [[GEOM.DAT|geom.dat]]) or
# time series at single station (file type [[BOEWRT.DAT|boewrt.dat]]) and (optionally) a file of type [[GEOPOS.DAT|geopos.dat]] or
# position description (file type [[GEOPOS.DAT|geopos.dat]]) or
# triangulated UNTRIM-VC mesh (file type [[UNTRIM_GRID.DAT|untrim_grid.dat]], version Vincenzo Casulli) or
# grid of the numerical method DELFT3D (file type [[DELFT3D.GRD|delft3d.grd]]) or
# triangulated UNTRIM-BAW mesh (file type [[UNTRIM_GRID.DAT|untrim_grid.dat]], BAW version) or
# system file for specific locations (file type [[LOCATION_GRID.DAT|location_grid.dat]]) and (optionally) files of type [[GEOPOS.DAT|geopos.dat]] or
# file IPDS to initialize models area wide (file type [[IPDS.DAT|ipds.dat]]) and (optionally) a files type [[GEOPOS.DAT|geopos.dat]] or
# world files which describe the georeference of an Image (typical file extensions are ''.pngw, .jpgw, .gifw'') or
# mesh of profiles (file type [[PROFIL05.BIN|profil05.bin]]) and (optionally) files of type [[GEOPOS.DAT|geopos.dat]] or
# CSV table ("comma seperated values") where columns are seperated by semicolon ( ; )
# indexed point data (index, x/longitude, y/latitude, z).

|methodology=
* Input and output list are opened at the same time. Every coordinate point will be read, transformed and written on the output list immediately. So the size of the input file is unlimited. Comments and other informations are copied "as is"! An input file is allowed in packed form (gzip, compress, zip) . Packing of the output file can be forced by giving the extension ".gz" or ."zip" (the latter at the moment only on LINUX systems).
* The formatting of decimal coordinates depends on the actual projection of coordinates (geographic or map coordinates). File type 08 (ASCII triple data) allows user defined Output Format via Environment variable GEOMFMT.
* The program first calculates spherical coordinates (WGS84) from input projected coordiantes. Then the new geodetic datum and projection is applied. In the '''datum cases DHDN or STN in input and/or output data''', the NTv2 method with grid shift file *.gsb is provided as Default alternative. The program should be used with the actual NTv2 grid shift files provided by the GNTRANS-WSV System conform to this system. It can be used with the BETA2007.gsb file to get conformity with the ATKIS system.
* on input in files of type 08 (geom.dat) the separators semicolon, tabulator, comma and colon are allowed. Additionally sperical coordinates are allowed to be written in nautical style, e.g. 4°17'16.62931"E 51°29'40.02423"N. Instead of characters (° ' ") also (d m s) or (^ ' ") may be used. The nautical format must include the information of hemisphere (N/S) and the orientation with respect to Greenwich (E/W).
* on input in files of type 09 ([[BOEWRT.DAT|boewrt.dat]]) or 10 ([[GEOPOS.DAT|geopos.dat]]), 13 ([[UNTRIM_GRID.DAT|untrim_grid.dat]], BAW version) and 14 ([[LOCATION_GRID.DAT|location_grid.dat]]) the coordinate reference system is first changed to the input system, if an internal CRS Information is available. In files of type 01 (gitter05.dat), 02 (digi.gkk) and 08 (geom.dat) the( well known!) coordinate reference system of the input files can be specified through the comment "C CRS=#####" at the beginning of the file. "#####" here is an EPSG code which is supported by libgeodesy. In this case also a Transformation to the input system is done first. The input system must have a valid EPSG code too.
* in input files of type 16 (world files) also the avarage pixel width and height transformation parameters are changed by assuming a virtual image of 800x800 pixels.
* To all ASCII formats which are not NAMELIST based, a file header with the current coordinate information is added as comments.
* UTM easting coordinates with 7 and 8 digits are recognized and changed into 6 digits representation. For recognition of valid 8 und 7 digits easting values both the number of digits and the actual UTM zone are used.
* for some of the file types an optional export of all original coordinates as file type [[GEOPOS.DAT|geopos.dat]] is possible. Those files can be used for control purpose and also in further pre processing programs e.g. [[TICLQ2]]. Please do not use this output option when transforming input files with a huge number of coordinates!!!
* file type 18 allows the user to define freely the columns, which have to be processed. A third column with altitude values can optionally be transformed during change of geodetic datum. Several coordinate pairs /tripel of a row may be transformed in a single step.

All transformation algorithms use double precision floating point values for representation inside memory. Inside the two supported binaryfile formats single precision REAL values of the coordinates are stored. Theese formats should be used carefully, because spherical coordinates are written with unacceptable accuracy:

* [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]]: Creation of the ASCII formatted variant is recommended on output, and usage in future projects!
* [[PROFIL05.BIN|profil05.bin]]: Write this format only with projected coordinates (UTM, Gauß-Krüger). The accuracy of coordinate representation with projected coordinates is limited to 0,5-1m.

Inside the supported ASCII file formats the accuracy of coordinate representation is choosen with respect to the reference system. This behavior ensures that accuracy is guaranteed to a certain limit, if spherical coordinates are written.

EPSG codes which are supported by libgeodesy are:
* Gauss-Krueger 3 degree / DHDN: EPSG 31466-31469 (EPSG = 31464 + stripe number), used with datum BKG >52,3 degree N
* Gauss-Krueger / ETRS89, stripe 3 ("Lagestatus 320", Hamburg): EPSG 8395
* Gauss-Krueger 3 degree / STN : EPSG 02397-02399, 05674-05675, 03838, 03829
* Gauss-Krueger 3 degree / DHDN: EPSG 31462-31465 ( EPSG = 31460 + Streifennummer ), reused for datum BKG between 50,3 degree N and 52,3 degree N
* Gauss-Krueger 3 degree / DHDN: EPSG 31492-31495 ( EPSG = 31490 + Streifennummer ), reused for datum BKG <50,3 degree N
* UTM / ETRS89 : EPSG 25828-25838 (EPSG = 25800 + zone number)
* UTM / ETRS89, 8 digits : 4647, 5649, 5650, 35832, 35833
* UTM / ED50 : EPSG 23028-23038 (EPSG = 23000 + zone number)
* UTM / WGS84 (North) : EPSG 32601-32660 (EPSG = 32600 + zone number)
* UTM / WGS84 (South) : EPSG 32701-32760 (EPSG = 32700 + zone number)
* UPS / WGS84 : EPSG 32661 and 32761
* RD Amersfoort New : EPSG 28992 and 7415
* OSGB 1936/British National Grid: EPSG 27700
* Geographic ETRS89 : EPSG 4258
* Geographic WGS84 : EPSG 4326
* Geographic ED 50 : EPSG 4230
* Geographic DHDN : EPSG 4314
* Geographic Amersfoort : EPSG 4289

Some CRS, which are not supported by an EPSG can be realized by using the expert mode (basic knowledge of CRS's necessary).

It is recommended, to store the coordinate reference system as an EPSG code inside the basic datasets (raw data), if it is known. This can be done by the magic comment"C CRS=#####" inside the most ASCII file types. Within file types, where storage is foreseen for an EPSG code, it should be placed there.

Actual datasets should be stored with UTM/ETRS89 coordinates of the valid zone or in geographic coordinates (ETRS89 or WGS84) . Transforming older datasets with Gauß-Krüger coordinates into UTM/ETRS89 should be done preferably with the NTv2 method after GNTRANS-WSV. The transformation grid is valid only for German area including coastal waters. Coordinates outside this area must not be transformed by NTv2 but should be transformed using a valid Helmert transformation parameter set. In case of doubt the provider of the coordinate data shall provide the coordinate reference information.

Transforming coordinates is '''not a trivial task'''. Therefor the transformation result should be tested for plausibility and usability. Multible transformations forward and back can destroy accuracy of coordinates due to accumulation of numeric errors inside the basic algorithms.

|preprocessor=all programs wich use above listed file formats
|postprocessor=all programs wich use above listed file formats
|language=Fortran2003, C
|add_software=NTv2 grids dhdn_to_etrs89_wsv_v1.gsb, stn_to_etrs89_wsv_v1.gsb and BETA2007.gsb
|contact_original=G. Seiß (main program, file I/O, libgeodesy)
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=interactive dialog, self explaining $PROGHOME/examples/geotransformer $PROGHOME/examples/geotransformer/Anleitung_GEOTRANSFORMER.pdf Junkins, D.R. and Farley, S.A. (1995) '''N'''ational '''T'''ransformation '''v'''ersion '''2''' Users Guide, Geodetic Survey Division Geomatics Canada 
Lott, Roger und OGP Geodesy Working Group (2015) Coordinate Conversions and Transformations including Formulas. [http://www.iogp.org/pubs/373-07-2.pdf Geomatics Guidance Note (IOGP Publication 373), 7. Part 2]. 
Bruijne, Arnoud de; van Buren, Joop; Kösters, Anton; van der Marel, Hans (2005): De geodetische referentiestelsels van Nederland. Geodetic reference frames in the Netherlands. Hg. v. Nederlandse Commissie voor Geodesie Netherlands Geodetic Commission. Delft. [http://www.ncgeo.nl/index.php?option=com_k2&view=item&id=2361:gs-43-a-de-bruijne-de-geodetische-referentiestelsels-van-nederland&Itemid=178&lang=nl Download here]. 
Federal Fairway Authority (Eds.) (2012): Handlungsanweisung für die Transformation der Datenbestände der WSV in das System ETRS89/UTM. In German language, with contribution of Hendrik Hampe, Sudau, Gunther Braun, Cornelius Zschunke, Egon Feigel, Helga Panknin et al. 
Lutter, H. (2009): Helmerttransformationsparameter für Gauss-Krüger Streifen 4 (Krassowski), WSA Stralsund. Pers. Communication.
}}

FRQ2ZEITR

2022-10-14T15:10:28Z

Ak3gseis:

{{ProgramDescription
|name_de=FRQ2ZEITR
|name=FRQ2ZEITR
|version=October 2022
|version_descr=October 2022
|catchwords=
Harmonic evaluation of tides 
forecast calculation of tides 
tidal harmonic constituents 
time series 
|shortdescription=
-
|inputfiles=
# input control file (file type [[FRQ2ZEITR.DAT|frq2zeitr.dat]]).
# file with keys of tidal harmonic constituents which will be used for calculation of the waterlevel (file type [[KENNUNGEN.DAT|kennungen.dat]]).
# file with the keys of geopositions for which the time series will be calculated (file type [[KENNUNGEN.DAT|kennungen.dat]]).
# file with the names of available extended geoposition files (file type [[DATEILISTE.DAT|dateiliste.dat]]).
# file with basic information about the tidal harmonic constituents (file [[TIDEGRUNDDATEN.DAT|tidegrunddaten.dat]]).
# the available extended geoposition files with information about the tidal amplitudes(file type [[GEOPOS.DAT|geopos.dat]]).
# (optional) file with absolute times, onto which the output timeseries should be mapped (file type [[BOEWRT.DAT|boewrt.dat]]). Only the time information of this file will be considered.
|outputfiles=
# files with time series of water level (file type [[BOEWRT.DAT|boewrt.dat]])
# printer file frq2zeitr.sdr
# (optional) file with test output (frq2zeitr.trc)
|methodology=
First the time vector is created. Then the neccessary frequencies and correctures are calculated. Further the local tidal amplitudes and phases are extracted. Then the tidal constituents are summed up to the total water level for the whole time vector. For calculation of the cosine the reference time is chosen as 01.01.yyyy-00:00:00 + n*T. T is the period of the harmonic constituent and n an integer number.

Additionally the status flag is generated and written on output. The flag is set to value 1 == "good".

'''Remarks''':

* It is possible, to choose an arbitrary time period and time step of the time series of the water level. If the time period is very long (several months) or the time step is rather short the calculation can take a significant amount of time. Its also possible to specify nonequidistant timestamps.
* If the user defines a coordinate reference System through the environment variable BAWCRS, coordinates of the input positions are transformed to this CRS.
* Commandline arguments are supported. Help: '''frq2zeitr -h'''; Look also inside the examples folder.
|preprocessor=
[[FRQWF]]
|postprocessor=
[[EXCELENZ]], [[GVIEW2D]], [[TSCALC]], [[UTRRND]], [[ZEITRIO]]
|language=Fortran2003
|add_software= -
|contact_original=G. Seiß, M. Haupt
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=
$PROGHOME/examples/frq2zeitr

Tafeln der Astronomischen Argumente V_0+v und der Korrekturen (j, v) von 1900 bis 1999, Bundesamt für Seeschiffahrt und Hydrographie, Hamburg.
}}

FRQ2ZEITR

2022-10-14T15:09:30Z

Ak3gseis:

{{ProgramDescription
|name_de=FRQ2ZEITR
|name=FRQ2ZEITR
|version=October 2022
|version_descr=October 2022
|catchwords=
Harmonic evaluation of tides 
forecast calculation of tides 
tidal harmonic constituents 
time series 
|shortdescription=
-
|inputfiles=
# input control file (file type [[FRQ2ZEITR.DAT|frq2zeitr.dat]]).
# file with keys of tidal harmonic constituents which will be used for calculation of the waterlevel (file type [[KENNUNGEN.DAT|kennungen.dat]]).
# file with the keys of geopositions for which the time series will be calculated (file type [[KENNUNGEN.DAT|kennungen.dat]]).
# file with the names of available extended geoposition files (file type [[DATEILISTE.DAT|dateiliste.dat]]).
# file with basic information about the tidal harmonic constituents (file [[TIDEGRUNDDATEN.DAT|tidegrunddaten.dat]]).
# the available extended geoposition files with information about the tidal amplitudes(file type [[GEOPOS.DAT|geopos.dat]]).
# (optional) file with absolute times, onto which the output timeseries should be mapped (file type [[BOEWRT.DAT|boewrt.dat]]). Only the time information of this file will be considered.
|outputfiles=
# files with time series of water level (file type [[BOEWRT.DAT|boewrt.dat]])
# printer file frq2zeitr.sdr
# (optional) file with test output (frq2zeitr.trc)
|methodology=
First the time vector is created. Then the neccessary frequencies and correctures are calculated. Further the local tidal amplitudes and phases are extracted. Then the tidal constituents are summed up to the total water level for the whole time vector. For calculation of the cosine the reference time is chosen as 01.01.yyyy-00:00:00 + n*T. T is the period of the harmonic constituent and n an integer number.

Additionally the status flag is generated and written on output. The flag is set to value 1 == "good".

'''Remarks''':

* It is possible, to choose an arbitrary time period and time step of the time series of the water level. If the time period is very long (several months) or the time step is rather short the calculation can take a significant amount of time. Its also possible to specify nonequidistant timestamps.
* If the user defines a coordinate reference System through the environment variable BAWCRS, coordinates of the input positions are transformed to this CRS.
* Commandline arguments are supported. Help: '''frq2zeitr -h'''; Look also inside the examples folder.
|preprocessor=
[[FRQWF]]
|postprocessor=
[[EXCELENZ]], [[GVIEW2D]], [[TSCALC]], [[UTRRND]], [[ZEITRIO]]
|language=Fortran95
|add_software= -
|contact_original=G. Seiß, M. Haupt
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=
$PROGHOME/examples/frq2zeitr

Tafeln der Astronomischen Argumente V_0+v und der Korrekturen (j, v) von 1900 bis 1999, Bundesamt für Seeschiffahrt und Hydrographie, Hamburg.
}}

DATAUS

2022-10-13T12:18:17Z

Ak3gseis:

{{ProgramDescription
|name_de=DATAUS
|name=DATAUS
|version=October 2022
|version_descr=October 2022
|catchwords=
extraction of soundings 
interesting area 
|shortdescription=
The program DATAUS extracts the soundings of an interesting area out of a file with soundings of a larger area.
|inputfiles=
# file which contains echo soundings of type [[GEOM.DAT|geom.dat]] (FORTRAN-Format '(2(f15.2,1x),f15.3)' ), [[DIGI.GKK|digi.gkk]] , written in FORTRAN format '(2(f10.2,1x),f6.2)' or another userdefined FORTRAN format (x,y,z).
# (optional) file with boundary of the interesting area (Typ [[POLY.DAT|poly.dat]])
|outputfiles=
# file which contains echo soundings for the interesting area of type [[GEOM.DAT|geom.dat]] (FORTRAN-Format '(2(f15.2,1x),f15.3)' ), written in FORTRAN format '(2(f10.2,1x),f6.2)' or another userdefined FORTRAN format (x,y,z).
# (optional) file of type gkslog.dat (terminal protocol). This file enables the user to rerun a session a second time!
|methodology=
The program reads the soundings sequentially, tests whether they are inside the given area and writes them into the new file if they are inside. A coordinate reference System which has been optionally specified through a comment "C CRS=####" inside the input file is transferred to the output file. 
'''Remarks:'''
* The program offers the possibility of a terminal protocol, as the GKS-programs HVIEW2D und VVIEW2D do. If the program is then run a second time, this protocol is automatically read and the same results are created again.
* User input can be done also by command line arguments
* "On the fly" transformation of coordinates into a user coordinate system is done when BAWCRS is set properly and the data contain the comment '''C CRS=<epsg>'''.
|preprocessor=
-
|postprocessor=
ARCGIS, [[ArcGIS-Applications]], CFLOOR, [[FD2ADDTOPO]], [[JANET]], DELFT3D software
|language=Fortran2003
|add_software= -
|contact_original=M. Boehlich, I. Uliczka
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=self-explanatory
}}

DATAUS

2022-10-13T12:17:33Z

Ak3gseis: commandline arguments and other remarks

{{ProgramDescription
|name_de=DATAUS
|name=DATAUS
|version=October 2022
|version_descr=October 2022
|catchwords=
extraction of soundings 
interesting area 
|shortdescription=
The program DATAUS extracts the soundings of an interesting area out of a file with soundings of a larger area.
|inputfiles=
# file which contains echo soundings of type [[GEOM.DAT|geom.dat]] (FORTRAN-Format '(2(f15.2,1x),f15.3)' ), [[DIGI.GKK|digi.gkk]] , written in FORTRAN format '(2(f10.2,1x),f6.2)' or another userdefined FORTRAN format (x,y,z).
# (optional) file with boundary of the interesting area (Typ [[POLY.DAT|poly.dat]])
|outputfiles=
# file which contains echo soundings for the interesting area of type [[GEOM.DAT|geom.dat]] (FORTRAN-Format '(2(f15.2,1x),f15.3)' ), written in FORTRAN format '(2(f10.2,1x),f6.2)' or another userdefined FORTRAN format (x,y,z).
# (optional) file of type gkslog.dat (terminal protocol). This file enables the user to rerun a session a second time!
|methodology=
The program reads the soundings sequentially, tests whether they are inside the given area and writes them into the new file if they are inside. A coordinate reference System which has been optionally specified through a comment "C CRS=####" inside the input file is transferred to the output file. 
'''Remarks:'''
* The program offers the possibility of a terminal protocol, as the GKS-programs HVIEW2D und VVIEW2D do. If the program is then run a second time, this protocol is automatically read and the same results are created again.
* User input can be done also by command line arguments
* "On the fly" transformation of coordinates into a user coordinate system is done when BAWCRS is set properly and the data contain the comment '''C CRS=<epsg>'''.
|preprocessor=
-
|postprocessor=
ARCGIS, [[ArcGIS-Applications]], CFLOOR, [[FD2ADDTOPO]], [[JANET]], DELFT3D software
|language=Fortran99
|add_software= -
|contact_original=M. Boehlich, I. Uliczka
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=self-explanatory
}}

TR2GEOM

2022-10-11T08:38:50Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2GEOM
|name=TR2GEOM
|version=December 1997
|version_descr=December 1997
|catchwords=postprocessor 
finite difference method 
conversion of a finite difference grid 
equivalent finite element grid 
numerical modelling system TRIM-2D 
numerical modelling system TRIM-3D
|shortdescription=The program TR2GEOM is a postprocessor for the numerical models TRIM-2D as well as TRIM-3D. This program serves to convert the bathymetry given in the TRIM-format into an equivalent one defined on a finite element grid given in the TICAD-format.

The application of this program is a prerequisite for the later usage of various model-independent postprocessors (for graphics and data analysis).
|inputfiles=
#general input data (filetype [[TR2GEOM.DAT|tr2geom.dat]])
#bathymetry and index-arrays (filetype [[TR2.TOPO.BIN.IND|tr2.topo.bin.ind]])
#(optional) protection polygons (filetype [[NODES.SAVE|nodes.save]])
:Notice:
#the name of the file must be nodes.save
#protection polygons are automatically taken into account when the file is present in the working directory
#see also comments in the example file
#use program [[UPDA2D]] as an alternative
|outputfiles=
#equivalent grid (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]]) or systemfile (filetype sysdat.bin, will no longer be supported in the future)
#list of edges (filetype [[FKVZ.BIN|fkvz.bin]])
#list of neighbour elements (filetype [[FKEZ.BIN|fkez.bin]])
(optional) trace of program execution (filetype tr2geom.trc)
|methodology=The TRIM-topography is defined at all U and V computational points on a regular finite difference grid with constant grid size. Linear interpolation is used to compute the bathymetric depth for the nodal points of an equivalent finite element grid. Each finite difference grid cell can be optionally split into 2 or 8 triangles.
|preprocessor=[[TR2KACHEL]], [[TRIM-2D]], [[TRIM-3D]], [[TRIMKACH]]
|postprocessor=[[DIDAMERGE]], [[TOUTR]], [[TR2DIDA]], [[TR3DIDA]], [[XTRLQ2]], [[ZEITR]], [[HVIEW2D]], [[JANET]], [[WARM]]
|language=Fortran90
|add_software=-
|contact_original=T. Damrau, G. Lang, I. Uliczka
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2geom/
}}

TR2RND

2022-10-11T08:22:54Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2RND
|name=TR2RND
|version=3.x / Juni 2000
|version_descr=3.x / Juni 2000
|catchwords=
preprocessor 
finite difference method 
boundary values 
numerical method TRIM-2D 
numerical method TRIM-3D (depth-independent boundary values)
|shortdescription=
The program TR2RND is a preprocessor for the numerical models TRIM-2D as well as TRIM-3D. TR2RND is used for conversion of boundary informations into a special storage format which enables a fast access for the simulation progams TRIM-2D and TRIM-3D to the grid cell boundary values (hydrodynamics, salinity, temperature, suspended load concentration, etc).

Please notice that TR2RND can only generate depth-independent boundary values for the three-dimensional numerical model TRIM-3D.
|inputfiles=
# file with informations about time span of the newly generated timeseries and about the number of FD grid cells at which the boundary values should be used (file type [[FD2RND.DAT|fd2rnd.dat]]).
# file with time series of boundary values (file type [[RNDWERTE.DAT|rndwerte.dat]]v).
# model topography (file type [[TR2.TOPO.BIN|tr2.topo.bin]])
|outputfiles=
# ASCII file with informations about the generated time series of boundary values (tr2rnd.echo).
# binary files with informations and boundary values for sea level and inflow/outflow ([[TR2.RBH.BIN.I|tr2.rbh.bin.i]]and [[TR2.RBH.BIN|tr2.rbh.bin]]).
# binary files with informations and boundary values for salinity ([[TR2.RBS.BIN.I|tr2.rbs.bin.i]] and [[TR2.RBS.BIN|tr2.rbs.bin]]).
# binary files with informations and boundary values for temperature ([[TR2.RBC.BIN.I|tr2.rbc.bin.i]] and [[TR2.RBC.BIN|tr2.rbc.bin]]).
# binary files with informations and boundary values for suspended load concentration (tr2.rbc.bin.I and tr2.rbc.bin).
# binary files with informations and boundary values for time varying weir /dam heights ([[TR2.RBW.BIN.I|tr2.rbw.bin.i]] and [[TR2.RBW.BIN|tr2.rbw.bin]]).
|methodology=
TR2RND creates binary boundary value files (*.bin.I and *.bin) for the noted physical parameters from ASCII files. The binary files contain informations about the number and indices of the boundary grid cells and their connection to a time series of boundary values. The timeseries are stored in the direct access files as single records.
|preprocessor=[[FD2TRIM]], [[BOERND]], [[TC2TR2]], [[TSCALC]], [[UTRRND]]
|postprocessor=[[TRIM-2D]], [[TRIM-3D]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang, E. Rudolph, S. Spohr
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=please refer to $PROGHOME/examples/tr2rnd
}}

TR2LQ2

2022-10-11T08:17:48Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2LQ2
|name=TR2LQ2
|version=November 2017
|version_descr=September 1999
|catchwords=preprocessor 
profile bathymetry 
extraction of bathymetry at profiles 
numerical model TRIM-2D 
numerical model TRIM-3D
|shortdescription=The program TR2LQ2 is a preprocessor for the mathematical models TRIM-2D and TRIM-3D. It was designed to extract bathymetry-data along longitudinal or cross-sectional profiles from a TRIM bathymetry and index arrays containing file. Every profile is defined by a sequence of an arbitrary number of 2D-locations which are connected by straight lines. Additional points can be easily inserted automatically at regular intervals in between these 2D-locations.
|inputfiles=
# general input data (filetype [[TR2LQ2.DAT|tr2lq2.dat]])
# (optional) old profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# (optional) profiles (filetype [[PROF.BIN|prof.bin]])
# several other files are necessary to define the 2D-Locations and profiles where data shall be extracted (see documentation for the file [[TR2LQ2.DAT|tr2lq2.dat]])
# bathymetry and index arrays (filetype [[TR2.TOPO.BIN.IND|tr2.topo.bin.ind]])
|outputfiles=
# profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# decriptions of all geo positions divided into profiles (filetype [[GPROFIL.DAT|gprofil.dat]])
# depth values of all points divided into profiles (filetype [[TPROFIL.DAT|tprofil.dat]])
# informative printer file (filetype tr2lq2.sdr)
# (optional) trace of program execution (filetype tr2lq2.trc)
|methodology=A comprehensive profile-topography is generated from the various input-data. 2D-locations are gathered to form profiles. Additional new points can be automatically inserted in between these locations at arbitrary intervals. Bathymetric depth is calculated as the maximum of the depth values given at the four computational nodes (U- and V- points) defining a cell in the computational grid. Text-strings can be related to locations and profiles. A list of node numbers as well as connexion-tables are generated for all segments. Optional information is also generated for data-interpolation (used by subsequent post-processors). New bathymetry data can overwritten to an already existing profile-topography.
|preprocessor=[[CROSSPRO]], [[DEPRO2D]]
|postprocessor=[[ADCP2PROFILE]], [[TRIM-2D]], [[TRIM-3D]]
|language=Fortran2003
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2lq2/
}}

TR2LQ2

2022-10-11T08:12:08Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2LQ2
|name=TR2LQ2
|version=November 1996
|version_descr=September 1999
|catchwords=preprocessor 
profile bathymetry 
extraction of bathymetry at profiles 
numerical model TRIM-2D 
numerical model TRIM-3D
|shortdescription=The program TR2LQ2 is a preprocessor for the mathematical models TRIM-2D and TRIM-3D. It was designed to extract bathymetry-data along longitudinal or cross-sectional profiles from a TRIM bathymetry and index arrays containing file. Every profile is defined by a sequence of an arbitrary number of 2D-locations which are connected by straight lines. Additional points can be easily inserted automatically at regular intervals in between these 2D-locations.
|inputfiles=
# general input data (filetype [[TR2LQ2.DAT|tr2lq2.dat]])
# (optional) old profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# (optional) profiles (filetype [[PROF.BIN|prof.bin]])
# several other files are necessary to define the 2D-Locations and profiles where data shall be extracted (see documentation for the file [[TR2LQ2.DAT|tr2lq2.dat]])
# bathymetry and index arrays (filetype [[TR2.TOPO.BIN.IND|tr2.topo.bin.ind]])
|outputfiles=
# profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# decriptions of all geo positions divided into profiles (filetype [[GPROFIL.DAT|gprofil.dat]])
# depth values of all points divided into profiles (filetype [[TPROFIL.DAT|tprofil.dat]])
# informative printer file (filetype tr2lq2.sdr)
# (optional) trace of program execution (filetype tr2lq2.trc)
|methodology=A comprehensive profile-topography is generated from the various input-data. 2D-locations are gathered to form profiles. Additional new points can be automatically inserted in between these locations at arbitrary intervals. Bathymetric depth is calculated as the maximum of the depth values given at the four computational nodes (U- and V- points) defining a cell in the computational grid. Text-strings can be related to locations and profiles. A list of node numbers as well as connexion-tables are generated for all segments. Optional information is also generated for data-interpolation (used by subsequent post-processors). New bathymetry data can overwritten to an already existing profile-topography.
|preprocessor=[[CROSSPRO]], [[DEPRO2D]]
|postprocessor=[[ADCP2PROFILE]], [[TRIM-2D]], [[TRIM-3D]]
|language=Fortran2003
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2lq2/
}}

SYNGRID

2022-10-11T08:06:27Z

Ak3gseis:

{{ProgramDescription
|name_de=SYNGRID
|name=SYNGRID
|version=September 1995
|version_descr=April 2008
|catchwords=Preprocessor 
Generation of artificial bearing data
|shortdescription=
The program SYNGRID creates user-defined, artificial bearing data. This data will be stored in a file of type geom.dat. In addition, the program can compute and store the border of the bearing data. The border data will be stored in a file of type rand.dat.
|inputfiles=
General input data (filetype [[SYNGRID.DAT|syngrid.dat]]).
|outputfiles=
# Artificial bearing data (filetype [[GEOM.DAT|geom.dat]]).
# (optional) coordinates of the border points, sorted counterclockwise around the bearing data (filetype [[RAND.DAT|rand.dat]]).
|methodology=
The user defines all artificial bearing data in the general input file syngrid.dat. The user has the following possibilities to choose from:

* single points,
* points along a line,
* points along a a circle

All defined points will be stored in one file of type geom.dat.
The computation of the border uses the principle of radar beams: Around the data point lying east-most the program simulated a radar beam with a constant, user-defined radius and a starting angle. This radar beam covers a circled area around this east-most point.
The first point found by the radar beam is the next border point.
In the next step the radar beam looks for a successor border point around the last found border point.
the search for the border comes to an end, if the border start point (lying east-most) is identified as the "next" border point by the radar beam.
|preprocessor= -
|postprocessor=[[DREHE2D]], [[GEOMFD2]], [[IGEL2D]], [[UPDA2D]]
|language=Fortran90
|add_software=-
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/syngrid/
}}

TSCALC

2022-10-11T08:04:01Z

Ak3gseis:

{{ProgramDescription
|name_de=TSCALC
|name=TSCALC
|version=October 2013
|version_descr=October 2013
|catchwords=preprocessor 
time series data 
mathematical operations on time series data
|shortdescription=The program TSCALC is a useful preprocessor. The program serves to perform some mathematical operations on different time series data of a single physical quantity - a single output time serie is generated from two different input time series. The original time series data can be added, subtracted, multiplied or divided in various ways. The relative weight of each data set can be set individually. An additional time shift can be also applied to the time series data.
|inputfiles=
#general input data (filetype [[TSCALC.DAT|tscalc.dat]])
#file containing time serie 1 (filetype [[BOEWRT.DAT|boewrt.dat]] or [[SOLWRT.DAT|solwrt.dat]])
#file containing time serie 2 (filetype [[BOEWRT.DAT|boewrt.dat]] or [[SOLWRT.DAT|solwrt.dat]])
|outputfiles=
#file for the newly generated time serie (filetype [[BOEWRT.DAT|boewrt.dat]]
#informative printer file (filetype tscalc.sdr)
#(optional) trace of program execution (filetype tscalc.trc)
|methodology=Both time series are read first from two different files, which might have different data formats. In the second processing step time shifts can be applied optionally. Afterwards the input time series data are interpolated at regular intervals using either a linear or a spline interpolation scheme. Finally an output time serie is generated via different mathematical operations from the two input time series. Optionally the coordinates of the output time serie can be computed by a linear interpolation from the coordinates on input (boewrt.dat only).
|preprocessor=[[FFT]], [[FRQ2ZEITR]], [[GVIEW2D]], [[XTRDATA]], [[ZEITRIO]]
|postprocessor=[[FRQ2ZEITR]], [[GVIEW2D]], [[TIDKEN]], [[TM2RND]], [[TR2RND]], [[UTRRND]], [[ZEITRIO]]
|language=Fortran90
|add_software=-
|contact_original=J. Jürges, G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=
}}

TSCALC

2022-10-11T08:02:58Z

Ak3gseis:

{{ProgramDescription
|name_de=TSCALC
|name=TSCALC
|version=October 2013
|version_descr=October 2013
|catchwords=preprocessor 
time series data 
mathematical operations on time series data
|shortdescription=The program TSCALC is a useful preprocessor. The program serves to perform some mathematical operations on different time series data of a single physical quantity - a single output time serie is generated from two different input time series. The original time series data can be added, subtracted, multiplied or divided in various ways. The relative weight of each data set can be set individually. An additional time shift can be also applied to the time series data.
|inputfiles=
#general input data (filetype [[TSCALC.DAT|tscalc.dat]])
#file containing time serie 1 (filetype [[BOEWRT.DAT|boewrt.dat]] or [[SOLWRT.DAT|solwrt.dat]])
#file containing time serie 2 (filetype [[BOEWRT.DAT|boewrt.dat]] or [[SOLWRT.DAT|solwrt.dat]])
|outputfiles=
#file for the newly generated time serie (filetype [[BOEWRT.DAT|boewrt.dat]]
#informative printer file (filetype tscalc.sdr)
#(optional) trace of program execution (filetype tscalc.trc)
|methodology=Both time series are read first from two different files, which might have different data formats. In the second processing step time shifts can be applied optionally. Afterwards the input time series data are interpolated at regular intervals using either a linear or a spline interpolation scheme. Finally an output time serie is generated via different mathematical operations from the two input time series. Optionally the coordinates of the output time serie can be computed by a linear interpolation from the coordinates on input (boewrt.dat only).
|preprocessor=[[FFT]], [[FRQ2ZEITR]], [[GVIEW2D]], [[XTRDATA]], [[ZEITRIO]]
|postprocessor=[[FRQ2ZEITR]], [[GVIEW2D]], [[TIDKEN]], [[TM2RND]], [[TR2RND]], [[UTRRND]], [[ZEITRIO]]
|language=Fortran77
|add_software=-
|contact_original=J. Jürges, G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=
}}

UPDA2D

2022-10-11T08:01:37Z

Ak3gseis:

{{ProgramDescription
|name_de=UPDA2D
|name=UPDA2D
|version=August 1994
|version_descr=April 2008
|catchwords=
Preprocessor 
Update of Model Bathymetry 
Protected Nodes 
Alignment of Edges of Elements along Structures 
|shortdescription=
Program UPDA2D serves as a preprocessor for several mathematical models of BAW-DH. It was designed to update bathymetry (depth with respect to mean sea level) at nodal points of a finite element grid using measured depth values from field surveys. The area where bathymetry should be actualized can be more precisely defined by means of a surrounding polygon. New depth values are calculated using different interpolation formulas. Obviously wrong data points are automatically neglected. Depths at protected nodes are not updated at all.
In addition to the functionality described above the bathymetrical depth at nodal points can be also set to a prescribed value given through a polygon (to describe a piecewise linear man made structure; e.g. groynes, dams, jetties). Beyond that edges of triangles can be re-oriented to follow polygons. All actions can be performed separately or at the same time.
|inputfiles=
# general input data (filetype [[UPDA2D.DAT|upda2d.dat]])
# finite element grid (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# (optional) list of edges (filetype [[FKVZ.BIN|fkvz.bin]])
# (optional) list of neighbour elements (filetype [[FKEZ.BIN|fkez.bin]])
# (optional) surrounding polygon (filetype [[POLY.DAT|poly.dat]])
# (optional) protected nodes (filetype [[NODES.SAVE|nodes.save]])
# (optional) measured data points (filetype [[GEOM.DAT|geom.dat]])
|outputfiles=
# (optional) finite element grid with updated bathymetry (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# (optional) list of edges (filetype [[FKVZ.BIN|fkvz.bin]])
# (optional) list of neighbour elements (filetype [[FKEZ.BIN|fkez.bin]])
# (optional) difference between original and updated bathymetry (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# (optional) trace of program execution (filetype upda2d.trc).
|methodology=
During update of bathymetry at a nodal point all measured data points which belong to the patch of the respective node are used (a patch is formed by the area of all elements which are connected to the node). Several interpolation methods take into account the distances of the measured data points with respect to the updated node as well their mutual radius of influence. Protected nodes are not updated at all.
|preprocessor=
[http://plasma-gate.weizmann.ac.il/Grace/ Grace], [[SYNGRID]]
|postprocessor=
[[HVIEW2D]], [[JANET]], [[TC2GEOM]], [[TC2TR2]], [[TICTRI]], [[TOUTR]], [[TR2REFRESH]]
|language=Fortran90
|add_software= -
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/upda2d
}}

VOLUMETHAUTO

2022-10-11T07:59:27Z

Ak3gseis:

{{ProgramDescription
|name_de=VOLUMETH
|name=VOLUMETH
|version=December 1999
|version_descr=December 1999
|catchwords=
morphology 
volume method 
|shortdescription=
The program VOLUMETHAUTO is a Daemon for automatic volume calculations using the program [[VOLUMETH]] and automatic generation of result graphics.
|inputfiles=
# Program flow control file (filetype [[VOLUMETH.DAT|volumeth.dat]])
# (optional) Graphic parameter file (filetype [[VOLUMETH.PLT|volumeth.plt]])
|outputfiles=
# Result file (filetype [[VOLSUM.DAT and VOLSUM.EXCEL.DAT|volsum.dat/excel.dat]])
# (optional) Result graphic files (filetype CGM or Postscript)
|methodology=
The daemon VOLUMETHAUTO is a shell script written in UNIX. The shell script is called each five minutes by cron. When called, it tests, if there is any program flow control file (filetype [[VOLUMETH.DAT|volumeth.dat]]) or graphic parameter file (filetype [[VOLUMETH.PLT|volumeth.plt]]), resp., in the input directory '''/home/ak3jfrae/VOLUMETH/IN''' on '''PERSEUS'''. Also it tests, if there is running another volume calculation job, which might have been started five minutes before. If a program flow control file is found and if there is running no other job, the files are moved to the directory '''/home/ak3jfrae/VOLUMETH/WORK''', and calculations are started. If a graphic parameter file (filetype [[VOLUMETH.PLT|volumeth.plt]]) was found, that has the same name as the program flow control file (filetype [[VOLUMETH.DAT|volumeth.dat]]), but a file extension .plt instead .dat, result graphics are generated. After finishing calculations and, possibly graphic generation, all result files are moved to the output directory '''/home/ak3jfrae/VOLUMETH/OUT''' on '''PERSEUS'''.

Model topographies for calculations are stored in the directory

: '''/home/ak3jfrae/VOLUMETH/TOPO''' on '''PERSEUS'''.

Predefined polygons for volume calculations are stored in the directory

: '''/home/ak3jfrae/VOLUMETH/POLY/VORDEFINIERT''' on '''PERSEUS'''.

Userdefined polygons must be copied to the directory

: '''/home/ak3jfrae/VOLUMETH/POLY/SELBSTDEFINIERT'''

before starting calculations.
|preprocessor=
-
|postprocessor=
-
|language=UNIX
|add_software= -
|contact_original=B. Mau, J. Fräßdorf, G. Seiß
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation= -
}}

UTRPRE

2022-10-11T07:57:24Z

Ak3gseis:

{{ProgramDescription
|name_de=UTRPRE
|name=UTRPRE
|version=April 2015
|version_descr=April 2015
|catchwords=
preprocessor 
finite volume method 
finite difference method 
rounded depth data 
computational grid with depth 
computational grid with subgrid depth and additional plot subgrid information 
profile grid with depth 
location grid with depth 
|shortdescription=
Program UTRPRE is a preprocessor for the mathematical models UNTRIM2007 and UNTRIM2 (subgrid). It can be used to round depth data for a computational grid, a profile grid as well as a location grid.

Depth has to be rounded in order to remove roundoff sensitivity during determination of the number of computational points. With this procedure, on different computer platforms the same number of computational points used during the numerical simulation will be safely computed, i. e. for three-dimensional model runs.

Depth data at single locations and profile grid positions are optionally adjusted to the values given by the computational grid. In case also subgrid depth classes related to the computational polygons are taken into account properly.
|inputfiles=
# general '''input data''' (filetype [[UTRPRE.DAT|utrpre.dat]])
# all other input files are described in the before mentioned input data file.
|outputfiles=
# result files are described in the above mentioned input data file [[UTRPRE.DAT|utrpre.dat]].
# informative '''printer file''' (filetype utrpre.master.sdr)
# (optional) '''trace''' of program execution (filetype utrpre.trc)
|methodology=
Grid and depth data are read first from file. Thereafter, depth data are rounded for the computational grid according to users request. Modified depth data are checked against the vertical structure (position of z-layers for the mathematical models UNTRIM2007 and UNTRIM2) with respect to the stability of the result for the number of computational points against small variations in depth. Optionally, rounded depth data are transferred to the profile as well as the location grid used during output of computational results. Finally, the modified depth data are written to the different grid files used by the program.

The input files of type [[GEOPOS.DAT|geopos.dat]], which are used in creation of the grid for results at special locations, may contain coordinates of different coordinate reference Systems (CRS). If such a mixed dataset is used, the user has to set the environment variable BAWCRS to the CRS of the UNTRIM computational grid coordinates. Alle coordinates specified in a different CRS will be transformed "on the fly" into the right CRS. If BAWCRS is not set (not recommended!) all geopositions have to be specified in the right CRS!

The actually supported EPSG codes (CRS) are found on page [[GEOTRANSFORMER]].
|preprocessor=
[[CREATE_SIMPLE_UNTRIM2_GRID]], [[GRIDCONVERT]], [[JANET]], [[TICLQ2]]
|postprocessor=
[[UNTRIM2]], [[UNTRIM2007]], [[UTRRND]]
|language=Fortran95
|add_software= -
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=template files are available in $PROGHOME/examples/utrpre/
}}

UTRRND

2022-10-11T07:53:37Z

Ak3gseis:

{{ProgramDescription
|name_de=UTRRND
|name=UTRRND
|version=7.x / February 2022
|version_descr=February 2022
|catchwords=
preprocessor 
boundary time-series data 
boundary time-series data from computational results 
boundary time-series data from measured data 
source- and sink-flow from measured data 
numerical model TELEMAC-2D 
numerical model TRIM-2D 
numerical model TRIM-3D 
numerical model UNTRIM 
numerical model UNTRIM2 (sub grid) 
|shortdescription=
Program UTRRND is used as a preprocessor to generate boundary time-series data for the different numerical models applied at BAW. The following services are provided by this program:

# Generation of boundary time-series data which can be directly used in the numerical model UNTRIM;
# Preparation of time-series data which can be later used as input in connexion with the generation of boundary time series data for the numerical models TELEMAC-2D, TRIM-2D and TRIM-3D.

At the moment time-series can be generated for the following physical quantities:

# water level elevation along open model boundaries,
# salinity along open model boundaries,
# temperature along open model boundaries,
# suspended sediment load (several sediment fractions) along open model boundaries,
# tracer load (several sediment fractions) along open model boundaries,
# sources (flow-volume with salinity, temperature and suspended sediment load (several fractions)) inside the modelling domain,
# sinks (flow-volume) inside the modelling domain, as well as
# sinks with immediate inflow of the withdrawn volume at a different location, with the possibility to alter temperature as well as salinity (e.g. due to the use as cooling water for a power plant) compared to the respective values at the outtake location.

The following data sources (input data) can be (alternatively) used:

* water level elevation along open boundaries
** results from a previous simulation run, and
** measured data from different locations.
* salinity, temperature, suspended sediment load and/or tracer load along open boundaries as well as sources and sinks (with or without temperature and/or salinity change).
** measured data from different locations.

Remark: input data must be in time series format. Measured data need not be available at constant time intervals.

Beyond that, program UTRRND offers a possibility to modify boundary time series data for water level elevation with respect to mean value, amplitude and phase when they are computed from numerical model results. In this situation the user must specify some additional data in files of type boewrt.dat.

Boundary nodes or grid cells can be either detected automatically by the program from the structure of the grid, or by means of some auxiliary informations prescribed by the user.

Time series data for sources and sinks are exclusively generated for the specific location given by the user.
|inputfiles=
# '''general input data''' (filetype [[UTRRND.DAT|utrrnd.dat]]).
# '''grid''' with boundary nodes or boundary grid cells for which boundary time series data shall be generated or which describes the modelling domain for which sources and sinks are going to be generated:
#: for [[Mathematical Model TELEMAC-2D|TELEMAC-2D]] - filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]]
#: '''or'''
#: for [[Mathematical Model TRIM-2D|TRIM-2D]] and [[Mathematical Model TRIM-3D|TRIM-3D]] - filetype [[TR2.TOPO.BIN.IND|tr2.topo.bin.ind]]
#: '''or'''
#: for UNTRIM - filetype [[UNTRIM_GRID.DAT|untrim_grid.dat]]
# (optional) description of the '''vertical structure''', e.g. the position of layers, when three-dimensional boundary time series data shall be generated for the numerical model UNTRIM (filetype [[VERTICAL.DAT|vertical.dat]]) This information is only of importance in connexion with the computation of salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions), along open boundaries or sources and sinks inside the modelling domain.
# (optional) if 2D-/3D-'''results of a previous numerical simulation''' shall be used:
## '''grid''' (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]] '''or''' [[UNTRIM_GRID.DAT|untrim_grid.dat]] '''or''' [[PROFIL05.BIN|profil05.bin]] '''or''' [[LOCATION_GRID.DAT|location_grid.dat]])
## '''computed time series data''' (files of type [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])
## (optional) manually prescribed '''time series for modification''' of mean value, amplitude and phase of the time series derived from numerically calculated results (files of type [[BOEWRT.DAT|boewrt.dat]])
#: This functionality is currently only available in connexion with water level elevation boundary data time series.
# (optional) if '''measured data''' shall be used to generate the boundary time series data (files of type [[BOEWRT.DAT|boewrt.dat]])
# (optional) '''definition of boundaries''', in situations where the positions of boundary nodes or grid cells shall not be automatically determined from analysis of the grid structure:
## (optional) '''indices of boundary''' cells - if the numerical models TRIM-2D or TRIM-3D shall be later used (filetype [[FD2RND.DAT|fd2rnd.dat]])
## (optional) '''definition of boundary sections''' - can be used together with all types of numerical models (filetype [[BSECTION.DAT|bsection.dat]]).
#: These informations may be useful when boundary data time series are going to be generated for water level elevation, salinity and temperature. For sources and sinks this information is not even useful.

'''Support of coordinate reference systems :'''
# Files containing coordinate Information of type boewrt.dat, gitter05.dat/bin and untrim_grid.dat will be transformed into the sytem specified by BAWCRS during the reading process, if they contain a supported CRS internally as EPSG code. Use of BAWCRS leads to an export of the (valid) EPSG code into the boundary grid file. Further remarks are foud on page GEOTRANSFORMER.
# The use of BAWCRS is recommended, especially, if meteorological input data from NetCDF files are used during a model run.
# Nevertheless, the user shall add the EPSG code to the input data in all cases .

Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).
|outputfiles=
# '''systemfiles with locations''' of the nodes or cells where boundary time series data were generated (filetype [[LOCATION_GRID.DAT|location_grid.dat]]); the system files will contain the user specified coordinate reference System (CRS), if the Environment variable '''BAWCRS''' is set to a valid EPSG code value. Valid EPSG codes are described on the page [[GEOTRANSFORMER]].
# '''synoptic boundary data''' for all boundary data locations (files of type [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])
#: Remark: these result files are especially useful in connexion with the application of the numerical model UNTRIM.
# (optional) '''boundary time series data''' (filetype [[RNDWERTE.DAT|rndwerte.dat]])
#: Remark: this data file can be used as input file for the programs [[TM2RND]] and [[TR2RND]] respectively to generate boundary time series data for the numerical models TELEMAC-2D or TRIM-2D and TRIM-3D.
#: Remark: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.
# (optional) '''indices of boundary cells''', if either TRIM-2D or TRIM-3D shall be later used, and the boundary grid cells have not been already specified as input data before (filetype [[FD2RND.DAT|fd2rnd.dat]])
#: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.
# (optional) '''lineprinter file''' contains useful informations related to program execution (filetype utrrnd.sdr);
# (optional) file with '''trace of program execution''' (filetype utrrnd.trc).
|methodology=
* '''how boundary locations are determined''' (water level elevation, salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions))
** If the user does not explicitely specify informations which describe the positions of boundary nodes or grid cells the latter ones will be automatically determined by the program. The algorithm tries to determine all open boundary nodes from the grid structure.
** If the user has specified additional informations (e.g. fd2rnd.dat or bsection.dat), they are used to determine the locations of boundary nodes or grid cells which are situated along the outer boundary of a computational grid.
* '''interpolation using computational results''' (water level elevation)
** For any location where boundary time series data shall be generated at first the closest lying computational points are determined. Thereafter the time serie at the location of the boundary node will be determined from the numerically computed time series by means of a linear interpolation. No interpolation is done with respect to time.
** If a boundary node or grid cell is located outside the computational domain the closest lying computational point will be determined and the computed time series data will be used directly without any interpolation or extrapolation.
** Interpolated data can be optionally modified using user-specified values with respect to mean value, amplitude and phase. The modification parameters can be both, space as well as time dependent. Data necessary must be prescribed by the user in files of type boewrt.dat.
* '''interpolation using measured data''' (water level elevation)
** If measured data form the basis for interpolation of boundary time series data they will be interpolated to the location of the boundary node or grid cell in an analogous manner as described above for computational result based data.
** An important difference exists for the generation of boundary time series data of water level elevation. In this situation an analysis to determine times of high and low water is carried through beforehand to determine the time shifts which are applied to the measured data before they are going to be interpolated to obtain a boundary time serie of water level elevation. This type of interpolation (time shift) can be optionally switched off in case the data to be interpolated are not dominated by the tides.

'''commandline mode:
'''

The interactive requests can be avoided by using the commandline mode.

Help about this mode: '''''utrrnd[.i18] --help''''' !

|preprocessor=
[[EXKNO]], [[FFT]], [[FRQ2ZEITR]], [[MESKOR]], [[TSCALC]], [[UTRPRE]], [[ZEITR]], [[ZEITRIO]]
|postprocessor=
[[FDGITTER05]], [[GVIEW2D]], [[TM2RND]], [[TR2RND]], [[UNTRIM]], [[UNTRIM2]], [[UNTRIM2007]], [[ZEITR]]
|language=Fortran95
|add_software= -
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=
* please refer to $PROGHOME/examples/utrrnd/
** '''./BSP_becken_src_snk/''' : example files for a closed basin with one sink and one source.
** '''./BSP_becken_wind/''' : example files for wind influence on water level elevation and current velocity in a closed basin.
** '''./BSP_hafen/''' : example files for wave propagation in a harbour basin.
** '''./BSP_kanal_w_gradient/''' : example files for a straight channel with constant water level gradient;
** '''./BSP_kanal_w_inflow/''' : example files for a straight channel with constant inflow (discharge).
** '''./BSP_soliton /''' : propagation of a solitary wave in a straight wave channel.
** '''./BSP_becken_power_plant/''' : example files for a closed basin with one sink, where the water is immediately re-introduced at a different location with respective alteration of temperature as well as salinity (useful for simulations of the cooling of a power plant).
* there are also more general informations concerning the [[Generation of Boundary Conditions|generation of boundary conditions]] available
* especially have a look to the [[Generation of Boundary Conditions#Literature about methods|literature list]] and the graphical representation for the [[Generation of Boundary Conditions#Graphical Representations of Complex Workflows|generation of time series data from measured or simulated data]]
}}

VOLUMETH

2022-10-11T07:50:32Z

Ak3gseis:

{{ProgramDescription
|name_de=VOLUMETH
|name=VOLUMETH
|version=5.x / September 2015
|version_descr=September 2015
|catchwords=
volume method 
horizontal area distribution 
volume sum 
isolines 
finite elements topography 
|shortdescription=
The program VOLUMETH calculates horizontal area distribution and volume sum curve for regions inside a finite elements topography. The size of a horizontal area is defined by the area where the depth is greater than a given isobath. The volume sum is the volume under this defined horizontal area. Besides morphological analysis the program can be used to check model grids on their hydraulic properties (volume of water which can flow into an area). Different subregions for which the curves are calculated separately can be defined by closed polygons.

Volume calculations may be optionally executed also for a bathymetry which is derived from a finite difference grid for the mathematical model UNTRIM. Please notice that volumes computed by VOLUMETH are not identical with volumes used in UNTRIM applications. This is due to the fact, that VOLUMETH uses interpolated depth at nodes for volume computation while in UNTRIM depth values at polygon centers are used instead.

VOLUMETH supports input data of different coordinate reference systems (CRS). The user has to specify a coordinate reference system into which all coordinates will be transformed on the fly by the Environment variable BAWCRS. '''The use of BAWCRS is recommended'''! The user CRS has to be a projected system (UTM, Gauß-Krüger)!

The program VOLUMETH has been developed on the basics of GISO2D and therefore includes the complete functionality of this program. Because of that GISO2D has been moved to the program cemetery.
|inputfiles=
# input file for program flow control (type [[VOLUMETH.DAT|volumeth.dat]]).
# file with finite element mesh (type [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]] or [[UNTRIM_GRID.DAT|untrim_grid.dat]]).
# (optional) file with edge information (type [[FKVZ.BIN|fkvz.bin]]).
# (optional) file with neighbour element information (type [[FKEZ.BIN|fkez.bin]]).
# (optional) file with definitions of subregions (type [[POLY.DAT|poly.dat]]).
|outputfiles=
# file with structure information of the isobaths which were found (type [[INSEL.DAT|insel.dat]]).
# ASCII file with results of the area distribution and volume sum function (type [[VOLSUM.DAT and VOLSUM.EXCEL.DAT|volsum.dat/excel.dat]])
# or EXCEL readable file with results of the area distribution and volume sum function (type [[VOLSUM.DAT and VOLSUM.EXCEL.DAT|volsum.dat/excel.dat]]) for each subregion.
# GKS logfile (type gkslog.dat)
|methodology=
For each isobath the intersection points with the mesh are determined first. During this process the element areas are summed up, when the lie inside the area which is deeper than the isobath. If an element is intersected by the isobath or the given boundary polygon of the current region, the element shape is modified such that the non relevant area of the element is cut. As the areas, the volumes above the element surfaces are summed up.
The points are ordered by the separate isoline parts and stored in correct sequence. The output of all isoline parts is done into a file of type [[INSEL.DAT|insel.dat]].

The values of the volume sum are exact with respect to approximation of the topography and the computer accuracy!
|preprocessor=
[[FDGITTER05]], [[GISMO]], [[JANET]], [[POLYUMFORM]]
|postprocessor=
EXCEL
|language=Fortran90
|add_software= -
|contact_original=G. Seiß
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=
$PROGHOME/examples/volumeth/*

BAW, 1996: Anpassung der Fahrrinne der Unter- und Außenelbe an die Containerschiffahrt - Gutachten zur morphologischen Entwicklung der Nebenelben und Nebenrinnen seit 1945/1950. Bundesanstalt für Wasserbau, Außenstelle Küste, Hamburg.
}}

ZWISCHENPUNKTE

2022-10-11T07:48:43Z

Ak3gseis:

{{ProgramDescription
|name_de=ZWISCHENPUNKTE
|name=ZWISCHENPUNKTE
|version=January 1999
|version_descr=April 2008
|catchwords=spline-interpolation 
contour line 
topography 
morphology 
volume method
|shortdescription=The program ZWISCHENPUNKTE generates topographical information by spline-interpolation. It can be used for a better interpretation of topographical data which is based on depth contours. Also its possible to generate depth information on a polygon to be used as a system boundary.
|inputfiles=
# input-file (filetype [[ZWISCHENPUNKTE.DAT|zwischenpunkte.dat]])
# file with depth contours (filetype [[INSEL.DAT|insel.dat]])
# (optional) file with profiles (filetype [[DIGI.GKK|digi.gkk]])
# (optional) file with a talweg-polygon (filetype [[DIGI.GKK|digi.gkk]])
# (optional) file with a system boundary polygon without depth information (filetype [[DIGI.GKK|digi.gkk]])
|outputfiles=
# file with generated depth information (filetype [[GEOM.DAT|geom.dat]])
# (optional) file with points of intersection of depth contours and profiles (filetype [[GEOM.DAT|geom.dat]])
# (optional) file with depth points which define depth contours (filetype [[GEOM.DAT|geom.dat]])
# (optional) file with generated profiles (filetype [[DIGI.GKK|digi.gkk]])
# (optional) file with a system boundary polygon containing depth information (filetype [[INSEL.DAT|insel.dat]])
|methodology=
The points of intersection between depth contours and profiles are found out. On each profile the points of intersection are used as fixed points for a spline interpolation. Depth information is generated by evaluating the spline-functions between the depth contours. The evaluation is carried out at points which are located at constant distances on the profile and/or at a constant number of points which are centered equidistant between two depth contours.
Profiles can be defined in an input file, or they will be generated by the program. The generation of profiles can be carried out either by generating profiles right-angled to a talweg-polygon (which is defined in an input file) or by generating profiles right-angled to the bank. The bank is defined as the contour line at MThw level (mean tidal high-water).
Profiles which cross more than one channel are divided into new profiles (which don’t cross more than one channel).
To avoid generation of not plausible depth data a smoothing routine is carried out after evaluating the spline-functions. The smoothing is carried out, if the depth value of a generated point is not within the depth intervall of the closest depth contours that surround the neighbouring depth contours to the point. The smoothing is carried out by replacing the spline-points by points of a second degree parable. The extrem value of the parable is defined by a smoothing parameter in the input-file.
Also its possible to suppress output of spline-points which are out of a depth intervall surroundig the depth values of the neighbouring contour lines. Also its possible to suppress generation of spline-points at profiles where the distance between at least two contour lines is greater than an maximum distance. The maximum depth intervall and the maximum distance must be defined in the input file.
An extra function allows to evaluate depth information on an polygon which defines the system boundary. The depth information is found out by evaluating the intersection points of the polygon and the contour lines. It is also possible to generate depth information between the intersection points as described above. It it also possible to generate depth information by linear interpolation of the depth information at the intersection points. The depth information at the angles of the polygon is calculated by the mean value of the neighbouring intersection points.
|preprocessor=[[POLWIND]], [[POLYUMFORM]]
|postprocessor=ARCGIS, [[ArcGIS-Applications]], [[MEDIANGLAETTUNG]]
|language=Fortran90
|add_software=-
|contact_original=J. Fräßdorf
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/zwischenpunkte/* 
see also Erzeugen von synthetischen Tiefenpunkten aus Isoliniendaten, published in Supercomputing News No. 4/1998 (available in German only).
}}

ZEITRIO

2022-10-11T07:43:36Z

Ak3gseis:

{{ProgramDescription
|name_de=ZEITRIO
|name=ZEITRIO
|version=April 2021
|version_descr=April 2021
|catchwords=preprocessor 
time series 
concatenation
|shortdescription=The program ZEITRIO reads and writes data files, that contain time series in different formats. It is possible to read the file-types listed below. They can be wrote as boewrt.dat, as ASCII columns or CSV format afterwards. Concatenation of multible files is supported. A BOEWRT status flag is eventually be generated or transported.
|inputfiles=
# data file(s) with time series of type [[BOEWRT.DAT|boewrt.dat]]. A list of several files can be concatenated by the command line argument ''-srclist=<file>''.
# data file(s) with time series of type [[SOLWRT.DAT|solwrt.dat]].
# data file(s) with time series of type 6dph.dat.
# data file(s) with time series of type trbnk.dat.
# data file(s) with time series of type aander.dat.
# data file(s) with time series of type dwdwin.dat.
# data file(s) with time series of type WSA Bremen.
# data file(s) with time series of type peg.dat.
# data file(s) with time series of type pegel.his.
# data file(s) with time series of type extab.dat (Excel table with separators Blanks, Tabs, comma, semicolon).
# data file(s) with time series of type WSA Emden.
# data file(s) with time series of type column oriented MATLAB matrix.
# data file(s) with time series of type ZRX.
# data file(s) with time series of type WOCE gauge data.
# data file(s) with time series of type [[KNOERG.BIN|knoerg.bin]].
# data file(s) with time series of type CSV of the BfG "Pegel-Online" Service.
# data file(s) with time series of type CSV provided by ftp://ftp-cdc.dwd.de/pub/CDC/
# data file(s) with time series of type ALL (Kisters export of WISKI database)
# netCDF files with timeseries from http://www.marineinsitu.eu/dashboard/
# generic CSV file interface allowing free choice of columns .
# optional input data of type [[ZEITRIO.DAT|zeitrio.dat]]. This file defines time intervals in case that the output ([[BOEWRT.DAT|boewrt.dat]] only) should be devided into several seperate files of a certain length.
|outputfiles=
The number of output file types was limited to really useful standard formats.
# data file with time series of type [[BOEWRT.DAT|boewrt.dat]] (output modes 1 and 2)..
# data file with time series as ASCII-columns and a separate header file (a format which can be used with MATLAB, SCILAB or Mathematica)
# data file with time series of type CSV with an one line header of type (Zeitpunkt; property 1; property 2; ....) for [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS] (output mode 4).
# printer protocol file (zeitrio.sdr).
# (optional) terminal input protocol of type gkslog.dat.
|methodology=After defining a reference date, which is important when reading or writing a file with relative time information (e.g. solwrt.dat) a time series file is read. Please note, that only one time series at one knot can be read and processed at the same time. Optionally further time series files can be concatenated then. The file type can be switched for each file to read. After reading process has finished, the time series will be ordered chronologically and double as well as unvalid times are rejected.

The time series are wrote to a file using the format defined by the user. If writing [[BOEWRT.DAT|boewrt.dat]] there is the additional option to write defined time intervals (e.g. days) into separate files. The date of the day is part of the file name. Measured values additionally get the BOEWRT status flag 2 ("untested") where the flag data are not read from the input file. Calculated values ("knoerg.bin") get the status "good" (1).

Optionally the time series will be interpolated to equidistant time steps. Larger time gaps can optionally filled with a dummy value (fill value, output mode 1) or eliminated (output mode 2) on output. The user defines a minmal value for time gaps to be recognized large. The printer protocol file provides information about significant gaps in time axis. Interpolation of smaller gaps is be done alternatively by spline or linear interpolation. The BOEWRT status flag indicates whether the values are interpolated. Those values get the flags "untested", "interpolated" and eventually "good" or "suspicious".

The output time period is determined by the interactive user input. If several input files are read during one cycle, the first start time and last end time determine the output period. If output mode 1 is chosen, eventually fill values are added during equidistant interpolation before the first valid measurement time and after the last valid measurement time. Unlike Versions before February 2020, the program doesent stop with an error, if the time period, specified by the user is not completely covered.
Check output files and standard output for warnings!

'''Attention:''' Versions before February 2020 were not able to correctly deal with fill values during interpolation of more than one physical quantity at once. Now this functionality is implemented. But still check your results! BOEWRT timeseries for input can start with empty data records ("fill_values") since version 2020_10_15 to be processed anyway.

Time series of type MATLAB matrix, ZRX or "exctab.dat" can be filtered and recalculated with an offset and scaling for the data values. Absolute date and time will always be calculated by special operators with high accuracy.

During reading and interpolation, eventually a BOEWRT status flag is created. Check correctness of those flags befor further processing the files.

Since Version June 2020 interpolation of BOEWRT status flags takes the neighbouring flag values into account. If both neighbours are "good", the interpolated value becomes "good" too. If one of them is "suspicious", the interpolated flag becomes "suspicious". Interpolated values are always "untested"!

The number of interactiv dialogs can be reduced by giving command line arguments. This feature is available since version 2020_10_15. The command '''''zeitrio[.i18] -h''''' helps in using this feature.

An executable is available for LINUX as well as WINDOWS platforms.

|preprocessor=spreadsheet software (e.g. [https://en.wikipedia.org/wiki/Microsoft_Excel MS Office EXCEL], [https://en.wikipedia.org/wiki/LibreOffice_Calc LibreOffice Calc] ),[[FFT]], [[FRQ2ZEITR]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [http://www.scilab.org/ SCILAB], [[TSCALC]], [[TRIM-2D]], [[TRIM-3D]], [[XTRDATA]]
|postprocessor=[[BOERND]], [[DATACONVERT]], [[EXCELENZ]], [[FFT]], [[FRQWF]], [[GVIEW2D]], [http://www.mathworks.co.uk/products/matlab/index.html?s_tid=gn_loc_drop MATLAB], [[MESKOR]], [[ROSE]], [http://www.scilab.org/ SCILAB], [[TIDKEN]], [[TSCALC]], [[UTRRND]], [http://www.deltares.nl/en/software/479962/delft-fews Delft-FEWS]
|language=Fortran2003
|add_software= libgeodesy, NTv2 mesh files for coordinate transformation (see also [[GEOTRANSFORMER]]).
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/zeitrio
}}

TR2REFRESH

2022-10-10T15:00:56Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2REFRESH
|name=TR2REFRESH
|version=V4.x / January 1999
|version_descr=April 2008
|catchwords=
preprocessor 
finite difference method 
mathematical models [[Mathematical Model TRIM-2D|TRIM-2D]], [[Mathematical Model TRIM-3D|TRIM-3D]] 
manipulation of grid 
actualization of bathymetry 
deepening and refillment
|shortdescription=
The program TR2REFRESH serves as a preprocessor for the numerical models [[Mathematical Model TRIM-2D|TRIM-2D]] and [[Mathematical Model TRIM-3D|TRIM-3D]]. TR2REFRESH is able to modify bathymetry of a TRIM computational grid according to depth information stored on a finite element grid or along structural lines. The area where bathymetry shall be modified can be restricted to an area inside or outside an arbitrary polygon.

The actual nodal depth can be modified in the following different ways by means of different modification options::
# uncoditional deepening/refillment: at all modification nodes the actual depth is modified with the modification value
# unconditioanl setting of the depth: at all modification nodes the actual depth is set to the modification value
# conditional deepening: at all modification nodes where the actual depth is smaller than the modification value the depth will be set to the modification value. Areas which are already deeper than the depth given by the modification value remain unchanged
# conditional refillment: at all modification nodes where the actual depth is larger than the modification value the depth will be set to the modification value. Areas which are shallower than the depth given by the modification value remain unchanged.

The modification value follows from the actual location of a node within the grid (depths of the grid defining real bathymetry or the a so called dredger bathymetry).
|inputfiles=
# general input data (filetype [[TR2REFRESH.DAT|tr2refresh.dat]]).
# (optional) surrounding polygon (filetype [[POLY.DAT|poly.dat]]).
# (optional) protected nodes (filetype [[NODES.SAVE|nodes.save]]).
# computational grid and asis bathymetry (filetype [[TR2.TOPO.BIN|tr2.topo.bin]])
# (optional) bathymetry/dredger-bathymetry of the model area which shall be modified (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]]).
|outputfiles=
# modified bathymetry (filetype [[TR2.TOPO.BIN|tr2.topo.bin]]).
# printer file (filetype tr2refresh.sdr).
# (optional) trace of program execution (filetype tr2refresh.trc).
|methodology=
For all nodes of a TRIM computational grid which are lying in the area defined by a surrounding polygon new depth values are calculated first for the so called ZETA-locations of the grid cells from the the values defined by the bathymetry/dredger-bathymetry. From these results the values are interpolated onto the locations of the U- and V-nodes by means of one of the following approaches:
* Depths at U- and V-points are mean values of the corresponding ZETA-points. Therefore the depths are approximated in the best possible way and the speed of the tidal wave can be calculated correctly. On the other hand side the volume of the system under investigation may be overestimated systematically.
* Depths at U- and V-points are minimum values of the corresponding ZETA-points. This guarantees the best approximation of the volume, but depths at U- and V-points are underestimated systematically. Therefore computed wave speed may be also underestimated.
Furthermore depths at selected U- and/or V-positions (computational points of a TRIM-grid) may be optionally modified using one of the following methods:
* mapping of depths along so called protection polygons (given in a file of type [[NODES.SAVE|nodes.save]]) by means of interpolation;
* direct setting of the depth values if the nodal locations (also prescribed in a file of type [[NODES.SAVE|nodes.save]]) are identical with the locations of the U- and V- computational points.

These methods are activated if a file of type [[NODES.SAVE|nodes.save]] has been prescribed in the input data file.
|preprocessor=[[FD2TRIM]], [[TC2TR2]], [[UPDA2D]]
|postprocessor=[[TR2VOR]], [[TRGITTER05]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2refresh/
}}

TR2LQ2

2022-10-10T14:53:50Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2LQ2
|name=TR2LQ2
|version=November 1996
|version_descr=September 1999
|catchwords=preprocessor 
profile bathymetry 
extraction of bathymetry at profiles 
numerical model TRIM-2D 
numerical model TRIM-3D
|shortdescription=The program TR2LQ2 is a preprocessor for the mathematical models TRIM-2D and TRIM-3D. It was designed to extract bathymetry-data along longitudinal or cross-sectional profiles from a TRIM bathymetry and index arrays containing file. Every profile is defined by a sequence of an arbitrary number of 2D-locations which are connected by straight lines. Additional points can be easily inserted automatically at regular intervals in between these 2D-locations.
|inputfiles=
# general input data (filetype [[TR2LQ2.DAT|tr2lq2.dat]])
# (optional) old profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# (optional) profiles (filetype [[PROF.BIN|prof.bin]])
# several other files are necessary to define the 2D-Locations and profiles where data shall be extracted (see documentation for the file [[TR2LQ2.DAT|tr2lq2.dat]])
# bathymetry and index arrays (filetype [[TR2.TOPO.BIN.IND|tr2.topo.bin.ind]])
|outputfiles=
# profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# decriptions of all geo positions divided into profiles (filetype [[GPROFIL.DAT|gprofil.dat]])
# depth values of all points divided into profiles (filetype [[TPROFIL.DAT|tprofil.dat]])
# informative printer file (filetype tr2lq2.sdr)
# (optional) trace of program execution (filetype tr2lq2.trc)
|methodology=A comprehensive profile-topography is generated from the various input-data. 2D-locations are gathered to form profiles. Additional new points can be automatically inserted in between these locations at arbitrary intervals. Bathymetric depth is calculated as the maximum of the depth values given at the four computational nodes (U- and V- points) defining a cell in the computational grid. Text-strings can be related to locations and profiles. A list of node numbers as well as connexion-tables are generated for all segments. Optional information is also generated for data-interpolation (used by subsequent post-processors). New bathymetry data can overwritten to an already existing profile-topography.
|preprocessor=[[CROSSPRO]], [[DEPRO2D]]
|postprocessor=[[ADCP2PROFILE]], [[TRIM-2D]], [[TRIM-3D]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2lq2/
}}

TR2LQ2

2022-10-10T14:53:22Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2LQ2
|name=TR2LQ2
|version=November 1996
|version_descr=September 1999
|catchwords=preprocessor 
profile bathymetry 
extraction of bathymetry at profiles 
numerical model TRIM-2D 
numerical model TRIM-3D
|shortdescription=The program TR2LQ2 is a preprocessor for the mathematical models TRIM-2D and TRIM-3D. It was designed to extract bathymetry-data along longitudinal or cross-sectional profiles from a TRIM bathymetry and index arrays containing file. Every profile is defined by a sequence of an arbitrary number of 2D-locations which are connected by straight lines. Additional points can be easily inserted automatically at regular intervals in between these 2D-locations.
|inputfiles=
# general input data (filetype [[TR2LQ2.DAT|tr2lq2.dat]])
# (optional) old profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# (optional) profiles (filetype [[PROF.BIN|prof.bin]])
# several other files are necessary to define the 2D-Locations and profiles where data shall be extracted (see documentation for the file [[TR2LQ2.DAT|tr2lq2.dat]])
# bathymetry and index arrays (filetype [[TR2.TOPO.BIN.IND|tr2.topo.bin.ind]])
|outputfiles=
# profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# decriptions of all geo positions divided into profiles (filetype [[GPROFIL.DAT|gprofil.dat]])
# depth values of all points divided into profiles (filetype [[TPROFIL.DAT|tprofil.dat]])
# informative printer file (filetype tr2lq2.sdr)
# (optional) trace of program execution (filetype tr2lq2.trc)
|methodology=A comprehensive profile-topography is generated from the various input-data. 2D-locations are gathered to form profiles. Additional new points can be automatically inserted in between these locations at arbitrary intervals. Bathymetric depth is calculated as the maximum of the depth values given at the four computational nodes (U- and V- points) defining a cell in the computational grid. Text-strings can be related to locations and profiles. A list of node numbers as well as connexion-tables are generated for all segments. Optional information is also generated for data-interpolation (used by subsequent post-processors). New bathymetry data can overwritten to an already existing profile-topography.
|preprocessor=[[CROSSPRO]], [[DEPRO2D]]
|postprocessor=[[ADCP2PROFILE]], [[TRIM-2D]], [[TRIM-3D]]
|language=Fortran77
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2lq2/
}}

TR2VOR

2022-10-10T14:52:14Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2VOR
|name=TR2VOR
|version=November 1997
|version_descr=November 1997
|catchwords=preprocessor 
bathymetry and index arrays 
numerical model TRIM-2D 
numerical model TRIM-3D
|shortdescription=
The program TR2VOR serves as a preprocessor for the mathematical models TRIM-2D and TRIM-3D. On the one hand side the program generates a very compact version of the models bathymetry (with the aim to reduce the amount of memory needed to store the depths at all computational points). On the other hand side some additional index arrays are also generated which are required for an optimized program execution on vector and/or parallel computers with shared memory.
|inputfiles=
# general input data (filetype [[TR2VOR.DAT|tr2vor.dat]])
# bathymetry (filetype [[TR2.TOPO.BIN|tr2.topo.bin]])
|outputfiles=
# bathymetry and index arrays (filetype [[TR2.TOPO.BIN.IND|tr2.topo.bin.ind]])
# (optional) trace of program execution (filetype tr2vor.trc)
|methodology=
From a fully two-dimensional matrix (bathymetrical depths) an optimized compact form is generated by this program. The optimized form does contain only one singular grid cell representing dry land (a dry land grid cell will never be flooded by water during the whole simulation). This single cell is a representative for all dry land cells in the modelling domain. To manage this in a good way, some index arrays are generated which allow for a proper identification of the correct geographical location of all cells (dry or wet).

Additionally index arrays are generated with the list of all red and black grid cells as well as lists for neighbourhood relationships (lower, right, top and left neighbour of a computational cell). The existence of these lists is a necessary prerequisite for any optimized vector-parallel program execution on multiprocessor vector machines using shared memory.
|preprocessor=[[FD2TRIM]], [[TC2TR2]], [[TR2REFRESH]], [[TRGITTER05]]
|postprocessor=[[TRIM-2D]], [[TRIM-3D]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2vor/
}}

TRGITTER05

2022-10-10T14:48:58Z

Ak3gseis:

{{ProgramDescription
|name_de=TRGITTER05
|name=TRGITTER05
|version=April 1997
|version_descr=November 2003
|catchwords= preprocessor 
finite difference method Trim-2D 
display topography 
change topography (not realized yet) 
display boundary grid cells (not realized yet) 
change boundary grid cells (not realized yet)
|shortdescription=
visualizing and changing a Trim-2D grid. 
the following functions are realized to [[TRGITTER05: visualization examples of a Trim-2D-grid|display a Trim-2D grid]]:
#[[TRGITTER05: visualization examples of a Trim-2D-grid#grid lines|grid lines]] (different colours for dry and wet cell edges)
#[[TRGITTER05: visualization examples of a Trim-2D-grid#depth numbers + grid lines|grid depth values]] (displaying depth values for u-, v- and zeta-points with different uniform or shade colours)
#[[TRGITTER05: visualization examples of a Trim-2D-grid#u- and v-depth edges|area shading]] (displaying all cells by filling these cells with shading colours)
#[[TRGITTER05: visualization examples of a Trim-2D-grid#isolines + grid lines|depth isolines]] (displaying along cell edges)
#[[TRGITTER05: visualization examples of a Trim-2D-grid#grid border + grid lines|grid borderline]] (displaying dry cell edges when lying nearby wet cells)
added functions:
#displaying islands and other structures
#displaying [[TRGITTER05: visualization examples of a Trim-2D-grid#echo-sound data + grid lines|echo-sound data]]
#GKS-editor
#automatic saving of created pictures (cgm- or gksm-format)
the following functions are highly desirable but not yet realized to change a Trim-2D grid:
#change single depth values for u-, v- or zeta-points
#change a group of depth values in an identical way
#change the dry/wet-code of cells
#change the whole number of cells in north-south- or/and east-west-direction
|inputfiles=
#general input data (file of type [[TRGITTER05.DAT|trgitter05.dat]])
#Trim-2D grid (file of type [[TR2.TOPO.BIN|tr2.topo.bin]])
#layout (file of type [[LAYOUT.DAT|layout.dat]])
#colour table definitions file (file of type [[LIGHTS.DAT|lights.dat]])
#colours file (file of type [[COLORS.DAT|colors.dat]])
#definition of additional isolines for bathymetry (file of type [[ISOERG.DAT|isoerg.dat]])
#(optional) definition of static frames (file of type [[FRAMES.DAT|frames.dat]])
#(optional) structural lines (file of type [[INSEL.DAT|insel.dat]])
#(optional) echo-sound data (file of type [[GEOM.DAT|geom.dat]])
#(optional) company logo (file of type bawlogo.dat)
#(optional) stamp information (file of type stamp.dat)
For TRGITTER05 the following standard configuration files from the directory '''$PROGHOME/public/cfg/''' are required:
:* GKS parameter file: '''gkssystem.computername.dat'''
:* definition of physical quantities and physical units: '''phydef.cfg.deen.dat and phydef.cfg.rest.dat'''
|outputfiles=
#graphical output to the screen
#plot metafiles (GKS, CGM, and others)
#informative printer file (file of type trgitter05.sdr)
#(optional) trace of program execution (file of type trgitter05.trc)
|methodology= -
|preprocessor= [[FD2TRIM]], [[POLWIND]], [[TC2TR2]], [[TR2REFRESH]]
|postprocessor=[[EDITOR]], [[TOUTR]], [[TR2VOR]]
|language=Fortran90
|add_software=GKS (graphical kernel system)
|contact_original=J. Jürges
|contact_maintenance= [mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/trgitter05
}}

TRASSE

2022-10-10T14:46:16Z

Ak3gseis:

{{ProgramDescription
|name_de=TRASSE
|name=TRASSE
|version=February 1996
|version_descr=April 2008
|catchwords=preprocessor 
modification of topography 
deepening and refillment
|shortdescription=The program TRASSE is a preprocessor which is used to generate nodal points for the later generation of a finite element grid (dredger grid). A polygon is given to the program by the user. The program generates sufficient additional nodal points to generate a grid at a later stage of the production line. In addition to the polygon data the width of the inner part (width of the fairway), the width of the lateral areas (slopes of the fairway) as well as the inclination of the slopes have to be prescribed. Furthermore the mean distances between nodal points along the fairway as well as orthogonal to it are required.
|inputfiles=general input-data (filetype [[TRASSE.DAT|trasse.dat]])
|outputfiles=
# nodal points as structural informations (filetype [[INSEL.DAT|insel.dat]])
# printer file (filetype trasse.sdr)
# (optional) trace of program execution (filetype trasse.trc)
|methodology=Starting with the given polygon parallel straight lines are generated whose direction is coincident with the directions of the different sections of the polygon. If the polygon is not a straight line but has a number of bends the intersections between the straight lines are automatically calculated. The resulting segments are subdivided conforming to the users requirements. In this way all nodal coordinates are generated. The depth of the nodes is calculated from the (orthogonal) distance to the polygon and the inclinations of the inner and lateral areas
|preprocessor=digitizer
|postprocessor=[[JANET]]
|language=Fortran90
|add_software=-
|contact_original=O. Kacholdt, G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/trasse
}}

TR2FIDI

2022-10-10T14:45:14Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2FIDI
|name=TR2FIDI
|version=July 1997
|version_descr=July 1997
|catchwords=finite differences, grid conversion
|shortdescription=The program TR2FIDI converts a TRIM topography back to a topography for the method FIDISOR/FIDIRB. This conversion is neccesary, when a FIDISOR/FIDIRB topography is needed to do modifications but the only existing topography in the specified resolution is a TRIM topography (created with FD2TRIM from a grid of different resolution).
|inputfiles=
# ile with input data for program control (type [[TR2FIDI.DAT|tr2fidi.dat]])
# file with TRIM topography (type [[TR2.TOPO.BIN|tr2.topo.bin]])
|outputfiles=
# file with FIDISOR/FIDIRB topography (type [[TOPO.BIN|topo.bin]])
|methodology=
:All steps of the program FD2TRIM are ecvaluated backwards. 

'''Remark:''' 

:Interpolation to other grid spacing as with the program FD2TRIM is not possible! Naturally the quality of the topography is worse after several conversions.
|preprocessor=[[FD2TRIM]], [[TC2TR2]]
|postprocessor=FD2CUT, [[FD2DEL]], [[FD2TRIM]], [[FDGITTER05]] a.o.
|language=Fortran90
|add_software=-
|contact_original=E. Rudolph
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2fidi/*
}}

TR2FIDI

2022-10-10T14:44:46Z

Ak3gseis:

{{ProgramDescription
|name_de=TR2FIDI
|name=TR2FIDI
|version=July 1997
|version_descr=July 1997
|catchwords=finite differences, grid conversion
|shortdescription=The program TR2FIDI converts a TRIM topography back to a topography for the method FIDISOR/FIDIRB. This conversion is neccesary, when a FIDISOR/FIDIRB topography is needed to do modifications but the only existing topography in the specified resolution is a TRIM topography (created with FD2TRIM from a grid of different resolution).
|inputfiles=
# ile with input data for program control (type [[TR2FIDI.DAT|tr2fidi.dat]])
# file with TRIM topography (type [[TR2.TOPO.BIN|tr2.topo.bin]])
|outputfiles=
# file with FIDISOR/FIDIRB topography (type [[TOPO.BIN|topo.bin]])
|methodology=
:All steps of the program FD2TRIM are ecvaluated backwards. 

'''Remark:''' 

:Interpolation to other grid spacing as with the program FD2TRIM is not possible! Naturally the quality of the topography is worse after several conversions.
|preprocessor=[[FD2TRIM]], [[TC2TR2]]
|postprocessor=FD2CUT, [[FD2DEL]], [[FD2TRIM]], [[FDGITTER05]] a.o.
|language=Fortran77
|add_software=-
|contact_original=E. Rudolph
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tr2fidi/*
}}

TOPVF

2022-10-10T14:43:50Z

Ak3gseis:

{{ProgramDescription
|name_de=TOPVF
|name=TOPVF
|version=September 1995
|version_descr=June 1997
|catchwords=Calculation of 2D/3D areas and volumes, finite element topography
|shortdescription=The program TOPVF calculates 2D/3D areas and volumes which lie between two arbirary referenc surfaces. Optinal the calculations can be done also for horizontal layers and columns sorted into depth classes.
|inputfiles=
# file with input data for program flow control (filetype [[TOPVF.DAT|topvf.dat]])
# file containing the finite elements mesh (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
|outputfiles=
# in table format for further processing with graphics software (e.g. Harvard Graphics)
# printer file topvf.sdr
|methodology=-
|preprocessor=programs for generation and modification of finite element meshes
|postprocessor=graphics programs
|language=Fortran90
|add_software=-
|contact_original=O. Kacholdt, G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/topvf
}}

TOUTR

2022-10-10T14:35:57Z

Ak3gseis:

{{ProgramDescription
|name_de=TOUTR
|name=TOUTR
|version=October 1999
|version_descr=April 2008
|catchwords=numerical model Untrim 
conversion of gridfile format
|shortdescription=programm toUtr reads gridfiles of different formats and writes these grids onto new files in Untrim gridfile format.
|inputfiles=
# program steering file (filetype [[TOUTR.DAT|toutr.dat]])
# finite element grid (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# 2D finite difference grid of hydro-numerical method [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/trim2d1.pdf Trim-2D] (filetype [[TR2.TOPO.BIN|tr2.topo.bin]])
|outputfiles=
# Untrim gridfile (filetype [[UNTRIM_GRID.DAT|untrim_grid.dat]])
# informative printer file (filetype toUtr.sdr)
|methodology=
first of all the program reads a dictionary file (filetype toUtr_dico.dat), which describes the principle structure of the program steering file. After this the program is able to read and evaluate the program steering file (filetype [[TOUTR.DAT|toutr.dat]]) Four steps are to be done to generate an Untrim gridfile out of a gridfile of any type:
* Read input grid from file into a type-specific grid data structure;
* Convert the type-specific grid data into a universal (unspecific) grid data structure (you will find more about this universal data structure in a portable document file [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/unigrid.pdf "Unigrid"] );
* Store unspecific grid data in Untrim grid data structure;
* Write Untrim type-specific grid data to file (filetype [[UNTRIM_GRID.DAT|untrim_grid.dat]])
|preprocessor=[[FD2TRIM]], [[JANET]], [[TC2BAGGER]], [[TR2GEOM]], [[TRGITTER05]], [[UPDA2D]]
|postprocessor=[[UNTRIM]]
|language=Fortran90
|add_software=-
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=* PDF [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/unigrid.pdf "Unigrid"] with information about the universal grid data structure
* $PROGHOME/examples/toUtr
}}

TM2RND

2022-10-10T14:34:46Z

Ak3gseis:

{{ProgramDescription
|name_de=TM2RND
|name=TM2RND
|version=3.x / August 2003
|version_descr=April 2008
|catchwords=preprocessor 
finite element grid 
boundary value generation 
numerical model TELEMAC-2D
|shortdescription=
The program TM2RND is a preprocessor for the numerical model TELEMAC-2D. TM2RND handles available time-series data-sets (hydrodynamics, salinity) and converts them into a special data format, which can be used in a TELEMAC-2D simulation run. The data which are used to define time- and space-dependent boundary conditions can be rapidly accessed by TELEMAC-2D through a modified TELEMAC-subroutine called BORD_baw.f.
|inputfiles=
# general input-data (filetype [[TM2RND.DAT|tm2rnd.dat]])
# boundary conditions (filetype [[RNDWERTE.DAT|rndwerte.dat]])
# grid (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# optimized grid (filetype [[SELAFIN|selafin]])
# boundary conditions file (filetype [[CONLIM.DAT|conlim.dat]])
|outputfiles=
# modified boundary conditions file (filetype [[CONLIM.DAT|conlim.dat]])
# boundary values file for hydrodynamics (filetype [[TM2.RBH.BIN.I|tm2.rbh.bin.i]] and filetype [[TM2.RBH.BIN|tm2.rbh.bin]])
# (optional) boundary values file for salinity (filetype [[TM2.RBS.BIN.I|tm2.rbs.bin.i]] and filetype [[TM2.RBS.BIN|tm2.rbs.bin]])
# informative printer file (filetype tm2rnd.sdr); please check the contents of this file after program execution
# (optional) trace of program execution (filetype tm2rnd.trc)
|methodology=
TM2RND relates the time-series data to the boundary nodes of the modell area. The correct TELEMAC-2D boundary code is also set automatically in the output-file of type conlim.dat. Additionally the program checks whether for all nodal points where a boundary condition was indicated in the input-file of type conlim.dat the coresponding data were defined in a file of type rndwerte.dat. The time-series data are stored as separate records in a direct access file.
|preprocessor=[[BOERND]], [[TICTRI]], [[TSCALC]], [[UTRRND]]
|postprocessor=[[TELEMAC-2D]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tm2rnd/ 
TELEMAC-2D Modelling System - Users Manual
}}

TICLQ2

2022-10-10T14:33:34Z

Ak3gseis:

{{ProgramDescription
|name_de=TICLQ2
|name=TICLQ2
|version=2.x / September 2013
|version_descr=Sepetmber 2013
|catchwords=preprocessor 
profile bathymetry 
extraction of bathymetry at profiles
|shortdescription=The program TICLQ2 is a preprocessor which is model-independent. It was designed to extract bathymetry-data along longitudinal or cross-sectional profiles. Every profile is defined by a sequence of an arbitrary number of 2D-locations which are connected by straight lines. Additional points can be easily inserted automatically at regular intervals in between these 2D-locations.
|inputfiles=
# general input data (filetype [[TICLQ2.DAT|ticlq2.dat]])
# (optional) old profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# (optional) profiles (filetype [[PROF.BIN|prof.bin]])
# several other files are necessary to [[GEOPOS.DAT|define the 2D-Locations]] and profiles where data shall be extracted (see documentation for the file ticlq2.dat)
# grid(s) (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]], [[UNTRIM_GRID.DAT|untrim_grid.dat]])

|outputfiles=
# profile-topography (filetype [[PROFIL05.BIN|profil05.bin]])
# decriptions of all geo positions divided into profiles (filetype [[GPROFIL.DAT|gprofil.dat]])
# structure type DAMM for every Profile as a separate file (filetype [[INSEL.DAT|insel.dat]]
# depth values of all points divided into profiles (filetype [[TPROFIL.DAT|tprofil.dat]])
# informative printer file (filetype ticlq2.sdr)
# (optional) trace of program execution (filetype ticlq2.trc)

|methodology=A comprehensive profile-topography is generated from the various input-data. 2D-locations are gathered to form profiles. Additional new points can be automatically inserted in between these locations at arbitrary intervals. Bathymetric depth is calculated at the points by means of interpolation from the grid-file. Text-strings can be related to locations and profiles. A list of node numbers as well as connexion-tables are generated for all segments. Optional information is also generated for data-interpolation (used by subsequent post-processors). New bathymetry data can be added in an incremental way to an already existing profile-topography. On input points can be given in coordinate reference Systems different from the one, in which the topography mesh is defined. In this case the user must set the Environment variable BAWCRS to the latter CRS.
|preprocessor=[[ADCP2PROFILE]], [[CROSSPRO]], [[DEPRO2D]], Perl script insel_to_profiles
|postprocessor=[[ADCP2PROFILE]], [[TELEMAC-2D]], [[TIMESHIFT]], [[UNTRIM]], [[UTRPRE]], [[XTRLQ2]]
|language=Fortran95
|add_software=libgeodesy
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/ticlq2/
}}

TIDKEN

2022-10-10T14:31:45Z

Ak3gseis:

{{ProgramDescription
|name_de=TIDKEN
|name=TIDKEN
|version=October 1999
|version_descr=December 2000
|catchwords=analyses of measured data 
analyses of numerically calculated data 
tidal characteristic numbers of water level 
tidal characteristic numbers of current velocity 
tidal characteristic numbers of salinity 
comparative statistical data for tidal characteristic numbers 
estuary 
postprocessor 
|shortdescription=
Program TIDKEN belongs to the various postprocessing programs of different [[Mathematical Models for Coastal Areas and Estuaries|mathematical models]]. In addition to numerically calculated results also measured data can be used as input. The program allows a (semi-) automatic computation of tidal characteristic numbers for different (computed and/or measured) time series given at individual locations. The following characteristic numbers can be obtained:

*[http://www.baw.de/methoden_en/index.php5/Tidal_Characteristic_Numbers_of_Water_Level tidal characteristic numbers of water level]
:*[[Tidal_Characteristic_Numbers_of_Water_Level#High Water Level (HW)|High Water HW ]]
:*[[Tidal_Characteristic_Numbers_of_Water_Level#Low Water Level (LW)|Low Water LW]]
:*[[Tidal_Characteristic_Numbers_of_Water_Level#Tidal Range|Tidal Range]]
:*[[Tidal_Characteristic_Numbers_of_Water_Level#Flood Period|Flood Period]]
:*[[Tidal_Characteristic_Numbers_of_Water_Level#Ebb Period|Ebb Period]]
:*[[Tidal_Characteristic_Numbers_of_Water_Level#High Water Time (T_HW)|High Water Time T_HW]]
:*[[Tidal_Characteristic_Numbers_of_Water_Level#Low Water Time (T_LW)|Low Water Time T_LW]]
:*frequency distribution
*[[Tidal Characteristic Numbers of Current|tidal characteristic numbers of current velocity]]
:*[[Tidal Characteristic Numbers of Current#Flood Current|flood current]]
::*[[Tidal Characteristic Numbers of Current#Flood Current|Maximum Flood Current Velocity]]
::*[[Tidal Characteristic Numbers of Current#Flood Current|Mean Flood Current Velocity]]
::*[[Tidal Characteristic Numbers of Current#Flood Current|Flood Current Duration]]
::*[[Tidal Characteristic Numbers of Current#Flood Current|Slack Water Time of Flood Current]]
::*[[Tidal Characteristic Numbers of Current#Flood Current|Flood Path]]
::*frequency distribution
:*[[Tidal Characteristic Numbers of Current#Ebb Current|ebb current]]
::*[[Tidal Characteristic Numbers of Current#Ebb Current|Maximum Ebb Current Velocity]]
::*[[Tidal Characteristic Numbers of Current#Ebb Current|Mean Ebb Current Velocity]]
::*[[Tidal Characteristic Numbers of Current#Ebb Current|Ebb Current Duration]]
::*[[Tidal Characteristic Numbers of Current#Ebb Current|Slack Water Time of Ebb Current]]
::*[[Tidal Characteristic Numbers of Current#Ebb Current|Ebb Path]]
::*frequency distribution
*[[Tidal Characteristic Numbers of Salinity|tidal characteristic numbers of salinity]]
::*[[Tidal Characteristic Numbers of Salinity#Flood Current|Maximum Salinity during a Tidal Cycle]]
::*[[Tidal Characteristic Numbers of Salinity#Flood Current|Minimum Salinity during a Tidal Cycle]]
::*[[Tidal Characteristic Numbers of Salinity#Flood Current|Variation of Salinity during a Tidal Cycle]]
::*frequency distribution

In addition to the above mentioned tidal characteristic numbers comparative statistical data may be also calculated when two different time series are analysed at the same time.

The program [[TDKTIE]] link the several result files and generates for example a table with the tidal characteristic numbers along a profile.
|inputfiles=
# general input data (filetype [[TDKNEU.DAT|tdkneu.dat]]).
# measured or numerically computed time series (filetype [[BOEWRT.DAT|boewrt.dat]] or [[KNOERG.BIN|knoerg.bin]]).
|outputfiles=
# (optional) lineprinter file with results of a single data analysis (filetype tidken.e.sdr).
# (optional) lineprinter file with results of comparative analysis (filetype tidken.v.sdr);
#:in addition a few ASCII files with analyses results of filetype [[ZEILE.TIDKEN.DAT|zeile.tidken.dat]]):
#:water level (zeile.H.xxx.dat and zeile.h.xxx.dat, x=001, ... 999)
#:current velocity (zeile.V.dat and zeile.v.dat)
#:and salinity (zeile.z.dat).
# (optional) binary file with results of a single data analysis (filetype tidken.e.bin).
# (optional) trace of program execution (filetype tidken.trc).
|methodology=
* in a first step a time serie which shall be subsequently analysed may be optionally filtered before (e.g. bandpass filter);
* thereafter a (semi-) automatic computation of tidal characteristic numbers will be carried through; for this step some user prescribed parameters are required;
* if necessary also a comparative analysis is carried through.
|preprocessor=[[EXCELENZ]], [[FFT]], [[MESKOR]], [[TSCALC]], [[XTRDATA]], [[ZEITRIO]]
|postprocessor=[[TDKTIE]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang, P. Schade, I. Uliczka
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=please refer to $PROGHOME/examples/tidken/
}}

TICTRI

2022-10-10T14:30:31Z

Ak3gseis:

{{ProgramDescription
|name_de=TICTRI
|name=TICTRI
|version=January 1996
|version_descr=April 2008
|catchwords=preprocessor 
finite element grid 
grid generation 
numerical model TELEMAC-2D
|shortdescription=The program TICTRI is a preprocessor for the numerical model TELEMAC-2D. TICTRI converts a finite element grid from TICAD-format to an equivalent grid in TRIGRID-format. Additional informations about boundary nodes and the type of the boundary conditions are generated by TICTRI too.
|inputfiles=
# general input-data (filetype [[TICTRI.DAT|tictri.dat]])
# grid which shall be converted (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# boundary conditions (filetype [[RNDWERTE.DAT|rndwerte.dat]])
|outputfiles=
# nodal point connexions in TRIGRID-format (filetype [[TRIANG.DAT|triang.dat]])
# list of neighbour nodes, coordinates and boundary informations (filetype [[NEIGH.DAT|neigh.dat]])
# (optional) trace of program execution (filetype tictri.trc)
|methodology=The nodal connexions are left unchanged but the node numbers are augmented by 1. Additionally all neighbours of a node are determined. The boundary condition file of type rndwerte.dat is interpreted and every boundary node is assigned a unique TRIGRID colour-code number.
|preprocessor=[[JANET]], [[TC2BAGGER]], [[UPDA2D]]
|postprocessor=[[TM2RND]]
|language=Fortran77
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tictri

TELEMAC-2D Modelling System - Users Manual
}}

TIMESHIFT

2022-10-10T14:29:30Z

Ak3gseis:

{{ProgramDescription
|name_de=TIMESHIFT
|name=TIMESHIFT
|version=1.1
|version_descr=December 2008
|catchwords=ADCP moving ship measurement 
comparison of measurement and model 
profile 
correction / shifting of data in time 
actual time 
target time
|shortdescription=The program TIMESHIFT performs a correction in time of model results on profile data. This improves the comparibility between model results and measurements for long profiles. Target times taken from an ADCP moving ship measurement are necessary for this purpose. They are computed from the mean measurement time and the measure time difference relative desired time with desired time meaning the mean measurement time. The time difference has to be available for each data point of the profile. The program ADCP2PROFILE generates this data.

The model result files are called actual time files from now on, whereas the measured data is contained in the target file. TIMESHIFT corrects all actual times in a two step procedure. The first step is the addition of the location dependant time difference relative desired time at every location. The dataset, which has the smallest difference towards the new target time, gets selected. Its values of the measure are stored for that location.

[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/TimeShift_20020515.pdf Fig.1: Profile after the first step of the correction in time. Model results and measurement display the same differences relative to their mean times (133k)]]

The second step is the optional addition of a constant time span. This enables the program to shift the actual time data exactly to the target time, even when actual and target time differ several years. The time span is computed out of the mean measure time and the estimated actual time, which is the time with probably the best fit of measurement and model. A value can be assigned to the estimated time in the general input data.

[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/TimeShift_to20060927.pdf Fig.2: The second step is an optional, constant shift in time. (133k)]]

Both methods are performed for all times of the actual time file. Thus, the output file contains the same number of times. Each of these datasets has the same internal temporal pattern. The modeller can select the dataset with the best fit from this ensemble.
|inputfiles=
# general input data (file of type [[TIMESHIFT.DAT|timeshift.dat]]);
# further input data is explained in the general input data mentioned above.
|outputfiles=
# output data is explained in the general input data mentioned above;
# lineprinter file containing useful information related to program execution (filetype Timeshift.sdr);
# optional file with trace of program execution (filetype Timeshift.trc).
|methodology=
The correction changes only the temporal mapping. The further attributes of the actual time files are passed to the output file without change.

Values with a big time difference would be interpolated at the first or last time of the actual time file, which would give a wrong impression. In order to avoid this, the interpolated values at the first or last time are not used. They are marked as null values and will be displayed in grey coulor.

[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/TimeShift_Nullvalue.pdf Fig.3: Profile with null values displayed in grey. At these locations the corrections leaves the time span of the actual times. (133k)]]

Furthermore figure 3 displays the temporal mapping to the actual times. In order to demonstrate the effect, the interval is rather long (1 hour). There is obviously an discontinuity in the waterlevel at the intersection from one point in time to the next.

The actual time file is allowed to contain several sub profiles. But one of them must have the same name and the same number of points as the single profile of the target time file. The depth values of the profiles are allowed to differ.

For application programmers: TIMESHIFT uses the Fortran 90 packages io_dataset which also supports non-BDF formats. But only reading and writing of BDF files has been tested and released for general use.
|preprocessor=[[ADCP2PROFILE]], [[DIDAMERGE]], [[TICLQ2]], [[UNTRIM]], [[XTRLQ2]]
|postprocessor=[[GVIEW2D]], [[LQ2PRO]], [[VVIEW2D]], [[XTRDATA]]
|language=Fortran90
|add_software=-
|contact_original=P. Schade
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=please refer to $PROGHOME/examples/TimeShift/
}}

TEOAX

2022-10-10T14:28:14Z

Ak3gseis:

{{ProgramDescription
|name_de=TEOAX
|name=TEOAX
|version=September 1998
|version_descr=November 1998
|catchwords=KUEDAT 
bearing axes 
extraction
|shortdescription=
programm TEOAX serves extraction of bearing axes of a file like KUEDAT. In this kind of file bearing data is sorted by time. Here is a short description of that specific type of file format:
# only ASCII-format
# the letter in the first column of each row specifies the type of that row:
:* H (header):
:a new bearing starts with every H-row. It contains information about that bearing (e.g. date) but no bearing data itself
:* B (B-row):
:description of a section of a bearing axis (these rows will be read and analysed)
:* R (real data):
:contains one real measured bearing point. Every bearing point is specified by two position coordinates and contains depth information in MSL (mean sea level) or NN (normal null)
:* D (D-row):
:like R-row, but maximum or minimum depth information
:* U (U-row):
:like R-row, but minimum or maximum depth information
R-, D- and U-rows will not be analysed
|inputfiles=
# original KUEDAT bearing data file (filetype [[KUEDAT.DAT|kuedat.dat]])
# program steering file (filetype [[TEOAX.DAT|teoax.dat]])
|outputfiles=
# all different bearing axes will be saved in one file of type [[INSEL.DAT|insel.dat]]
# every bearing axis will be stored in files of type [[POLY.DAT|poly.dat]]
|methodology=
Every B-row contains one section of a bearing axis. This section can be a straight forward section (with given start and end point coordinates) or a circular arc, for which also two information are given: first the mid point of that circle and second the end point coordinates of that section (the start point is the end point of the section before). The program reads all section information, concatenate the sections to a bearing axis, controls whether the axis is known or not and stores the axis to a file (if not known).
|preprocessor=-
|postprocessor=[[TEO]]
|language=Fortran90
|add_software=-
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=supercomputing news # 3/1998 and $PROGHOME/examples/teoax
}}

TEO

2022-10-10T14:26:28Z

Ak3gseis:

{{ProgramDescription
|name_de=TEO
|name=TEO
|version=September 1998
|version_descr=April 2008
|catchwords=KUEDAT 
bearing data 
extraction
|shortdescription=
programm TEO serves extraction of bearing data of a file like KUEDAT. In this kind of file bearing data is sorted by time. Here is a short description of that specific type of file format:
# only ASCII-format
# the letter in the first column of each row specifies the type of that row:
:* H (header):
:a new bearing starts with every H-row. It contains information about that bearing (e.g. date) but no bearing data itself
:* B (B-row):
:description of a section of a bearing axis (for extracting bearing axes use program [[TEOAX]])
:* R (real data):
:contains one real measured bearing point. Every bearing point is specified by two position coordinates and contains depth information in MSL (mean sea level) or NN (normal null)
:* D (D-row):
:like R-row, but maximum or minimum depth information
:* U (U-row):
:like R-row, but minimum or maximum depth information
|inputfiles=
# original KUEDAT bearing data file (filetype [[KUEDAT.DAT|kuedat.dat]])
# program steering file (filetype [[TEO.DAT|teo.dat]])
# (opt) polygon file (filetype [[POLY.DAT|poly.dat]]) containing the border line of the extraction area
# (opt) polygon file (filetype [[POLY.DAT|poly.dat]]) containing a bearing axis
|outputfiles=
# bearing data file of format [[GEOM.DAT|geom.dat]] containing all extracted bearing points (optional sorted by months in several files of that type)
# bearing lines file of format [[INSEL.DAT|insel.dat]] containing all those bearing lines whose points were extracted
# bearing data file of format [[GEOM.DAT|geom.dat]] containing bearing points not extracted by the program
# KUEDAT bearing data file (filetype [[KUEDAT.DAT|kuedat.dat]]) containing not extracted bearing lines in original format
|methodology=
The criteria for extracting bearing data are listed below:
* extraction area: The program gives you several possibilities of specifying your area of interest:
:* whole area: all bearing points can be extracted, no matter where they lie
:* rectangle area: bearing points within a rectangle area (specified by four corner points) can be extracted
:* polygon area: bearing points within an area specified by numerous points can be extracted
:* axis area: bearing points possessing a lower distance to an axis than specified can be extracted
* type of bearing lines:
:* longitudinal bearing lines: Only bearing points defined in bearing lines parallel to a specified bearing axis can be extracted
:* cross sectional bearing lines: Only bearing points defined in bearing lines orthogonal to a specified bearing axis can be extracted
:* you can switch off this limitation
* type of bearing points:
:* extracting bearing points of type R
:* extracting bearing points of type D
:* extracting bearing points of type U
:* you can also combine these criteria
* range of depth values: Only bearing point with depth values lying inside a legal range can be extracted. The range will be specified by a lower and a higher threshold
* type of depth values:
:* Mean Sea Level (MSL): all extracted bearing points will get the MSL depth values
:* Normal Null (NN): all extracted bearing points will get the NN depth values
* type of output file
:* output of bearing points in FORTRAN format 3F15.3 (file of type [[GEOM.DAT|geom.dat]])
:* output of bearing points in space saving FORTRAN format 2(F10.2,1x),F6.2
* all extracted bearing points can be sorted by months and stored in several files of the same type
* totally not extracted bearing lines will be saved in original file format to give you the chance of extracting these lines with another strategy
* You can extracting all different bearing axes with the program [[TEOAX]]
|preprocessor=[[TEOAX]]
|postprocessor=[[FDGITTER05]], [[IGEL2D]]
|language=Fortran90
|add_software=-
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=supercomputing news # 3/1998 and $PROGHOME/examples/teo
}}

TDKTIE

2022-10-10T14:25:31Z

Ak3gseis:

{{ProgramDescription
|name_de=TDKTIE
|name=TDKTIE
|version=August 1994
|version_descr=December 2000
|catchwords=
tidal characteristic numbers 
linking TIDKEN results 
link table for different data sources 
link table for different parameters of influence 
preparing the visualization
|shortdescription=
The program TDKTIE ties together the '''tidal characteristic numbers''' which have been calculated by the analysis tool [[TIDKEN]]. The results can e.g. cover several analysed stations along an estuary which are linked to a profile. BT2PRO running after TDKTIE is able to visualize the profile data.
|inputfiles=
# '''general input data''' (filetype [[TDKTIE.DAT|tdktie.dat]]) where the linking is defined
# '''analysis results''' (filetype [[ZEILE.TIDKEN.DAT|zeile.tidken.dat]]) for water level, current velocity or salinity
|outputfiles=
# '''newly linked data sets''' in ASCII format (filetype [[TTASF.ASF|ttasf.asf]]).
# '''newly linked data sets''' in binary format (filetype [[TTBPT.BPT|ttbpt.bpt]]).
# (optional) file with trace of program execution (filetype tdktie.trc).
|methodology=
For connecting the TIDKEN results you have to select a '''physical measure'''. It can be mileage, fresh water flow rate, time etc.. The values of the measure will represent the abscissa values for a later visualization.

In the ASCII-table ttasf.asf this measure stands in the first column.
|preprocessor=[[TIDKEN]]
|postprocessor=BT2PRO
|language=Fortran90
|add_software=-
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tdktie/
}}

TDKTIE

2022-10-10T14:24:07Z

Ak3gseis:

{{ProgramDescription
|name_de=TDKTIE
|name=TDKTIE
|version=August 1994
|version_descr=December 2000
|catchwords=
tidal characteristic numbers 
linking TIDKEN results 
link table for different data sources 
link table for different parameters of influence 
preparing the visualization
|shortdescription=
The program TDKTIE ties together the '''tidal characteristic numbers''' which have been calculated by the analysis tool [[TIDKEN]]. The results can e.g. cover several analysed stations along an estuary which are linked to a profile. BT2PRO running after TDKTIE is able to visualize the profile data.
|inputfiles=
# '''general input data''' (filetype [[TDKTIE.DAT|tdktie.dat]]) where the linking is defined
# '''analysis results''' (filetype [[ZEILE.TIDKEN.DAT|zeile.tidken.dat]]) for water level, current velocity or salinity
|outputfiles=
# '''newly linked data sets''' in ASCII format (filetype [[TTASF.ASF|ttasf.asf]]).
# '''newly linked data sets''' in binary format (filetype [[TTBPT.BPT|ttbpt.bpt]]).
# (optional) file with trace of program execution (filetype tdktie.trc).
|methodology=
For connecting the TIDKEN results you have to select a '''physical measure'''. It can be mileage, fresh water flow rate, time etc.. The values of the measure will represent the abscissa values for a later visualization.

In the ASCII-table ttasf.asf this measure stands in the first column.
|preprocessor=[[TIDKEN]]
|postprocessor=BT2PRO
|language=Fortran77
|add_software=-
|contact_original=J. Jürges
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tdktie/
}}

TC2TR2

2022-10-10T14:23:16Z

Ak3gseis:

{{ProgramDescription
|name_de=TC2TR2
|name=TC2TR2
|version=
|version_descr=
|catchwords=
preprocessor 
conversion of a finite element grid 
equivalent finite difference grid 
numerical model TRIM-2D 
numerical model TRIM-3D
|shortdescription=
The program TC2TR2 is a preprocessor for the numerical models [[TRIM-2D]] and [[TRIM-3D]].
This program serves to convert the bathymetry given in the data format of the finite element method TICAD-2S into an equivalent one defined in the format of the finite difference methods TRIM-2D, as well as TRIM-3D.
|inputfiles=
# control parameters and general input data (file type [[TC2TR2.DAT|tc2tr2.dat]])
# finite element topography (file type [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# (optional) surrounding polygon (file type [[POLY.DAT|poly.dat]])
# (optional) file with polygon traces to set depth values explicitly along these traces (file type [[NODES.SAVE|nodes.save]])

|outputfiles=
# equivalent TRIM grid and topography (filetype [[TR2.TOPO.BIN|tr2.topo.bin]])
# informative printer file (file type tc2tr2.sdr)
# (optional) trace of program execution (file type tc2tr2.trc)

|methodology=
# Reading input topography in TICAD-2S-format.
# Optional : Reading the boundary polygon which surrounds the area to be converted.
# Generating an element table which describes the area to be converted.
# Calculating the bathymetrical depth at the nodes U, V, Z and O of the TRIM grid by appropriate interpolation of depth at the nodes of the FE-grid:
## Depths at U- and V-points are mean values of the corresponding ZETA-points. Therefore the depths are approximated in the best possible way and the speed of the tidal wave can be calculated correctly. On the other hand side the volume of the system under investigation may be overestimated systematically.
## Depths at U- and V-points are minimum values of the corresponding ZETA-points. This guarantees the best approximation of the volume, but depths at U- and V-points are underestimated systematically. Therefore computed wave speed may be also underestimated.
# Modification of depth to fulfill the TRIM convention.
# Optional : Consideration of structures (e.g. dams, groynes, etc.).
# Automatic Determination of isolated grid cells (cells without connexions to neighbour grid cells).
# Expanding the grid at the outer boundaries to fulfill the following conditions :
#* Computational domain is surrounded at least by two additional rows of grid cells;
#* even number of grid cells in both spatial directions.
# Model topography is written in TRIM-format to an ASCII- or binary file.

|preprocessor=[[UPDA2D]]
|postprocessor=[[FD2MET]], [[TR2FIDI]], [[TR2REFRESH]], [[TR2RND]], [[TR2VOR]], [[TRGITTER05]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation= -
}}

TC2GEOM

2022-10-10T14:22:26Z

Ak3gseis:

{{ProgramDescription
|name_de=TC2GEOM
|name=TC2GEOM
|version=October 1998
|version_descr=April 2008
|catchwords=preprocessor 
finite difference method TRIM-2D 
finite difference method TRIM-3D 
conversion of a finite element mesh 
equivalent finite Difference grid 
generation of list of boundary nodes
|shortdescription=
The program TC2GEOM is one of the tools connected to the hydronumerical methods TRIM-2D and TRIM-3D. It is used to transfer the model topography which is stored in the data format of the finite element method TICAD-2S into an equivalent topography stored in the format of the finite difference method FIDISOR/FIDIRB. This topography can subsequently be converted by means of the program [[FD2TRIM]] into a grid which can be equivalently used by TRIM-2D and TRIM-3D as well.
|inputfiles=
# input file which controls the program flow (filetype [[TC2GEOM.DAT|tc2geom.dat]])
# file containing the finite element mesh of the model topography (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# (optional) file with polygon traces to set depth values explicitly along these traces (filetype [[NODES.SAVE|nodes.save]])
# (optional) list of nodal markers (filetype [[KNOK.GITTER05.DAT and KNOK.GITTER05.BIN|knok.gitter05.dat/bin]])
|outputfiles=
# topography stored in the format of method FIDISOR/FIDIRB (filetype [[TOPO.BIN|topo.bin]])
# (optional) printer protocol with more ore less informative messages about the automatic grid conversion (file type tc2geom.sdr)
# (optional) list of boundary grid cells (filetype [[RGZ.DAT|rgz.dat]])
:: Notice: boundary grid cells can be visualized and interactively modified using the graphical program [[FDGITTER05]]. Furthermore the may be easyli converted into a file of type fd2rnd.dat which can be later used for generation of boundary data using program [[TR2RND]] umgesetzt werden.
|methodology=
For each grid cell lying inside the finite element grid the depth value of the cell center is obtained by interpolation . If depth values given in the file [[NODES.SAVE|nodes.save]] for polygon traces explicitly shall be transferred, the depth at the cell centers is changed in grid cells lying along the polygon trace (the polygon trace is projected to the cell centers).

With interpretation of the boundary indices of the finite element mesh (open, i.e. flow passing through, or closed, i.e. no flow passing through) the open parts of the boundary are identified automatically. If a file of type [[KNOK.GITTER05.DAT and KNOK.GITTER05.BIN|knok.gitter05.dat/bin]] has been optionally specified on input the grid cells are further differntiated in dependence of their location with respect to different sections along the open boundaries.
|preprocessor=[[UPDA2D]]
|postprocessor=[[FD2HYPSO]], [[FD2TRIM]], [[FDGITTER05]], [[FDGLUE]]
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=
}}

TC2BAGGER

2022-10-10T14:20:51Z

Ak3gseis:

{{ProgramDescription
|name_de=TC2BAGGER
|name=TC2BAGGER
|version=February 1996
|version_descr=April 2008
|catchwords=preprocessor 
finite element grid
modification of topography
deepening and refillment
|shortdescription=
The program TC2BAGGER is a preprocessor which is used to modify the bathymetrical depth given at each node of an existing (triangular) finite element grid. The nodes which shall be modified (modification nodes) are selected in accordance with one of the following criteria:

* their position can be either inside or outside of an (optional) surrounding polygon
* they can be situated either inside of an additional dredger-polygon or they are lying inside of a second finite element grid (dredger-grid) which contains spacially varying informations for the modification of the actual water depth
* modification of the nodal values for the bathymetrical depth can can be explicitely forbidden for nodes to which selected nodal marker values are attached

The actual nodal depth can be modified in the following different ways (modification options):

# uncoditional deepening/refillment: at all modification nodes the actual depth is modified with the modification value
# unconditioanl setting of the depth: at all modification nodes the actual depth is set to the modification value
# conditional deepening: at all modification nodes where the actual depth is smaller than the modification value the depth will be set to the modification value. Areas which are already deeper than the depth given by the modification value remain unchanged
# conditional refillment: at all modification nodes where the actual depth is larger than the modification value the depth will be set to the modification value. Areas which are shallower than the depth given by the modification value remain unchanged.

The modification value is either connected with a dredger-polygon or results from the local depth in the dredger-grid.
|inputfiles=
# general input-data (filetype [[TC2BAGGER.DAT|tc2bagger.dat]])
# grid with actual bathymetry (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# dredger-polygons (filetype [[BAGGER.DAT|bagger.dat]])
# dredger-grid (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# (optional) surrounding polygon (Dateityp [[POLY.DAT|poly.dat]])
# (optional) list of nodal markers (filetype [[KNOK.GITTER05.DAT and KNOK.GITTER05.BIN|knok.gitter05.dat/bin]])
|outputfiles=
# grid with modified bathymetry (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# (optional) grid with differences for bathymetry (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])
# printer file (filetype tc2bagger.sdr)
# (optional) trace of program execution (filetype tc2bagger.trc)
|methodology=
The nodal depths at the modification nodes are either set to the values related to the dredger-polygons or to the interpolated values from the nodal depths given in the dredger-grid.
|preprocessor=
|postprocessor=[[HVIEW2D]], [[JANET]], [[TICTRI]], [[TOUTR]], UPDATE
|language=Fortran90
|add_software=-
|contact_original=G. Lang
|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
|documentation=$PROGHOME/examples/tc2bagger
}}