ioannis@37: .. _uploading_measurements: ioannis@37: ioannis@37: Uploading measurements ioannis@37: ====================== ioannis@42: ioannis@42: New measurements can be uploaded using the "Quick Upload" link in the data ioannis@42: processing submenu. There, you will need to fill and submit the provided form. ioannis@42: ioannis@42: ioannis@42: Form fields ioannis@42: ----------- ioannis@42: ioannis@42: System (Required) ioannis@42: This field specifies the system configuration that was used to perform the ioannis@42: measurement. The available systems can be managed in the "Station Admin" ioannis@42: section of the site. You can later change the system used in the processing ioannis@42: of the measurement again in the "Station Admin" section. ioannis@42: ioannis@42: Data file (Required) ioannis@42: In this field you have to select the measurement file that will be processed. ioannis@42: The file has to be in the specific format described in :ref:`netcdf_file`. ioannis@42: ioannis@42: Sounding file (Optional) ioannis@42: In this optional field you can submit a sounding file that will be used ioannis@44: by your measurements in the processing. The file needs to follow the netCDF ioannis@42: file format specified in the pdf file found in the :ref:`netcdf_file` section. ioannis@42: The file you submit will not be necessarily connected with the ioannis@42: submitted measurement; which sounding file will be used in the processing of ioannis@42: each measurement is specified in the measurement's file. The file you upload ioannis@42: will, nevertheless, remain on the SCC and will be used whenever needed. ioannis@42: ioannis@42: Overlap file (Optional) ioannis@42: In this optional field you can submit a overlap file that will be used ioannis@44: by your measurements in the processing. The file needs to follow the netCDF ioannis@42: file format specified in the pdf file found in the :ref:`netcdf_file` section. ioannis@42: The file you submit will not be necessarily connected with the ioannis@42: submitted measurement; which overlap file will be used in the processing of ioannis@42: each measurement is specified in the measurement's file. The file you upload ioannis@42: will, nevertheless, remain on the SCC and will be used whenever needed. ioannis@42: ioannis@42: Lidar ratio file (Optional) ioannis@42: In this optional field you can submit a lidar ratio file that will be used ioannis@44: by your measurements in the processing. The file needs to follow the netCDF ioannis@42: file format specified in the pdf file found in the :ref:`netcdf_file` section. ioannis@42: The file you submit will not be necessarily connected with the ioannis@42: submitted measurement; which lidar ratio file will be used in the processing ioannis@42: of each measurement is specified in the measurement's file. The file you ioannis@42: upload will, nevertheless, remain on the SCC and will be used whenever needed. ioannis@42: ioannis@50: Comments (Optional) ioannis@50: In this field you can add a small comment (up to 100 characters) to the ioannis@50: measurement. ioannis@50: ioannis@42: Categories (Optional) ioannis@42: You can assign a number of categories to the uploaded measurement. The ioannis@42: categories you assign can be lated changed in the in the "Station Admin" ioannis@42: section of the site. You can select multiple categories by holding down the ioannis@42: "Control" key (PC) or "Command" key (MAC) while selecting. ioannis@42: ioannis@42: .. note:: ioannis@42: ioannis@42: Uploading the measurement file can take considerable time, depending on ioannis@42: the size of the file and the speed of your Internet connection. In the ioannis@42: current version of the site, no feedback is provided during the upload. ioannis@43: You can get information on your upload progress depending on your browser. ioannis@42: ioannis@42: Firefox ioannis@43: You can install this `add-on `_. ioannis@43: ioannis@42: Chrome ioannis@45: A progress indicator is built-in. ioannis@42: ioannis@42: IE 9- ioannis@42: No progress bar is available (as far as we know). ioannis@42: ioannis@44: ioannis@44: Form Validation ioannis@44: --------------- ioannis@44: ioannis@46: The aim of form validation is to detect errors in your submitted data as early ioannis@46: as possible. In this way you can save time by correcting errors before the ioannis@46: processing of your data fails. ioannis@46: ioannis@46: The data you provide in the form are check in two stages, before you submit ioannis@46: and after you submit the form. ioannis@44: ioannis@44: Before you submit the form ioannis@44: ~~~~~~~~~~~~~~~~~~~~~~~~~~ ioannis@44: ioannis@44: Before you submit the form the following checks are performed: ioannis@44: ioannis@44: * All the necessary fields (i.e. "system" and "data file") need to be submitted. ioannis@44: ioannis@44: * The ancillary file names have to be in the appropriate format described ioannis@44: in :ref:`netcdf_file`. In brief, a sounding file should have a name ioannis@44: rs_YYYYMMDDccNN.nc, a overlap file a name ov_YYYYMMDDccNN.nc, and a lidar ratio ioannis@44: file a name lr_YYYYMMDDccNN.nc, where YYYY is a year, MM is the month, DD is ioannis@44: the day, cc is the EARLINET station call sign and NN is a number. ioannis@44: ioannis@44: ioannis@44: After you submit the form ioannis@44: ~~~~~~~~~~~~~~~~~~~~~~~~~~ ioannis@44: ioannis@44: After you submit the form: ioannis@44: ioannis@44: * The uploaded **data file** needs to have a unique name. ioannis@44: ioannis@44: * The **measurement id** defined in the file should *not* exist in the SCC. ioannis@44: ioannis@44: * All channels declared in the measurement file should correspond to declared ioannis@44: channels in the SCC. ioannis@44: ioannis@44: * The submitted measurement file should have the correct netCDF format. All ioannis@44: mandatory variables and attributes should be present in the file. All ioannis@44: variables and attributes should have the correct type (float, integer, etc). ioannis@44: This check is not exhaustive, and it is possible that some errors are **not** ioannis@44: detected. For example "conditionally" mandatory variables are not checked ioannis@44: (as, for example "LR_Input", that is mandatory if elastic backscatter retrievals ioannis@44: have to be done). ioannis@44: ioannis@44: If ancillary files are submitted ioannis@44: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ioannis@44: ioannis@44: Additionally, if ancillary files are also uploaded, the following checks are ioannis@44: performed: ioannis@44: ioannis@44: * The submitted measurement file should have the correct netCDF format. All ioannis@44: mandatory variables and attributes should be present in the file. All ioannis@44: variables and attributes should have the correct type (float, integer, etc). ioannis@44: ioannis@44: * A file with the same filename should not exist in the SCC or, if it exists, ioannis@44: it should have status "Missing" or "Error". If a file with the same filename ioannis@47: exists, and its status is "OK" the submitted file is rejected.