Event

The EVENT table includes metadata fields defining the location for sampling or measurements (synonyms: site, station). Double click on an event label in 4D will open the event window showing the fields on two cards: Basics and Details; the list of related data series is given on the Basics card. If data are georeferenced, the event label and latitude/longitude are mandatory. (If an event does not have a position, import with values -999.999 in the fields latitude and longitude and the position will not be shown in the metaheader.) A single event can be defined directly by starting from the campaign level or clicking on the New button in the Event window. To add a list of events use the import form and import via Menue File/Import, choose Sites/Events.

Basics tab
 * Event label does not contain blanks and must be unique. This can be ensured by combining the station numbers with the campaign label, using an underline to join (e.g. Taymyr97_3).
 * Optional label may be used, if the same station as different labels (see Event label problem)
 * Device tool, gear or method used to take a sample or to make measurements; not_given may be used if not needed
 * Device type is used to group devices
 * Latitude is mandatory for georeferenced data, display format can be changed in the Menue File/Preferences/Geographical positions
 * Longitude dito
 * Elevation relative to sea level, positive above sea level, negative below sea level (i.d. water depth)
 * Date when did the event happen
 * Time dito
 * Recovery is a special field only used for coring; gives the length of the core in [m], otherwise filled with -999.999

Details tab
 * Latitude, Longitude, Elevation, Date, Time are repeated from the Basics tab
 * in case an event is a profile, having a start and an end point, all fields are repeated also to describe the second point
 * Penetration and Recovery are fields for coring, see recovery
 * Project, Campaign, Site, Area are relational to the corresponding tables
 * Comment may be used to add any event specific text
 * Keywords is relational to the thesaurus and may be used to define specific groups of event
 * the fields Begin/Top, End/Bottom, Top age, Bottom age are not further used and will be removed
 * an URL field may be added to link to web pages describing an event

Event label problem: there is a great risk of confusion with event 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.

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 system, the station labeling on Polarstern is described:
 * 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, those are identified by an increasing number added with a hyphen, e.g. a complete station label would be PS07/025-3 labeling the third device event on the 25th station during the 7th expedition.