FAAM Data Submission

Updated 30 June 2005.
N.B. This page explains how to submit core and test flight data. It does not deal with non-core data from field campaigns, which are submitted via the uploaders of the various projects involved.

Contents

1. Preliminaries

Before submitting your data to the BADC, please make sure that your files comply with the FAAM File Name Convention and that they are properly formatted. An online NetCDF File Format Checker is available.

Access to the /incoming/faam/ directory is reserved to FAAM staff who are registered BADC users (please register with the BADC if you have not done so yet) and have been granted access to FAAM test flight data (you can apply here).

Whether you use the uploader or FTP, please choose carefully the subdirectory to where you upload the data. The FAAM archive directory where the data is to be copied, as well as the access permissions, will be automatically determined from both the file name and the name of the /incoming/faam/ subdirectory.

2. Submission via the FAAM web file uploader

This route is recommended for most cases. The uploader will accept any type of file format. File names will be checked at the time of uploading, as well as the format of NetCDF files.

You will be led through the following steps.

  1. Directory selection. Select the directory to which you want to upload the data. The options are

    • campaign-processed-core Processed data from core instruments, collected during a field campaign, to be made public right away
    • restricted-processed-core Processed data from core instruments, collected during a field campaign, to be kept restricted for some time
    • campaign-raw-core Raw data from core instruments, collected during a field campaign, and associated flight constants
    • test-processed-core Processed data from core instruments, collected during a test or calibration flight
    • test-raw-core Raw data from core instruments, collected during a test or calibration flight, and associated flight constants
    • test-processed-non-core Processed data from non-core instruments, collected during a test or calibration flight
    • test-raw-non-core Raw data from non-core instruments, collected during a test or calibration flight
    • flight-constants Flight constants for individual or grouped flights
    • flight-logs Flight logs
    • documentation All documentation on data (e.g. instrument metadata not already included in data files)
    • software Reading and processing software (source codes, executables, etc.)

    The FAAM Flight Schedule shows which past flights were test or calibration flights and which ones belonged to field campaigns.

  2. Data type selection. The options are

    • NetCDF data file
    • Image fileGIF, JPEG, etc.
    • Software/text file Any ASCII or plain text file (e.g. source codes such as .f fortran programs)
    • PDF/other file Anything not included in the previous three options, including PDF files (e.g. scanned flight-logs), zipped VMS files, gzipped files, etc.

  3. Login to the BADC. Please enter your BADC user ID and password.

  4. Upload your file(s). A browser allows you to select from your home computer the file you want to upload.

  5. If your file fails the checkings, you will be returned an error message. If your file is accepted, you will be asked to confirm that you want it copied to the BADC.

3. Submission via FTP

If you have a large number of files to upload, you can do so by FTP. General instructions on how to use FTP are available from the BADC Guide to FTP.

Example of Unix-based uploading ftp session:

$ ftp ftp.badc.rl.ac.uk <Return>

Connected to ftp.badc.rl.ac.uk (130.246.191.168).
220 ProFTPD 1.2.9 Server (ProFTPD Default Installation) [web.badc.rl.ac.uk]

Name (ftp.badc.rl.ac.uk:my-local-user-id): my-badc-user-id <Return>

331 Password required for my-badc-user-id.

Password: my-badc-password <Return>

230 User my-badc-user-id logged in.
Remote system type is UNIX.
Using binary mode to transfer files.

ftp> cd incoming <Return>

250 CWD command successful.

ftp> cd faam <Return>

250 CWD command successful.

ftp> ls <Return>

campaign-processed-core
campaign-raw-core
documentation
flight-constants 		flight-logs
format-testing-samples
restricted-processed-core
software 		test-processed-core
test-processed-non-core
test-raw-core
test-raw-non-core

ftp> cd test-processed-core <Return>

ftp> mput core_faam_2004*.nc <Return>

ftp> ls <Return>

core_faam_20040406_r0_b007.nc
core_faam_20040406_r1_b007,nc
core_faam_20040407_r1_b008.nc
core_faam_20040506_r0_b017.nc

ftp> quit <Return>