The core partner data centres that are integrated in NorDataNet are listed in https://www.nordatanet.no/en/node/69. In addition to this NorDataNet harvests information on relevant datasets from a number of other data centres. The data centre responsible for the data presented is usually (but not always) listed in the discovery metadata. In essence NorDataNet is an aggregating service that combines information from a number of existing data centres.
Citation of data and service
If you use data retrieved through this portal, please acknowledge our funding source:
Research Council of Norway, project number 245967/F50, Norwegian Scientific Data Network.
Always remember to cite data when used!
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)
All partner repositories of NorDataNet support Digital Object Identifiers (DOI), but not all datasets are minted. Whether or not minted depends often on source of the data (e.g. operational data are often yet not minted). However, all data centres support persistent identifiers according to local systems. The information required to properly cite a dataset is normally provided in the discovery metadata the datasets.
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 identified in the drop down menu with and phrases embedded in quotation marks. Prefixing a phrase with '-' negates the phrase (i.e. should not occur in the results). Searches are case insensitive.
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. The combination of search fields (including facets) is based on a logical "AND" combination of the fields, i.e. all conditions are fulfilled for the results provided.
Atmospheric profiles of temperature, humidity, wind speed and direction from radiosondes released from the ship. A total of 258 radiosonde launches were conducted during the N-ICE 2015 cruise from January 12th to June 22nd. Sondes were launched two times a day around 0 UTC and 12 UTC.
Quality
The data has been postprocessed using the stored edt-files.
The rsData_gridded.nc is in NetCDF classic format
Dimensions: "height" = 1201 (0,25,50,...,30000) "launches" = 258 (1,2,3,...,258) "dim_launch_date_vector" = 6 (1,2,3,...,6) "serial_number" = 9 (1,2,3,...,9 Variables: "height" = height(height) long name = 'geopotential height' units = 'm' Datatype: double "time" = time(height,launches) long name = 'time after launch' units = 's' Datatype: double "press" = press(height,launches) long name = 'pressure' units = 'hPa' Datatype: double "temp" = temp(height,launches) long name = 'air temperature' units = 'degree Celsius' Datatype: double "rh" = rh(height,launches) long name = 'relative humidity' units = '% RH' Datatype: double "wd" = wd(height,launches) long name = 'wind direction' units = 'degree' Datatype: double "ws" = ws(height,launches) long name = 'wind speed' units = 'ms^-1' Datatype: double "SN" = SN(launches,serial_number) long name = 'serial number sonde' Datatype: char "lt" = lt(launches,dim_launch_date_vector) long name = 'date of launch' units = 'yyyy_mm_dd_HH_SS' Datatype: double "lat" = lat(launches) long name = 'latitude' units = 'dec. degree' Datatype: double "lon" = lon(launches) long name = 'longitude' units = 'dec .degree' Datatype: double "gc_p" = gc_p(launches) long name = 'GC pressure offset' units = 'hPa' Datatype: double "gc_T" = gc_T(launches) long name = 'GC temperature offset' units = 'degree Celsius' Datatype: double "gc_RH" = gc_RH(launches) long name = 'GC humidity offset' units = '% RH' Datatype: double
Issues
During the campaign period only minor problems occurred with the radio sounding: (1)The biggest problem during processing is the missing ground check values during 57 launches. However, the ground check is just an offset correction and some people argue not to use it in analyzing radiosonde data. (Miloshevich et. al. 2004). I have therefore removed the ground check correction from the profiles and icluded it seperately in the file in the variables “gc_p”, “gc_T” and “gc_RH”. (2)Whenever strong winds occurred while filling the balloon on deck, the amount of helium inside the balloon could vary, causing the ascend speed during launch beeing somewhat smaller or faster than 5 ms^-1 in the lowest 1.5-2 km of the troposhere. (3)A few radiosonde launches where ended very early due to the balloon bursting. The balloons must have gotten damaged during the launch procedure.