SDI Operator's Manual
Revised July 2000
[Search Manual] [Table of Contents] [FAQ] [Go to Previous] [Go to Next]
One index file is generated for each image detected in the SDFs.
The naming convention is: signal_type.ccyy.ddd.hhmmss.mode
signal_type | is the satellite signal type, e.g., poes |
cc | the century the image ingest started |
yy | the year the image ingest started |
ddd | the julian day the image ingest started |
hh | the UTC hour the image ingest started |
mm | is the minute the image ingest started |
ss | is the second the image ingest started |
mode | is the transmission mode of the satellite, e.g., LAC, GAC, HRPT |
As an example, the index file name for a 1996 GAC image, whose start of ingestion date and time are 228 and 12:20:00, respectively, has the name poes.1996.228.122000.GAC.
Each index file text entry has the following eight fields. One entry exists in the index file for each data frame.
The screen display below is a portion of a POES index file for an HRPT image. Each line consists of eight fields, described below.
components that form the name of an SDF containing a portion of this image, where: a is
the signal type, e.g., POES |
|
the byte address offset in the SDF that contains the start bit of the scan; for example, the first line in the screen display above begins somewhere in the 772,767th byte |
|
the location of this scan's starting bit in the byte pointed to by e |
|
the spacecraft address, not the McIDAS sensor source number, e.g., 5 (see the table at the beginning of this chapter) |
|
subblock; for GAC, this should always be zero; for HRPT and LAC this should be a repeating pattern, e.g., 1, 2, 3, 1, 2, 3,... |
|
millisecond within the nominal second (e.g., 50) described in j |
|
[Search Manual] [Table of Contents] [FAQ] [Go to Previous] [Go to Next]