• Procedure to FTP files

 
• How to submit files via e-mail

 
• Naming syntax for files

 

If you want to submit a small number of products to the the field catalog, you might prefer to use the product upload form. Contact José Meitín for the password to this form. You can also submit products to the field catalog via the ftp or email method described below. 

1. Submission of files for inclusion in the catalog using ftp


All products and reports submitted to the catalog should meet certain naming conventions. If a file does not meet the naming convention, it will not be inserted into the catalog automatically. Files with improper names will be moved to a holding area for renaming or deletion.

Files to be included in the catalog must be placed in the anonymous ftp area in a particular directory as shown below:
 

FTP to catalog machine (ftp.eol.ucar.edu) - ftp ftp.eol.ucar.edu

Login anonymous - anonymous

Password "your email" - "your email"

Change directory to pub/incoming/catalog/name/ - cd pub/incoming/catalog/name/

Change to binary mode - binary

Put files - put your_file

Quit - quit
 
 

If your file does not appear in the catalog within 10 minutes the file has been moved to a holding area as it does not meet the naming convention. To check if your file has been moved log back into the catalog machine as follows:
 
 

FTP to catalog server (ftp.eol.ucar.edu) - ftp ftp.eol.ucar.edu

Login anonymous - anonymous

Password "your email" - "your email"

Change directory to pub/incoming/catalog/junk - cd pub/incoming/catalog/junk
 
 

All misnamed files will reside here. Resubmit your file after renaming on your machine. If you do not have a copy of your own file, you may down load it from this site now. If you are having persistent problems with files being moved to the junk area ask a JOSS staff member to help you.
 
 

2. Submitting files via Electronic Mail.

 

Files can be submitted to the catalog as Attachments to electronic mail. The attachment must follow the Naming Syntax described below.

 Submissions to the NAME field catalogs should be sent to catalog@eol.ucar.edu

3. Naming of files for submission to the catalog.

 

All files submitted to the catalog must conform to the following convention:

name1.name2.yyyymmdddhhmm.name3.ext  or   category.platform.date.product.extension
 

where,
 
 


1. In the case of products being sent to the catalog (to be accessed from the "PRODUCTS" button of the catalog)

name1 - must always be "ops"; for the Operational Products.

name2 - should be the platform name; e.g. radar, sounding, goes-8

yyyymmddhhmm - This is the 4 digit year, two digit month (01-12), two digit day (01,02...11,12...), two digit hour (00-23), and two digit minute (00-59) in UTC. Every file MUST have this block. If hour and minute are not relevant they can be left out.

name3 - should be the product name. This may be temperature, visible, IR, theta or similar.

ext - This is the file extension. For all files being submitted to the catalog, the acceptable extensions are .gif , .png , .jpg , .txt , .pdf , .doc , .html only. If you have trouble with converting a file to one of these file types, contact a JOSS staff member for advice.

(example file name: ops.goes-8.200210180939.Bolivia_ch1_vis.gif) 
 



2. In the case of products being sent for a Research platform (to be accessed from the "Research Products" button of the catalog)

name1 - must always be "research" . To be included under "Research Products".

name2 - should be of the form "platform". Examples are "S-Pol", "NRL_P-3".

yyyymmddhhmm - the same as for "PRODUCTS" above.

name3 - should be the product name. This may be temperature, visible, IR, theta or similar.

ext - the same as for "PRODUCTS" above.

(example file name: research.S-Pol.200204191200.base_reflectivity.jpg) 



3. In the case of products being sent for a Model Run  (to be accessed from the "Model/Fcst Products" button of the catalog)

name1 - must always be "model" . To be included under "Model/Fcst Products".

name2 - should be of the form "model name". Examples are "NCEP_Eta", "CPTEC_MM5".

yyyymmddhhmm - the same as for "PRODUCTS" above. Please note that the date and time used here should correspond to the model initialization time.

name3 - should be the product name. This may be temperature, divergence, theta or similar. If this product corresponds to, for example, a 36 hour forecast then precede "name3" with "36_".

ext - the same as for "PRODUCTS" above.

(example file name: model.UBA_Eta_NAME.200204191200.36_850_DIV.jpg)
 



4. In the case of products being sent for report (to be accessed from the "REPORTS" button of the catalog)

name1 - must always be "report".

name2 - should always be platform or location, Operations, NRL_P-3, or one that has been predefined by JOSS. Check with a JOSS staff member before submitting a report for the first time.

yyyymmddhhmm - the same as for "PRODUCTS" above.

name3 - should be the product name. This may be Summary, Status, Mission_Summary or similar.

ext - the same as for "PRODUCTS" above.

(example file name: report.Operations.200204191200.Summary.html)
 

4. How to include a figure in a report

Sample HTML to link to this image:
<a href="/name/catalog/products/joss/goes-8/20010402/goes-8.200104020501.svissr_ir1.jpg">goes-8.200104020501.svissr_ir1.jpg</a>

If none of the above makes sense or you have any problems/questions please contact José Meitín (meitin@ucar.edu)

---