Actions

GETDATA: Difference between revisions

From BAWiki

imported>BAWiki 3
mNo edit summary
(working group POS)
 
(11 intermediate revisions by 2 users not shown)
Line 2: Line 2:
|name_de=GETDATA
|name_de=GETDATA
|name=GETDATA
|name=GETDATA
|version=2.18 / August 2008
|version=2.44 / August 2011
|version_descr=February 2010
|version_descr=September 2022
|catchwords=conversion of Delft3D computational results  
|catchwords=conversion of Delft3D computational results  
|shortdescription=The program GETDATA converts Delft3D computational results into the network Common Data Form [[NETCDF.DAT|netcdf.dat]]. [[DATACONVERT]] offers the opportunity to convert these netCDF files in a further step into [[DIRZ.BIN|PDF files]].  
|shortdescription=The program GETDATA converts Delft3D computational results into the network Common Data Form [[NETCDF.CDF|netcdf.cdf]]. [[DATACONVERT]] offers the opportunity to convert these netCDF files in a further step into [[DIRZ.BIN|BDF files]].  
|inputfiles=
|inputfiles=
# '''computational results in Delft3D map files'''
# '''computational results in Delft3D map files'''
#: Each dataset requires a data file trim-*.dat and a definition file trim-*.def. These files are also referred to as NEFIS files. #: NEFIS may include more than Delft3D results, but this description is restricted to the map files. For more information have a
#: Each dataset requires a data file trim-*.dat and a definition file trim-*.def. These files are
#: look in the Delft3D-FLOW-User Manual (see below), p. 6-7.
#: also referred to as NEFIS files.
#: NEFIS may include more than Delft3D results, but this description is restricted to the map
#: files. For more information have a look in the Delft3D-FLOW-User Manual (see below), p. 6-7.
# '''nefis.ini for initialisation'''
# '''nefis.ini for initialisation'''
# '''simetf'''
# '''simetf'''
Line 19: Line 21:


|outputfiles=
|outputfiles=
# '''converted computational results as [[NETCDF.DAT|netcdf.dat]]'''
# '''converted computational results as [[NETCDF.CDF|netcdf.cdf]]'''
:: This file differs from the netCDF files written by BAW software. This type can neither be loaded by the ArcGIS-GEI-Dataloader
:: This file differs from the netCDF files written by BAW software. This type can neither be loaded by the ArcGIS-GEI-Dataloader
:: nor by Davit
:: nor by Davit


|methodology=
|methodology=
*  Reading the map files is done by methods of the NEFIS 5 library, whereas the netCDF library performs the netCDF output. 3D results are in both formats stored in sigma layers.
*  Reading the map files is done by methods of the NEFIS 5 library, whereas the netCDF library performs the NETCDF output. 3D results are in both formats stored in sigma layers.
* NEFIS 5 has overcome the 2 GB file size barrier. For large datasets it is recommended to convert the physical measures seperately, since the file size of the netCDF files has become the new bottleneck.
* NEFIS 5 has overcome the 2 GB file size barrier. For large datasets it is recommended to convert the physical measures seperately, since the file size of the NETCDF files has become the new bottleneck.
* GETDATA requires two lines of console input. It is recommended to import them from a txt file,
* GETDATA requires two lines of console input. It is recommended to import them from a txt file,
e.g. '''from $PROGHOME/examples/getdata/getdata_input.txt.'''  
: e.g. '''from $PROGHOME/examples/getdata/getdata_input.txt.'''
|preprocessor=[[DELFT3D]]
* The second input line can contain the -t option steering the output times.
|postprocessor=[[DATACONVERT]]
:start_time and stop_time are given in s since the reference date / time. The output time step difference time_step is given in seconds as well. Blanks between the time values are not allowed.
:''-t start_time,time_step,stop_time''
:: Example -t 3600,600,7200 starts 1 h after and ends 2 h after the reference date / time.
:''-t start_time,stop_time''  converts all times between start and stop time.
:''-t one_time''  extracts just one time.
* The current version writes netCDF files that can be greater than 2GB. This is possible since the netCDF mode has been set to ''cmode=nf90_64bit_offset''.
|preprocessor=DELFT3D
|postprocessor=[[DATACONVERT]], QUICKPLOT
|language=?
|language=?
|add_software=netCDF.dll
|add_software=netCDF.dll
|contact_original=Deltares
|contact_original=Deltares
|contact_maintenance=Deltares
|contact_maintenance=[mailto:pos.proghome@baw.de Working group POS] and Deltares
|documentation=User manual $PROGHOME/examples/getdata/getdata_UM.pdf,
|documentation=User manual $PROGHOME/examples/getdata/getdata_UM.pdf,
description of map files in $PROGHOME/examples/Delft3D/Delft3D-FLOW_User_Manual.pdf
description of map files in $PROGHOME/examples/Delft3D/Delft3D-FLOW_User_Manual.pdf
}}
}}

Latest revision as of 09:37, 6 September 2022

Basic Information

Name of Program

GETDATA

Version-Date

2.44 / August 2011

Description-Date

September 2022

Catchwords

conversion of Delft3D computational results

Short Description of Functionality

The program GETDATA converts Delft3D computational results into the network Common Data Form netcdf.cdf. DATACONVERT offers the opportunity to convert these netCDF files in a further step into BDF files.

Input-Files

  1. computational results in Delft3D map files
    Each dataset requires a data file trim-*.dat and a definition file trim-*.def. These files are
    also referred to as NEFIS files.
    NEFIS may include more than Delft3D results, but this description is restricted to the map
    files. For more information have a look in the Delft3D-FLOW-User Manual (see below), p. 6-7.
  2. nefis.ini for initialisation
  3. simetf
  4. simona.cfg for configuration
  5. simona.env for setting the environment;
Files 2 to 5 and the executable have to be located in the working directory. The batchfile copy_getdata.bat copies them there.
It is located in the search path. Use:
copy_getdata [working_directory], e.g. copy_getdata C:\temp

Output-Files

  1. converted computational results as netcdf.cdf
This file differs from the netCDF files written by BAW software. This type can neither be loaded by the ArcGIS-GEI-Dataloader
nor by Davit

Methodology

  • Reading the map files is done by methods of the NEFIS 5 library, whereas the netCDF library performs the NETCDF output. 3D results are in both formats stored in sigma layers.
  • NEFIS 5 has overcome the 2 GB file size barrier. For large datasets it is recommended to convert the physical measures seperately, since the file size of the NETCDF files has become the new bottleneck.
  • GETDATA requires two lines of console input. It is recommended to import them from a txt file,
e.g. from $PROGHOME/examples/getdata/getdata_input.txt.
  • The second input line can contain the -t option steering the output times.
start_time and stop_time are given in s since the reference date / time. The output time step difference time_step is given in seconds as well. Blanks between the time values are not allowed.
-t start_time,time_step,stop_time
Example -t 3600,600,7200 starts 1 h after and ends 2 h after the reference date / time.
-t start_time,stop_time converts all times between start and stop time.
-t one_time extracts just one time.
  • The current version writes netCDF files that can be greater than 2GB. This is possible since the netCDF mode has been set to cmode=nf90_64bit_offset.

Program(s) to run before this Program

DELFT3D

Program(s) to run after this Program

DATACONVERT, QUICKPLOT

Additional Information

Language

?

Additional software

netCDF.dll

Original Version

Deltares

Maintenance

Working group POS and Deltares

Documentation/Literature

User manual $PROGHOME/examples/getdata/getdata_UM.pdf, description of map files in $PROGHOME/examples/Delft3D/Delft3D-FLOW_User_Manual.pdf

back to Program Descriptions

Overview

Retrieved from "http://wiki.baw.de/en/index.php?title=GETDATA&oldid=14873"