Environmental Data Archive - Data description

The EDMS application queries a schema completely independent of the file database. This catalogue is populated with a subset of the data archived in files and all relevant metadata needed to extract the data, such as the spatio-temporal coordinates and the data type description. The information is organized in the following way:

  • Environment: Physical environment where the data were collected (hydrosphere, atmosphere, benthic zone).
  • Datatype: File type in which the data is archived.
  • Subdatatype: How the data was collected.
  • Variable : Description and units of the data.
  • Data: Data value.

The EDMS schema is detailed below. Each level of information is represented by one or two EDMS tables with the exception of the Data level, which is divided into as many DONNEES_* tables as there are distinct Subdatatype. For example, DONNES_CTD holds CTD profile data, DONNEES_BOTL holds discrete data from seawater sampling bottles, DONNEES_ADCP holds data on seawater currents measured with a moored ADCP device, and so on. A DONNEES_* table has a certain number of metadata columns such as latitude (LATD), longitude (LOND), depth (DEPH), and date-time (SYTM) of the measurement in addition to the data (Variable) columns, which could include variables such as temperature (TE90) and salinity (PSAL).

Table contents are as follows:

ENVIRONMENT table (subset of MILIEU table)

EAUHydrosphereAquatic environment(…)
AIRAtmosphereAtmospheric environment(…)
BENBenthosphereBenthic environment(…)

DATATYPE table (subset of TYPE_DONNEES table)


SUBDATATYPE table (subset of SOUS_TYPE_DONNEES table)

BOTLBOUTEILLESEAUdonnees_bouteillesBouteilleDonnées de bouteille/Rosette.(…)
CTDCTDEAUdonnees_ctdCTDDonnées de CTD.(…)
MADCPADCP_MOUILLEEAUdonnees_adcpADCP mouilléDonnées de mouillage d`ADCP.(…)

VARIABLE table (subset of VARIABLE table)

PSALSalinityWater practical salinity [PSU](…)
TE90TemperatureWater temperature (ITS-90 scale) [degrees C](…)

CTD DATA table (subset of DONNEES_CTD table)

4219253179276148,8084-68,236122014-11-20 15:152,22925,67(…)
4219254179276248,8084-68,236132014-11-20 15:151,98925,61
4219255179276348,8084-68,236142014-11-20 15:152,06025,68
4219256179276448,8084-68,236152014-11-20 15:152,05125,80
4219257179276548,8084-68,236162014-11-20 15:152,03725,88
4219258179276648,8084-68,236172014-11-20 15:152,06826,03
4219259179276748,8084-68,236182014-11-20 15:152,08226,27
4219260179276848,8084-68,236192014-11-20 15:152,07026,41
4219261179276948,8084-68,2361102014-11-20 15:152,06326,48
42192621792761048,8084-68,2361112014-11-20 15:152,04426,57
42192631792761148,8084-68,2361122014-11-20 15:152,01226,76
42192641792761248,8084-68,2361132014-11-20 15:151,96427,02(…)

EDMS Schema

In the schema above, tables are named using “SGDO” tags; the EDMS was developed as part of another schema called SGDO due to computer limitations.

In the EDMS schema, the orange tables are those described above, the blue table is the CTD profile table (one of several data tables, DONNEES_*), and the yellow tables hold further information concerning the spatial details of the sampling (TYPE_TRACK table) and the sampling survey during which the data were collected (SOUS_TYPE_DONNEES_MISSION_JD table). The spatial nature of a data set is used any time the application displays the location on a map; it can be a point, a rectangular area, a linear track, or an area of any shape.

The data set sequence number (SEQ_JD) is exactly the same in both the file archive system and the EDMS. From a database point of view, these sequence numbers are not related to each other, but in fact, this important feature is used by data managers to keep track of a data set since the SEQ_JD is the only link between the EDMS and the file catalogue.

The description of table columns may be viewed by following this link: EDMS Tables