Please fill out all Mandatory Profile details to continue:
Repository
Instructions
- Select the repository from the left menu
- Select the category of data from the dropdown
- Use the filter panes to refine your search/selections
- Use the search box for full text search
- To select multiple files [from the list], please use Ctrl+Click (multi-select) or Shift+Click (for range)
- Click on the file name to see more information
- Use the Column visibility button to toggle columns on/off
Welcome to the Field Terminal Support (FTS) System
The Suomi National Polar-orbiting Partnership (S-NPP) and Joint Polar Satellite System (JPSS) satellites include a High-Rate Data (HRD) antenna that continuously downlinks sensed data as the data are collected. Such a downlink is often referred to as a Direct Broadcast (DB). The Field Terminal Support (FTS) System provides FTS fundamental processing "building blocks" (software components, data, and documentation) using a public web portal. This includes Mission Support Data (including ancillary data, auxiliary data) and the necessary hardware and software specifications needed for processing the broadcasts. Orbital data are also provided on the FTS web portal to assist the DB community in locating the satellites of interest. With their own equipment (a local antenna and a remote terminal) and the above-provided information, the DB community can capture and process the HRD content and generate data products, such as Raw Data Records (RDRs), Sensor Data Records (SDRs), and a subset of Environmental Data Records (EDRs).
Algorithm Maturity information (NOAA STAR):
Profile
Hello, FTS User
Support
For FTS data outages and events, please refer to the General Satellite Messages webpage
For any operational concerns, including outages and administrative information, contact the 24/7 Help Desk at ESPCOperations@noaa.gov or (301) 817-3880
For general public comments and inquiries, contact User Services at SPSD.Userservices@noaa.gov
For website information or issues, contact the Webmaster (OSPOWebmaster@noaa.gov). If a specific page or product is involved, please include the page URL or product information when writing, so your comment or question may be more easily directed to the appropriate person.
Downloader
ftsdl is a toolkit (set of scripts) that provide options with which to batch download data from the FTS web interface.
Download: ftsdl.zip
Contains:
- ftsdl.py
- ftsdl.sh
- ftsdl_no_python.bash
- ftsdl_demo.py
- README.txt
Usage
The recommended downloader script is ftsdl.py for users who have Python 3 installed. This toolkit also requires the command line tool, curl
ftsdl.sh contains an example of how to use ftsdl.py to download files available using a file list manifest. ftsdl_demo.py is a sample Python program that uses ftsdl.py as a module.
If you choose to use bash instead of the recommended Python downloader script, you may use the ftsdl_no_python.bash script. Similarly, using this script, if you have a list of files such as those given in the manifests, you can download them with: ./ftsdl USERNAME PASSWORD < filelist
Please also consult the documentation within each script (self-contained Docstrings) for more information.
Examples:
The following provides examples of how to use this toolkit to download data from FTS.
Example script: ftsdl.sh
#!/bin/sh
# Example of calling ftsdl.py from sh or bash. This assumes ftsdl.py
# is located in the same directory as the caller. python3 and curl
# must be accessible from your $PATH.
# The first line generates a line by line list of fnmoc*np.grib2 file
# names created within the past 7 days. The second line reads that
# list of file names and downloads all which are not already present
# below the myoutputdir directory.
# Edit the example to fit your needs.
echo "myusername
mypassword" > userpassfile
python3 ftsdl.py -p userpassfile --manifest 'ancillary/fnmoc*_np.grib2' --ctime -7 | \
python3 ftsdl.py -p userpassfile -o myoutputdir
# See "python3 ftsdl.py --help" for more information.
# Here's another example that works with the "jq" JSON query utility
# to download the 5 fnmoc_naaps entries with the most recent
# CreatedDate/Time:
# python3 ftsdl.py -p userpassfile --metadata 'ancillary/fnmoc_naaps' | \
# jq -r "sort_by(.CreatedTime) | sort_by(.CreatedDate) | .[] | \
# (.Prefix + .Basename)" | tail -5 | \
# python3 ftsdl.py -p userpassfile -o mydir
Script: ftsdl.py
This script can be invoked several ways. It can also be used as a
Python module (Python programmers can use pydoc3 to learn more).
1. Download multiple FTS data files.
ftsdl.py -p userpassfile [-o outputdir] [--overwrite] < files.lst
The file userpassfile contains your FTS username on line one
and your FTS password on line two.
where files.lst contains one FTS data file per line, such as
auxiliary/mission_schedules/daily/gw1_ops_mssc_mms.xml
anciliary/fnmoc_naaps/nosuchfile.bin
documentation/atbd/READMEV2.txt
software/adl/ADL_5.3_I2.3.01.00/DVD1/adlHdfNPPDataLinks.md5
Downloaded files are stored as
outputdir/documentation/atbd/READMEV2.txt
et cetera. If "-o outputdir" is not specified then outputdir will be
"output."
Downloads that would overwrite existing files are not performed
unless the --overwrite option is selected.
2. Download one FTS data file to standard output.
ftsdl.py -p userpassfile ancillary/fnmoc_naaps/myfile \
> myfilename.txt
3. Print a list of FTS data files loaded to FTS in the past 7 days
that match the given path prefix.
ftsdl.py -p userpassfile --manifest 'ancillary/fnmoc*np.grib2' \
--ltime -7d > filelist.txt
You may pipe the output back into this script invoked as in (1):
ftsdl.py -p userpassfile --manifest 'ancillary/fnmoc*np.grib2' \
--ltime -7d | ftsdl.py -p userpassfile -o my/dir
4. Like --manifest, but print a JSON array of hashes with metadata
for each match.
ftsdl.py -p userpassfile --metadata ancillary/fnmoc_naaps \
> metadata.json
Use -v or even -v -v -v for more verbose output.
Options for forms (3) and (4) (--manifest and --metadata):
The argument to --manifest or --metadata must start with "ancillary",
"auxiliary", "documentation", or "software". It may include the
wildcards '*' (match any number of characters) and '?' (match one
single character of any time), or character ranges such as [a-z]. You
may need to put the argument in quotes to prevent your shell from
expanding wildcards. Matching is not case sensitive.
These options can be used to narrow the range of output of --manifest
and --metadata:
1. --ctime myspec: compare the file creation time with myspec
2. --ltime myspec: compare the time of file load into FTS with myspec
The 'myspec' argument has the same format as an -atime, -ctime, or
-mtime argument to the Unix 'find' command:
[+-](number[wdhms])*(number)
The units whdms stand for weeks, days, hours, minutes,
or seconds. For example:
+5 : At least 5 days old.
5 : Exactly 5 days old, rounded to the closest day.
-40h : Less than 40 hours old.
You can repeat arguments:
--ctime +7 --ctime -14 : Between 7 and 14 days old.
To obtain names of HRD Reports with a creation date less than 10 days
ago:
ftsdl.py -p userpassfile --manifest 'auxiliary/*HRD_Report' --ctime -10
FTS Information
The Field Terminal Support (FTS) provides the resources needed to support the NOAA polar satellite Direct Broadcast community. FTS provides the ancillary and auxiliary data needed for processing the S-NPP and JPSS High Rate Data (HRD) broadcasts as well as the orbital data required to locate and track the satellites. FTS distributes the JPSS Algorithm Development Library (ADL) Sensor Data Record (SDR) processing software and JPSS specifications. The HRD LInk Monitoring Reports are also available on FTS.
Please refer to the FTS User Guide for information on how to use this portal.
Please contact us for more information.