At the request of the HIPPO PIs, HIPPO PI data currently reside in a secure ftp site. As data are finalized they will also be available via the EOL long-term data archive. The EOL HIPPO project page contains relevant links to project and data documentation, distributed data access, and other collaborating projects' data sets for all 5 HIPPO phases.

There is a separate master list of datasets for each HIPPO phase in the EOL long-term data archive. These are linked as "EOL Data Access" under each phase. If you collected data for HIPPO, please review this list to verify that your data set(s) are properly named with the appropriate Principal Investigators (PIs) identified. Please e-mail any corrections, additions, or deletions directly to eol-archive@ucar.edu. If you already have your data sets available on-line, please provide the WWW link or FTP access information. Once your data set (with metadata) is available, a link will be provided from the master list page along with a submission date to track future data set upgrades or revisions (if needed).

Please submit your data set(s) (including accompanying metadata or documentation files) to the HIPPO Data Archive at NCAR/EOL. Data set (and metadata) submission guidelines are available from the HIPPO-1 Project Page or by direct link to: HIPPO-1 Data Set Documentation Guidelines .

For users without direct Internet access, or if your data set(s) are too large to FTP, you may send digital file(s) on magnetic or optical media (with documentation) by conventional mail to the EOL shipping address at the bottom of this page.

The secure ftp site is just a directory to put or retrieve files from, so it is possible if people aren't careful to overwrite others files. If everyone follows the naming convention (below) that will help greatly alleviate this problem. To reach this ftp area:



ftp ftp.eol.ucar.edu

login: hippo

p: ***** (contact eol-archive@ucar.edu if you need the password)



after login you're in the hippo directory



cd to appropriate sub-project dir (HIPPO_1, HIPPO_2, etc)

cd to appropriate RF# and "put" or "get" as needed.





The preferred data format is:



NASA-Ames ascii file(s), with the NCAR variant requiring simple column headers as the last line of the header. Time is in UT seconds, either elapsed from the start of the mission or wrapping around when the day changes. A 1-line header should consist of column names only. Column names should short and obvious, and be the same for every flight file submitted They should contain only letters, numbers, and the characters "." and "_". Names should not contain characters like /,%()" or blanks/spaces. Use _ or . instead of spaces. Do not use date formats like 2008/12/13 or times like 17:45:12.

Compress if possible.

NetCDF is acceptable also. That will be the format of the reduced-size NCAR file



Some things to consider:



1. Try to keep files small but include any data for which a quicklook merge is useful, e.g. key housekeeping data can be included.



2. Time intervals should be 1s if possible, slower rates ok as appropriate.



3. Naming convention: instrument_YYYYMMDD_RF##.extension where YYYYMMDD is the UT date for the start of the flight (flights may start on different days UT vs local).  Extensions (case sensitive):



.nc = netcdf



.GV = NASA-Ames format, last header line is col headings (letters, numbers, ".", and "_" only; no spaces or commas!



.txt = flat file with col headings





4. Nothing should be in data files except the header and the data.



5. Additional information that is needed should be uploaded in a file named README_instrument_YYYYMMDD.txt





[]Updates: We encourage you to update your files after reprocessing etc. We will develop a "preliminary data" archive also, but it may not be as accessible as the quicklook. If you update your file, first rename your old one ("rename oldname newname") by adding a version number at the end, after the extension.





Note that Aeros can process both types of files and can serve as a simple quicklook tool. Tom suggested that to me, and it worked well in a Windows environment. If Aeros can indeed read the files that the team uploads I may use that to generate quicklook figures for the catalog.

Thank you very much for your assistance in providing final data to the HIPPO archive. Feel free to contact us should you encounter any problems or have any questions.

NCAR/EOL HIPPO Data Management