Example label ============= PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 1024 ^SPICE_KERNEL = "ORMM__040701000000_00086.BSP" MISSION_NAME = "MARS EXPRESS" SPACECRAFT_NAME = "MARS EXPRESS" DATA_SET_ID = "MEX-E/M-SPICE-6-V1.0" KERNEL_TYPE_ID = SPK PRODUCT_ID = "ORMM__040701000000_00086.BSP" PRODUCT_CREATION_TIME = 2008-09-12T09:52:50 PRODUCER_ID = ESA_ESTEC MISSION_PHASE_NAME = { "MR Phase 1" } PRODUCT_VERSION_TYPE = ACTUAL START_TIME = 2004-06-30T20:41:39 STOP_TIME = 2004-07-31T23:57:44 SPACECRAFT_CLOCK_START_COUNT = "N/A" SPACECRAFT_CLOCK_STOP_COUNT = "N/A" TARGET_NAME = "N/A" INSTRUMENT_NAME = "N/A" NAIF_INSTRUMENT_ID = "N/A" SOURCE_PRODUCT_ID = "ORMM__040701000000_00086.BSP" NOTE = "See comments in the file for details" OBJECT = SPICE_KERNEL INTERCHANGE_FORMAT = BINARY KERNEL_TYPE = EPHEMERIS DESCRIPTION = "MEX ephemeris information for one month, starting in the date indicated in the file name (YYMMDDhhmmss) " END_OBJECT = SPICE_KERNEL END General notes regarding label ============================= * Strings appear in quotes. * Integers and PDS times do not take quotes. * Lists are enclosed within {} type brackets. * If a field is unknown, "UNK" may be entered. * If a field is not applicable to this file, "N/A" can be used. * If a field is unknown at the moment of the creation, but it will be know at a later time, "NULL" can be used. * Fields can spill freely, with or without white space, onto following lines. Definition of Keywords/Values for SPICE Kernels: ================================================ PDS_VERSION_ID The version of the present PDS standards document PDS3. RECORD_TYPE Record format of the file, For files with fixed-length records, FIXED_LENGTH; for text files, STREAM. RECORD_BYTES Record length in the case of fixed-length records, an integer (no quotation marks). If records have variable length, "N/A". ^SPICE_KERNEL Actual file name to which this label applies. MISSION_NAME Name of the Mission for which this data set contains information (MARS EXPRESS for all products). SPACECRAFT_NAME Name of the spacecraft for which this product contains data (MARS EXPRESS for all labels). DATA_SET_ID "MEX-E/M-SPICE-6-V1.0". 'MEX' stands for Mars Express, 'E/M' identifies the targets of the mission (Earth, Mars). 'SPICE' is the SPICE data identifier. '6' is the CODMAC processing level; V1.0 is the data set version number. KERNEL_TYPE_ID Type of SPICE kernel, one of CK, EK, FK, IK, LSK, PCK, SCLK, or SPK. PRODUCT_ID Actual file name. PRODUCT_CREATION_TIME Time file was created. This follows PDS time format: YYYY-MM-DDThh:mm:ss. hh:mm:ss is not compulsory and might not appear in all files. PRODUCER_ID Team and/or individual who made the file. MISSION_PHASE_NAME The name(s) of the mission phase(s) for which this kernel stores information. PRODUCT_VERSION_TYPE It can be PREDICT or ACTUAL, depending on the type of data the product stores. PLATFORM_OR_MOUNTING_NAME This keyword is present only in labels for CK files and is always set to UNK. START_TIME Data start time. This follows the PDS time format: YYYY-MM-DDThh:mm:ss.ttt. No quotes are needed. For files not covering a specific time interval, "N/A". STOP_TIME Data stop time. This follows the PDS time format: YYYY-MM-DDThh:mm:ss.ttt. SPACECRAFT_CLOCK_START_COUNT "N/A". We think that for products created on ground it is inappropriate to associate them with a spacecraft clock. SPACECRAFT_CLOCK_STOP_COUNT Same as SPACECRAFT_CLOCK_START_COUNT. TARGET_NAME This keyword identifies the targets that are referenced in a data product. Since for some SPICE kernels it is not appropriate to define a target (for instance, the LSK kernel), while for others the list of targets depends on the mission phase and could be very long, we have chosen to set this keyword to "N/A" in all labels. INSTRUMENT_NAME Instrument name (when applicable) otherwise "N/A". NAIF_INSTRUMENT_ID Instrument NAIF ID code (when applicable), otherwise "N/A". SOURCE_PRODUCT_ID Set to actual file name, same as PRODUCT_ID. This field may also be UNK or "N/A". NOTE A brief note that forwards the reader to the comments in the kernel. OBJECT SPICE_KERNEL for SPICE kernels. INTERCHANGE_FORMAT Format of the file, either ASCII or BINARY. KERNEL_TYPE SPICE information type, Examples of possible values: EPHEMERIS, EVENTS, INSTRUMENT, LEAPSECONDS. etc. DESCRIPTION Brief description of the data in the file. END_OBJECT End of the object SPICE_KERNEL for SPICE kernels.