The term derived files (or in some cases, derived products) refer to products or files derived from other PDS science products. In some cases, these are generated by the instrument teams and included in the PDS Archives. An example is the Derived Data Records (DDRs) of the CRISM instrument.
ODE itself also generates derived files to improve PDS usability. There are four classes of ODE derived files:
|1.||Static one PDS product to one or more derived files - These files are derived from a single PDS product. They are static, i.e. they are pre-derived from the PDS product, usually when the product is loaded into ODE. These are listed under the Product Results page’s Derived Files tab.|
|2.||Dynamic one PDS to one or more derived files – These derived files are similar to static except they are generated when a user requests them.|
|3.||Static many PDS to one derived files – These files are derived from many PDS products. They are static, i.e. they are pre-derived from the PDS products, usually when the products are loaded into ODE. The best example is the product coverage KML and Shapefiles found under the tools tab.|
|4.||Dynamic many PDS to one derived files – Finally, these products are dynamically generated products based on multiple PDS products. The most obvious example is the MOLA PEDR query tool results . These are generated from multiple PEDR products and only generated when a user asks for them.|