Glossary

Analytical instrument manufacturer
The manufacturer of the laboratory instrument in case of offline measurements. This is controlled vocabulary, valid values depend on Analytical measurement technique. More information can be found in the description of Time dependent analytical instrument metadata in the data model description.
Analytical instrument model
The model name of the laboratory instrument in case of offline measurements. This is controlled vocabulary, valid values depend on Analytical measurement technique. More information can be found in the description of Time dependent analytical instrument metadata in the data model description.
Analytical instrument name

A unique name for a laboratory instrument in case of offline measurements. This name is assigned by the instrument operator. A laboratory performing measurements has to assign a unique name for each instrument they report measurements for. The naming is managed by the laboratory (data originator).

Example: Laboratory NO01L (NILU) uses instrument name NILU_IC_03 as a name for one laboratory instruments.

Analytical instrument reference

A unique identifier for one laboratory instrument in EBAS. Consists of:

Example: NO01L_NILU_IC_03 (laboratory NO01L assigned the name NILU_IC_03 for their instrument.

The Analytical instrument name must be unique within the laboratory, thus the analytical instrument reference will always be unique within the whole system.

Analytical measurement technique

The measurement technique used by a laboratory instrument. The analytical measurement technique is independent of manufacturer or model of the instruments.

Some examples for different analytical measurement techniques are IC, AES or pH_meter.

Component name
Standardized name for a component measured in EBAS. It specifies the physical quantity of the measurement (e.g. temperature, sodium or aerosol_light_scattering_coefficient). The component name is one important part of defining a measurement parameter in EBAS, be aware that one and the same component can be used for different parameters (e.g. sodium in matrix aerosol is a different parameter as sodium in matrix precip)
Component synonym

New in version 3.01.00.

A componnet may have one or more synonyms (or aliases). Synonyms can be used for component lookup. They may be strict (i.e. exactly the same meaning) or loose (somehow similar meaning, sometimes one term is a subset of the other term).

In case of strict synonyms, the name must be unique. No component may have the same name, no other synonym for anouther component may have the same name.

Strict synonyms are used for component lookup, e.g. when using the commanline option --component.

Each synonym may have an nameing schema associated in order to give the synonym additional meaning. Examples for naming schemas: CAS Number, IUPAC Name, Historic EBAS Name, Lookup Name, Condensed Formula and Molecular Formula

It is also possible to assign a synonym without naming schema.

CAS Number, IUPAC Name, Historic EBAS Name and Lookup Name are usually strict synonyms, while Condensed Formula and Molecular Formula are loose synonyms as they are not always unique names (e.g. isomers).

Lookup Names are strict synonyms with a special bahavior.

Lookup Name

Lookup names are strict component synonyms which are treated case insensitive in the lookup for the commandline option --component. The case insensitivity works only if there are not conflicts with other component names and synonyms! E.g.:

Country code

EBAS stores three different types of country identifiers for each country. All three types are defined by ISO 3166-1:

  • Alpha-2 code (e.g. NO for Norway, DE for Germany)
  • Alpha-3 code (e.g. NOR for Norway, DEU for Germanny)
  • Numeric code (e.g. 578 for Norway, 276 for Germany)

Most important for the user is the alpha-2 code, which is used in all references to countries within the metadata (e.g. station code).

Data level

Data level describes the level of processing of the data within the data life cycle. EBAS uses the following concept of data levels:

  • Data level 0 (raw instrument data)

    Raw data as they come out of the instrument. Original time resolution (native to instrument). This data level is generally not meant for long term preservation in ebas and is mostly used for near realtime processing dataflow through EBAS.

  • Data level 0.5 (raw instrument data, flagged)

    Raw instrument data, flagged. Raw data as they come out of the instrument. Original time resolution (native to instrument). Flag information included. This data level is generally not meant for long term preservation in ebas and is mostly used for near realtime processing through EBAS.

  • Data level 1 (physical parameters)

    Data processed to physical parameters. Same time resolution as level 0. This data level is generally not meant for long term preservation in ebas and is mostly used for near realtime processing dataflow through EBAS.

  • Data level 1.5 (processed, no manual QA)

    Data processed to physical parameters, aggregated to hourly averages, info on atmospheric variability included. This format is the result of automated (unattended) near-real-time data processing. Not quality assured by human inspection.

  • Data level 2 (final)

    Physical parameters, aggregated (if needed), info on variability recommended, quality assured by human inspection. This is the typical EBAS data level meant for dissemination and long term preservation.

  • Data level 3a (derived)

    Data product generated from lower data levels of one or several instruments. Otherwise like level 2.

  • Data lebel 3b (derived nrt)

    Data product generated from NRT data of one or several instruments.

Data originator

The scientifical responsible person(s) for a measurement (PI). This should be the persons who can be contacted about scientific questions. See also data submitter for differentiation of the term.

See also the chapter about submission roles in the data model documentation.

Data submission
A datafile that has been reported to EBAS and ingested into the database. See also the chapter about <submissions in the data model documentation.
Data submitter

The person(s) who technically

  • processed the data
  • prepared the data files or
  • submitted the data files

This should be the persons who should be contacted about technical questions. See also data originator for differentiation of the term.

See also the chapter about submission roles in the data model documentation.

Dataset
The term dataset defines all metadata and data for a specific time series variable in EBAS. See also the chapter about datasets in the data model documentation.
Dataset core metadata
Set of metadata which identifies the dataset (makes it unique). See Dataset core metadata in the EBAS User’s Guide.
Dataset setkey
The setkey (setkey, DS_SETKEY) is a unique identifier for a dataset. The setkey is an integer number.
Dataset-year

A term used in connection with database inventory reports and access statistics. A dataset-year is one year of continous data for one dataset in ebas.

See also: Instrument-year, Instrument/component-year (including and example)

EBAS
EBAS is a proper name, not an acronym. Even though the roots of EBAS go back to emep, and that EBAS comes from emep-database, we did not find a documented statement about this.
EBAS Commandline
Collection of EBAS commandline utilities. Sometimes also called “EBAS UNIX Programs”, although this is not true, as they are platform independent.
EBAS Core
Synonym for EBAS Commandline.
emep
The European Monitoring and Evaluation Programme (EMEP) is a scientifically based and policy driven programme under the Convention on Long-range Transboundary Air Pollution (CLRTAP) for international co-operation to solve transboundary air pollution problems.
Framework

Project and Framework are synonyms in EBAS. The historic term Project is used for backward compatibility, mainly in EBAS Commandline programs. The term Framework is the correct term to be used (as it is a wider term; not all frameworks in EBAS are technically a project).

See also the chapter about project associations in the data model documentation.

Instrument/component-year

A term used in connection with database inventory reports and access statistics. An instrument/component-year is one year of continous data for one component measured by one instrument).

Example:

A nephelometer which measures aerosol_scattering_coefficient and ``aerosol_light_backscattering_coefficient will report two instrument/component-years per year of data reporting.

Because each component is reported in 3 wavelength, and each of those in 3 statistical variables (iarithmetic mean, percentile:15.87 and percentile:84.13), the same data would be consindered 9 dataset-years. Finally, the same data would count for 1 instrument-year.

See also: Instrument-year, Dataset-year

Instrument manufacturer
Instrument manufacturer is a controlled vocabulary lists, valid values depend on Instrument type. More information can be found in the description of Time dependent instrument metadata in the data model description.
Instrument model
Instrument model is a controlled vocabulary lists, valid values depend on Instrument type and instrument manufacturer. More information can be found in the description of Time dependent instrument metadata in the data model description.
Instrument name

A unique name for an instrument in the field, assigned by the instrument operator. A laboratory performing measurements in the field has to assign a unique name for each instrument they report measurements for. The naming is managed by the laboratory (data originator).

Example: Laboratory NO01L (NILU) uses instrument name dmps_no42 as a name for the dmps instrument located at Zeppelin mountain (Station code NO0042G), meaning something like “our dmps at Zeppelin”.

More information can be found in an note on the implications of instrument naming in the data model chapter.

Instrument reference

A unique identifier for one field instrument in EBAS. Consists of:

Example: NO01L_dmps_no42 (laboratory NO01L assigned the name dmps_no42 for their instrument.

The Instrument name must be unique within the laboratory, thus the instrument reference will always be unique within the whole system.

Instrument type

The instrument type describes the measurement or sampling principle of the field instrument used for a measurement. The instrument type is independent of manufacturer or model of the instruments.

An example for different sampling instrument types is the distinction between bulk_sampler and wet_only_sampler in precipitation chemistry samplers.

An example for different instrument types for different measurement principles is the distinction between dmps and smps in online particle size distribution measurements.

Instrument-year

A term used in connection with database inventory reports and access statistics. An instrument-year is one year of continous data for one instrument (identified by one instrument reference).

See also: Instrument/component-year (including an example), Dataset-year

Laboratory code

Unique identifier for a laboratory in EBAS. Laboratories are special organizations which

  • operate field instruments or
  • perform chemical analyses in the lab

Laboratories use organization codes with the organization type L (for laboratory)

Matrix name
The matrix describes the type of matter the measurement is performed in. Examples: aerosol means the aerosols in the atmosphere have been analysed, for matrix air the gaseous fraction has been analyzed, and for matrix precip the precipitation has been analyzed. Matrix is necessary to describe the parameter of a measurement.
Method reference

A unique identifier for a specific method of a measurement. Consists of:

Example: NO01L_GC_FID_Chrompack_VOCAIR_Analyzer (laboratory NO01L assigned the name GC_FID_Chrompack_VOCAIR_Analyzer for their instrument.

The method name must be unique within the laboratory, thus the method reference will always be unique within the whole system.

Near realtime
Near realtime (NRT) data in EBAS are usually available within two hours after the observation. NRT dataset are specially handled in the database in many respects. See Near realtime data for more information.
NRT
Abbreviation for near realtime.
Offline measurements
Observations which are performed by taking a sample and analysing it later in the laboratory. Examples are filter measurements or precipitation samples.
Organization code

Unique identifier for an organization in EBAS. Organizations

  • report data
  • operate field instruments or
  • perform chemical analyses in the lab

The organization code consists of three parts:

  • Alpha-2 country code (e.g. NO for Norway, DE for Germany)
  • 2 digit numeric organization number (unique number within the country for the organization within EBAS)
  • 1 character organization type (O for general organizations, L for laboratories)

Example: NO01L

Organizations which only report data use the organization type O. Organizations which operate field instruments or perform chemical analyses in the lab are a special form of organizations called laboratory and use the organization type L.

Parameter

The measurement parameter defines exactly the physical quantity measured. It is specified by a triple of metadata elements.

Each unique combination of the triple defines a different physical quantity.

EBAS defines a standard unit for each physical quantity All measurements in EBAS are always stored in the EBAS standard unit (they might be converted on import and export though).

For example, Regime code IMG, Matrix name aerosol, Component name sodium define one parameter with the standard unit ug/m3. Whereas Regime code IMG, Matrix name precip, Component name sodium define another parameter with the standard unit mg/l.

Project

Project and Framework are synonyms in EBAS. The historic term Project is used for backward compatibility, mainly in EBAS Commandline programs. The term Framework is the correct term to be used (as it is a wider term; not all frameworks in EBAS are technically a project).

See also the chapter about project associations in the data model documentation.

Project Acronym
Unique identifier for a project in EBAS (e.g. EMEP, ACTRIS).
Project association
Every dataset in EBAS is associated to one or meres projects. Those associations can be used as a search criteria and additionally control the access rights. For more information, see the
Regime code
The regime is is a coarse classification for EBAS time series. Currently only IMG is used, which means immission measurement at groundlevel. (A logical extension might be model results in the future) The regime is necessary to describe the parameter of a measurement.
Resolution code

Specifies the temporal resolution of a dataset. The resolution code specifies the approximate average time between consecutive sample start times (sample frequency) and should not be confused with the sample duration.

The code consists of an integer number followed by an alpha interval identifier. Valid interval identifiers are:

  • s for seconds
  • mn for minutes
  • h for hours
  • d for days
  • w for weeks
  • mo for months
  • y for years

Examples for valid resolution codes are 1h, 30mn, 6w, 2mo.

The resolution code is an approximation, for example 6w could describe a timeseries with sample frequencies of 40 days or 42 days. When dealing with irregular time series, the resolution code should best describe the average (median) sample frequency.

Sample duration

Specifies the temporal resolution of a dataset. The sample duration specifies the approximate average time interval of one sample and should not be confused with the resolution code.

The sample duration code consists of an integer number followed by an alpha interval identifier. Valid interval identifiers are:

  • s for seconds
  • mn for minutes
  • h for hours
  • d for days
  • w for weeks
  • mo for months
  • y for years

Examples for valid sample duration codes are 1h, 30mn, 6w, 2mo.

The sample duration is an approximation, for example 6w could describe a timeseries with sample durations of 40 days or 42 days. When dealing with irregular time series, the sample duration code should best describe the average (median) sample duration.

Standard method

A standardised description of the method used for performing measurements. In contrast to the Method, which consists of an arbitrary name for the method selected by the laboratory, the standard method is contralled vocabolary and the valid values depend on the instrument type.

Standard methods very often refer to a Standard operating procedure - in this case, the standard method is named in the form SOP=....

Station code

Unique identifier for a measurement station in EBAS. The station code consists of three parts:

  • Alpha-2 country code (e.g. NO for Norway, DE for Germany)
  • 4 digit numeric station number (unique number within the country for the station within EBAS)
  • 1 character station type

The first 2 parts of a station code (country code and station number) are already identifying (the station type is informational).

Example for a station code: NO0002R (Birkenes, Norway, regionally representative station)

Station type
The station type describes the category of a station. Most important types are: G for globally representative background station, R for regionally representative station.
Statistics code

The statistics code defines the statical dimension of a dataset. Statistics code may be:

  • arithmetic mean
  • geometric mean
  • median
  • maximum
  • minimum
  • stddev
  • percentile:15.87
  • percentile:84.13
  • 68.27% lower confidence bound
  • 68.27% upper confidence bound
  • absolute error
  • uncertainty
  • accuracy
  • precision
  • expanded uncertainty 2sigma
  • expanded uncertainty 3sigma

Usually measurements are arithmetic mean, because the measured value represents the arithmetic mean of the measured parameter (determined by integration over sample duration).

Unit
The magnitude of a physical quantity. Each Parameter in EBAS has one defined primary unit in which the measurements are stored in the database. There may be unit conversions on import or export for some parameters.