Data Usage Guidance/RestrictionsThe operational data for this datatype is available to all registered CLASS users. Pre-operational data may be restricted to authorized users. To become an authorized user, send a request to the CLASS Help Desk. |
|||
Dataset NameFile Naming convention has the following format: <PROCESSING-CENTER>.<PROJECT-ID>.<VERSION>.<PRODUCT-TYPE>.<SENEOR-ID>.<SPACECRAFT_ID>.<YEAR-DAY>.<START-TIME>.<STOP-TIME>.< PROCESSING-BLOCK-ID>.<SOURCE>.<FILE-TYPE> Where: PROCESSING-CENTER = Processing-Center where the data were created. Length: 3 char. Domain: PROJECT-ID = I dentifies the project name. Length: 4 Char. Domain: VERSION = The product's algorithm version number Length: 2 char. Domain: PRODUCT-TYPE = Identifies the type of product. length: 3 char. Domain: "SND" = Sounding-type products. Note that the fimename convention covers two types of products, and each type includes a suite of individual products. For example, the "SND" file will contain three sounding profiles: T(z), Q(z), and Hy(Z), and the "IMG" file will contain 9 integrated and surface products: TPW, CLW, RR, SWE, Snow,Cover, Sea Ice, LSE, LST and IWP. This approach allows onefile to store duplicate geolocation and other auxiliary data for each individual product type. SENSOR-ID = Short Name for the instrument used to derive the product. Length 4 to 5 char. domain: SPACECRAFT_ID = Spacecraft-Unique-ID. Length: 2 char. Domain: YEAR-DAY = Year-Day. E.g. “D79104”, where “D” identifies this group as a Julian day delimiter, “79” identifies the year in which the spacecraft began recording the data set and “104” identifies the Julian day on which the spacecraft began recording the data set. Length: 6 char. (5 characters for the date string, plus one for the “D” at the beginning). Domain: “D”+”YYJJJ” FILE-TYPE = File extension that indicates file type. Length: variable. Domain: “hdf”, “he4”, “netcdf”, “bin”, etc. Filename example: |
|||
DatatypeThe data types available for MIRS are: |
|||
End OrbitThe number of the orbit (revolution) in which the satellite was traveling at the end of the coverage of the given dataset. |
|||
End TimeThe UCT date and time corresponding to the end of the coverage of the given dataset. Format is yyyy-mm-dd hh:mm:ss.fff where fff is the fraction of a second in milliseconds. |
|||
Inventory IDA unique numerical ID assigned to the data set for CLASS inventory purposes. |
|||
NodeNot applicable to this Datatype. |
|||
Processing ModeNot applicable to this Datatype. |
|||
ResolutionNot applicable to this Datatype. |
|||
SatelliteThe satellite that acquired the MIRS Orbital data. MetOp M02 |
|||
Size (Bytes)The size of the file to be delivered to the user in bytes. |
|||
Start OrbitThe number of the orbit (revolution) in which the satellite was traveling at the beginning of the coverage of the given dataset. |
|||
Start TimeThe UCT date and time corresponding to the beginning of the coverage of the given dataset. Format is yyyy-mm-dd hh:mm:ss.fff where fff is the fraction of a second in milliseconds. |
|||
TemporalRefers to the time span of interest to the user. This section of the search page allows the user to define the range of dates/times of interest. |
|||
UTCCoordinated Universal Time (UTC) is the international time standard. It is the current term for what was referred to as Greenwich Meridian Time (GMT). Zero (0) hours UTC is midnight in Greenwich England, which lies on the zero longitudinal meridian. Universal time is based on a 24 hour clock, therefore, afternoon hours such as 4 pm UTC are expressed as 16:00 UTC (sixteen hours, zero minutes). |