Indicates the breathing gas consumption volume for this breathing gas.
Last statement inside the < mix> section.
Example: see < tank>
Additional (optional) information is bracketed with <addinfo>.
Elements inside <addinfo> are: < persinfo>, < totaldives>, and < serialid>.
Stands in the file header after the < device> section and before <repgroup>.
Example:
<!-- previous statements -->
</device>
<addinfo>
<persinfo>+49-931-123456</persinfo>
<totaldives>124</totaldives>
<serialid>71.60.66</serialid>
</addinfo>
<repgroup>
<!-- following statements -->
Warnings of the recording dive computer. At the time the following keywords are recognized:
keyword announcement of dive computer
-----------------------------------------------------------------
rbt remaining bottom time exceeded
error general error (deco stop missed, etc.)
ascent ascent too fast
deco announcement of a deco stop
breath breathing frequency too high
surface surface reached
Stands inside the < samples> section after the belonging depth statement. Various warnings can follow after one depth statement.
Example: see 2. example < samples>
Height above sealevel of the entrance given as a real number with one digit after decimalcomma.
Stands inside the < dive> section after < density> as the last statement before the < gases> section.
Example:
<!-- height above sealevel 800m (Walchensee - a lake in the Bavarian alps) -->
<altitude>800.0</altitude>
Depth statement given as a real number in Meter (SI, metric) or feet (imperial), respectively.
Stands inside the < samples > section.
The first and last depth statement inside a dive profile must be <d>0.0</d>, because every dive begins and ends at the surface at a depth of 0m (but in Datatrak files, for example, a dive profile does not begin at 0m :-) )
Example: see < samples>
Inside this section specific information concerning the data format used by Aladin dive computers manufactured by Uwatec are given. At time the following elements are used:
Stands inside the optional < program> section as the only statement.
example:
<!-- previous statements -->
</gases>
<program>
<datatrak>
<tissues>8</tissues>
<!-- 2 bytes per tissue, not decoded yet -->
<ip> 95 11</ip>
<ip>103 11</ip>
<ip>107 11</ip>
<ip>110 11</ip>
<ip>224 11</ip>
<ip>156 12</ip>
<ip>122 12</ip>
<ip>212 11</ip>
</datatrak>
</program>
<deltamode/>
<samples>
<!-- here profile data -->
The date at which the dive was performed or the profile was generated by a program, respectively.
The elements inside <date> are: < year>, < month> and < day>, exactly in this order.
Stands inside the < day> section after < place> (if given) and before < time>.
Example:
<profile udcf="1">
<!-- here statements about units used and manufacturer -->
<repgroup>
<dive>
<!-- here statements about place, if known -->
<!-- date April 6th, 1999 -->
<date><year>1999</year><month>4</month><day>6</day></date>
<!-- here more statements -->
</dive>
<!-- following statements -->
</profile>
The day of the month, in which the dive was performed or the profile was generated by a program, respectively, given as an integer number.
Stands inside < date>. The sequence is < year>, < month>, < day>.
Example: see < date>
Indicates the time interval, with which the subsequent depth statements were recorded. This statement is active after the following depth statement.
<delta> is the first statement inside the < samples> section, if switched to < deltamode/> before; it is allowed to appear as often as necessary inside the < samples> section.
Example: see 2. example < samples>
Indicates that inside the < samples> section follow only depth statements (with constant time interval).
Stands directly before the < samples> statement. See also < timedepthmode/>.
When using < deltamode/> it's necessary that the first statement inside the following < samples> section is a < delta> statement to provide the recording time interval.
Example: see < samples>
Density of water.
Stands inside the < dive> section after < temperature> and before < altitude>.
Pure freshwater has a density of 1000.0 kg/m^3, whereas the mean density of seawater (saltwater) is 1030.0 kg/m^3.
Examples:
<!-- saltwater -->
<density>1030.0</density>
<!-- freshwater -->
<density>1000.0</density>
Inside this section the information about the manufacturer of the recording dive computer or the generating program, respectively, are bracketed.
The elements inside <device> are: < vendor>, < model>, and < version>, in this order.
Belongs to the file header and stands after the < units> statement.
Example:
<profile udcf="1">
<units>metric</units>
<device>
<vendor>Suunto</vendor>
<model>EON</model>
<version>1</version>
</device>
<!-- here more statements -->
</profile>
inside a < repgroup> section the data for a specific profile are bracketed inside the <dive> section. When there are several dive profiles inside a lt; repgroup> section each profile is capsuled by <dive>. In this case several <dive> sections follow each other.
The elements, with which a dive profile is clearly described are as follows: < place>, < date>, < time>, < surfaceinterval>, < temperature>,< density>, < altitude>, < gases>, < program>, and < samples>.
Example:
<profile udcf="1">
<!-- here information about the units used and the manufacturer -->
<repgroup>
<dive>
<place>Illes Medes, coast, arch (Costa Brava, Spain)</place>
<date><year>1999</year<month>4</month><day>6</day>></date>
<time><hour>16</hour><minute>21</minute></time>
<surfaceinterval>293.0</surfaceinterval>
<temperature>12.0</temperature>
<density>1030.0</density>
<altitude>0.0</altitude>
<gases>
<!-- here information about the breathing gases used -->
</gases>
<program>
<!-- here dive computer- or program-specific data -->
</program>
<samples>
<!-- here time/depth statements describing the profile -->
</samples>
</dive>
<dive>
<!-- place, date, time, breathing gases, profile data -->
</dive>
<!-- here can follow more dive profiles -->
</repgroup>
</profile>
inside this section the breathing gases used (one or more) are specified. For each gas used a several < mix> section must be given.
The <gases> section stands inside the < dive> section after < altitude> and before < program>.
Example:
<!-- previous statements of the UDCF file -->
<altitude>0.0</altitude>
<gases>
<!-- first breathing gas used -->
<mix>
<mixname>air</mixname>
<tank>
<!-- here additionally the tankvolume can be given -->
<pstart>20000000.0</pstart>
<pend>10400000.0</pend>
</tank>
<o2>0.21</o2>
<n2>0.79</n2>
<he>0.0</he>
<!-- here additionally the gas consumption volume can be given -->
</mix>
<!-- second gas used -->
<mix>
<!-- spezification of the second breathing gas -->
</mix>
<!-- here more breathing gases can follow -->
</gases>
<program>
<!-- here follow more statements -->
The fraction of Helium in the breathing gas, given as a real number less or equal 1.0 in percent (of volume).
Stands inside the < mix> section after < n2> and before < acv> (if given).
Example:
<-- fraction of 90% Helium -->
<he>0.9</he>
The full hour at which the dive is performed or the profile is generated by a program, respectively, given as an integer number.
Stands inside the < time> section. The required order is <hour>, < minute>.
Example: see < time>
At arbitrarily chosen positions comments can be inserted. A comment begins with the characters "<!--" and ends with "-->". In between this arbitrarily chosen strings are possible (carriage return, too).
Example: <!-- This is a comment. -->
The minutes of the hour at which the dive was performed or the profile was generated by a program, respectively, given as an integer number.
Stands inside the < time> section. The required order is < hour>, <minute>.
Example: see < time>
The statements bracketed by <mix> define a breathing gas used. When more than one gas is used, several <mix> sections follow each other.
The elements which clearly define a breathing gas are as follows: < mixname>, < tank>, < o2>, < n2>, < he>, and < acv>.
Stands inside the < gases> section.
Example: see < gases>
The unambiguous name of a breathing gas.
To switch to a specific breathing gas inside the < samples> section this name is used by the statement < switch>.
<mixname> is the first element inside the < mix> section.
Example: see < gases>
inside <model> the model of the recording dive computer or the name of the generating program, respectively, is given.
Stands inside the < device> section after < vendor> and before < version>.
Example: see < device>
The month in which the dive was performed or the profile was generated by a program, respectively, given as an integer number.
Stands inside the < date> section. The required order is < year>, < month>, < day>.
Example: see < date>
The fraction of nitrogen in the breathing gas, given as a real number less or equal 1.0 in percent (of volume).
Stands inside the < mix> section after < o2> and before < he>.
Example:
<mixname>my_nitrox</mixname>
<tank>
<!-- information for the gas consumption calculation -->
</tank>
<!-- oxygen fraction 37,5% -->
<o2>0.375</o2>
<n2>0.625</n2>
<he>0.0</he>
The fraction of nitrogen in the breathing gas, given as a real number less or equal 1.0 in percent (of volume).
Stands inside the < mix> section after < mixname> and < tank> (if given) and before < n2>.
Example:
<mixname>my_nitrox</mixname>
<tank>
<!-- information for the gas consumption calculation -->
</tank>
<!-- oxygen fraction 37,5% -->
<o2>0.375</o2>
<n2>0.625</n2>
<he>0.0</he>
Fill pressure of tank at the end of dive.
Stands (if given) inside the optional < tank> section as the last statement after < pstart>.
Example: see <tank>
Here some personal information can be given, if wanted.
Stands inside the (optional) < addinfo> section as the first statement (if given).
Example: see < addinfo>
The place where the dive was performed - if known.
If the place is known, <place> is the first statement inside the < dive> section, otherwise it is dropped.
Example:
<profile udcf="1">
<!-- here some general statements -->
<dive>
<place>Illes Medes, coast, arch (Costa Brava, Spain)</place>
<!-- here more statements -->
</dive>
<!-- here more statements -->
</profile>
Each UDCF file begins with <profile udcf="1"> and ends with </profile> as the last statement. In between these all other statements are given.
Program specific information, which is necessary for the calculation of the tissue saturation or internal parameters for the graphical presentation of data, respectively, are bracketed inside <program>.
The data between <program> and </program> are not analysed by an UDCF parser, but are forwarded to the calling program. This allows to provide specific meta-information, which are unknown to UDCF. The only convention is, that every program has to place its meta-information inside <program> and </program>.
Note for programmers: please document how tissue saturation parameters or other important information are provided in your <program> section to allow other programs to correctly read and interpret the data!
At the time the following keywords are supported: < datatrak>, < tausim>.
<program> stands inside the < dive> section after the < gases> and before the < samples> section.
Example: see < datatrak> and < tausim>
Fill pressure of tank at the beginning of dive.
Stands inside the optional < tank> section after < tankvolume> (if given) and before < pend> (if given).
Opposite to < tankvolume> or < pend>, which can be given alternatively, <pstart> must always be given inside the < tank> section. Otherwise a gas consumption calculation wouldn't be possible.
Example: see < tank>
With <repgroup> "related dives" are grouped together. Here "related dives" means, that all the dives have a finite surface interval (except the first one) and were all performed during a holiday, for example. The single dives inside <repgroup> are devided from each other by the element < dive>.
Several <repgroup> sections can appear directly after each other. Inside a <repgroup> section at least one dive must appear. The first dive in a <repgroup> section should show an "infinite" surface interval.
Example:
<profile udcf="1">
<!-- here statements concerning units and the manufacturer -->
<repgroup>
<dive>
<!-- here information concerning the first dive -->
<!-- (should show an infinite surface interval) -->
</dive>
<dive>
<!-- here information concerning the second dive -->
<!-- (should show a finite surface interval) -->
</dive>
<dive>
<!-- here information concerning a third dive -->
<!-- (should show a finite surface interval) -->
</dive>
</repgroup>
<repgroup>
<!-- here more dive profiles follow -->
</repgroup>
</profile>
Inside <samples> the real profile data are stored (only depth statements at constant time interval or time and depth statements, respectively, and possibly warnings given by the dive computer). As well the presently used breathing gas or gas changes are given here. The occurence of the first < switch> statement directly after <samples> is required.
<samples> is the last section inside a < dive> section.
Example 1:
<!-- more statements -->
<!-- profiles generated by dive simulation programs -->
<!-- normally use "timedepthmode" and provide time and -->
<!-- depth statements -->
<timedepthmode/>
<samples>
<!-- at beginning of dive use breathing gas "1" -->
<!-- (defined in the <gases> section) -->
<switch>1</switch>
<!-- a dive always starts at 0 minutes and at the surface at 0 metre ! -->
<t>0.0</t><d>0.0</d>
<t>5.0</t><d>40.0</d>
<t>15.0</t><d>40.0</d>
<t>18.0</t><d>28.0</d>
<t>25.0</t>15.0<d></d>
<t>31.0</t><d>6.0</d>
<!-- switch to breathing gas "2" -->
<switch>2</switch>
<t>34.0</t><d>3.0</d>
<t>38.0</t><d>3.0</d>
<!-- a dive always ends at the surface at 0 metre ! -->
<t></t><d>0.0</d>
</samples>
</dive>
<!-- here more dives can follow -->
Example 2:
<!-- previous statements -->
<!-- dive computer do the recordings at a constant time interval -->
<!-- and only store the depths, therefore an additional giving -->
<!-- of time to each depth can be dropped -->
<deltamode/>
<samples>
<!-- depths recorded with a 20 seconds interval -->
<delta>20.0</delta>
<!-- use air at beginning of dive -->
<!-- (defined in <gases> section) -->
<switch>air</switch>
<!-- a dive always starts at 0 minutes and at the surface at 0 metre ! -->
<d> 0.0</d>
<d> 4.7</d>
<d> 7.0</d>
<d>11.1</d>
<!-- here some more depth statements -->
<d>13.9</d>
<d>13.9</d><work>1</work>
<d>14.1</d><work>1</work>
<d>14.5</d><work>1</work>
<d>15.0</d><work>1</work>
<d>15.2</d>
<d>13.8</d>
<d>12.8</d><alarm>ascent</alarm>
<d>10.2</d>
<d> 9.4</d>
<d> 8.1</d>
<d> 7.2</d>
<d> 6.1</d>
<d> 5.3</d>
<d> 4.2</d><alarm>breath</alarm>
<d> 3.4</d>
<d> 3.6</d>
<d> 4.1</d>
<d> 3.6</d>
<d> 2.8</d>
<d> 2.7</d>
<d> 2.0</d>
<d> 1.1</d>
<!-- a dive always ends at the surface at 0 metre ! -->
<d>0.0</d>
</samples>
</dive>
<!-- here more dives can follow -->
Serial number of the recording dive computer.
Stands inside the (optional) < addinfo> section as last statement (if given) after < totaldives> (if given).
Example: see < addinfo>
The surface interval between two subsequent dives.
If the following dive is a "repetitive dive" (tissues not yet fully desaturated), the surface interval is given in seconds as a real number with one digit after the decimal point. When all the tissues are desaturated the keyword "infinity" is bracketed by <surfaceinterval> instead.
Stands inside the < dive> section after the statements concerning place, date, and time, and before < temperature>.
Examplee:
<!-- surface interval 36 minutes: -->
<surfaceinterval>2160.0</surfaceinterval>
<!-- tissues fully desaturated -->
<surfaceinterval>infinity</surfaceinterval>
Indicates the breathing gas used.
Stands inside the <samples> section before the first depth or time/depth statement, respectively. In < deltamode/> it's the second statement after < delta>, in < timedepthmode/> it's the first statement.
The statement is effective after the following depth or time/depth statement, respectively. It's possible to arbitrarily often change the breathing gas used.
Example: see < samples>
The absolutely elapsed time since beginning of dive, given in minutes (metric or imperial units, respectively) or seconds (SI units).
Stands inside the <samples> section.
The first <t> statement must be <t>0.0</t> (in connection with <d>0.0</d>).
Example: see < samples>
In this section the necessary information to perform a gas consumption calculation is given.
Elements inside <tank> are: < tankvolume>, < pstart>, and < pend>.
<tank> follows directly after < mixname> and before the breathing gas statements inside the < mix> section.
Example 1:
<!-- previous statements -->
<mix>
<mixname>air</mixname>
<tank>
<tankvolume>10.0</tankvolume>
<pstart>20000000.0</pstart>
<!-- because the air consumption volume is given below -->
<!-- the information concerning the fill pressure at the -->
<!-- end of dive can be dropped here -->
</tank>
<o2>0.21</o2>
<n2>0.79</n2>
<he>0.0</he>
<acv>20.0</acv>
</mix>
<!-- more statements -->
Example 2:
<!-- previous statements -->
<mix>
<!-- the name of the gas used is allowed to be just a digit for example -->
<mixname>1</mixname>
<tank>
<!-- since fill pressures at beginning and end of dive -->
<!-- are given the air consumption volume can be calculated -->
<!-- without knowing the tankvolume -->
<pstart>20000000.0</pstart>
<pend>10400000.0</pend>
</tank>
<o2>0.21</o2>
<n2>0.79</n2>
<he>0.0</he>
</mix>
<!-- more statements -->
The volume of the tank used in litre (SI, metric) or cubic feet (imperial), respectively.
Stands inside the optional < tank> section as first statement (if given) before < pstart>.
Example: see <tank>
Bracketing of specific information concerning the dive simulation program "Tausim". At time (Tausim v0.99) the following elements are used:
Stands inside the optional < program> section as the only statement.
example:
<!-- previous statements -->
</gases>
<program>
<tausim>
<pres>4000000.0</pres>
<timeinc>5</timeinc>
<depthinc>5</depthinc>
<durdep>0</durdep>
<nstatic>7</nstatic>
<rls>50</rls>
<decomodel>ZH-L16</decomodel>
<buehl>5</buehl>
<tissues>16</tissues>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
<ip>75073.70000</ip>
</tausim>
</program>
<timedepthmode/>
<samples>
<!-- profile data follow -->
The lowest water temperature during dive, if known. If unknown the element <temperature> is dropped.
Stands inside the < dive> section after the < surfaceinterval> statement and before < density>. The temperature is given as a real number with one digit after the decimal point.
Example:
<!-- lowest water temperature 12 degrees Celsius -->
<temperature>12.0</temperature>
Alternatively this tag can be used in the samples-section to indicate the temperature of the actual sample.
The time the dive was performed or the profile was generated by a program, respectively.
Elements inside <time> are as follows: < hour> and < minute>, in this required order.
Stands inside the < dive> section after < date>.
Example:
<profile udcf="1">
<!-- here statements concerning units and manufacturer -->
<repgroup>
<dive>
<!-- here statements concerning place (if known) and date -->
<time><hour>16</hour><minute>21</minute></time>
<!-- here more statements -->
</dive>
<!-- here more statements -->
</profile>
Indicates that in the following < samples> section time and depth statements will follow.
Stands directly before the < samples> section. See also < deltamode>.
Opposite to < deltamode/> there is no additional statement inside the following < samples> section concerning the time/depth mode.
Example: see <samples>
Total number of dives.
Stands inside the (optional) < addinfo> section after < persinfo> (if given) and before < serialid> (if given).
Example: see < addinfo>
Indicates the system of units used. Allowed keywords are "si", "metric", or "imperial", respectively.
First statement after < profile udcf="1">.
units: si: pressure [Pa], height [m], temperature [K],
density [kg/m^3], time [s]
metric: pressure [bar], height [m], temperature [degrees Celsius],
density [kg/m^3], time [min]
imperial: pressure [psi], height [feet], temperature [degrees Fahrenheit],
density [ ??? ], time [min]
Example:
<profile udcf="1">
<units>metric</units>
<!-- here more statements -->
</profile>
The manufacturer of the recording dive computer or the generating dive simulation program, respectively.
Stands inside the < device> section as first statement before < model>.
Example: see < device>
The version number of the recording dive computer or the generating dive simulation program, respectively.
Stands inside the < device> section as last statement after < model>.
Example: see < device>
Indicates the work load when using air integrated dive computers. At the time the following degrees in Datatrak files are recognized: 1, 2, and 4.
Stands inside the <samples> section and after the belonging depth statement.
Example: see 2. example < samples>
The year in which the dive was performed or the profile was generated by a program, respectively, should be given as a four digit :-) integer number. (integer) erfolgen.
Stands inside the < date> section. The required sequence is <year>, < month>, and < day>.
Example: see < date>