Call Us: US - +1 845 478 5244 | UK - +44 20 7193 7850 | AUS - +61 2 8005 4826

files atural body rotation and size/shape constants)

Subdirectories Beneath the root directory, the top-level subdirectories have a one-to-one correspondence with the bundle’s collections. Within each collection subdirectory there will usually be an XML label with a name of the form “collection[_*].xml”; each label file is accompanied by a collection inventory table with a name of the form “collection[_*].csv”. See Section 9C.1 for details on construction of collection tables. Labels for collections and the associated collection inventory tables must reside in the top-level subdirectories (see Table 2B-2). The member products for each of the collections must reside in lower level sub-directories (Figure 2B-1) An exception may be made for collections containing two dozen or fewer products, in which case the products and their labels may be co-located with the collection label in the top-level subdirectory (Figure 2B-2). The lower-level sub-directories are named and organized at the discretion of the data provider except for SPICE kernels subdirectories (see Section 2B.2.2.3). An example directory structure may be found on the PDS4 Examples web page at Table 2B-2 – SPICE_Kernels Subdirectory File or Directory Name Notes spice_kernels_* collection[_*].xml collection[_*].csv ck as needed dbk as needed dsk as needed ek as needed fk as needed ik as needed lsk as needed mk as needed pck as needed sclk as needed spk as needed PDS Standards Reference 1.11.0 2018-10-01 16 In cases where a bundle contains multiple collections of the same type, the names of the subdirectories containing these collections must be distinguished by a suffix to the mandated subdirectory name. For example, if two calibration collections are present in the archive, the two calibration subdirectories might be named calibration_flight and calibration_ground (Figure 2B-3). Figure 2B-1: Illustration of the structure for one browse subdirectory (one collection) with many basic products organized into sub-directories. Figure 2B-2: Illustration of the structure for one xml_schema subdirectory (one collection) with a small root | – bundle.xml | – readme.txt | | – browse | – collection.xml | – collection.csv | | – flight | – flight_0001_1.0.jpg | – flight_0001_1.0.xml | – flight_0002_1.0.jpg | – flight_0002_1.0.xml | … root | … | … | … | | – xml_schema | – collection.xml | – collection.csv | – imaging_dictionary_1.0.xml | – imaging_dictionary_1.0.xml | – mpf_dictionary_1.0.xml | – mpf_dictionary_1.0.xsd | – mpf_imp_raw_1.0.sch | – mpf_imp_raw_1.0.xml | – PDS4_PDS_1400.sch | – PDS4_PDS_1400.xml | – PDS4_PDS_1400.xsd PDS Standards Reference 1.11.0 2018-10-01 17 number of basic products (e.g., two dozen or fewer) placed at the same level as the collection label and inventory table. Figure 2B-3: Illustration of the structure for two subdirectories containing two collections of the same type (calibration). Lower level sub-directories (cruise, orbit_0001-0100, 2010_03, and possibly others) are defined and named by the data provider. 2B.2.2.3 SPICE_Kernels Subdirectory and Sub-Directories A SPICE_Kernels subdirectory contains individual SPICE files and their XML labels, organized by kernel type (see Table 2B-2), which must be placed in the corresponding sub-directories: ck CK files (spacecraft and instrument orientation data) dbk DBK files (databases in SPICE format) dsk DSK files (digital shape data for natural bodies) root | … | … | … | | – calibration_flight | – collection.xml | – collection.csv | | – cruise | – flightcal_product01.jpg | – flightcal_product01.xml | – flightcal_product02.jpg | – flightcal_product02.xml | … | | – orbit_0001-0100 | | – calibration_ground | – collection.xml | – collection.csv | | – 2010_03 | -2010_03_04_0001.jpg | -2010_03_04_0001.jpg | -2010_03_04_0001.jpg | -2010_03_04_0001.jpg | … PDS Standards Reference 1.11.0 2018-10-01 18 ek EK files (events information) fk FK files (reference frames definitions) ik IK files (instrument parameters and FOV definitions) lsk LSK files (leapsecond information) mk MK files (meta-kernels listing kernels to be used together) pck PCK files (natural body rotation and size/shape constants) sclk SCLK files (spacecraft clock correlation data) spk SPK files (trajectory and ephemeris data)