Buoy metadata notifcation scheme
Buoy metadata and buoy deployment notification scheme (EGOS&DBCP)
Version 2.1, 6 January 2004
The EGOS sub-group comprised of Anne A. Hageberg, Enrique Alvarez Fanjul, and Etienne
Charpentier met in Toulouse, 2-3 October 2003, and defined the buoy metadata database
relational model based upon DBCP and EGOS user requirements as requested by the EGOS
Management Committee meeting, Madrid, 27_28 May 2003. All questions which need to be
answered from the database were reviewed and model created and updated accordingly.
Proposed model is detailed in annex A, detailed description of proposes tables in annex C.
Brief description of required tools is given in annex B. Database will be uploaded through
different means, namely:




By manufacturers upon buoy purchase (via web)
By buoy operators upon buoy deployments (via web)
Manually to complete database with complementary information once it’s known (via web
or locally where the database is implemented, e.g. designated person to make changes)
Automatically based upon data subsequently available (e.g. GTS data access would permit
to initialize GTS starting and ending dates)
It was proposed to use the database as a global database for all buoy data monitored via the
DBCP. Specific developments for EGOS will be defined by EGOS separately. Data from the
database will be available online e.g. via FTP through flat files so that anybody can copy the
information onto its own database.
Developments can be made in two steps:
1. Database implementation and basic tools (data upload, notification web pages, basic
tools to access the data).
2. Advanced tools to query the database (lists, statistics, graphics, maps, etc.).
Only step 1 was considered during this meeting.
In order to simplify relational model and not to add too many fields in the database, it was
proposed to deal with additional information in some tables using an XML field instead of
creating multiple additional fields. Content of XML field will contain information in XML
format by using tags. Some of the tags are defined here. Other tags will be defined later.
Example (here field Mooring type is defined using tag “moortype”, its value is “AC”, i.e. “All
Chain”):
<?xml version="1.0"?>
<BUOYPERIOD>
<param name=”moortype” type=”ASCII” units=”none”>
AC
</param>
</BUOYPERIOD>
-1/62-
Buoy metadata notifcation scheme
Annex A
Proposed buoy metadata database relational model
Diagrams 1 to 4 show the relational model of the proposed database, how tables are linked together, etc.
Diagram 1: Relational model for batches of buoys
-2/62-
Buoy metadata notifcation scheme
Diagram 2: Relational model for BUOYPERIODs
-3/62-
Buoy metadata notifcation scheme
Diagram 3: Relational model for contacts
-4/62-
Buoy metadata notifcation scheme
Diagram 4: Relational model for pictures
-5/62-
Buoy metadata notifcation scheme
Specific comments:
Table BUOYPERIOD
Table BUOYPERIOD corresponds to a physical buoy operated during an operational
period. In practice there is only one BUOYPERIOD record for a drifting buoy unless
it’s being refurbished (or redeployed at another location after displacement, e.g. after
fishing vessel pickup). For moored buoys we have as many BUOYPERIODs as periods
of the buoy operations with no human intervertion. In other words, whenever
maintenance is being done on a moored buoy we have to create a new BUOYPERIOD
record. One single moored buoy position (or one drifting buoy refurbished several
times) is identified with field SERIAL_NO. Each time a new BUOYPERIOD is added
for a given serial number, field PERIOD_NO is increment by 1 (initial value=1).
XMLtags:
chul: Colour of the hull
mhul: Markings on the hull
af: Anti-fouling
dfmt: GTS data format
plt: Payload type
argosprog : Argos programme number
To be defined by Enrique: Deployment conditions
package_type: Packaging type
depl_height: deployment height
depl_speed: deployment ship speed
depl_ship: deployment ship
Table EQUIPMENT
Any equipment attached to the buoy, e.g. transmitter, GPS unit, radar reflector,
navigation light, mooring line, data processing unit. Details about the equipment are
stored in the XML field.
Typical equipments:

MOORING
Mooring type is indicated using XML tag moortype which can take following
values
AC: All chain
ST: Semitaut
FC: Float inverse
PC: Poly-nylon inverse catenary
OT: Other
-6/62-
Buoy metadata notifcation scheme
Mooring line is indicated using XML tag moorline which can take following values:
SW: Steel wire
NR: Nilon rope
PLYPRO: Polypropylene
VC: Vectron
KV: Kevlar
OT: Other
Ratio between mooring length and water depth is indicated using tag sope_ratio
(indicates degree of tautness or lack of tautness)

TRANSMITTER
XML tags
TX_POWER: Output power of transmitter
tx_type: Type of transmitter

CONTROLLER
XML tags:
controller_type: Type of controller

GPS
XML tags:
GPSt : GPS type
GPSa: GPS Antenna type

RADAR_REFLECTOR

NAVI_LIGHT

DATA_PROCESSING_UNIT

BATTERY
XML tags:
bct: Cell type
nc : Number of cells
ncs : Number of cell series
vol : Voltage
bc : Battery capacity
battery_descr: Description of battery pack
voltage_sensor: Type of battery voltage sensor
-7/62-
Buoy metadata notifcation scheme
Table BUOYBATCH
This table corresponds to an order of several identical buoys to a manufacturer. Basic
information on such buoys is initially entered together and then automatically written
into other appropriate tables (e.g. BUOYPERIOD).
Table SENSORBATCH
Sensor batch table. One record for every sensor of the buoy batch. For example, if
there is a thermistor string with probes at different levels we'll have to create as many
sensors as there are probes (field SENSOR_HEIGHT used to indicate the probe level).
Table EQUIPMENTBATCH
Any equipment batch attached to the considered batch of buoys, e.g. transmitter, GPS
unit, radar reflector, navigation light, mooring line, data processing unit. Details about
the equipment are stored in the XML field.
Table BUOYBATCH_PROGRAM
Many to many relationship between table BUOYBATCH and table PROGRAM to
indicate to what program(s) a buoy batch belongs to or is participating to.
Table BUOYMODEL
A buoy model is a particular type of buoy as proposed in the manufacturer’s
catalogue, e.g. C/S of CMR is a particular type of buoy made by CMR company.
XML tags:
drdi: Drogue diameter
drl: Drogue length in meters (Lagrangian drifters)
sfd: Surface float description
td: Tether description
drd: Detailed drogue description (Lagrangian drifters)
csaa: Cross section area above float (cm2) (Lagrangian drifters)
csda: Cross section area of the drogue (cm2) (Lagrangian drifters)
sr: Stress relief
dar: Drag area ratio
floatdescr: Detailed description of surface float (Lagrangian drifters) (e.g. 41 cm.
diameter, ABS plastic surface float.)
tetherdescr: Detailed tether description (Lagrangian drifters)
droguesen_type: Drogue sensor type (Lagrangian drifters)
drogue_attach_type: Type of drogue attachment
Table BUOYTYPE
-8/62-
Buoy metadata notifcation scheme
A buoy type is a generic type of buoy, e.g. SVPB (Lagrangian drifter equipped with
barometer). See WMO documentation and BUFR descriptor 0 02 149 "Type of data
buoy". Examples of types of buoys:
ABBREV
UNKNOWN
SVP
FGGE
FGGEW
ICE_LOAT
FLOAT
SOFAR
ALACE
MARVOR
RAFOS
MOORING
NOMAD
DISCUS_3
DISCUS_10
ODAS-30
ATLAS
TRITON
OMNI_WAVE
DIR_WAVE
ARGO
NAME_
Unspecified drifting buoy
Standard Lagrangian drifter (Global Drifter
Programme)
Standard FGGE type drifting buoy
(non-Lagrangian meteorological drifting buoy)
Wind measuring FGGE type drifting buoy
(non-Lagrangian meteorological drifting buoy)
Ice float
Unspecified sub-surface float
SOFAR
ALACE
MARVOR
RAFOS
Unspecified moored buoy
Nomad
3-metre discus
10-12-metre discus
ODAS 30 series
ATLAS (e.g. TAO area)
TRITON buoy
Omnidirectional waverider
Directional waverider
Sub-surface ARGO float
Table SENSOR
XML tags:
senDB: distance of sensor from the bow or front of platform
senDC: Distance of sensor from center of discus
senL: Sensor location. Possible values:
FM: Foremast
AM: Aftermast
CM: Centermast
RY: Right yardarm
LY: Left yardarm
OT: Other
Or a description in free format
cmpT: Compass type
apWG: Averaging period (seconds), wind gust
amWG: Averaging method, wind gust. Possible values:
S: Scalar
-9/62-
Buoy metadata notifcation scheme
V: Vector
mSA: Method used to compute salinity (e.g. chlorinity, electrical, conductivity,
refractive index, etc.)
Nblks: Number of blocks used for averaging - wave spectra
Npts: Number of points in each block - wave spectra
Table SENSORMODEL
XML tags:
anmI: Anemometer type. Possible values:
P: Propeller
T: Three cup
FC: Four cup
S: Sonic
WT: Wotan
OT: Other
ats: Air temperature instrumentation type. Possible values:
ER: Electrical resistance thermometer
M: mercury in glass thermometer
MS: screen shelter mercury thermometer
AG: Alcohol in glass thermometer
AS: Screen shelter – alcohol thermometer
OT: Other
wts: Water temperature instrumentation type. Possible values:
Value
Name
HC
Hull contact sensor
HT
‘Through hull’ sensor
RT
Radiation thermometer
ER
Electrical resistance thermometer
TT
Trailing thermistor
BU
Bucket thermometer
CTD
CTD ( conductivity-temperature-depth)
STD
STD (salinity-temperature-depth)
RM
refractometer
XC
XCTD (expendable CTD probe)
NS
Nansen cast
AL
ALACE (autonomus Lagrangian Circulation Explorer)
XBT
Expendable Bathythermograph
OT
Other (specify in footnote # 1 in the water temperature data record)
satp: Salinity sensor instrumentation type. Possible values:
Value
Name
CTD
CTD ( conductivity-temperature-depth)
STD
STD (salinity-temperature-depth)
RM
refractometer
-10/62-
Buoy metadata notifcation scheme
XC
XCTD (expendable CTD probe)
NS
Nansen cast
AL
SEABIRD
ALACE
(autonomus
Lagrangian
Explorer)
Seabird type conductivity sensor
FSI
FSI type conductivity sensor
OT
Other (specify in footnote # 1 in the salinity data
record)
Circulation
hs: Relative humidity instrumentation type. Possible values:
WB: Wet bulb
DP: Dew point
CP: Capacity sensor
OT: Other type of hygrometer
pg: Precipitation gauge instrumentation type. Possible values:
WB: Weighing bucket
TIP: Tipping
BU: Bucket
CG: Capacitance gauge
OG: Optical gauge
OT: Other
srs: Solar radiation sensor instrumentation type. Possible values:
PYRANO: Pyranometer
PYRGEO: Pyrgeometer (loss of heat by radiation from the earth's surface)
OT: Other
wasp: Wave spectra - type of surface elevation sensor (From which wave
spectra is derived)
digf: Digital filter used - wave spectra
spAT: Spectral analysis technique (e.g. FFT, MEM, etc.)
Table SENSORTYPE
Generic type of sensor, e.g.










AP: Air Pressure
AT: Air Temperature
SST: Sea Surface Temperature
WT: Water Temperature
WS: Wind speed
WD: Wind Direction
WAVE
WAVE_HEIGHT
WAVE_PERIOD
WAVE_DIR
-11/62-
Buoy metadata notifcation scheme
Table PROGRAM
National or international programme. Programmes are linked to BUOYPERIODs via
table BUOY_PROGRAM.
Table BUOY_PROGRAM
Many to many relationship between table BUOYPERIOD and table PROGRAM to
indicate to what program(s) a buoy belongs to or is participating to.
Table ORGANISM
An agency, institute, university, or private company.
Table CONTACT
Contact points, i.e. programme managers, coordinators, notifiers of deployments,
notifiers of buoy purchase (manufacturers).
Table TELECOMFORMAT
Satellite data telecommunication format, e.g. DBCP-M2 format which is one of the
formats recommended by the DBCP.
Table ENDINGCAUSE
Table containing all possible reasons for end of operational period (e.g. all failure
causes, recovery, maintenance, etc.).
Table COUNTRY
Countries.
Table PICTURE
Pictures.
Table BUOY_PICTURE
Many to many table to associate pictures to buoys, typically pictures corresponding to
an event for a buoy (i.e. PICTURE.EVENT=1)
Management of dates:
DEPL_DATE: Initiated by buoy operator upon deployment (or just after maintenance
in case of mooring) via appropriate web page.
ENDING_DATE: End of period for the considered buoy. For drifting buoys this
corresponds to the end of the operational life-time or the time when the buoy was
-12/62-
Buoy metadata notifcation scheme
picked up, beached, ceased functioning, etc. For a mooring this corresponds to the end
of the period, i.e. just before the next maintenance or to the end of the buoy operations.
GTS_START_DATE: Date when the first observation was distributed on GTS. Set up
automatically through appropriate access to GTS data or manually if no GTS access is
available.
GTS_END_DATE: Date when the last observation was distributed on GTS for the
considered operational period. Set up automatically through appropriate access to GTS
data or manually if no GTS access is available.
DROGUE_LOSS_DATE: Date when the drifter lost its drogue. Set up manually.
MANUF_DATE: Date of manufacturing, provided by manufacturer through
specifications sheet.
Purchase date is obtained through table BUOYBATCH.
-13/62-
Buoy metadata notifcation scheme
Annex B
Basic tools
1. Notification by manufacturer
Dedicated web pages were the manufacturer can log (username/password) and enter
relevant information for a batch of buoys and associated sensors/equipment that was
purchased. Information is initially entered in tables BUOYBATCH,
SENSORBATCH, EQUIPMENTBATCH, BUOYBATCH_PROGRAM, and then
automatically copied onto newly created BUOYPERIODs and associated tables
SENSOR, EQUIPMENT, BUOY_PROGRAM respectively. Purchaser of buoy tells
the manufacturer to what PROGRAM(s) the batch of buoys should be attached. Only
the programme notifier will then be authorized to make changes via the web to created
buoys.
Once the individual BUOYPERIODs have been created, the manufacturer must enter
more specific information for each of them. For example, the serial number or
transmission number will be used by the programme notifyer upon buoy deployment
to complement information.
In case required SENSORMODEL, or BUOYMODEL does not exist in the database,
then the manufacturer must contact the person in charge of the database in order to
create required records.
2. Notification by buoy operator
Upon buoy deployment, the person in charge at the program level of deployment
notification will log in (username/password) the system via the web and enter relevant
and complementary information into the database for tables BUOYPERIOD,
SENSOR, EQUIPMENT, and BUOY_PROGRAM. Only programme notifiers
(NOTIFIER_ID in table PROGRAM) linked to the BUOYPERIOD(s) via table
BUOY_PROGRAM are authorized to make such changes.
3. Handling of GDP files
Annex D provides some details regarding SVPB DBCP-Format Specification Sheet as
provided by Mayra Pazos on 14 March 2003. Specification sheet is dated November 2001.
Examples are given then corresponding fields in metadata database are indicated. At this
point we have two options for drifters participating in the Global Drifter Programme:
(i)
(ii)
Manufacturer’s specification sheet continues to be produced by the manufacturers
and delivered to the GDC once filled out. Then GDC also sends a copy of the sheet
to the person responsible of the global DBCP metadata database so that it can be
loaded automatically. Correspondence between spec sheet and fields in database is
also given in annex D.
GDP relies upon new notification scheme; fields present in the specification’s
sheet are mandatory; when manufacturers fill in DBCP notification web pages,
then the specification’s sheet is automatically produced and forwarded to the GDC
so that GDC can also update its database.
-14/62-
Buoy metadata notifcation scheme
This must be discussed with GDC.
4. Local edition of tables
All tables must be editable individually and locally. Specific screen must be created to
edit/display a BUOYPERIOD and its associated SENSOR(s), EQUIPMENT(s),
BUOY_PROGRAM(s) locally. Associated SENSORMODEL(s), BUOYMODEL(s)
will be edited via drop lists.
5. Basic query to obtain all information concerning a particular BUOYPERIOD
Query fields:
WMO, NAME, SERIAL_NO, TRANSMITTER_NUM,
BUOYMODEL.ABBREV, BUOY_OPERATOR_ID (ABBREV of
ORGANISM), DEPLOY_ORGANISM_ID (ABBREV of ORGANISM),
PROGRAM (via BUOY_PROGRAM).
Results: List of BUOYPERIOD(s) that match the query. Then every individual
BUOYPERIOD can be displayed in more detail.
6. Data access (flat files) via FTP: One flat file per table, e.g. in XML using tags
providing field name, field type, field value. E.g.
<?xml version="1.0"?>
<BUOYPERIOD>
<field name=”DEPL_DATE” type=”DATE” format=”DD/MM/YYYY HH24:MI:SS”>
01/01/2003 12:00:00
</field>
…
</BUOYPERIOD>
-15/62-
Buoy metadata notifcation scheme
Annex D
Database definition of tables
Table Name : BUOYBATCH
Alias
BUOYB
Display Title : Buoy batch
Description :This table corresponds to an order of several identical
buoys to a manufacturer. Basic information on such buoys is
initially entered together and then automatically written
into other appropriate tables (e.g. BUOYPERIOD).
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
NAME_
22
PURCHASE_DATE
25
NB_BUOYS
30
REPETITION_PERIOD
40
DUTY_CYCLE
100
OBS_FREQUENCY
110
TRANSMISSION_SYS
120
LOCATION_SYSTEM
121
MANUFACTURER_ID
122
PURCHASER_ID
125
MODEL_ID
130
TELECOM_FMT_ID
140
XML
Primary Key
--------Name
--BUOYBATCH_PK
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
Column
----ID
Foreign Keys
---------BUOYB_BUOYMOD_FK
MODEL_ID references
Transferable Yes
Mandatory ? Yes
BUOYMODEL.ID
Update Rule Restricted
Delete Rule Restricted
BUOYB_MANUF_FK
MANUFACTURER_ID references ORGANISM.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
BUOYB_PURCHASER_FK
PURCHASER_ID references ORGANISM.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
-16/62-
Type
--NUMBER ()
VARCHAR2 (80)
DATE
NUMBER (3, 0)
NUMBER ()
VARCHAR2 (240)
NUMBER (4, 0)
VARCHAR2 (240)
VARCHAR2 (240)
NUMBER ()
NUMBER ()
NUMBER ()
NUMBER ()
LONG RAW ()
Buoy metadata notifcation scheme
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
NAME_
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Batch name of identification number for the batch
22
PURCHASE_DATE
Optional ? :No ; Date ;() ; ; Uppercase ? :No ;
Date of purchase of the batch of buoys
25
NB_BUOYS
Optional ? :No ; Number (3, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Number of identical buoys from the buoy order.
30
REPETITION_PERIOD
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
Transmission repetition period (seconds), e.g. Argos repetition
period is typically 90s for a drifter
40
DUTY_CYCLE
Optional ? :Yes ; Varchar2 (240) ;() ; ; Uppercase ? :No ;
Satellite transmission duty cycle (e.g. continuous, or 8 hours on,
16 hours on)
100 OBS_FREQUENCY
Optional ? :Yes ; Number (4, 0) ;() ; ; Uppercase ? :No ;
Frequency of observations (number of observations per day)
110 TRANSMISSION_SYS
Optional ? :No ; Varchar2 (240) ;() ; ; Uppercase ? :No ;
Satellite (or other) data telecommunication system.
DCP
ARGOS
VHF
INMARSAT-C
IMNARSAT-D
IRIDIUM
GSM
ORBCOMM
METEOSAT
GOES
GMS
120 LOCATION_SYSTEM
Optional ? :No ; Varchar2 (240) ;() ;
Location system, e.g. ARGOS, GPS
; Uppercase ? :No ;
121 MANUFACTURER_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table ORGANISM for the manufacturer
122 PURCHASER_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table ORGANISM for the purchaser of the batch of buoys
-17/62-
Buoy metadata notifcation scheme
125 MODEL_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table BUOYMODEL of the buoy manufacturer's model
130 TELECOM_FMT_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID in table TELECOMFORMAT of the description of the data
telecommunication format
140 XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
-18/62-
Buoy metadata notifcation scheme
Table Name : BUOYBATCH_PROGRAM
Alias
BUOYB_PROG
Display Title : Buoybatch Program
Description :Many to many relationship between table BUOYBATCH and table
PROGRAM to indicate to what program(s) a buoy batch belongs
to or is participating to. The buoy operator, when
purchasing buoys indicates to the manufacturer to what
programme the batch should be attached.
Column Summary
------------Col.Seq.Column
------ ----10
BUOYBATCH_ID
20
PROG_ID
Primary Key
--------Name
--BUOYB_PROG_PK
Nulls ?
---NOT NULL
NOT NULL
Type
--NUMBER ()
NUMBER ()
Column
----BUOYBATCH_ID
PROG_ID
Foreign Keys
---------BUOYBPROG_BUOYB_FK
BUOYBATCH_ID references BUOYBATCH.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
BUOYBPROG_PROG_FK
PROG_ID references
Transferable Yes
Mandatory ? Yes
PROGRAM.ID
Update Rule Restricted
Delete Rule Restricted
Column Detail
----------10
BUOYBATCH_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table BUOYBATCH of concerned batch of buoys
20
PROG_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table PROGRAM of programme to which the batch of buoys
should be associated
-19/62-
Buoy metadata notifcation scheme
Table Name : BUOYMODEL
Alias
BUOYMOD
Display Title : Buoymodel
Description :A buoy model is a particular type of buoy as proposed in
the manufacturer's catalogue, e.g. C/S of CMR is a
particular type of buoy made by CMR company.
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
ABBREV
30
NAME
50
AIR_DEPL_CERTIF
70
WIDTH
80
HEIGHT_ABOVE
90
TOTAL_HEIGHT
100
WEIGHT
110
HULL_TYPE
120
URL
122
MANUFACTURER_ID
125
BUOYTYPE_ID
127
PICTURE_ID
130
XML
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
NULL
NULL
NOT NULL
NOT NULL
NULL
NULL
Primary Key
--------Name
--BUOYMOD_PK
Column
----ID
Other Unique Keys
-------------Name
--BUOYMOD_UK
Column
----ABBREV
Foreign Keys
---------BUOYMOD_BUOYTYP_FK
BUOYTYPE_ID references BUOYTYPE.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
BUOYMOD_ORGANISM_FK
MANUFACTURER_ID references ORGANISM.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
BUOYMOD_PICT_FK
PICTURE_ID references
Transferable Yes
Mandatory ? No
PICTURE.ID
Update Rule Restricted
Delete Rule Restricted
-20/62-
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
NUMBER ()
NUMBER (5, 2)
NUMBER (5, 2)
NUMBER (5, 2)
NUMBER (6, 1)
VARCHAR2 (10)
VARCHAR2 (240)
NUMBER ()
NUMBER ()
NUMBER ()
LONG RAW ()
Buoy metadata notifcation scheme
Column Detail
----------10
ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
Abbreviation for the buoy model
; Uppercase ? :No ;
30
NAME
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Complete or detailed name for the buoy model
50
AIR_DEPL_CERTIF
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Boolean; Air deployment certification obtained
70
WIDTH
Optional ? :Yes ; Number (5, 2) ;() ; ; Uppercase ? :No ;
Maximum width or diameter of platform (meters)
80
HEIGHT_ABOVE
Optional ? :Yes ; Number (5, 2) ;() ; ; Uppercase ? :No ;
Maximum height (meters) above sea surface
90
TOTAL_HEIGHT
Optional ? :Yes ; Number (5, 2) ;() ; ; Uppercase ? :No ;
Total height (meters) of the platform (i.e. above plus below sea
surface)
100 WEIGHT
Optional ? :Yes ; Number (6, 1) ;() ;
Weight (kg) of the buoy
110 HULL_TYPE
Optional ? :Yes ; Varchar2 (10) ;() ;
Uppercase ? :No ;
Type of buoy hull
; Uppercase ? :No ;
; Domain :HULL_TYPE ;
120 URL
Optional ? :Yes ; Varchar2 (240) ;() ; ; Uppercase ? :No ;
An URL corresponding to a web page providing more details
concerning the buoy model (e.g. manufacturer's web page)
122 MANUFACTURER_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table ORGANISM for the manufacturer
125 BUOYTYPE_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table BUOYTYPE for the corresponding type of buoy
127 PICTURE_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID in table PICTURE for the picture of the buoy model
-21/62-
Buoy metadata notifcation scheme
130 XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
-22/62-
Buoy metadata notifcation scheme
Table Name : BUOYPERIOD
Alias
BUOY
Display Title : Buoyperiod
Description :Table BUOYPERIOD corresponds to a physical buoy operated
during an operational period. In practice there is only one
BUOYPERIOD record for a drifting buoy unless it's being
refurbished (or redeployed at another location after
displacement, e.g. after fishing vessel pickup). For moored
buoys we have as many BUOYPERIODs as periods of the buoy
operations with no human intervertion. In other words,
whenever maintenance is being done on a moored buoy we have
to create a new BUOYPERIOD record. One single moored buoy
position (or one drifting buoy refurbished several times)
is identified with field SERIAL_NO.
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
SERIAL_NO
30
NAME
35
PERIOD_NO
40
DEPL_DATE
50
ENDING_DATE
60
MODIF_DATE
70
MANUF_DATE
80
DROGUE_LOSS_DATE
90
GTS_START_DATE
100
GTS_END_DATE
105
GTS
110
WMO
120
ODAS_NO
130
TRANSMITTER_NUM
140
TRANSMISSION_SYS
150
REPETITION_PERIOD
160
DUTY_CYCLE
165
LUT
170
LOCATION_SYSTEM
180
WATCH_CIRCLE
185
MOORING_DEPTH
190
OBS_FREQUENCY
220
DEPLOYMENT_TYPE
245
DEPL_LAT
247
DEPL_LON
250
ENDCAUSE_ID
260
ENDING_LAT
270
ENDING_LON
280
SCRAPPED
310
DEPLOY_ORGANISM_ID
320
BUOY_OPERATOR_ID
330
BUOYMODEL_ID
340
TELECOM_FMT_ID
350
BUOYBATCH_ID
360
COMMENT_
370
XML
Primary Key
--------Name
Nulls ?
---NOT NULL
NULL
NOT NULL
NULL
NULL
NULL
NOT NULL
NULL
NULL
NULL
NULL
NOT NULL
NULL
NULL
NULL
NOT NULL
NULL
NULL
NULL
NOT NULL
NULL
NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
NULL
NOT NULL
NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
Column
-23/62-
Type
--NUMBER ()
VARCHAR2 (80)
VARCHAR2 (80)
NUMBER (6, 0)
DATE
DATE
DATE
DATE
DATE
DATE
DATE
NUMBER(1, 0)
VARCHAR2 (8)
VARCHAR2 (20)
VARCHAR2 (20)
VARCHAR2 (20)
NUMBER (4, 0)
VARCHAR2 (240)
NUMBER (1, 0)
VARCHAR2 (20)
NUMBER (6, 0)
NUMBER (5, 0)
NUMBER (4, 0)
VARCHAR2 (40)
NUMBER (8, 3)
NUMBER (9, 3)
NUMBER ()
NUMBER (8, 3)
NUMBER (9, 3)
NUMBER (1, 0)
NUMBER ()
NUMBER ()
NUMBER ()
NUMBER ()
NUMBER ()
VARCHAR2 (1000)
LONG RAW ()
Buoy metadata notifcation scheme
--BUOYPERIOD_PK
Other Unique Keys
-------------Name
--BUOY_UK
----ID
Column
----SERIAL_NO
DEPL_DATE
Foreign Keys
---------BUOY_BUOYBATCH_FK
BUOYBATCH_ID references BUOYBATCH.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
BUOY_BUOYMOD_FK
BUOYMODEL_ID references BUOYMODEL.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
BUOY_OPERATOR_FK
BUOY_OPERATOR_ID
Transferable Yes
Mandatory ? Yes
references ORGANISM.ID
Update Rule Restricted
Delete Rule Restricted
BUOY_TELECOM_FM_FK
TELECOM_FMT_ID references TELECOMFORMAT.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
DEPLOY_ORGANISM_FK
DEPLOY_ORGANISM_ID
Transferable Yes
Mandatory ? No
references ORGANISM.ID
Update Rule Restricted
Delete Rule Restricted
BUOY_ENDCAUSE_FK
ENDCAUSE_ID references ENDINGCAUSE.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete rule Restricted
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
SERIAL_NO
Optional ? :Yes ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Serial number of the buoy. All operational periods of a given buoy
should have the same serial number. Normally this number is
attributed by the manufacturer (drifting buoys) or by the buoy
operator (moorings).
30
NAME
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Name of the buoy as attributed by the buoy operator
-24/62-
Buoy metadata notifcation scheme
35
PERIOD_NO
Optional ? :Yes ; Number (6, 0) ;() ; ; Uppercase ? :No ;
Period number of the BUOYPERIOD. Starts with value 1 for the first
operational period for the considered serial number.
40
DEPL_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Initiated by buoy operator upon deployment (or just after
maintenance in case of mooring) via appropriate web page.
50
ENDING_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
End of period for the considered buoy. For drifting buoys this
corresponds to the end of the operational life-time or the time
when the buoy was picked up, beached, ceased functioning, etc. For
a mooring this corresponds to the end of the period, i.e. just
before the next maintenance or to the end of the buoy operations.
60
MODIF_DATE
Optional ? :No ; Date ;() ; ; Uppercase ? :No ;
Date when a mdification was made in the database for that record
and/or associated sensors/equipments (automatic)
70
MANUF_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Date of manufacturing, provided by manufacturer through
specifications sheet.
80
DROGUE_LOSS_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Date when the drifter lost its drogue. Set up manually.
90
GTS_START_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Date when the first observation was distributed on GTS. Set up
automatically through appropriate access to GTS data or manually
if no GTS access is available.
100 GTS_END_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Date when the last observation was distributed on GTS for the
considered operational period. Set up automatically through
appropriate access to GTS data or manually if no GTS access is
available.
105 GTS
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Indicates whether data are distributed on GTS
(at least for some time during the operational period).
Automatically set to false when a BUOYPERIOD is created
110 WMO
Optional ? :Yes ; Varchar2 (8) ;() ;
Buoy WMO number
120 ODAS_NO
Optional ? :Yes ; Varchar2 (20) ;() ;
Buoy ODAS number, if any
-25/62-
; Uppercase ? :No ;
; Uppercase ? :No ;
Buoy metadata notifcation scheme
130 TRANSMITTER_NUM
Optional ? :Yes ; Varchar2 (20) ;() ; ; Uppercase ? :No ;
Data telecommunication system identification number (e.g. ARGOS
number)
140 TRANSMISSION_SYS
Optional ? :No ; Varchar2 (20) ;() ; ; Uppercase ? :No ;
Satellite (or other) data telecommunication system.
DCP
ARGOS
VHF
INMARSAT-C
IMNARSAT-D
IRIDIUM
GSM
ORBCOMM
METEOSAT
GOES
GMS
150 REPETITION_PERIOD
Optional ? :Yes ; Number (4, 0) ;() ; ; Uppercase ? :No ;
Transmission repetition period (seconds), e.g. Argos repetition
period is typically 90s for a drifter
160 DUTY_CYCLE
Optional ? :Yes ; Varchar2 (240) ;() ; ; Uppercase ? :No ;
Satllite transmission duty cycle (e.g. continuous, or 8 hours on,
16 hours on)
165 LUT
Optional ? :Yes ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether an LUT not connected to Argos is being
used
170 LOCATION_SYSTEM
Optional ? :No ; Varchar2 (20) ;() ;
Location system, e.g. ARGOS, GPS
; Uppercase ? :No ;
180 WATCH_CIRCLE
Optional ? :Yes ; Number (6, 0) ;() ; ; Uppercase ? :No ;
Watch circle (meters). Relevant for moorings only.
185 MOORING_DEPTH
Optional ? :Yes ; Number (5, 0) ;() ; ; Uppercase ? :No ;
Depth at which the buoy is moored (moored buoys only)
190 OBS_FREQUENCY
Optional ? :No ; Number (4, 0) ;() ; ; Uppercase ? :No ;
Frequency of observations (number of observations per day)
220 DEPLOYMENT_TYPE
Optional ? :No ; Varchar2 (40) ;() ; ; Domain :DEPLOYMENT_TYPE ;
Uppercase ? :No ; Default Value :UNKNOWN ;
Type of deployment, e.g. AIR, SHIP, R/V (research vessel)
245 DEPL_LAT
Optional ? :Yes ; Number (8, 3) ;() ; ; Uppercase ? :No ;
Deployment position: Latitude in decimal degrees (N>0, S<0).
-26/62-
Buoy metadata notifcation scheme
247 DEPL_LON
Optional ? :Yes ; Number (9, 3) ;() ; ; Uppercase ? :No ;
Deployment position: Longitude in decimal degrees (E>0, W<0).
250 ENDCAUSE_ID
Optional ? :Yes ; Number (9, 3) ;() ; ; Uppercase ? :No ;
ID of cause of end of operational period in table ENDINGCAUSE
260 ENDING_LAT
Optional ? :Yes ; Number (8, 3) ;() ; ; Uppercase ? :No ;
Position at the end of the operational period: Latitude, decimal
degrees (N>0, S<0)
270 ENDING_LON
Optional ? :Yes ; Number (9, 3) ;() ; ; Uppercase ? :No ;
Position at end of operational period: Longitude, decimal degrees
(E>0, W<0)
280 SCRAPPED
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ;
Boolean to indicate that the buoy corresponding to the SERIAL_NO
was scrapped after ENDING_DATE.
310 DEPLOY_ORGANISM_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID of ORGANISM which was in charge of the actual buoy deployment
320 BUOY_OPERATOR_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of ORGANISM which is operating the buoy
330 BUOYMODEL_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of BUOYMODEL (buoy manufacturer's model)
340 TELECOM_FMT_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of TELECOMFORMAT (format of data telecommunication
transmission, e.g. Argos message format)
350 BUOYBATCH_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of BUOYBATCH for the batch of buoys in which the buoy was
ordered
360 COMMENT_
Optional ? :Yes ; Varchar2 (1000) ;() ;
Any coment regarding the buoy
; Uppercase ? :No ;
370 XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
Index Summary
-----------Name
--BUOY_MODEL_IDX
Seq. Column
--- ----5
BUOYMODEL_ID
-27/62-
Index Type
-------NOT UNIQUE
Buoy metadata notifcation scheme
BUOY_ORGANISM_IDX
0
BUOY_OPERATOR_ID
NOT UNIQUE
BUOY_POSITION_IDX
BUOY_POSITION_IDX
2
4
DEPL_LAT
DEPL_LON
NOT UNIQUE
NOT UNIQUE
DEPL_TYPE_IDX
5
DEPLOYMENT_TYPE
NOT UNIQUE
DROGUE_LOSS_IDX
5
DROGUE_LOSS_DATE
NOT UNIQUE
ENDING_CAUSE_IDX
5
ENDING_CAUSE
NOT UNIQUE
GTS_PERIOD_IDX
GTS_PERIOD_IDX
0
2
GTS_START_DATE
GTS_END_DATE
NOT UNIQUE
NOT UNIQUE
TELECOM_SYS_IDX
0
TRANSMISSION_SYS
NOT UNIQUE
-28/62-
Buoy metadata notifcation scheme
Table Name : BUOYTYPE
Alias
BUOYTYP
Display Title : Buoytype
Description :A buoy type is a generic type of buoy, e.g. SVPB
(Lagrangian drifter equipped with barometer). e.g.
See WMO documentation and BUFR descriptor 0 02 149 "Type of
data buoy"
UNKNOWN Unspecified drifting buoy
SVP
Standard Lagrangian drifter (Global Drifter
Programme)
FGGE
Standard FGGE type drifting buoy
(non-Lagrangian meteorological drifting
buoy)
FGGEW
Wind measuring FGGE type drifting buoy
(non-Lagrangian meteorological drifting
buoy)
ICE_LOAT
Ice float
FLOAT
Unspecified sub-surface float
SOFAR
SOFAR
ALACE
ALACE
MARVOR
MARVOR
RAFOS
RAFOS
MOORING
Unspecified moored buoy
NOMAD
Nomad
DISCUS_3
3-metre discus
DISCUS_10
10-12-metre discus
ODAS-30
ODAS 30 series
ATLAS
ATLAS (e.g. TAO area)
TRITON
TRITON buoy
OMNI_WAVE
Omnidirectional waverider
DIR_WAVE
Directional waverider
ARGO
Sub-surface ARGO float
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
ABBREV
30
NAME_
35
MOORED
40
DRIFTING
50
LAGRANGIAN
60
DROGUE_TYPE
70
DROGUE
80
DROGUE_DEPTH
85
ICEFLOAT
90
WAVE
100
SUB_SURFACE
110
ATMOSPHERIC
112
PICTURE_ID
Primary Key
--------Name
--BUOYTYPE_PK
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
Column
----ID
-29/62-
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
NUMBER (1, 0)
NUMBER (1, 0)
NUMBER (1, 0)
VARCHAR2 (20)
NUMBER (1, 0)
NUMBER (5, 1)
NUMBER (1, 0)
NUMBER (1, 0)
NUMBER (1, 0)
NUMBER (1, 0)
NUMBER ()
Buoy metadata notifcation scheme
Other Unique Keys
-------------Name
--BUOYTYP_UK
Foreign Keys
---------BUOYTYPE_PICT_FK
PICTURE_ID references
Transferable Yes
Mandatory ? No
Column
----ABBREV
PICTURE.ID
Update Rule Restricted
Delete Rule Restricted
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
30
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
Abbreviation for the type of buoy
; Uppercase ? :No ;
NAME_
Optional ? :No ; Varchar2 (80) ;() ;
Description of the type of buoy
; Uppercase ? :No ;
35
MOORED
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this type of buoy is a moored buoy
40
DRIFTING
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this type of buoy is a drifting buoy
50
LAGRANGIAN
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this type of buoy is a Lagrangian
drifter
60
DROGUE_TYPE
Optional ? :No ; Varchar2 (20) ;() ; ; Uppercase ? :No ;
Type of drogue; used only for Lagrangian drifters, e.g.
HOLEY SOCK
TRISTAR
PARACHUTE
WINDOW SHAPE
70
DROGUE
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean 1/0 used only for Lagrangian drifters
80
DROGUE_DEPTH
Optional ? :No ; Number (5, 1) ;() ;
-30/62-
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Drogue depth in meters used only for Lagrangian drifters
85
ICEFLOAT
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this type of buoy is an ice float
90
WAVE
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this type of buoy is a wave buoy
100 SUB_SURFACE
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this type of buoy make sub-surface
measurements
110 ATMOSPHERIC
Optional ? :No ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this type of buoy make atmospheric
measurements
112 PICTURE_ID
Optional ? :Yes ; Number () ;() ;
ID of PICTURE of the type of buoy
-31/62-
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Table Name : BUOY_PICTURE
Alias
BUOYPICT
Display Title : Buoy Picture
Description :Many to many table to associate pictures to buoys,
typically pictures corresponding to an event for a buoy
(i.e. PICTURE.EVENT=1)
Column Summary
------------Col.Seq.Column
------ ----10
BUOY_ID
20
PICTURE_ID
Nulls ?
---NOT NULL
NOT NULL
Type
--NUMBER ()
NUMBER ()
Primary Key
--------Name
--BUOYPICT_PK
Foreign Keys
---------BUOYPICT_BUOY_FK
BUOY_ID references
Transferable Yes
Mandatory ? Yes
Column
----BUOY_ID
PICTURE_ID
BUOYPERIOD.ID
Update Rule Restricted
Delete Rule Restricted
BUOYPICT_PICT_FK
PICTURE_ID references
Transferable Yes
Mandatory ? Yes
PICTURE.ID
Update Rule Restricted
Delete Rule Restricted
Column Detail
----------10 BUOY_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of the BUOYPERIOD for which we have a picture
20
PICTURE_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of the PICTURE for the corresponding buoy
-32/62-
Buoy metadata notifcation scheme
Table Name : BUOY_PROGRAM
Alias
BUOYPROG
Display Title : Buoy Program
Description :Many to many relationship between table BUOYPERIOD and
table PROGRAM to indicate to what program(s) a buoy belongs
to or is participating to.
Column Summary
------------Col.Seq.Column
------ ----10
BUOY_ID
12
PROG_ID
Primary Key
--------Name
--BUOY_PRG_PK
Nulls ?
---NOT NULL
NOT NULL
Type
--NUMBER ()
NUMBER ()
Column
----PROG_ID
BUOY_ID
Foreign Keys
---------BUOY_PRG_BUD_FK
BUOY_ID references
Transferable Yes
Mandatory ? Yes
BUOYPERIOD.ID
Update Rule Restricted
Delete Rule Restricted
BUOY_PRG_PRG_FK
PROG_ID references
Transferable Yes
Mandatory ? Yes
PROGRAM.ID
Update Rule Restricted
Delete Rule Restricted
Column Detail
----------10 BUOY_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table BUOYPERIOD of concerned buoy
12
PROG_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID in table PROGRAM of programme to which the buoy operational
period (BUOYPERIOD) should be associated
-33/62-
Buoy metadata notifcation scheme
Table Name : CONTACT
Alias
CONTACT
Display Title : Contacts
Description :Contact points, i.e. programme managers, coordinators,
notifiers of deployments, notifiers of buoy purchase
(manufacturers).
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
USERNAME
30
PASSWORD
40
FIRST_NAME
50
LAST_NAME
60
EMAIL
70
TEL
80
FAX
Primary Key
--------Name
--CONTACT_PK
Nulls ?
---NOT NULL
NOT NULL
NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (20)
VARCHAR2 (40)
VARCHAR2 (40)
VARCHAR2 (100)
VARCHAR2 (30)
VARCHAR2 (30)
Column
----ID
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
USERNAME
Optional ? :No ; Varchar2 (20) ;() ;
Username of the contact
; Uppercase ? :No ;
30
PASSWORD
Optional ? :Yes ; Varchar2 (20) ;() ; ; Uppercase ? :No ;
Password of the contact (for the given USERNAME)
40
FIRST_NAME
Optional ? :No ; Varchar2 (40) ;() ;
First name of contact
; Uppercase ? :No ;
LAST_NAME
Optional ? :No ; Varchar2 (40) ;() ;
Last name of contact
; Uppercase ? :No ;
50
60
70
80
EMAIL
Optional ? :Yes ; Varchar2 (100) ;() ;
Email address of contact
TEL
Optional ? :Yes ; Varchar2 (30) ;() ;
Telephone number
FAX
Optional ? :Yes ; Varchar2 (30) ;() ;
-34/62-
; Uppercase ? :No ;
; Uppercase ? :No ;
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Fax number
-35/62-
Buoy metadata notifcation scheme
Table Name : COUNTRY
Alias
COUNTRY
Display Title : Country
Description :Countries
Column Summary
------------Col.Seq.Column
------ ----7
ID
15
ABBREV
20
COUNTRY
40
ISO_CODE2
50
ISO_CODE3
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
Primary Key
--------Name
--COUNTRY_PK
Column
----ID
Other Unique Keys
-------------Name
--COUNTRY_UK
Column
----ABBREV
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
VARCHAR2 (2)
VARCHAR2 (3)
Column Detail
----------7
ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
15
20
40
50
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
Abbreviation of the country
; Uppercase ? :No ;
COUNTRY
Optional ? :No ; Varchar2 (80) ;() ;
Full name of country
; Uppercase ? :No ;
ISO_CODE2
Optional ? :No ; Varchar2 (2) ;() ;
2 letters ISO code for the country
; Uppercase ? :No ;
ISO_CODE3
Optional ? :No ; Varchar2 (3) ;() ;
3 letters ISO code for the country
; Uppercase ? :No ;
-36/62-
Buoy metadata notifcation scheme
Table Name : EQUIPMENT
Alias
EQUIP
Display Title : Equipment
Description :Any equipment attached to the buoy, e.g. transmitter, GPS
unit, radar reflector, navigation light, mooring line, data
processing unit. Details about the equipment are stored in
the XML field.
Column Summary
------------Col.Seq.Column
------ ----10
ID
15
SERIAL_NO
20
ABBREV
30
NAME_
80
BUOY_ID
82
MANUFACTURER_ID
87
PICTURE_ID
92
XML
102
COMMENT_
Nulls ?
---NOT NULL
NULL
NOT NULL
NOT NULL
NULL
NOT NULL
NULL
NULL
NULL
Primary Key
--------Name
--EQUIP_PK
Foreign Keys
---------EQUIP_BUOY_FK
BUOY_ID references
Transferable Yes
Mandatory ? No
Type
--NUMBER ()
VARCHAR2 (100)
VARCHAR2 (20)
VARCHAR2 (80)
NUMBER ()
NUMBER ()
NUMBER ()
LONG RAW ()
VARCHAR2 (132)
Column
----ID
BUOYPERIOD.ID
Update Rule Restricted
Delete Rule Restricted
EQUIP_ORGANISM_FK
MANUFACTURER_ID references ORGANISM.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
EQUIP_PICT_FK
PICTURE_ID references
Transferable Yes
Mandatory ? No
PICTURE.ID
Update Rule Restricted
Delete Rule Restricted
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
15
20
SERIAL_NO
Optional ? :Yes ; Varchar2 (100) ;() ;
Equipment serial number
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
-37/62-
; Uppercase ? :No ;
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Abbreviation for the equipment
30
NAME_
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Full name or description of the equipment
80
BUOY_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID of BUOYPERIOD to which this equipment is attached
82
MANUFACTURER_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of the ORGANISM which is the manufacturer of this equipment
87
PICTURE_ID
Optional ? :Yes ; Number () ;() ;
ID of PICTURE of the equipment
92
; Uppercase ? :No ;
XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
102 COMMENT_
Optional ? :Yes ; Varchar2 (132) ;() ; ; Uppercase ? :No ;
Any additional comment regarding the equipment
-38/62-
Buoy metadata notifcation scheme
Table Name : ENDINGCAUSE
Alias
ENDCAUSE
Display Title : Ending causes
Description : All possible reasons for end of operational period (e.g.
failure causes)
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
ABBREV
30
TEXT
Nulls ?
---NOT NULL
NOT NULL
NULL
Type
--NUMBER ()
VARCHAR2(20)
VARCHAR2(80)
Primary Key
--------Name
--ENDCAUSE_PK
Column
----ID
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ;
Primary key
; Uppercase ? :No ;
20
ABBREV
Optional ? :No ; Varchar2(20) ;() ; ; Uppercase ? :No ;
Abbreviation for considered reason for end of operational period
20
TEXT
Optional ? :Yes ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Full description of considered reason for end of operational period
Possible values for ABBREV:
DROGUE_LOST
BATTERY_EXHAUSTED
SENSOR_FAILURE
MAINTENANCE
CONTROLLER_FAILURE
TRANSMITTER_FAILURE
UNKNOWN
BEACHED
MOORING_BROKE
PICKED_UP
RECOVERED
BAD_DATA
-39/62-
Buoy metadata notifcation scheme
Table Name : EQUIPMENTBATCH
Alias
EQUIPB
Display Title : Equipment
Description :Any equipment batch attached to the considered batch of
buoys, e.g. transmitter, GPS unit, radar reflector,
navigation light, mooring line, data processing unit.
Details about the equipment are stored in the XML field.
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
ABBREV
30
NAME_
82
MANUFACTURER_ID
84
BUOYBATCH_ID
89
PICTURE_ID
94
XML
104
COMMENT_
Primary Key
--------Name
--EQUIPBATCH_PK
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
NUMBER ()
NUMBER ()
NUMBER ()
LONG RAW ()
VARCHAR2 (132)
Column
----ID
Foreign Keys
---------EQUIPB_BUOYBATCH_FK
BUOYBATCH_ID references BUOYBATCH.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
EQUIPB_ORGANISM_FK
MANUFACTURER_ID references ORGANISM.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
EQUIPB_PICT_FK
PICTURE_ID references
Transferable Yes
Mandatory ? No
PICTURE.ID
Update Rule Restricted
Delete Rule Restricted
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
30
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
Abbreviation for the equipment batch
NAME_
Optional ? :No ; Varchar2 (80) ;() ;
-40/62-
; Uppercase ? :No ;
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Full name or description of the equipment batch
82
MANUFACTURER_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of the ORGANISM which is the manufacturer of this equipment
batch
84
BUOYBATCH_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID of the BUOYBATCH corresponding to the batch of buoys to which
this equipment belongs
89
PICTURE_ID
Optional ? :Yes ; Number () ;() ;
ID of PICTURE of the equipment
94
; Uppercase ? :No ;
XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
104 COMMENT_
Optional ? :Yes ; Varchar2 (132) ;() ; ; Uppercase ? :No ;
Any additional comment regarding the equipment batch
-41/62-
Buoy metadata notifcation scheme
Table Name : ORGANISM
Alias
ORGANISM
Display Title : Organism
Description :An agency, institute, university, or private company.
Column Summary
------------Col.Seq.Column
------ ----10
ID
15
ABBREV
20
NAME_
26
BUOY_MANUF
32
URL
34
COUNTRY_ID
44
NOTIFIER_ID
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NOT NULL
NULL
Primary Key
--------Name
--ORGANISM_PK
Column
----ID
Other Unique Keys
-------------Name
--ORGANISM_UK
Column
----ABBREV
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
NUMBER (1, 0)
VARCHAR2 (150)
NUMBER ()
NUMBER ()
Foreign Keys
---------ORGANISM_CONTACT_FK
NOTIFIER_ID references CONTACT.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
ORGANISM_COUNTRY_FK
COUNTRY_ID references
Transferable Yes
Mandatory ? Yes
COUNTRY.ID
Update Rule Restricted
Delete Rule Restricted
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
15
20
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
Abbreviation of the organism
; Uppercase ? :No ;
NAME_
Optional ? :No ; Varchar2 (80) ;() ;
Full name of organism
; Uppercase ? :No ;
-42/62-
Buoy metadata notifcation scheme
26
BUOY_MANUF
Optional ? :Yes ; Number (1, 0) ;() ; ; Uppercase ? :No ;
Boolean to indicate whether this is a buoy manufacturer
32
URL
Optional ? :Yes ; Varchar2 (150) ;() ; ; Uppercase ? :No ;
The URL for the organism web site or web page dedicated to its
buoy programme
34
COUNTRY_ID
Optional ? :No ; Number () ;() ;
ID of COUNTRY of the organism
44
; Uppercase ? :No ;
NOTIFIER_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID of CONTACT for the person in charge of notifying buoy purchase
-43/62-
Buoy metadata notifcation scheme
Table Name : PICTURE
Alias
PICT
Display Title :
Description :Pictures.
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
PICTURE
40
DATE_
47
EVENT
52
COMMENT_
Primary Key
--------Name
--PICTURE_PK
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NULL
NOT NULL
Type
--NUMBER ()
LONG RAW ()
DATE
NUMBER (1, 0)
VARCHAR2 (240)
Column
----ID
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
PICTURE
Optional ? :No ; Long Raw () ;() ; ; Uppercase ? :No ;
Binary content of picture (e.g. gif format)
40
DATE_
Optional ? :No ; Date ;() ; ; Uppercase ? :No ;
Date of event corresponding to this picture
47
EVENT
Optional ? :Yes ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether this picture corresponds to an event
(e.g. buoy maintenance, buoy deployment, etc.)
52
COMMENT_
Optional ? :No ; Varchar2 (240) ;() ;
Any addtional comment
-44/62-
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Table Name : PROGRAM
Alias
PROG
Display Title : Program
Description :National or internation programme
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
ABBREV
30
NAME_
40
URL
42
MANAGER_ID
44
COORDINATOR_ID
46
NOTIFIER_ID
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
Primary Key
--------Name
--PROG_PK
Column
----ID
Other Unique Keys
-------------Name
--PROG_UK
Column
----ABBREV
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
VARCHAR2 (240)
NUMBER ()
NUMBER ()
NUMBER ()
Foreign Keys
---------PROG_COORDINATOR_FK
COORDINATOR_ID references CONTACT.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
PROG_MANAGER_FK
MANAGER_ID references
Transferable Yes
Mandatory ? No
CONTACT.ID
Update Rule Restricted
Delete Rule Restricted
PROG_NOTIFIER_FK
NOTIFIER_ID references CONTACT.ID
Transferable Yes
Update Rule Restricted
Mandatory ? No
Delete Rule Restricted
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
Abbreviation of the programme
-45/62-
; Uppercase ? :No ;
Buoy metadata notifcation scheme
30
NAME_
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Full name or description of programme
40
URL
Optional ? :Yes ; Varchar2 (240) ;() ;
URL of web page of programme
; Uppercase ? :No ;
42
MANAGER_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID of CONTACT who is the programme manager
44
COORDINATOR_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID of CONTACT who is the programme coordinator
46
NOTIFIER_ID
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
ID of CONTACT who is the person in charge of notifying deployments
-46/62-
Buoy metadata notifcation scheme
Table Name : SENSOR
Alias
SENSOR
Display Title : Sensor
Description :Sensor table. One record for every sensor of the buoy. For
example, if there is a thermistor string with probes at
different levels we'll have to create as many sensors as
there are probes (field SENSOR_HEIGHT used to indicate the
probe level).
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
SERIAL
30
NAME_
35
SENSOR_HEIGHT
40
BEGIN_DATE
45
END_DATE
47
LAST_CALIB_DATE
48
GTS
60
TIME_OFFSET
70
SAMPLING_RATE
80
AVERAGING_PERIOD
90
AVERAGING_METHOD
140
BUOYPERIOD_ID
150
SENSORMODEL_ID
160
XML
170
COMMENT_
Primary Key
--------Name
--SENSOR_PK
Nulls ?
---NOT NULL
NULL
NOT NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NOT NULL
NOT NULL
NULL
NULL
Type
--NUMBER ()
VARCHAR2 (80)
VARCHAR2 (80)
NUMBER (9, 2)
DATE
DATE
DATE
NUMBER (1, 0)
NUMBER (6, 1)
NUMBER (6, 0)
NUMBER (7, 2)
VARCHAR2 (40)
NUMBER ()
NUMBER ()
LONG RAW ()
VARCHAR2 (1000)
Column
----ID
Foreign Keys
---------SENSOR_BUOY_FK
BUOYPERIOD_ID references BUOYPERIOD.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
SENSOR_SENSMOD_FK
SENSORMODEL_ID references SENSORMODEL.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
Index Summary
-----------Name
--SENSOR_MODEL_IDX
Seq. Column
--- ----5
SENSORMODEL_ID
Column Detail
-----------
-47/62-
Index Type
-------NOT UNIQUE
Buoy metadata notifcation scheme
10
ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
SERIAL
Optional ? :Yes ; Varchar2 (80) ;() ;
Serial number of sensor
; Uppercase ? :No ;
30
NAME_
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Full name or description of sensor. The name of the sensor which is
installed on the considered buoy, e.g. "Air pressure", or
"Air pressure #2" in case we have two pressure sensors on
the same buoy
35
SENSOR_HEIGHT
Optional ? :Yes ; Number (9, 2) ;() ; ; Uppercase ? :No ;
Height of sensor compared to platform reference level
(meter, e.g. if platform reference level is buoy average flotation
line then value is >0 for above sea level, and value is <0 for below
sea level)
40
BEGIN_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Date when sensor began to report valuable data
45
END_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Date when the sensor is out of operations (see JCOMM field anOO)
47
LAST_CALIB_DATE
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Last date of sensor calibration
48
GTS
Optional ? :Yes ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether sensor data are distributed on GTS or
have been distributed on GTS
60
TIME_OFFSET
Optional ? :Yes ; Number (6, 1) ;() ; ; Uppercase ? :No ;
Time offset of measurement (minutes) compared to nominal
observation cycle.
70
SAMPLING_RATE
Optional ? :Yes ; Number (6, 0) ;() ; ; Uppercase ? :No ;
Sampling rate (number of samplings per second)
80
AVERAGING_PERIOD
Optional ? :Yes ; Number (7, 2) ;() ;
Averaging period in minutes
; Uppercase ? :No ;
AVERAGING_METHOD
Optional ? :Yes ; Varchar2 (40) ;() ;
Averaging method
; Uppercase ? :No ;
90
140 BUOYPERIOD_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of BUOYPERIOD to which sensor belongs
-48/62-
Buoy metadata notifcation scheme
150 SENSORMODEL_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of SENSORMODEL corresponding to the sensor manufactuter's model
160 XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
170 COMMENT_
Optional ? :Yes ; Varchar2 (1000) ;() ;
Any additional comment
-49/62-
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Table Name : SENSORBATCH
Alias
SENBATCH
Display Title : Sensor
Description :Sensor batch table. One record for every sensor of the buoy
batch. For example, if there is a thermistor string with
probes at different levels we'll have to create as many
sensors as there are probes (field SENSOR_HEIGHT used to
indicate the probe level).
Column Summary
------------Col.Seq.Column
------ ----2
ID
4
NAME_
5
GTS
7
TIME_OFFSET
12
SAMPLING_RATE
13
AVERAGING_PERIOD
50
SENSOR_HEIGHT
23
AVERAGINGMETHOD
100
SENSORMODEL_ID
102
BUOYBATCH_ID
112
XML
122
COMMENT_
Primary Key
--------Name
--SENSORBATCH_PK
Nulls ?
---NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
NOT NULL
NULL
NOT NULL
NOT NULL
NULL
NULL
Type
--NUMBER ()
VARCHAR2 (80)
NUMBER (1, 0)
NUMBER ()
NUMBER (6, 0)
NUMBER (7, 2)
NUMBER (9, 2)
VARCHAR2 (40)
NUMBER ()
NUMBER ()
LONG RAW ()
VARCHAR2 (1000)
Column
----ID
Foreign Keys
---------SENSORB_BUOYBATCH_FK
BUOYBATCH_ID references BUOYBATCH.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
SENSORB_SENSMOD_FK
SENSORMODEL_ID references SENSORMODEL.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
Column Detail
----------2
ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
4
5
NAME_
Optional ? :No ; Varchar2 (80) ;() ;
Full name or description of sensor
; Uppercase ? :No ;
GTS
Optional ? :Yes ; Number (1, 0) ;() ; ; Uppercase ? :No ; Default
Value :0 ;
Boolean to indicate whether sensor is normally for GTS
-50/62-
Buoy metadata notifcation scheme
distribution
7
TIME_OFFSET
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
Time offset of measurement (minutes) compared to nominal
observation cycle.
12
SAMPLING_RATE
Optional ? :Yes ; Number (6, 0) ;() ; ; Uppercase ? :No ;
Sampling rate (number of samplings per second)
13
AVERAGING_PERIOD
Optional ? :Yes ; Number (7, 2) ;() ;
Averaging period in minutes
; Uppercase ? :No ;
AVERAGINGMETHOD
Optional ? :Yes ; Varchar2 (40) ;() ;
Averaging method
; Uppercase ? :No ;
23
50
SENSOR_HEIGHT
Optional ? :Yes ; Number (9, 2) ;() ; ; Uppercase ? :No ;
Height of sensor compared to platform reference level
(meter, e.g. if platform reference level is buoy average flotation
line then value is >0 for above sea level, and value is <0 for below
sea level)
100 SENSORMODEL_ID
Optional ? :No ; Number () ;() ;
; Uppercase ? :No ;
102 BUOYBATCH_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of BUOYBATCH to which sensor belongs
112 XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
122 COMMENT_
Optional ? :Yes ; Varchar2 (1000) ;() ;
Any additional comment
-51/62-
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Table Name : SENSORMODEL
Alias
SENSMOD
Display Title : Sensormod
Description :A sensor model from manufacturer's catalogue, e.g. SBE-17
of SEABIRD company
Column Summary
------------Col.Seq.Column
------ ----10
ID
12
ABBREV
13
NAME_
20
ACCURACY
30
RESOLUTION
35
YEARLY_DRIFT
40
MIN_VALUE
50
MAX_VALUE
60
CALIB_FREQUENCY
100
SENSORTYPE_ID
110
MANUFACTURER_ID
120
PICTURE_ID
130
XML
140
COMMENT_
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
NULL
NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
Primary Key
--------Name
--SENSMOD_PK
Column
----ID
Other Unique Keys
-------------Name
--SENSMOD_UK
Column
----ABBREV
Foreign Keys
---------SENSMOD_MANUF_FK
MANUFACTURER_ID references ORGANISM.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
SENSMOD_PICT_FK
PICTURE_ID references
Transferable Yes
Mandatory ? No
PICTURE.ID
Update Rule Restricted
Delete Rule Restricted
SENSMOD_SENTYP_FK
SENSORTYPE_ID references SENSORTYPE.ID
Transferable Yes
Update Rule Restricted
Mandatory ? Yes
Delete Rule Restricted
Column Detail
-----------
-52/62-
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
NUMBER ()
NUMBER ()
NUMBER ()
NUMBER ()
NUMBER ()
VARCHAR2 (40)
NUMBER ()
NUMBER ()
NUMBER ()
LONG RAW ()
VARCHAR2 (1000)
Buoy metadata notifcation scheme
10
ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
12
ABBREV
Optional ? :No ; Varchar2 (20) ;() ; ; Uppercase ? :No ;
Abbreviation of sensor manufactuter's model
13
NAME_
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Full name or description of sensor model
the name of the sensor model as the manufacturer would call it,
e.g. "Vaisala PTB 100"
20
ACCURACY
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
Accuracy of sensor model in units given by associated SENSORTYPE
30
RESOLUTION
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
Resolution of sensor model in units given by associated SENSORTYPE
35
YEARLY_DRIFT
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
Yearly drift of sensor model in units/year (units given by
associated SENSORTYPE)
40
MIN_VALUE
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
Minimal range of sensor model in units given by associated
SENSORTYPE
50
MAX_VALUE
Optional ? :Yes ; Number () ;() ; ; Uppercase ? :No ;
Maximum range of sensor model in units given by associated
SENSORTYPE
60
CALIB_FREQUENCY
Optional ? :Yes ; Varchar2 (40) ;() ; ; Uppercase ? :No ;
Recommended calibration frequency, e.g.
MONTHLY
SEMESTRIAL
YEARLY
(see JCOMM field anSD)
100 SENSORTYPE_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of SENSORTYPE for the type of sensor of this sensor model
110 MANUFACTURER_ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
ID of ORGANISM corresponding to the sensor model's manufacturer
120 PICTURE_ID
Optional ? :Yes ; Number () ;() ;
ID of PICTURE of the sensor model
; Uppercase ? :No ;
130 XML
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Record and additional fields coded in XML
-53/62-
Buoy metadata notifcation scheme
140 COMMENT_
Optional ? :Yes ; Varchar2 (1000) ;() ;
Any additional comment
-54/62-
; Uppercase ? :No ;
Buoy metadata notifcation scheme
Table Name : SENSORTYPE
Alias
SENTYP
Display Title : Sensortype
Description :Generic type of sensor, e.g.
AP: Air Pressure
AT: Air Temperature
SST: Sea Surface Temperature
WT: Water Temperature
WS: Wind speed
WD: Wind Direction
WAVE
WAVE_HEIGHT
WAVE_PERIOD
WAVE_DIR
Column Summary
------------Col.Seq.Column
------ ----10
ID
12
ABBREV
13
GEOPHYS_VARIABLE
15
UNITS
Primary Key
--------Name
--SENTYP_PK
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NOT NULL
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
VARCHAR2 (10)
Column
----ID
Other Unique Keys
-------------Name
--SENTYP_UK
Column
----ABBREV
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
12
ABBREV
Optional ? :No ; Varchar2 (20) ;() ;
Abbreviation of the type of sensor
; Uppercase ? :No ;
13
GEOPHYS_VARIABLE
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Name of the geo-physical variable(s) that this type of sensor is
measuring, e.g. Air pressure
15
UNITS
Optional ? :No ; Varchar2 (10) ;() ; ; Uppercase ? :No ;
Units (if applicable) for the considered geo-physical variable
measured by this type of sensor
-55/62-
Buoy metadata notifcation scheme
-56/62-
Buoy metadata notifcation scheme
Table Name : TELECOMFORMAT
Alias
FMT
Display Title : Telecom Format
Description :Satellite data telecommunication format, e.g. DBCP-M2
format which is one of the formats recommended by the DBCP.
Column Summary
------------Col.Seq.Column
------ ----10
ID
20
ABBREV
30
NAME_
50
NB_BITS
60
DESCRIPTION
Nulls ?
---NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
Primary Key
--------Name
--TELECOM_FMT_PK
Column
----ID
Other Unique Keys
-------------Name
--TELECOM_FM_UK
Column
----ABBREV
Type
--NUMBER ()
VARCHAR2 (20)
VARCHAR2 (80)
NUMBER (4, 0)
LONG RAW ()
Column Detail
----------10 ID
Optional ? :No ; Number () ;() ; ; Uppercase ? :No ;
Identification number of record (primary key)
20
ABBREV
Optional ? :No ; Varchar2 (20) ;() ; ; Uppercase ? :No ;
Abbreviation for the telecommunication format
30
NAME_
Optional ? :No ; Varchar2 (80) ;() ; ; Uppercase ? :No ;
Full name or short description of the telecommunication format
50
NB_BITS
Optional ? :No ; Number (4, 0) ;() ;
Number of bits of message
60
; Uppercase ? :No ;
DESCRIPTION
Optional ? :Yes ; Long Raw () ;() ; ; Uppercase ? :No ;
Description of the format in PDF format
-57/62-
Buoy metadata notifcation scheme
Annex D
GDP Specifications sheet
SVPB DBCP-Format Specification Sheet (as provided by Mayra Pazos, 14 March 2003). Examples are given
then corresponding fields in metadata database are indicated.
Argos ID(s)
39673
39674
 Field BUOYPERIOD.TRANSMITTER_NUM
Manufacturer
Technocean
 Field ORGANISM.ABBREV
Sensor array
SVPB
Battery voltage, drogue sensor, SST, barometer
 Fields SENSOR.NAME_
Surface float description
41 cm. diameter, ABS plastic surface float.
 XML tag “floatdescr” in table BUOYMODEL
Tether description
a) 0.476 cm OD polypropylene-impregnated wire rope between surface float
and drogue.
b) Tether attachment to 3.0 cm 316 stainless steel ring at base of
surface float; marine epoxy filled cavity surrounding ring for restraint.
c) 7.1 cm dia. by 40 cm long polyurethane carrots molded below surface
float.
Attachment point of tether to drogue covered by 6.35 cm dia by 40 cm long
polyurethane carrot.
 XML tag “tetherdescr” in table BUOYMODEL
Drogue description
a) Holey sock made from Cordura nylon cloth; diameter 92 cms, length 552
cms. construction consists of 6 cylindrical sections, each 92 cm long. Two
44 cm dia. holes cut opposite each other in each section. Axis joining
holes is rotated by 90° between successive sections. Drogue is centered at
15 m.
b) 2 kg lead weight sewn into base of sock inside a 2.5 cm 'schedule 40'
PVC-pipe ring.
c) 2.0 cm ID, 0.16 cm wall, polypropylene 'irrigation' pipe ring between
each 92 cm segment for support. Rings are drilled to allow flooding.
d) 2.5 cm 'schedule 80' PVC-pipe top ring, filled with closed cell
polyurethane foam.
e) Attachment bridle consisting of hub and 6 x 0.4 cm OD
polypropylene-impregnated wire rope radials, positively attached and
epoxy-restrained at hub to tether from surface float. Radials attach to top
PVC ring using abrasions resistant cushions fixed at 60° spacing. 10
cm-long rubber air hose carroting fitted where radials enter hub.
Attachment point of tether to hub covered with 40-cm long polyurethane
carrot.
-58/62-
Buoy metadata notifcation scheme
 XML tag “droguedescr” in table BUOYMODEL
Drogue depth
15 m at center
 Field BUOYTYPE.DROGUE_DEPTH
Drogue length
5.52 meters
 XML tag “droguelength” in table BUOYMODEL
Cross-sectional area above the drogue
1571 cm2
 XML tag “crossect_abv” in table BUOYMODEL (cm2)
Cross-sectional area of the drogue
70433 cm2
 XML tag “crossect_drog” in table BUOYMODEL (cm2)
Transmitter type
SmartCat
 For EQUIPMENT.ABBREV=”TRANSMITTER”, XML tag “tx_type”
Transmitter manufacturer
Seimac
 ORGANISM.ABBREV for EQUIPMENT.MANUFACTURER_ID
Controller manufacturer
Technocean
 For EQUIPMENT.ABBREV=”CONTROLLER”, XML tag “controller_type”
Duty cycle
Continuous
 Field BUOYPERIOD.DUTY_CYCLE
Message Length
56 bits
 Field TELECOMFORMAT.NB_BITS
Message format
8 bits
4 bits
6 bits
11 bits
9 bits
9 bits
6 bits
3 bits
Checksum
Rank
Age
Barometric pressure
Sea surface temperature
Air pressure tendency
Submergence count
Battery voltage
 Field TELECOMFORMAT.ABBREV
-59/62-
Buoy metadata notifcation scheme
Observation cycle
60 minutes
 1440/(Field BUOYPERIOD.OBS_FREQUENCY)
Repetition rate
90 seconds
 Field BUOYPERIOD.REPETITION_PERIOD
Power Supply
8 diode-protected battery packs, each consisting of 8 alkaline D-cells;
total capacity > 112 Ah.
 For EQUIPMENT.ABBREV=”BATTERY”, XML tag “battery_descr”
Antifouling
Cuprous oxide anti-fouling coating on bottom half of ABS surface float.
Inflatable boat anti-fouling paint on polyurethane carrots
 XML tag “af” in BUOYPERIOD
Checksum Calculation
Modulus 256 of the sum of all of the other bytes
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Rank Calculation
Rank = n
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Age Calculation
Age = n
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Battery voltage sensor
Precision resistive divider
 For EQUIPMENT.ABBREV=”BATTERY”, XML tag “voltage_sensor”
Battery voltage equation
Battery volts (V) = n + 6.0
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Temperature sensor type (include manufacturer and model)
BetaTHERM #36K53A106i linearized thermistor imbedded in a capped 316ss
Swagelock through-hull fitting at base of surface float.
 SENSORMODEL.COMMENT_
Temperature equation (Specific equation for each ID on this sheet)
SST (C) = n x 0.08 - 4.963
39673
39674
SST
SST
(C)
(C)
= 0.07995
= 0.08005
* n
* n
-4.943
-5.137
-60/62-
Buoy metadata notifcation scheme
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Drogue sensor type
Submergence
 XML tag "droguesen_type" of table BUOYMODEL
Submergence equation
Percent of time submerged = n x 1.58, 100% = fully submerged, 0% = no
submergence detected
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Salinity Sensor Type (include manufacturer and model)
None
 Field SENSORMODEL.ABBREV
Salinity Equation
None
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Barometer type
Honeywell HPB
 Field SENSORMODEL.ABBREV
BP equation
pressure (hPa) = n x 0.1 + 850
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Air Pressure Tendency
n x 0.1 - 25.5
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Wind Speed Sensor Type (include manufacturer and model)
None
 Field SENSORMODEL.ABBREV
Wind Speed Equations
None
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Wind Direction Sensor Type (include manufacturer and model)
None
 Field SENSORMODEL.ABBREV
Wind Direction Equations
None
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
GPS Type (include manufacturer and model)
None
 XML tag “GPSt“ of table EQUIPMENT
-61/62-
Buoy metadata notifcation scheme
GPS Equations
None
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Additional Sensor Types (include manufacturer and model)
None
 Field SENSORMODEL.ABBREV
Additional Sensor Equations
None
 If proper TELECOMFORMAT is associated to the BUOYPERIOD then this field can be ignored.
Shipping container
46x35x22 inches, 110 lbs, 2 drifters/box
surface floats packaged in protective deployment boxes.
Each individual unit is also packaged so it can be directly deployed in the
ocean without removal of the cardboard box thereby minimizing possible
tangling of the unit. Instructions for pre - testing and deployment are
fastened on the outside of each unit. Each individual box is clearly
stenciled with "LEAVE THIS BOX ON DURING HANDLING AND DEPLOYMENT"
 XML tag “package_type” of BUOYPERIOD
-62/62-