Citation information for individual datasets is often provided in the metadata. However, not all datasets have this information embedded in the discovery metadata. On a general basis a citation of a dataset include the same components as any other citation:
author,
title,
year of publication,
publisher (for data this is often the archive where it is housed),
edition or version,
access information (a URL or persistent identifier, e.g. DOI if provided)
The information required to properly cite a dataset is normally provided in the discovery metadata the datasets.
If you use data retrieved through this portal, please acknowledge the SAON Data Portal.
Brief user guide
The Data Access Portal has information in 3 columns. An outline of the content in these columns is provided above. When first entering the search interface, all potential datasets are listed. Datasets are indicated in the map and results tabulation elements which are located in the middle column. The order of results can be modified using the "Sort by" option in the left column. On top of this column is normally relevant guidance information to user presented as collapsible elements.
If the user want to refine the search, this can be done by constraining the bounding box search. This is done in the map - the listing of datasets is automatically updated. Date constraints can be added in the left column. For these to take effect, the user has to push the button marked search. In the left column it is also possible to specific text elements to search for in the datasets. Again pushing the button marked "Search" is necessary for these to take action. Complex search patterns can be constructed using logical operators through the drop down menu above the text field. Text strings that are not quoted are treated as separate words and will match any of the words (i.e. assuming the OR operator). Phrases may be prefixed with '-' to indicate no occurence of the phrase in the results.
Other elements indicated in the left and right columns are facet searches, i.e. these are keywords that are found in the datasets and all datasets that contain these specific keywords in the appropriate metadata elements are listed together. Further refinement can be done using full text, date or bounding box constraints. Individuals, organisations and data centres involved in generating or curating the datasets are listed in the facets in the right column.
On the four N-ICE2015 floes we installed in total seven hot-wire fields and seven snow-stake fields following the routine outlined in Perovich [2003]. A rectangular hot-wire field with a side length of approximately 10 m was designed in a way that in each corner a wire was installed close to an ablation stake, and in the middle of the hot-wire field nine snow-stakes with even spacing were set up. Snow depth and ice thickness changes were recorded on a regular basis, and the readings were averaged in space to cover small scale spatial variability.
Data position, ice floe, instrument number (stake number) are added in the json files. Positions are taken from the ice_floe_track at noon (=12:05 UTC). The ice floe name and the stake number are indicated in the original file name. The unit of snow thickness are converted to meters.
Quality
Filename contains snowstake_floe, thereafter floe number, thereafter unique number for field
file contains 2 headerlines and 3 columns, seperator: [space]
#header1: fieldnumber #header2: [date] [thickness in cm] [standard deviation in cm]
Field1 Date cm std 23.01.2015 55.0 12.9 25.01.2015 52.7 13.6 27.01.2015 NAN NAN 01.02.2015 53.4 12.7 08.02.2015 56.1 13.6 12.02.2015 56.6 13.9 16.02.2015 66.4 20.2
On the four N-ICE2015 floes we installed in total seven hot-wire fields and seven snow-stake fields following the routine outlined in Perovich [2003]. A rectangular hot-wire field with a side length of approximately 10 m was designed in a way that in each corner a wire was installed close to an ablation stake, and in the middle of the hot-wire field nine snow-stakes with even spacing were set up. Snow depth and ice thickness changes were recorded on a regular basis, and the readings were averaged in space to cover small scale spatial variability.
Data position, ice floe, instrument number (wire number) are added in the json files. Positions are taken from the ice_floe_track at noon (=12:05 UTC). Ice floe and the wire number are indicated in the original file name. The unit of ice thickness are converted to meters (original files = cm).
Quality
variables: date, ice thickness, standard deviation