Intern:Event

The EVENT table includes metadata required to define an event of sampling or measurement.

Event labels german research vessels:
In March 2014 the "Senatskomission Ozean" and others agreed on a common syntax for station lists: XXnn/mm_ss-rr

e.g.: PS80/1_101-1 (campaign with legs) or PS81_131-1 (campaign without legs)

For stations that were NOT logged in DShip we agreed on the following SOPs with AWI/marum/GEOMAR on the following in Feb. 2023:

Two cases:

A) Event exists but needs to be divided into many sub-events (e.g. underway with interruption, ROV)

B) Event was not at all logged in DShip

A) Event exists but needs to be divided into many sub-events (e.g. underway with interruption, ROV)
Example underway events: https://www.pangaea.de/expeditions/events/PS133%2F1 s: Measurements were switched off for 2 days, but after switching on again the old numbers continued. In PANGAEA we can only have one start and one end for each Event. The chief scientist insisted on having the events seperated because they did not have permission to collect data during the break.

Example sampling from ROV, e.g. cruise SO242/2: the ROV Event is SO242/2_232-1 but during this event many different device were used with different lat/long and time of sampling/measurement. Here, sub-events were created: SO242/2_232_COLBOX-1-nodule-1 → und angehängt wird dann die spezifische Nummer vom ROV Sampling https://www.pangaea.de/expeditions/events/SO242/2

SOP event => subevents separation:
The complete event label is taken including the device operation number, e.g. SO242/2_142-1, and "_1"," _2"," _3" and so on is added at the end or, if absolutely necessary, another specification. The seperator always should be an underscore ("_").

For ROV there are ROV protokols but a common definition (for all german research vessels) of ROV sub-events is still missing

B) Event was not logged at all in DShip
Previously : label was invented, or “common names” taken, e.g. for snow buoys: 2021S115. => event created with label PS124_20210306_SB02

Special case MOSAiC : Since the numbering in MOSAiC was a little different and station/activity 99 was never assigned, we marked all missing stations with Campaign/leg_99-running number, e.g. PS122/1_99-78; for details see MOSAiC Wiki

Example MSM105: some CTD stations were not logged in DShip, see PDI-33572, https://www.pangaea.de/expeditions/events/MSM105 e.g. at station 10 only one CTD device operation was logged (MSM105_10-1), but several CTDs were deployed

Example SO202/2 Radiosondes: transit cruise, no stations were logged but radiosondes were launched. Events were created here which contained the ID of the corresponding file (https://www.pangaea.de/expeditions/events/SO202%2F2)

SOP Underway events: https://wiki.pangaea.de/wiki/Intern:Underway_Event
If there is no Underway Event given for your underway device create a new underway event (also for underway data of cruises before 2015)! First you check, which underway events already exist for this campaign, then create your event taking the next highest activity number. e.g. for M185 https://www.pangaea.de/expeditions/events/M185 there already is an event M185_0_Underway-1 and M185_0_Underway-2, so the next higher number would be M185_0_Underway-3.

ALWAYS ADD AN EVENT COMMENT: "event was not logged in DSHIP"

Caution with POLARSTERN underway events: there is often no consistent numbering here (z.B. https://www.pangaea.de/expeditions/events/PS129 )

SOP non-underway events connected to a certain station:
If you know at which station/science activity your device operation was done, then use this station/science activity for your event label and attach the next higher device operation number at the end. e.g. the labels MSM105_10-1 and MSM105_10-2 already exists, then create a new event label MSM105_10-3, MSM105_10-4 etc.. Note that it is irrelevant if the device operations are not entirely chronological.

For helicopter missions, rubber boat trips, or ice stations, it is important to even keep the respective device operation number in the newly created event. For example if a device was deployed but not logged during an ice station, the newly created event for the device operation should have the complete device operation number of the ice station (e.g. PS131_47-1) plus the addition of “_1", "_2" and so on (e.g. PS131_47-1_1), see the MSSP events of ice station PS131_47-1: https://www.pangaea.de/expeditions/events/PS131.

ALWAYS ADD AN EVENT COMMENT: "event was not logged in DSHIP"

SOP non-underway events, not connected to a certain station:
If the connection to a certain station number/science activity is unknown, then Campaign/leg_somename (or just a name without Campaing/leg_ for additional events such as long-term moorings, e.g. AWI262-1) is sufficient.

ALWAYS ADD AN EVENT COMMENT: "event was not logged in DSHIP"

Define new Events (other ships, non-ship events)
Double click on an event label in 4D will open the event window with all required (relational) fields on a Basics and a Details card. If data are georeferenced, event label and latitude/longitude are mandatory. If data are not georeferenced, the definition of an event is not required.
 * To add a SINGLE EVENT click on the New button in the Event list window and type in the required information.

SOP Events

 * About 1000 events per dataset possible
 * Create event with all available metadata. It is often possible to update events in connection with other submissions (e.g., campaign, elevation, date/time,...)
 * Event Label: no space, no special characters
 * When several sampling points in a very small area (e.g., 20 m distance), create only one event (mean latitude, longitude) and add latitude and longitude in the dataset.
 * For CTDs: one CTD Cast = one Event (can be different for special types of CTD, e.g. continuous)

Import new Events
EVENT IMPORT FORM 
 * To add a LIST of EVENTS, use the
 * Fill with event information by using the predefined header (mandatory fields are shown in red ).
 * For importing event Attributes, add the attribute name or ID in the header.
 * Export from excel as tab-delimited text-file.
 * Save text-file with UTF-8 encoding.
 * Import via 4D-Menu Import, choose Events. In the Import stations/sites window, fill out the fields accordingly:
 * Project is relational to the PROJECT table; choose not_given if the project is not relevant
 * If a list of events need to be corrected, the list may be imported again. In this case check Overwrite existing events.

Field descriptions

 * Event table fields are described below; recommendations on how to fill out the columns in the import form are given in italic.
 * If an event has NO position (e.g. name of an experiment), Latitude and Longitude can be imported with values -999.999; consequently the position will not appear in the metaheader.
 * If you have an Event column and NO EVENT for some lines, just leave a blank cell for those lines in the data import file.

Basics tab

 * Event Label is the name of a sampling/measuring event (synonyms site, station). The label should not contain blanks and must be unique throughout the event table. This can be ensured by combining the station numbers with the campaign label, using an underline to join (e.g. Taymyr97_3). Devices or projects should not be replicated in the label (avoid redundancies).
 * Optional label may be used, if the same station has different labels (see Event label problem)
 * Method device, tool, gear or method used to take a sample or to measure something; use not_given if not applicable, use Abbreviation or full name for import (column headed 'Device' in event import form).
 * Abbreviation is set automatically when adding the Method
 * Latitude is mandatory for georeferenced data and given in decimal degree (positive for North, negative for South)
 * Longitude is mandatory for georeferenced data and given in decimal degree (positive for East, negative for West)
 * Elevation [m a.s.l.] is given relative to sea level: positive above sea level, negative below sea level (=water depth).
 * Date/Time of event execution must be given in ISO-format: YYYY-MM-DDThh:mm:ss; date only is allowed.
 * in case an event is a profile with start and an end point, all fields are repeated to describe the second point with a '2' added to the corresponding field name.
 * Project, Campaign are relational to the corresponding tables.
 * Location is relational to the Term table, terminology Locations, PANGAEA.
 * Comment may be used to add free text which should be closely event specific (no limit of characters). If an invalid position is imported, the text Unknown event! may be added (keep in mind, that georeferenced data with missing position is useless).
 * Keywords is relational to the Term table, terminology Keywords, PANGAEA, and can used to define e.g. specific groups of event.
 * URI link to a more detailed description of an event, e.g. on a external web page or a document.

Details tab

 * Method/device is redundant with the Basic tab
 * Additional attributes after selecting Schema, give the possibility to add more sampling information. All fields are free text fields and must be given with the unit:

Event label problem: there is a great risk of confusion with event labels (also with campaign labels). Please consider that clarity for the relation between event and data is paramount for the curator and the import procedure. The event labels published in the expedition report should be exactly those that appear in a publication and in the data sets provided for import (first column). In some cases, an additional labeling of events can not be avoided; in this case please use the field Optional label in the event table to add a second label. In the final data set, it will appear behind the event label in parenthesis (example with 3 labels ).

Three different systems exist for labeling events during expeditions:
 * 1) ship related (e.g. Vema, Polarstern)
 * 2) institution related (e.g. GIK..., Geob...)
 * 3) free format

As a well defined example, the station labeling system of Polarstern is described as:
 * Station labels start with PS as a reference to the ship.
 * Each expedition is numbered starting with 1 and written with a leading zero; e.g. PS07 is the seventh expedition.
 * Station numbers start with 1 on each new expedition and are numbered throughout, independent from the legs, leading zeros to fill a three digit number; e.g. PS07/025 is the 25th station during the 7th expedition.
 * During a station, several devices may be used (events), those are identified by an increasing number added with a hyphen, e.g. a complete event label would be PS07/025-3 labeling the third device on the 25th station during the 7th expedition.
 * It is a Pangaea convention that measurements along the track are related to an event label consisting of the leg number and the extension *-track, e.g. PS07/1-track.