docs/data_processing/uploading_measurements.rst

Wed, 12 Mar 2014 11:43:36 +0200

author
Iannis <ioannis@inoe.ro>
date
Wed, 12 Mar 2014 11:43:36 +0200
changeset 44
c37ebdf6d03f
parent 43
bda5e7160bf6
child 45
156eaee2f510
permissions
-rw-r--r--

Form validation

ioannis@37 1 .. _uploading_measurements:
ioannis@37 2
ioannis@37 3 Uploading measurements
ioannis@37 4 ======================
ioannis@42 5
ioannis@42 6 New measurements can be uploaded using the "Quick Upload" link in the data
ioannis@42 7 processing submenu. There, you will need to fill and submit the provided form.
ioannis@42 8
ioannis@42 9
ioannis@42 10 Form fields
ioannis@42 11 -----------
ioannis@42 12
ioannis@42 13 System (Required)
ioannis@42 14 This field specifies the system configuration that was used to perform the
ioannis@42 15 measurement. The available systems can be managed in the "Station Admin"
ioannis@42 16 section of the site. You can later change the system used in the processing
ioannis@42 17 of the measurement again in the "Station Admin" section.
ioannis@42 18
ioannis@42 19 Data file (Required)
ioannis@42 20 In this field you have to select the measurement file that will be processed.
ioannis@42 21 The file has to be in the specific format described in :ref:`netcdf_file`.
ioannis@42 22
ioannis@42 23 Sounding file (Optional)
ioannis@42 24 In this optional field you can submit a sounding file that will be used
ioannis@44 25 by your measurements in the processing. The file needs to follow the netCDF
ioannis@42 26 file format specified in the pdf file found in the :ref:`netcdf_file` section.
ioannis@42 27 The file you submit will not be necessarily connected with the
ioannis@42 28 submitted measurement; which sounding file will be used in the processing of
ioannis@42 29 each measurement is specified in the measurement's file. The file you upload
ioannis@42 30 will, nevertheless, remain on the SCC and will be used whenever needed.
ioannis@42 31
ioannis@42 32 Overlap file (Optional)
ioannis@42 33 In this optional field you can submit a overlap file that will be used
ioannis@44 34 by your measurements in the processing. The file needs to follow the netCDF
ioannis@42 35 file format specified in the pdf file found in the :ref:`netcdf_file` section.
ioannis@42 36 The file you submit will not be necessarily connected with the
ioannis@42 37 submitted measurement; which overlap file will be used in the processing of
ioannis@42 38 each measurement is specified in the measurement's file. The file you upload
ioannis@42 39 will, nevertheless, remain on the SCC and will be used whenever needed.
ioannis@42 40
ioannis@42 41 Lidar ratio file (Optional)
ioannis@42 42 In this optional field you can submit a lidar ratio file that will be used
ioannis@44 43 by your measurements in the processing. The file needs to follow the netCDF
ioannis@42 44 file format specified in the pdf file found in the :ref:`netcdf_file` section.
ioannis@42 45 The file you submit will not be necessarily connected with the
ioannis@42 46 submitted measurement; which lidar ratio file will be used in the processing
ioannis@42 47 of each measurement is specified in the measurement's file. The file you
ioannis@42 48 upload will, nevertheless, remain on the SCC and will be used whenever needed.
ioannis@42 49
ioannis@42 50 Categories (Optional)
ioannis@42 51 You can assign a number of categories to the uploaded measurement. The
ioannis@42 52 categories you assign can be lated changed in the in the "Station Admin"
ioannis@42 53 section of the site. You can select multiple categories by holding down the
ioannis@42 54 "Control" key (PC) or "Command" key (MAC) while selecting.
ioannis@42 55
ioannis@42 56 .. note::
ioannis@42 57
ioannis@42 58 Uploading the measurement file can take considerable time, depending on
ioannis@42 59 the size of the file and the speed of your Internet connection. In the
ioannis@42 60 current version of the site, no feedback is provided during the upload.
ioannis@43 61 You can get information on your upload progress depending on your browser.
ioannis@42 62
ioannis@42 63 Firefox
ioannis@43 64 You can install this `add-on <https://addons.mozilla.org/en-US/firefox/addon/uploadprogress/>`_.
ioannis@43 65
ioannis@42 66 Chrome
ioannis@42 67 A progress indicator is built it.
ioannis@42 68
ioannis@42 69 IE 9-
ioannis@42 70 No progress bar is available (as far as we know).
ioannis@42 71
ioannis@44 72
ioannis@44 73 Form Validation
ioannis@44 74 ---------------
ioannis@44 75
ioannis@44 76 The data you submit in the form are check in two stages.
ioannis@44 77
ioannis@44 78 Before you submit the form
ioannis@44 79 ~~~~~~~~~~~~~~~~~~~~~~~~~~
ioannis@44 80
ioannis@44 81 Before you submit the form the following checks are performed:
ioannis@44 82
ioannis@44 83 * All the necessary fields (i.e. "system" and "data file") need to be submitted.
ioannis@44 84
ioannis@44 85 * The ancillary file names have to be in the appropriate format described
ioannis@44 86 in :ref:`netcdf_file`. In brief, a sounding file should have a name
ioannis@44 87 rs_YYYYMMDDccNN.nc, a overlap file a name ov_YYYYMMDDccNN.nc, and a lidar ratio
ioannis@44 88 file a name lr_YYYYMMDDccNN.nc, where YYYY is a year, MM is the month, DD is
ioannis@44 89 the day, cc is the EARLINET station call sign and NN is a number.
ioannis@44 90
ioannis@44 91
ioannis@44 92 After you submit the form
ioannis@44 93 ~~~~~~~~~~~~~~~~~~~~~~~~~~
ioannis@44 94
ioannis@44 95 After you submit the form:
ioannis@44 96
ioannis@44 97 * The uploaded **data file** needs to have a unique name.
ioannis@44 98
ioannis@44 99 * The **measurement id** defined in the file should *not* exist in the SCC.
ioannis@44 100
ioannis@44 101 * All channels declared in the measurement file should correspond to declared
ioannis@44 102 channels in the SCC.
ioannis@44 103
ioannis@44 104 * The submitted measurement file should have the correct netCDF format. All
ioannis@44 105 mandatory variables and attributes should be present in the file. All
ioannis@44 106 variables and attributes should have the correct type (float, integer, etc).
ioannis@44 107 This check is not exhaustive, and it is possible that some errors are **not**
ioannis@44 108 detected. For example "conditionally" mandatory variables are not checked
ioannis@44 109 (as, for example "LR_Input", that is mandatory if elastic backscatter retrievals
ioannis@44 110 have to be done).
ioannis@44 111
ioannis@44 112 If ancillary files are submitted
ioannis@44 113 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ioannis@44 114
ioannis@44 115 Additionally, if ancillary files are also uploaded, the following checks are
ioannis@44 116 performed:
ioannis@44 117
ioannis@44 118 * The submitted measurement file should have the correct netCDF format. All
ioannis@44 119 mandatory variables and attributes should be present in the file. All
ioannis@44 120 variables and attributes should have the correct type (float, integer, etc).
ioannis@44 121
ioannis@44 122 * A file with the same filename should not exist in the SCC or, if it exists,
ioannis@44 123 it should have status "Missing" or "Error". If a file with the same filename
ioannis@44 124 exists, and its status is "OK" the submitted file is regected.

mercurial