BOEWRT.DAT - Revision history

imported>Schade Peter: same icode and classes

2018-02-13T09:02:58Z

same icode and classes

← Older revision		Revision as of 09:02, 13 February 2018
Line 2:		Line 2:
	\|name_de=BOEWRT.DAT		\|name_de=BOEWRT.DAT
	\|filetype=boewrt.dat		\|filetype=boewrt.dat
	\|version=~~October 2017~~		\|version=February 2018
	\|version_descr=~~October 2017~~		\|version_descr=February 2018
	\|significance=contains measured or calculated time-series data in ASCII for the usage in various programs.		\|significance=contains measured or calculated time-series data in ASCII for the usage in various programs.
	===General remarks===		===General remarks===
Line 26:		Line 26:
	# name of the location (written in FORTRAN format "(A)").		# name of the location (written in FORTRAN format "(A)").
	# coordinates (x,y and optionally z) of the station position. Z values are as default depths with positiv values in the downward direction.(unformatted with separating blanks!)		# coordinates (x,y and optionally z) of the station position. Z values are as default depths with positiv values in the downward direction.(unformatted with separating blanks!)
	# number and type-codes for the physical quantities stored in the file (FORTRAN format "(I10,nI8)".		# number and type-codes for the physical quantities stored in the file (FORTRAN format "(I10,nI8)". Since February 2018 the same icode can appear more than once, e.g. for several fractions of suspended load.
	# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>		# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>

Line 41:		Line 41:
	# platform comment: commenting on the platform given by platform name (optional)		# platform comment: commenting on the platform given by platform name (optional)
	# valid range: defining minimal and maximal limits for values of quantities identified by BAW' icode number, e.g. 3 for waterlevel (optional)		# valid range: defining minimal and maximal limits for values of quantities identified by BAW' icode number, e.g. 3 for waterlevel (optional)
			# class: name of a sub class of a quantity, e.g. 'sum of all fractions' identified by BAW's icode number, e.g. 7 for suspended load (optional)
	# measure comment: individual comment on a quantity (optional)		# measure comment: individual comment on a quantity (optional)
	# line comment: optionally commenting on the values of one data line as displayed in the subsequent example, where "!" separates the quantities from the line comment "2_QMag 2_QDir":<br/>		# line comment: optionally commenting on the values of one data line as displayed in the subsequent example, where "!" separates the quantities from the line comment "2_QMag 2_QDir":<br/>

imported>Lang Guenther: new headings inserted to improve readability, section on status flag variables added

2017-10-17T07:39:07Z

new headings inserted to improve readability, section on status flag variables added

← Older revision		Revision as of 07:39, 17 October 2017
Line 2:		Line 2:
	\|name_de=BOEWRT.DAT		\|name_de=BOEWRT.DAT
	\|filetype=boewrt.dat		\|filetype=boewrt.dat
	\|version=~~May 2014, classic version September 2001~~		\|version=October 2017
	\|version_descr=~~May 2014~~		\|version_descr=October 2017
	\|significance=contains measured or calculated time-series data in ASCII for the usage in various programs.		\|significance=contains measured or calculated time-series data in ASCII for the usage in various programs.
	===General remarks===		===General remarks===
Line 22:		Line 22:
	If the new boewrt.dat gets accessed by the io_dataset software the header has to contain more mandatory meta information, i.e. time zone, CRS and fill value, s. file-contents. The environment variables are not interpreted by io_dataset . The metadata is packed into objects of type dimension (dim), variable (var) and attribute (att) as common for netcdf files. From outside the package the data is accessed in a generic way, meaning the same interfaces are used for different file formats.		If the new boewrt.dat gets accessed by the io_dataset software the header has to contain more mandatory meta information, i.e. time zone, CRS and fill value, s. file-contents. The environment variables are not interpreted by io_dataset . The metadata is packed into objects of type dimension (dim), variable (var) and attribute (att) as common for netcdf files. From outside the package the data is accessed in a generic way, meaning the same interfaces are used for different file formats.
	\|filecontents=		\|filecontents=
	~~Content of the~~ classic ~~and the~~ new ~~boewrt.dat~~ format:		===Data for classic as well as new file format===
	# node number, time zone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see [[GEOTRANSFORMER]] for example) should be used. Certain abbrevations as "GK3B" or "SPHW" are valid as well. Time zone and CRS are mandatory for the new boewrt.dat version.		# node number, time zone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see [[GEOTRANSFORMER]] for example) should be used. Certain abbrevations as "GK3B" or "SPHW" are valid as well. Time zone and CRS are mandatory for the new boewrt.dat version.
	# name of the location (written in FORTRAN format "(A)").		# name of the location (written in FORTRAN format "(A)").
Line 28:		Line 28:
	# number and type-codes for the physical quantities stored in the file (FORTRAN format "(I10,nI8)".		# number and type-codes for the physical quantities stored in the file (FORTRAN format "(I10,nI8)".
	# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>		# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>
	~~Content~~ only ~~of the classic boewrt.dat:~~
			===Data for classic file format only===
	# minimum and maximum time step: on failure of reading a file, these comments should be erased. Files manipulated by an editor should never contain these comments!		# minimum and maximum time step: on failure of reading a file, these comments should be erased. Files manipulated by an editor should never contain these comments!
	# FORTRAN format specifications of the lines in the data part. The FORTRAN format is used to accelerate the reading procedure of uniformly formatted records. On failure of reading a file it should be erased. Files manipulated by an editor should never contain the format.<br/>		# FORTRAN format specifications of the lines in the data part. The FORTRAN format is used to accelerate the reading procedure of uniformly formatted records. On failure of reading a file it should be erased. Files manipulated by an editor should never contain the format.<br/>

			===Data for new file format only===
	Content of the new boewrt.dat format, the keywords refer to NODC's standard attributes and guidance tables ( http://www.nodc.noaa.gov/data/formats/netcdf/#guidancetable )		Content of the new boewrt.dat format, the keywords refer to NODC's standard attributes and guidance tables ( http://www.nodc.noaa.gov/data/formats/netcdf/#guidancetable )
	# fill value: a real number defining invalid values of quantities (mandatory)		# fill value: a real number defining invalid values of quantities (mandatory)
Line 42:		Line 44:
	# line comment: optionally commenting on the values of one data line as displayed in the subsequent example, where "!" separates the quantities from the line comment "2_QMag 2_QDir":<br/>		# line comment: optionally commenting on the values of one data line as displayed in the subsequent example, where "!" separates the quantities from the line comment "2_QMag 2_QDir":<br/>
	29.02.2004 12:00:31; 0.066 122.010 !2_QMag 2_QDir<br/>		29.02.2004 12:00:31; 0.066 122.010 !2_QMag 2_QDir<br/>

			===Status flag variable===
			This variable is used to characterize the qualtity of individual data values. PHYDEF-code for this type of data is 3180.
			During conversion using [[DATACONVERT]] a
			[http://cfconventions.org/Data/cf-conventions/cf-conventions-1.6/build/cf-conventions.html#flags flag] variable consistent with CF metadata standard is created. [http://cfconventions.org/Data/cf-conventions/cf-conventions-1.6/build/cf-conventions.html#standard-name-modifiers Modificator] ''status_flag'' is part of the standard name of this variable. Attributes flag_masks and flag_meanings are used to describe the quality of individual data items:
			* flag_mask='''1b''', flag_meaning='''''good''''': valid data, will be used by [[NCANALYSE]] and [[NCDELTA]];
			* flag_mask='''2b''', flag_meaning='''''unchecked''''': quality not checked;
			* flag_mask='''4b''', flag_meaning='''''estimated''''': derived from neighbouring data;
			* flag_mask='''8b''', flag_meaning='''''suspect''''': doubtful or obviously wrong data.

	\|nutzerprogramme=		\|nutzerprogramme=
	classic: [[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]<br>		classic: [[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]<br>

imported>Schade Peter at 14:15, 6 May 2014

2014-05-06T14:15:05Z

← Older revision		Revision as of 14:15, 6 May 2014
Line 25:		Line 25:
	# node number, time zone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see [[GEOTRANSFORMER]] for example) should be used. Certain abbrevations as "GK3B" or "SPHW" are valid as well. Time zone and CRS are mandatory for the new boewrt.dat version.		# node number, time zone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see [[GEOTRANSFORMER]] for example) should be used. Certain abbrevations as "GK3B" or "SPHW" are valid as well. Time zone and CRS are mandatory for the new boewrt.dat version.
	# name of the location (written in FORTRAN format "(A)").		# name of the location (written in FORTRAN format "(A)").
	# coordinates (x,y and optionally z) of the station position, as a default ~~z values are~~ depths with positiv values in the downward direction.(unformatted with separating blanks!)		# coordinates (x,y and optionally z) of the station position. Z values are as default depths with positiv values in the downward direction.(unformatted with separating blanks!)
	# number and type-codes for the physical quantities stored in the file (FORTRAN format "(I10,nI8)".		# number and type-codes for the physical quantities stored in the file (FORTRAN format "(I10,nI8)".
	# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>		# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>
Line 39:		Line 39:
	# platform comment: commenting on the platform given by platform name (optional)		# platform comment: commenting on the platform given by platform name (optional)
	# valid range: defining minimal and maximal limits for values of quantities identified by BAW' icode number, e.g. 3 for waterlevel (optional)		# valid range: defining minimal and maximal limits for values of quantities identified by BAW' icode number, e.g. 3 for waterlevel (optional)
	# measure comment: ~~commenting~~ on ~~the quantities~~ (optional)		# measure comment: individual comment on a quantity (optional)
	# line comment: optionally commenting on the values of one data line as in subsequent example, where "!" separates the quantities from the line comment "2_QMag 2_QDir":<br/>		# line comment: optionally commenting on the values of one data line as displayed in the subsequent example, where "!" separates the quantities from the line comment "2_QMag 2_QDir":<br/>
	29.02.2004 12:00:31; 0.066 122.010 !2_QMag 2_QDir<br/>		29.02.2004 12:00:31; 0.066 122.010 !2_QMag 2_QDir<br/>
	\|nutzerprogramme=		\|nutzerprogramme=

imported>Schade Peter: beta version of new boewrt.dat before Guntram's comments

2014-05-06T14:06:59Z

beta version of new boewrt.dat before Guntram's comments

← Older revision		Revision as of 14:06, 6 May 2014
Line 9:		Line 9:
	The file has a header where meta data is identified by its position in the file, the first data line e.g. contains the node number. This is the classic boewrt.dat that can be processed by classical methods of BAW's io library. Since May 2014 the new boewrt.dat header can contain key-value pairs with additional meta data, the key Fill_Value is for example followed by a value in real format. The additional meta information is only evaluated by methods of BAW's io_dataset software package.		The file has a header where meta data is identified by its position in the file, the first data line e.g. contains the node number. This is the classic boewrt.dat that can be processed by classical methods of BAW's io library. Since May 2014 the new boewrt.dat header can contain key-value pairs with additional meta data, the key Fill_Value is for example followed by a value in real format. The additional meta information is only evaluated by methods of BAW's io_dataset software package.

	Programs using the io and the io_dataset library can read the ~~boewrt.dat files in the~~ classical as well as the new version. The data part is for both the same and rather flexible; each of the ASCII time formats used by the BAW is allowed. But the date and time format with two digit year should not be used any longer. A ";" should be used to separate date and time from the values of the quantities. <br/>		Programs using the io and the io_dataset library can read the classical as well as the new version of boewrt.dat. The data part is for both the same and rather flexible; each of the ASCII time formats used by the BAW is allowed. But the date and time format with two digit year should not be used any longer. A ";" should be used to separate date and time from the values of the quantities. <br/>

	But the libraries interpret the meta information in a different way. <br/>		But the libraries interpret the meta information in a different way. <br/>

	===Io library ~~preferrably~~ for classic boewrt.dat===		===Io library preferably for classic boewrt.dat with support of environment variables===
	This library can ~~evaluate~~ environment variables. If the environment variable $BAWCRS is set to a valid value (EPSG code), the station coordinate will be transformed to that system during the reading process on the fly. If the file CRS is not valid, the coordinate is used "as is". The user should set $BAWCRS when using the software listed below as classic programs.<br />		This library can interpret environment variables. If the environment variable $BAWCRS is set to a valid value (EPSG code), the station coordinate will be transformed to that system during the reading process on the fly. If the file CRS is not valid, the coordinate is used "as is". The user should set $BAWCRS when using the software listed below as classic programs.<br />

	If the two digit year is used, the century after $BAWCENTURY (inclusive) will be assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900). <br />		If the two digit year is used, the century after $BAWCENTURY (inclusive) will be assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900). <br />
	The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!<br />		The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!<br />

	~~Files of type~~ boewrt.dat ~~may contain three Special comments at~~ the ~~top, which contain Minimum and Maximum time step and~~ the ~~FORTRAN Format of~~ the ~~data records. These comments are used~~ to ~~accelerate the reading procedure~~, ~~when data are in ascending order in~~ time and ~~the records~~ are ~~uniformly formatted~~. ~~On failure~~ of ~~reading~~ a ~~file~~, ~~these comments should be erased. Files manipulated by an Editor should never contain these comments!<br />~~		===Io_dataset library preferably for new boewrt.dat===
			If the new boewrt.dat gets accessed by the io_dataset software the header has to contain more mandatory meta information, i.e. time zone, CRS and fill value, s. file-contents. The environment variables are not interpreted by io_dataset . The metadata is packed into objects of type dimension (dim), variable (var) and attribute (att) as common for netcdf files. From outside the package the data is accessed in a generic way, meaning the same interfaces are used for different file formats.
	~~===Io_dataset library preferrably~~ for ~~classic boewrt~~.~~dat===~~
	\|filecontents=		\|filecontents=
	of the classic and the new boewrt.dat format:		Content of the classic and the new boewrt.dat format:
	# ~~nodenumber and (optional) timezone~~ and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see at [[GEOTRANSFORMER]] for example) should be used.		# node number, time zone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see [[GEOTRANSFORMER]] for example) should be used. Certain abbrevations as "GK3B" or "SPHW" are valid as well. Time zone and CRS are mandatory for the new boewrt.dat version.
	# name of the ~~Location~~ (written ~~with~~ FORTRAN~~-Format~~ "(A)").		# name of the location (written in FORTRAN format "(A)").
	# coordinates (x,y,z) of the ~~Station~~ position (unformatted with separating blanks!)		# coordinates (x,y and optionally z) of the station position, as a default z values are depths with positiv values in the downward direction.(unformatted with separating blanks!)
	# number and type-codes for the physical quantities stored in the file (FORTRAN~~-Format~~ "(I10,nI8)".		# number and type-codes for the physical quantities stored in the file (FORTRAN format "(I10,nI8)".
	# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>		# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>
			Content only of the classic boewrt.dat:
			# minimum and maximum time step: on failure of reading a file, these comments should be erased. Files manipulated by an editor should never contain these comments!
			# FORTRAN format specifications of the lines in the data part. The FORTRAN format is used to accelerate the reading procedure of uniformly formatted records. On failure of reading a file it should be erased. Files manipulated by an editor should never contain the format.<br/>

	~~content~~ of the new boewrt.dat format, the keywords refer to NODC's standard attributes and guidance tables ( http://www.nodc.noaa.gov/data/formats/netcdf/#guidancetable )		Content of the new boewrt.dat format, the keywords refer to NODC's standard attributes and guidance tables ( http://www.nodc.noaa.gov/data/formats/netcdf/#guidancetable )
	# fill value: a real number defining invalid values of quantities (mandatory)		# fill value: a real number defining invalid values of quantities (mandatory)
	# instrument name (optional)		# instrument name (optional)
Line 38:		Line 40:
	# valid range: defining minimal and maximal limits for values of quantities identified by BAW' icode number, e.g. 3 for waterlevel (optional)		# valid range: defining minimal and maximal limits for values of quantities identified by BAW' icode number, e.g. 3 for waterlevel (optional)
	# measure comment: commenting on the quantities (optional)		# measure comment: commenting on the quantities (optional)
	# line comment: commenting on the values of one data line as in ~~this~~ example:<br/>		# line comment: optionally commenting on the values of one data line as in subsequent example, where "!" separates the quantities from the line comment "2_QMag 2_QDir":<br/>
	29.02.2004 12:00:31; 0.066 122.010 !2_QMag 2_QDir<br/>		29.02.2004 12:00:31; 0.066 122.010 !2_QMag 2_QDir<br/>
	~~whith the line comment "2_QMag 2_QDir". It is a time dependant variable containing strings.~~
	\|nutzerprogramme=		\|nutzerprogramme=
	classic: [[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]<br>		classic: [[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]<br>
Line 49:		Line 50:
	\|fileextension=.dat		\|fileextension=.dat
	\|writemodules=classic: $PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:write_boewrt_info; <br/>		\|writemodules=classic: $PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:write_boewrt_info; <br/>
	new: -		new: -
	\|readmodules=classic: $PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:read_boewrt_info; <br/>		\|readmodules=classic: $PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:read_boewrt_info; <br/>
	new: $PROGHOME/fortran/lib/io/*/mod_io_dataset_ui.f90 ~~for filetype boewrt~~		new: $PROGHOME/fortran/lib/io_dataset/*/mod_io_dataset_ui.f90, mod_m_dataset_boewrt_info.f90 and mod_m_dataset_boewrt.f90.
	\|contact_original=[mailto:ingrid.uliczka@baw.de I. Uliczka]		\|contact_original=[mailto:ingrid.uliczka@baw.de I. Uliczka]
	\|contact_maintenance=[mailto:ingrid.uliczka@baw.de I. Uliczka], [mailto:guntram.seiss@baw.de G. Seiß]; [mailto:peter.schade@baw.de P. Schade]		\|contact_maintenance=[mailto:ingrid.uliczka@baw.de I. Uliczka], [mailto:guntram.seiss@baw.de G. Seiß]; [mailto:peter.schade@baw.de P. Schade]
	\|examplefile= classic: $PROGHOME/examples/zeitrio/boewrt.new.dat~~<br />~~		\|examplefile= classic: $PROGHOME/examples/zeitrio/boewrt.new.dat and $PROGHOME/examples/zeitrio/boewrt.dat<br/>
	$PROGHOME/examples/zeitrio/boewrt.dat<br/>		new: $PROGHOME/examples/dataconvert/boewrt.optionalheader.dat and
	new: $PROGHOME/examples/dataconvert/boewrt.optionalheader.dat~~;<br/>~~
	$PROGHOME/examples/dataconvert/boewrt.linecomments.dat<br/>		$PROGHOME/examples/dataconvert/boewrt.linecomments.dat<br/>
	}}		}}

imported>Schade Peter at 09:48, 6 May 2014

2014-05-06T09:48:31Z

← Older revision		Revision as of 09:48, 6 May 2014
Line 9:		Line 9:
	The file has a header where meta data is identified by its position in the file, the first data line e.g. contains the node number. This is the classic boewrt.dat that can be processed by classical methods of BAW's io library. Since May 2014 the new boewrt.dat header can contain key-value pairs with additional meta data, the key Fill_Value is for example followed by a value in real format. The additional meta information is only evaluated by methods of BAW's io_dataset software package.		The file has a header where meta data is identified by its position in the file, the first data line e.g. contains the node number. This is the classic boewrt.dat that can be processed by classical methods of BAW's io library. Since May 2014 the new boewrt.dat header can contain key-value pairs with additional meta data, the key Fill_Value is for example followed by a value in real format. The additional meta information is only evaluated by methods of BAW's io_dataset software package.

	Programs using the io and the io_dataset library can read the classical ~~and~~ the new version. The data part is for both the same and rather flexible; each of the ASCII time formats used by the BAW is allowed. But the date and time format with two digit year should not be used any longer. A ";" should be used to separate date and time from the values of the quantities. <br/>		Programs using the io and the io_dataset library can read the boewrt.dat files in the classical as well as the new version. The data part is for both the same and rather flexible; each of the ASCII time formats used by the BAW is allowed. But the date and time format with two digit year should not be used any longer. A ";" should be used to separate date and time from the values of the quantities. <br/>

	But the libraries interpret the meta information in a different way. <br/>		But the libraries interpret the meta information in a different way. <br/>

	===IO library preferrably for classic boewrt.dat===		===Io library preferrably for classic boewrt.dat===
	This library can ~~process additional information by evaluating~~ environment variables. If the coordinate ~~reference~~ system is not ~~given in the file~~, the ~~value of the environment variable~~ $BAWCRS ~~will be assigned to~~ the ~~file content~~.		This library can evaluate environment variables. If the environment variable $BAWCRS is set to a valid value (EPSG code), the station coordinate will be transformed to that system during the reading process on the fly. If the file CRS is not valid, the coordinate is used "as is". The user should set $BAWCRS when using the software listed below as classic programs.<br />

	~~When it~~ is used, the century after $BAWCENTURY (inclusive) is assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900).		If the two digit year is used, the century after $BAWCENTURY (inclusive) will be assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900). <br />
	<br />The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!<br />		The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!<br />

			Files of type boewrt.dat may contain three Special comments at the top, which contain Minimum and Maximum time step and the FORTRAN Format of the data records. These comments are used to accelerate the reading procedure, when data are in ascending order in time and the records are uniformly formatted. On failure of reading a file, these comments should be erased. Files manipulated by an Editor should never contain these comments!<br />

	~~The reading procedure supports the coordinate reference System in the following manner:<br />~~		===Io_dataset library preferrably for classic boewrt.dat===
	If the environment variable $BAWCRS is set to a valid value (EPSG code), the station coordinate will be transformed to that system during the reading process on the fly. If the file CRS is not valid, the coordinate is used "as is". The user should set $BAWCRS when using the programs listed below.<br />
	~~Files of type~~ boewrt.dat may contain three Special comments at the top, which contain Minimum and Maximum time step and the FORTRAN Format of the data records. These comments are used to accelerate the reading procedure, when data are in ascending order in time and the records are uniformly formatted. On failure of reading a file, these comments should be erased. Files manipulated by an Editor should never contain these comments!
	\|filecontents=		\|filecontents=
			of the classic and the new boewrt.dat format:
	# nodenumber and (optional) timezone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see at [[GEOTRANSFORMER]] for example) should be used.		# nodenumber and (optional) timezone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see at [[GEOTRANSFORMER]] for example) should be used.
	# name of the Location (written with FORTRAN-Format "(A)").		# name of the Location (written with FORTRAN-Format "(A)").
	# coordinates (x,y,z) of the Station position (unformatted with separating blanks!)		# coordinates (x,y,z) of the Station position (unformatted with separating blanks!)
	# number and type-codes for the physical quantities stored in the file (FORTRAN-Format "(I10,nI8)".		# number and type-codes for the physical quantities stored in the file (FORTRAN-Format "(I10,nI8)".
	# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.		# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.<br/>

			content of the new boewrt.dat format, the keywords refer to NODC's standard attributes and guidance tables ( http://www.nodc.noaa.gov/data/formats/netcdf/#guidancetable )
			# fill value: a real number defining invalid values of quantities (mandatory)
			# instrument name (optional)
			# instrument comment: commenting on the instrument given by instrument name (optional)
			# platform name: name of the geophysical platform hosting the instrument (optional)
			# platform comment: commenting on the platform given by platform name (optional)
			# valid range: defining minimal and maximal limits for values of quantities identified by BAW' icode number, e.g. 3 for waterlevel (optional)
			# measure comment: commenting on the quantities (optional)
			# line comment: commenting on the values of one data line as in this example:<br/>
			29.02.2004 12:00:31; 0.066 122.010 !2_QMag 2_QDir<br/>
			whith the line comment "2_QMag 2_QDir". It is a time dependant variable containing strings.
	\|nutzerprogramme=		\|nutzerprogramme=
	[[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]		classic: [[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]<br>
			new: [[DATACONVERT]]
	\|language=Fortran95		\|language=Fortran95
	\|fileform=FORMATTED		\|fileform=FORMATTED
	\|fileaccess=SEQUENTIAL		\|fileaccess=SEQUENTIAL
	\|fileextension=.dat		\|fileextension=.dat
	\|writemodules=$PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:write_boewrt_info		\|writemodules=classic: $PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:write_boewrt_info; <br/>
	\|readmodules=$PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:read_boewrt_info		new: -
			\|readmodules=classic: $PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:read_boewrt_info; <br/>
			new: $PROGHOME/fortran/lib/io/*/mod_io_dataset_ui.f90 for filetype boewrt
	\|contact_original=[mailto:ingrid.uliczka@baw.de I. Uliczka]		\|contact_original=[mailto:ingrid.uliczka@baw.de I. Uliczka]
	\|contact_maintenance=[mailto:ingrid.uliczka@baw.de I. Uliczka], [mailto:guntram.seiss@baw.de G. Seiß]		\|contact_maintenance=[mailto:ingrid.uliczka@baw.de I. Uliczka], [mailto:guntram.seiss@baw.de G. Seiß]; [mailto:peter.schade@baw.de P. Schade]
	\|examplefile=$PROGHOME/examples/zeitrio/boewrt.new.dat<br />		\|examplefile= classic: $PROGHOME/examples/zeitrio/boewrt.new.dat<br />
	$PROGHOME/examples/zeitrio/boewrt.dat		$PROGHOME/examples/zeitrio/boewrt.dat<br/>
			new: $PROGHOME/examples/dataconvert/boewrt.optionalheader.dat;<br/>
			$PROGHOME/examples/dataconvert/boewrt.linecomments.dat<br/>
	}}		}}

imported>Schade Peter at 08:45, 6 May 2014

2014-05-06T08:45:11Z

← Older revision		Revision as of 08:45, 6 May 2014
Line 2:		Line 2:
	\|name_de=BOEWRT.DAT		\|name_de=BOEWRT.DAT
	\|filetype=boewrt.dat		\|filetype=boewrt.dat
	\|version=September 2001		\|version=May 2014, classic version September 2001
	\|version_descr=~~April~~ 2014		\|version_descr=May 2014
	\|significance=contains measured or calculated time-series data for the usage in various programs.		\|significance=contains measured or calculated time-series data in ASCII for the usage in various programs.
	===~~Remarks about the new version~~===		===General remarks===
	The file format is rather flexible~~:<br />inside the lines of data~~ each of the time ~~formates~~ used by BAW is allowed.~~<br />Use~~ ";" to separate ~~datetime~~ and ~~physical~~ values!<br />~~The date time format with two digit year should not be used further~~.<br />When it is used, the century after $BAWCENTURY (inclusive) is assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900).<br />The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!<br />
			The file has a header where meta data is identified by its position in the file, the first data line e.g. contains the node number. This is the classic boewrt.dat that can be processed by classical methods of BAW's io library. Since May 2014 the new boewrt.dat header can contain key-value pairs with additional meta data, the key Fill_Value is for example followed by a value in real format. The additional meta information is only evaluated by methods of BAW's io_dataset software package.

			Programs using the io and the io_dataset library can read the classical and the new version. The data part is for both the same and rather flexible; each of the ASCII time formats used by the BAW is allowed. But the date and time format with two digit year should not be used any longer. A ";" should be used to separate date and time from the values of the quantities. <br/>

			But the libraries interpret the meta information in a different way. <br/>

			===IO library preferrably for classic boewrt.dat===
			This library can process additional information by evaluating environment variables. If the coordinate reference system is not given in the file, the value of the environment variable $BAWCRS will be assigned to the file content.

			When it is used, the century after $BAWCENTURY (inclusive) is assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900).
			<br />The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!<br />


	The reading procedure supports the coordinate reference System in the following manner:<br />		The reading procedure supports the coordinate reference System in the following manner:<br />
	If the environment variable $BAWCRS is set to a valid value (EPSG code), the station coordinate will be transformed to that system during the reading process on the fly. If the file CRS is not valid, the coordinate is used "as is". The user should set $BAWCRS when using the programs listed below.<br />		If the environment variable $BAWCRS is set to a valid value (EPSG code), the station coordinate will be transformed to that system during the reading process on the fly. If the file CRS is not valid, the coordinate is used "as is". The user should set $BAWCRS when using the programs listed below.<br />

imported>Seiss Guntram: Description of processing of the CRS and "magic comments"

2014-04-03T13:37:54Z

Description of processing of the CRS and "magic comments"

← Older revision		Revision as of 13:37, 3 April 2014
Line 3:		Line 3:
	\|filetype=boewrt.dat		\|filetype=boewrt.dat
	\|version=September 2001		\|version=September 2001
	\|version_descr=~~June 2010~~		\|version_descr=April 2014
	\|significance=contains measured or calculated time-series data for the usage in ~~different~~ programs.		\|significance=contains measured or calculated time-series data for the usage in various programs.
	===Remarks about the new version===		===Remarks about the new version===
	The file format is rather flexible:<br />inside the lines of data each of the time formates used by BAW is allowed.<br />Use ";" to separate datetime and physical values!<br />The date time format with two digit year should not be used further.<br />When it is used, the century after $BAWCENTURY (inclusive) is assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900).<br />The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!		The file format is rather flexible:<br />inside the lines of data each of the time formates used by BAW is allowed.<br />Use ";" to separate datetime and physical values!<br />The date time format with two digit year should not be used further.<br />When it is used, the century after $BAWCENTURY (inclusive) is assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900).<br />The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!<br />
			The reading procedure supports the coordinate reference System in the following manner:<br />
			If the environment variable $BAWCRS is set to a valid value (EPSG code), the station coordinate will be transformed to that system during the reading process on the fly. If the file CRS is not valid, the coordinate is used "as is". The user should set $BAWCRS when using the programs listed below.<br />
			Files of type boewrt.dat may contain three Special comments at the top, which contain Minimum and Maximum time step and the FORTRAN Format of the data records. These comments are used to accelerate the reading procedure, when data are in ascending order in time and the records are uniformly formatted. On failure of reading a file, these comments should be erased. Files manipulated by an Editor should never contain these comments!
	\|filecontents=		\|filecontents=
	# nodenumber and (optional) timezone and coordinate system		# nodenumber and (optional) timezone and coordinate reference System (CRS). This record has to be written FORMATTED with FORTRAN-Format "(I10,1X,A4,1X,A5)". Preferably you should use known abbreviations for the time zones ("CET", "CEST", "UTC"). For the coordinate reference system of the station coordinate the EPSG codes used by BAW (see at [[GEOTRANSFORMER]] for example) should be used.
	# name of the ~~location~~		# name of the Location (written with FORTRAN-Format "(A)").
	# coordinates (x,y) of the ~~location~~		# coordinates (x,y,z) of the Station position (unformatted with separating blanks!)
	# number and type-codes for the physical quantities stored in the file		# number and type-codes for the physical quantities stored in the file (FORTRAN-Format "(I10,nI8)".
	# date, time and data for each time-step stored		# date, time and data for each time-step stored. Preferably the date and time should be separated from the physical values by a ";"-character.
	\|nutzerprogramme=		\|nutzerprogramme=
	[[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]		[[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]
	\|language=~~Fortran90~~		\|language=Fortran95
	\|fileform=FORMATTED		\|fileform=FORMATTED
	\|fileaccess=SEQUENTIAL		\|fileaccess=SEQUENTIAL

imported>Juerges Jens at 14:45, 24 June 2010

2010-06-24T14:45:42Z

← Older revision		Revision as of 14:45, 24 June 2010
Line 3:		Line 3:
	\|filetype=boewrt.dat		\|filetype=boewrt.dat
	\|version=September 2001		\|version=September 2001
	\|version_descr=~~May 2009~~		\|version_descr=June 2010
	\|significance=contains measured or calculated time-series data for the usage in different programs.		\|significance=contains measured or calculated time-series data for the usage in different programs.
	===Remarks about the new version===		===Remarks about the new version===
Line 14:		Line 14:
	# date, time and data for each time-step stored		# date, time and data for each time-step stored
	\|nutzerprogramme=		\|nutzerprogramme=
	[[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]		[[EVENTFILTER]], [[EXCELENZ]], [[EXKNO]], [[FD2MET]], [[FRQWF]], [[GEOTRANSFORMER]], [[GVIEW2D]], [[HVIEW2D]], [[MESKOR]], [[ROSE]], [[TIDKEN]], [[TSCALC]], [[UNTRIM2007MONITOR]], [[UTRRND]], [[VVIEW2D]], [[XTRDATA]], [[ZEITRIO]]
	\|language=Fortran90		\|language=Fortran90
	\|fileform=FORMATTED		\|fileform=FORMATTED

imported>BAWiki 2 at 12:54, 1 June 2010

2010-06-01T12:54:49Z

← Older revision		Revision as of 12:54, 1 June 2010
Line 6:		Line 6:
	\|significance=contains measured or calculated time-series data for the usage in different programs.		\|significance=contains measured or calculated time-series data for the usage in different programs.
	===Remarks about the new version===		===Remarks about the new version===
	The file format is rather flexible:		The file format is rather flexible:<br />inside the lines of data each of the time formates used by BAW is allowed.<br />Use ";" to separate datetime and physical values!<br />The date time format with two digit year should not be used further.<br />When it is used, the century after $BAWCENTURY (inclusive) is assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900).<br />The time zone is used only, when the used begin or end date have a defined time zone.<br />For this case MEZ is assumed for the file, when the file contains no time zone!
	inside the lines of data each of the time formates used by BAW is allowed.
	Use ";" to separate datetime and physical values!
	The date time format with two digit year should not be used further.
	When it is used, the century after $BAWCENTURY (inclusive) is assumed. You should specify $BAWCENTURY inside your environment (DEFAULT: 1900).
	The time zone is used only, when the used begin or end date have a defined time zone.
	For this case MEZ is assumed for the file, when the file contains no time zone!
	\|filecontents=		\|filecontents=
	# nodenumber and (optional) timezone and coordinate system		# nodenumber and (optional) timezone and coordinate system
Line 25:		Line 19:
	\|fileaccess=SEQUENTIAL		\|fileaccess=SEQUENTIAL
	\|fileextension=.dat		\|fileextension=.dat
	\|writemodules=$PROGHOME/fortran/lib/io~~<br />~~/*/mod_boewrt_io.f90:write_boewrt_info		\|writemodules=$PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:write_boewrt_info
	\|readmodules=$PROGHOME/fortran/lib/io~~<br />~~/*/mod_boewrt_io.f90:read_boewrt_info		\|readmodules=$PROGHOME/fortran/lib/io/*/mod_boewrt_io.f90:read_boewrt_info
	\|contact_original=[mailto:ingrid.uliczka@baw.de I. Uliczka]		\|contact_original=[mailto:ingrid.uliczka@baw.de I. Uliczka]
	\|contact_maintenance=[mailto:guntram.seiss@baw.de G. Seiß]		\|contact_maintenance=[mailto:ingrid.uliczka@baw.de I. Uliczka], [mailto:guntram.seiss@baw.de G. Seiß]
	\|examplefile=$PROGHOME/examples/zeitrio/boewrt.new.dat<br />		\|examplefile=$PROGHOME/examples/zeitrio/boewrt.new.dat<br />
	$PROGHOME/examples/zeitrio/boewrt.dat		$PROGHOME/examples/zeitrio/boewrt.dat
	}}		}}

imported>BAWiki 1 at 09:33, 25 May 2010

2010-05-25T09:33:10Z

← Older revision		Revision as of 09:33, 25 May 2010
Line 27:		Line 27:
	\|writemodules=$PROGHOME/fortran/lib/io<br />/*/mod_boewrt_io.f90:write_boewrt_info		\|writemodules=$PROGHOME/fortran/lib/io<br />/*/mod_boewrt_io.f90:write_boewrt_info
	\|readmodules=$PROGHOME/fortran/lib/io<br />/*/mod_boewrt_io.f90:read_boewrt_info		\|readmodules=$PROGHOME/fortran/lib/io<br />/*/mod_boewrt_io.f90:read_boewrt_info
	\|contact_original=[mailto:ingrid.uliczka@baw.de I.Uliczka]		\|contact_original=[mailto:ingrid.uliczka@baw.de I. Uliczka]
	\|contact_maintenance=[mailto:guntram.seiss@baw.de G. Seiß]		\|contact_maintenance=[mailto:guntram.seiss@baw.de G. Seiß]
	\|examplefile=$PROGHOME/examples/zeitrio/boewrt.new.dat<br />		\|examplefile=$PROGHOME/examples/zeitrio/boewrt.new.dat<br />
	$PROGHOME/examples/zeitrio/boewrt.dat		$PROGHOME/examples/zeitrio/boewrt.dat
	}}		}}