Search Results
51–100 of 467 results (0.000 seconds)
-
class definition:
software_online
The SOFTWARE_ONLINE catalog object contains the identifier for each node that provides online access to the software in the PDS. -
class definition:
bit_column
The bit_column object identifies a bit string embedded in a column. Bit_columns defined within columns are analogous to columns defined within rows. Note: It is recommended by the Planetary Data System that all new objects should be defined with all fields on byte boundaries. This precludes having multiple values strung together in bit strings, as occurs in the bit_column object. Bit_column is intended for use in describing existing binary data strings, but is not recommended for use in defining new data objects because it will not be recognized by most general-purpose software. Additional Note: A bit column cannot contain embedded objects. -
class definition:
event_spatial
The EVENTSPAT (Event Spatial) catalog object is completed for the event specified in the EVENT Product Catalog object. -
class definition:
nssdc_data_set_id
This template shall be completed for each PDS Data Set. The PDS Data Engineer shall fill in the PDS data set information and forward it to NSSDC who shall be responsible for supplying the value of the NSSDC_DATA_SET_ID keyword. -
class definition:
history
A HISTORY object is a dynamic description of the history of one or more associated data objects in a file. It supplements the essentially static description contained in the PDS label. The HISTORY object contains text in a format similar to that of the ODL statements used in the label. It identifies previous computer manipulation of the principal data object(s) in the file. It includes an identification of the source data, processes performed, processing parameters, as well as dates and times of processing. It is intended that the history be available for display, be dynamically extended by any process operating on the data, and automatically propagated to the resulting data file. Eventually, it might be extracted for loading in detailed level catalogs of data set contents. The HISTORY object is structured as a series of History Entries, one for each process which has operated on the data. Each entry contains a standard set of ODL element assignment statements, delimited by GROUP = program_name and END_GROUP = program_name statements. A subgroup in each entry, delimited by GROUP = PARAMETERS and END_GROUP = PARAMETERS, contains statements specifying the values of all parameters of the program. HISTORY ENTRY ELEMENTS Attribute Description VERSION_DATE Program version date, ISO standard format. DATE_TIME Run date and time, ISO standard format. NODE_NAME Network name of computer USER_NAME Username. SOFTWARE_DESC Program-generated (brief) description. USER_NOTE User-supplied (brief) description. Unlike the above elements, the names of the parameters defined in the PARAMETERS subgroup are uncontrolled, and must only conform to the program. The last entry in a HISTORY object is followed by an END statement. The HISTORY object, by convention, follows the PDS label of the file, beginning on a record boundary, and is located by a pointer statement in the label. There are no required elements for the PDS label description of the object; it is represented in the label only by the pointer statement, and OBJECT = HISTORY and END_OBJECT = HISTORY statements. The HISTORY capability has been implemented as part of the Integrated Software for Imaging Spectrometers (ISIS) system (see QUBE object definition). ISIS Qube applications add their own entries to the Qube file's cumulative History object. ISIS programs run under NASA's TAE (Transportable Applications Executive) system, and are able to automatically insert all parameters of their TAE procedure into the history entry created by the program. Consult the ISIS System Design document for details and limitations imposed by that system. (See the QUBE object description for further references.) -
class definition:
articulation_state
The ARTICULATION_STATE object provides values for articulation devices on a spacecraft. -
class definition:
palette
The PALETTE object is a sub-class of the table object. It contains entries which represents color assignments for SAMPLE values contained in an IMAGE. If the palette is stored in an external file from the data file, then it should be stored in ASCII format as 256 ROWS, each composed of 4 COLUMNS. The first column contains the SAMPLE value (0 to 255 for an 8-bit SAMPLE), and the remaining 3 COLUMNS contain the relative amount (a value from 0 to 255) of each primary color to be assigned for that SAMPLE value. If the palette is stored in the data file, then it should be stored in BINARY format as 256 consecutive 8-bit values for each primary color (RED, GREEN, BLUE) resulting in a 768 byte record. -
class definition:
band_bin
The BAND_BIN group provides a mechanism for grouping keywords that describe the properties of each 'bin' along a spectral axis. It is primarily designed for use within the SPECTRAL_QUBE object. -
class definition:
data_set_housekeeping
The DATA_SET_HOUSEKEEPING object is used to submit information about the resources (e.g. web pages, data set browsers etc) associated with a particular data set. These resources are used to select and download data products or other files associated with the data set. -
class definition:
spreadsheet
The SPREADSHEET object provides a variable-length, delimited ASCII format for labeling sparse tables and matrices. It is designed for use with spreadsheet and database text dump files in formats such as the comma-separated value (CSV) format. -
class definition:
event_positional
The EVENTPOS (Event Positional) catalog object is completed for the event specified in the EVENT Product Catalog object. -
class definition:
event_information
The EVENTINFO (Event Information) catalog object is completed for the event specified in the EVENT Product Catalog object. -
class definition:
container
The container object is a method of grouping a set of sub-objects (such as columns) that repeat within a data objects (such as a table). Use of the container object allows repeating groups to be defined within a data structure. -
class definition:
array
The ARRAY object is provided to describe dimensioned arrays of homogeneous objects. Note that an ARRAY can contain only a single object, which can itself be another ARRAY or COLLECTION if required. A maximum of 6 axes is allowed in an ARRAY. The optional _AXIS_ elements can be used to describe the variation between successive objects in the ARRAY. Values for AXIS_ITEMS and _AXIS_ elements for multidimensional arrays are supplied as sequences in which the rightmost or last item varies the fastest as the default. The default may be changed to leftmost or first item varying the fastest by including the optional element AXIS_ORDER_TYPE with a value of FIRST_INDEX_FASTEST. -
class definition:
data_set_host
The DATA_SET_HOST catalog object contains the identifier for each host/instrument pair associated with a data set. -
class definition:
element
The ELEMENT object provides a means of defining a lowest level component of a data object that is stored in an integral multiple of 8-bit bytes. Element objects may be embedded in COLLECTION and ARRAY data objects. The optional START_BYTE element identifies a location relative to the enclosing object. If not explicitly included, a START_BYTE = 1 is assumed for the ELEMENT. -
class definition:
instrument
The INSTRUMENT catalog object is used to submit information to the PDS about a particular instrument. It contains a detailed description and identifies any references associated with the instrument. -
class definition:
node
The NODE catalog object forms part of a standard set for the submission of a Node to the PDS. The NODE object contains the following subobjects: NODEINFO. -
class definition:
event
The EVENT catalog object is used to submit the information about a particular event for a PDS Product Catalog. -
class definition:
data_set_coll_assoc_data_sets
This template shall be repeated for each data set associated with the data set collection identifier in the Data Set Collection template. -
class definition:
spectral_qube
Note that the SPECTRAL_QUBE described here is specifically a PDS SPECTRAL_QUBE. While similar to the ISIS Qube, it is not identical. (For guidelines on producing a spectral qube that is compliant with both PDS and ISIS, see the SPECTRAL_QUBE chapter of Appendix A of the PDS Standards Reference.) The SPECTRAL_QUBE object is a three-dimensional object with two spatial dimensions and one spectral dimension. The axes have the interpretations 'sample', 'line', and 'band', respectively. Each of the three axes in a SPECTRAL_QUBE object may optionally include suffix data that extend the length of the axis. Conceptually, this can be viewed as forming one or more suffix planes that are attached to the core qube. Suffix planes that extend the band dimension are called BACKPLANES. Suffix planes that extend the sample dimension are called SIDEPLANES. Suffix planes that extend the line dimension are called BOTTOMPLANES. Note that these terms refer to the 'logical' axes -- that is, how the axes are conceptually modeled -- and are not necessarily related to the physical storage of the SPECTRAL_QUBE object. The suffix planes are used for storing auxiliary data that are associated with the core data. For example, a backplane might be used for storing the latitude values for each spatial-spatial pixel. Another backplane might be used for storing the wavelength of the deepest absorption feature that was found in the spectrum at each spatial-spatial pixel. One or more SIDEPLANES might be used for storing engineering data that are associated with each spatial line. Within the logical structure of the SPECTRAL_QUBE, SAMPLE=1 is the left edge of the spatial-spatial core image. LINE=1 is the top edge of the spatial-spatial core image. BAND=1 corresponds to the spatial-spatial images at the 'front' of the qube. Core coordinates do not carry over to the suffix regions. The file in which a SPECTRAL_QUBE data object is stored is physically access as though it were a one-dimensional data structure. Storing the SPECTRAL_QUBE thus requires that the 'logical' three-dimensional structure be mapped into the one-dimensional physical file structure. This involves moving through the three-dimensional structure in certain patterns to determine the linear sequence of core and suffix pixel values that occur in the file. In SPECTRAL_QUBE files, this pattern is defined by specifying which axis index varies fastest in the linear sequence of pixel values in the file, which axis varies second fastest, and which axis varies slowest. In SPECTRAL_QUBE files, the names of the three axes are always SAMPLE, LINE, and BAND. The AXIS_NAME keyword has an array of values that list the names of the axes in the qube. The order of the names specifies the qube storage order in the file. The first axis is the fastest varying, and the third axis is the slowest varying. The SPECTRAL_QUBE supports the following three storage order: - (SAMPLE, LINE, BAND) - Band Sequential (BSQ) - (SAMPLE, BAND, LINE) - Band Interleaved by Line (BIL) - (BAND, SAMPLE, LINE) - Band Interleaved by Pixel (BIP) The lengths of the core axes are given by the CORE_ITEMS keyword and the lengths of the suffix axes are given by the SUFFIX_ITEMS keyword. Both these keywords have array values, whose order corresponds to the order of the axes given by the AXIS_NAME keyword. In the physical file storage, suffix pixel data (if present) are interspersed with the associated core pixel data. For example, in a BSQ storage order file, the physical qube storage in the file begins with the pixels in the first (top) line of the spatial-spatial image plane at the first wavelength band. This is followed by the sideplane pixel values that extend this line of core pixels. Next are the core pixels for the second line, followed by the sideplane pixels for the second line. After the last line of this first core image plane (and its associated sideplane pixels) comes the bottomplane pixels associated with the first band. This is then repeated for the second through last bands. Finally, all the backplane data are stored after all the core data and associated sideplane and bottomplane pixels. If a SPECTRAL_QUBE file includes suffixes on more than one axis, then the region that is the intersection between two (or all three) of the suffix regions is called a CORNER region. The PDS requires that space for CORNER region data be allocated in the data files. However, this space is never actually used. In a SPECTRAL_QUBE file, core pixels can occupy one, two or four bytes. All core pixels within a single file must be of the same physical storage size. Suffix pixels can also occupy one, two, or four bytes of storage in the file. All the suffix pixels within a single file must be of the same physical storage size. Suffix pixels need not be the same size as core pixels. Handling of different pixel data types is described in detail below. In SPECTRAL_QUBE files, core pixel values can be represented by one of several formats. The formats available are dependent on the number of bytes used to store the values in the file. The format is given by the CORE_ITEM_TYPE keyword and the number of bytes stored is given by the CORE_ITEM_BYTES keyword. The following table shows the allowable formats and the number of bytes of storage the use: CORE_ITEM_BYTES CORE_ITEM_TYPE Type Conversion Parameters 1, 2, or 4 UNSIGNED_INTEGER Yes 1, 2, or 4 MSB_UNSIGNED_INTEGER Yes 1, 2, or 4 LSB_UNSIGNED_INTEGER Yes 1, 2, or 4 INTEGER Yes 1, 2, or 4 MSB_INTEGER Yes 1, 2, or 4 LSB_INTEGER Yes 4 IEEE_REAL No 4 VAX_REAL No 4 PC_REAL No As the table above indicates, stored integer values can be converted to real values, representing the actual pixel. The type conversion parameters are given by the CORE_BASE and CORE_MULTIPLIER keywords, and the real value being represented is determined as follows: 'real_value' = CORE_BASE + (CORE_MULTIPLIER * REAL(stored_value)) For 4-byte real formats, the stored values are floating point values that directly represent the pixel values. The same data types and number of storage bytes that are shown in the above table are also available to suffix pixels. However, suffix pixels need not be the same size or have the same data type as the core pixels. Therefore, there is a SUFFIX_ITEM_BYTES keyword to indicate the number of bytes stored for suffix pixels and a SUFFIX_ITEM_TYPE keyword to describe the data type of the suffix pixels. Each suffix plane within a single file can have a different data format. Thus, the values of these keywords are arrays. Each element of the array refers to a separate suffix plane. The SPECTRAL_QUBE allows the number of bytes used to store data in each suffix pixel (SUFFIX_ITEM_BYTES) to be less than the total number of bytes allowcated to each suffix pixel (SUFFIX_BYTES). It is therefore necessary to describe how the stored bytes are aligned within the allocated bytes. The BIT_MASK keyword is used for this purpose. Note that in the following list of required and optional objects and groups, while the *_SUFFIX groups are listed as optional, they are required if their named axis appears in the qube. -
class definition:
gazetteer_table
The Gazetteer table object provides information about the geographical features for a planet. It contains information about a named feature such as location, size, origin of feature name, etc. The Gazetteer table contains one row for each feature named on the planet. The table is formatted so that it may be read directly into many data management systems on various host computers. All fields (columns) are separated by commas, and character fields are enclosed by double quotation marks. Each record consist of 480 bytes, with a carriage return/line feed sequence in bytes 479 and 480. This allows the table to be treated as a fixed length record file on hosts that support this file type and as a normal text file on other hosts. The required columns have the following required keywords: NAME, DATA_TYPE, START_BYTE, BYTES, FORMAT, UNIT, DESCRIPTION. The required column names are: TARGET_NAME, SEARCH_FEATURE_NAME, DIACRITIC_FEATURE_NAME, MINIMUM_LATITUDE, MAXIMUM_LATITUDE, CENTER_LATITUDE, MINIMUM_LONGITUDE, MAXIMUM_LONGITUDE, CENTER_LONGITUDE, LABEL_POSITION_ID, FEATURE_LENGTH, PRIMARY_PARENTAGE_ID, SECONDARY_PARENTAGE_ID, MAP_SERIAL_ID, FEATURE_STATUS_TYPE, APPROVAL_DATE, FEATURE_TYPE, REFERENCE_NUMBER, MAP_CHART_ID, FEATURE_DESCRIPTION. For more information related to the definition of the columns, please refer to the PDS Data Preparation Workbook. -
class definition:
software
The SOFTWARE catalog object forms part of a standard set for the submission of software to the PDS. The SOFTWARE object contains the following subobjects: SWINFO, SWONLINE, and SWPUR. -
class definition:
index_table
The INDEX_TABLE object is a specific type of TABLE object that provides information about the data stored on an archive volume. The INDEX table contains one row for each data file (or data product label file in the case where detached labels are used) on the volume. The table is formatted so that it may be read directly by many data management systems on various host computers. All fields (columns) are separated by commas, and character filesd are enclosed by double quotation marks. Each record ends in a carriage return/line feed sequence. This allows the table to be treated as a fixed length record file on hosts that support this file type, and as a normal text file on other hosts. It is recommended that RECORD_BYTES and ROW_BYTES be even numbers to simplify ingestion of these files on systems where byte-level parsing is either difficult or impossible. There are two categories of columns for an Index table: Identification and Search. PDS data element names should be used as column names wherever appropriate. The required columns are used for identification. The optional columns are data dependent and are used for search. For example, the following may be useful for searching: LOCATION (e.g., LATITUDE, LONGITUDE,ORBIT_NUMBER) TIME (e.g., START_TIME,SPACECRAFT_CLOCK_START_COUNT) FEATURE (e.g., FEATURE_TYPE) OBSERVATIONAL CHARACTERISTICS (e.g., INCIDENCE_ANGLE) INSTRUMENT CHARACTERISTICS (e.g., FILTER_NAMES) For archive volumes created before this standard was approved: 1) If the keyword INDEX_TYPE is not present, the value defaults to SINGLE unless the Index's filename is given as CUMINDEX.TAB. 2) If the keyword INDEXED_FILE_NAME is not present, the value defaults to '*.*' indicating that the index encompasses all files on the volume. The required COLUMN objects must be named (NAME=): FILE_SPECIFICATION_NAME OR PATH_NAME and FILE_NAME PRODUCT_ID (**) VOLUME_ID (*) DATA_SET_ID (*) PRODUCT_CREATION_TIME (*) LOGICAL_VOLUME_PATH_NAME (must be used with PATH_NAME and FILE_NAME for a logical volume) (*) (*) If the value is constant across the data in the index table, this keyword can appear as a keyword inside the INDEX_TABLE object. If the value is not constant, then a column of the given name must be used. (**) PRODUCT_ID is not required if it has the same value as FILE_NAME or FILE_SPECIFICATION_NAME. Required keywords for required COLUMN Objects: NAME DATA_TYPE START_BYTE BYTES DESCRIPTION Optional keywords for required COLUMN Objects: UNKNOWN_CONSTANT NOT_APPLICABLE_CONSTANT NULL_CONSTANT Optional COLUMN Objects (NAME=): MISSION_NAME INSTRUMENT_NAME (or ID) INSTRUMENT_HOST_NAME (or ID) TARGET_NAME PRODUCT_TYPE MISSION_PHASE_NAME VOLUME_SET_ID START_TIME STOP_TIME SPACECRAFT_CLOCK_START_COUNT SPACECRAFT_CLOCK_STOP_COUNT any other search columns -
class definition:
spectrum
The spectrum object is a form of table used for storing spectral measurements. The spectrum is assumed to have a number of measurements of the observation target taken in different spectral bands. It uses the same physical format specification as the table object, but includes sampling parameter information which indicates the spectral region measured in successive columns or rows. The common sampling parameters for spectrum objects are wavelength, frequency, and velocity. -
class definition:
data_set_information
The DATASETINFO (Data Set Information) catalog object is completed for the data set specified in the DATASET catalog object, in order to provide information specific to the given data set, such as the boundaries of the data set. -
class definition:
image_map_projection
The IMAGE_MAP_PROJECTION object is one of two distinct objects that define the map projection used in creating cartographically registered digital images in a PDS data set. The other associated object that completes the definition is called DATA_SET_MAP_PROJECTION. The map projection information resides in these two objects to reduce redundancy and at the same time to allow the inclusion of elements needed to process the data at the image level. Basically, static information that is applicable to the complete data set resides in the DATA_SET_MAP_PROJECTION object, while dynamic information that is applicable to the individual images resides in the IMAGE_MAP_PROJECTION object. The line_first_pixel, line_last_pixel, sample_first_pixel, and sample_last_pixel keywords are used to indicate spatial orientation of a stored image. An image may have been shifted or flipped prior to being physically recorded. These keywords give the mapping of pixels between the original image and the stored image. The IMAGE_MAP_PROJECTION object is to be included in a data product label, and used to load the map projection catalog data into a PDS Catalog. Note: For pre-V3.1 PDS Standards the default coordinate system was Planetographic. -
class definition:
line_suffix
The LINE_SUFFIX group provides a mechanism for grouping keywords that describe the properties of each LINE suffix plane, or BOTTOMPLANE, of a SPECTRAL_QUBE. -
class definition:
personnel_information
The PERSINFO (Personnel Information) catalog object is completed for the PDS user id entered in the PERSON catalog object, in order to provide general information about the user. -
class definition:
data_set_collection
The following templates form part of a standard set for the submission of a data set collection to the PDS. -
class definition:
instrument_information
The INSTINFO (Instrument Information) catalog object is completed for the instrument id entered in the EBINSTRUMENT or SCINSTRUMENT catalog object. -
class definition:
sample_suffix
The SAMPLE_SUFFIX group provides a mechanism for grouping keywords that describe the properties of each SAMPLE suffix plane, or SIDEPLANE, of a SPECTRAL_QUBE. -
class definition:
image
An image object is a regular array of sample values. Image objects are normally processed with special display tools to produce a visual representation of the sample values. This is done by assigning brightness levels or display colors to the various sample values. Images are composed of LINES and SAMPLES. They may contain multiple bands, in one of several storage orders. Note: Additional engineering values may be prepended or appended to each LINE of an image, and are stored as concatenated TABLE objects, which must be named LINE_PREFIX and LINE_SUFFIX. IMAGE objects may be associated with other objects, including HISTOGRAMs, PALETTEs, HISTORY, and TABLEs which contain statistics, display parameters, engineering values, or other ancillary data. -
class definition:
mission_host
The MISSION_HOST catalog object contains the identifier for each instrument host associated with a mission. -
class definition:
volume
The volume object describes a physical unit used to store or distribute data products (e.g. a magnetic tape, CD_ROM disk, On-Line Magnetic disk or floppy disk) which contains directories and files. The directories and files may include documentation, software, calibration and geometry information as well as the actual science data. -
class definition:
series
The series object is a sub-class of the table object. It is used for storing a sequence of measurements organized in a specific way (e.g., ascending time, radial distances). The current version uses the same physical format specification as the table object, but includes sampling parameter information that describes the variation between elements in the series. The sampling parameter keywords are required for the series object, and may be optional for one or more column sub-objects, depending on the data organization. -
class definition:
directory
The Directory object is used to define a hierarchical file organization on a linear tape media. It identifies all directories and subdirectories below the root level (Note: The root directory object is implicit). Subdirectories are identified by embedding DIRECTORY objects. Files within the directories and subdirectories are sequentially identified by using FILE objects with a sequence_number value corresponding to their position on the tape. A sequence_number value will be unique for each file on the tape. -
class definition:
collection
The COLLECTION object allows the ordered grouping of heterogeneous objects into a named collection. The COLLECTION object may contain a mixture of different object types including other COLLECTIONS. The optional START_BYTE data element provides the starting location relative to an enclosing object. If a START_BYTE is not specified, a value of 1 is assumed. -
class definition:
spice_kernel
The spice_kernel object defines a single kernel from a collection of SPICE kernels. SPICE kernels provide ancillary data needed to support the planning and subsequent analysis of space science observations. The SPICE system includes the software and documentation required to read the SPICE kernels and use the data contained therein to help plan observations or interpret space science data. This software and associated documentation are collectively called the NAIF Toolkit. Kernel files are the major components of the SPICE system. The EPHEMERIS kernel type (SPK) contains spacecraft and planet, satellite or other target body ephemeris data that provide position and velocity of a spacecraft as a function of time. The TARGET_CONSTANTS kernel type (PCK) contains planet, satellite, comet or asteroid cartographic constants for that object. The INSTRUMENT kernel type (IK) contains a collection of science instrument information, including specification of the mounting alignment, internal timing, and other information needed to interpret measurements made with the instrument. The POINTING kernel type (CK) contains pointing data (e.g., the inertially referenced attitude for a spacecraft structure upon which instruments are mounted, given as a function of time). The EVENTS kernel type (EK) contains event information (e.g., spacecraft and instrument commands, ground data system event logs, and experimenter's notebook comments). The LEAPSECONDS kernel type (LSK) contains an account of the leapseconds needed to correlate civil time (UTC) with ephemeris time (TDB). This is the measure of time used in the SP kernel files. The SPACECRAFT CLOCK COEFFICIENTS kernel type (CLK) contains the data needed to correlate a spacecraft clock with ephemeris time. -
class definition:
Product_Bundle
A Product_Bundle is an aggregate product and has a table of references to one or more collections. -
class definition:
ASCII_Numeric_Base2
The ASCII Numeric Base2 class indicates an ASCII character representation of a non-negative unsigned integer in base 2. Must consist of the characters 0 and 1. May not be preceded by any sign (+/-) notation. -
class definition:
Field_Bit
The Field_Bit class provides parameters for extracting one field out of a string of bytes which contains packed data (that is, data values either smaller than a single byte, or crossing byte boundaries, or both. -
class definition:
Quaternion
The Quaternion class models a mathematical construct that consists of four individual numeric components. Quaternions are a convenient mechanism for encapsulating orientation information since they require only four units of numeric storage, as opposed to the nine needed for a rotation matrix. -
class definition:
TNDO_Context_PDS3
The Tagged NonDigital Object (TNDO) Context PDS3 class is an abstract class for the PDS3 context class hierarchy. -
class definition:
Other
The Other class provides a description of activities involved in the collection of data which are not otherwise modeled. -
class definition:
SignedMSB2
Signed 2's-complement MSB 2-byte integer -
class definition:
Units_of_Area
Units_of_Area is a magnitude of area. -
class definition:
Observing_System
The Observing System class describes the entire suite used to collect the data. -
class definition:
DD_Class_Reference
The DD Class Reference class provides a reference to a class using a namespace identifier and the class name. -
class definition:
Product_Software
Product Software is a product consisting of a set of one or more software formats.
Data Sets and Information