|a_axis_radius|,|1|,|The a_axis_radius element provides the value of the a_axis|
|a_axis_radius|,|2|,|of a solar system body.|
|a_axis_radius|,|3|,|The a_axis is the semimajor axis of the ellipsoid that|
|a_axis_radius|,|4|,|defines the approximate shape of the body.|
|acceptance_detector_desc|,|1|,|Definition TBD.|
|acceptance_information_desc|,|1|,|Definition TBD.|
|algorithm_desc|,|1|,|The algorithm_description element describes the data|
|algorithm_desc|,|2|,|processing function performed by an algorithm and the data|
|algorithm_desc|,|3|,|types to which the algorithm is applicable.|
|algorithm_name|,|1|,|The algorithm_name element provides (where applicable) the|
|algorithm_name|,|2|,|formal name which identifies an algorithm.|
|algorithm_name|,|3|,|Example value:  RUNGE-KUTTA.|
|algorithm_version_id|,|1|,|The algorithm_version_identification element identifies|
|algorithm_version_id|,|2|,|(where applicable) the version of an algorithm.|
|alt_along_track_footprint_size|,|1|,| The alt_along_track_footprint_size element provides the|
|alt_along_track_footprint_size|,|2|,|value of along-track dimension of the Venus surface area|
|alt_along_track_footprint_size|,|3|,|whose mean radius, RMS slope, and reflectivity are reported|
|alt_along_track_footprint_size|,|4|,|in this data record. The along track dimension is chosen to|
|alt_along_track_footprint_size|,|5|,|be the smallest multiple of the doppler resolution of the|
|alt_along_track_footprint_size|,|6|,|altimeter (at this point in the spacecraft orbit) that is|
|alt_along_track_footprint_size|,|7|,|greater than 8 km.|
|alt_coarse_resolution|,|1|,| The alt_coarse_resolution element provides the value of|
|alt_coarse_resolution|,|2|,|the altimeter coarse time resolution factor taken from the|
|alt_coarse_resolution|,|3|,|radar burst header in which the raw_rad_antenna_power was|
|alt_coarse_resolution|,|4|,|reported.|
|alt_cross_track_footprint_size|,|1|,| The alt_cross_track_footprint_size element provides the|
|alt_cross_track_footprint_size|,|2|,|value of the cross-track footprint dimension determined|
|alt_cross_track_footprint_size|,|3|,|solely by the radar baud length and the spacecraft altitude|
|alt_cross_track_footprint_size|,|4|,|at this point in the orbit.|
|alt_flag2_group|,|1|,| Additional flag fields (unused).|
|alt_flag_group|,|1|,| The ALT_FLAG_GROUP element identifies the following flag|
|alt_flag_group|,|2|,|fields.|
|alt_flag_group|,|4|,|AR_FIT=0x0001|
|alt_flag_group|,|6|,|Record contains footprint values that have been|
|alt_flag_group|,|8|,|fitted in the altimetry and radiometry|
|alt_flag_group|,|10|,|mgmtac processing phase.|
|alt_flag_group|,|12|,|AR_EPHC=0x0002|
|alt_flag_group|,|14|,|Geometry values have been corrected|
|alt_flag_group|,|16|,|for ephemeris errors in the mgmorb phase.|
|alt_flag_group|,|18|,|AR_RHOC=0x0004|
|alt_flag_group|,|20|,|Reflectivity values have been corrected from C-BIDR|
|alt_flag_group|,|22|,|backscatter values in the mgmgen phase.|
|alt_flag_group|,|24|,|AR_RS2=0x0008|
|alt_flag_group|,|26|,|Range-sharpened values have passed the 2nd-order|
|alt_flag_group|,|28|,|template fitting criteria in the mgmtac phase.|
|alt_flag_group|,|30|,|AR_NRS2=0x0010|
|alt_flag_group|,|32|,|Non-range-sharpened values have passed the 2nd-order|
|alt_flag_group|,|34|,|template fitting criteria in the mgmtac phase.|
|alt_flag_group|,|36|,|AR_BAD=0x0020|
|alt_flag_group|,|38|,|Ignore this record entirely.|
|alt_flag_group|,|40|,|AR_RBAD=0x0040|
|alt_flag_group|,|42|,|Ignore the range-sharpened profile|
|alt_flag_group|,|44|,|range_sharp_echo_profile[] and the associated|
|alt_flag_group|,|46|,|derived_planetary_radius value.|
|alt_flag_group|,|48|,|AR_CBAD=0x0080|
|alt_flag_group|,|50|,|Ignore the non_range_sharp_echo_prof[]|
|alt_flag_group|,|52|,|and the associated derived_rms_surface_slope and|
|alt_flag_group|,|54|,|derived_fresnel_reflectivity values.|
|alt_flag_group|,|56|,|AR_TMARK=0x0100|
|alt_flag_group|,|58|,|Temporary derived_planetary_radius|
|alt_flag_group|,|60|,|marker flag, used in the mgmdqe phase.|
|alt_flag_group|,|62|,|AR_CMARK=0x0200|
|alt_flag_group|,|64|,|Temporary derived_rms_surface_slope marker flag, used|
|alt_flag_group|,|66|,|in the mgmdqe phase.|
|alt_flag_group|,|68|,|AR_FMARK=0x0400|
|alt_flag_group|,|70|,|Temporary derived_fesnel_reflect marker flag, used in|
|alt_flag_group|,|78|,|the mgmdqe phase.|
|alt_flag_group|,|80|,|AR_HAGFORS=0x0800|
|alt_flag_group|,|82|,|ar_slope and its errors and correlations are expressed|
|alt_flag_group|,|84|,|as Hagfors' C parameter instead of degrees of RMS|
|alt_flag_group|,|86|,|slope. This flag will not be set in any standard|
|alt_flag_group|,|88|,|ARCDR products. It is solely used during some|
|alt_flag_group|,|90|,|phases of internal MIT processing.|
|alt_flag_group|,|92|,|AR_BADALTA=0x1000|
|alt_flag_group|,|94|,|The altimetry antenna was pointed more than 5 degrees|
|alt_flag_group|,|96|,|from its expected location as given by the nominal|
|alt_flag_group|,|98|,|look-angle profile.|
|alt_flag_group|,|100|,|AR_SLOPEBAD=0x2000|
|alt_flag_group|,|102|,|The ar_slope parameter value|
|alt_flag_group|,|104|,|is suspect, and ar_prof should also be disregarded.|
|alt_flag_group|,|106|,|AR_RHOBAD=0x4000|
|alt_flag_group|,|108|,|The ar_rho value is suspect.|
|alt_flag_group|,|110|,|AR_RAD2=0x8000|
|alt_flag_group|,|112|,|This record was created under software|
|alt_flag_group|,|114|,|version 2 or higher, in which the data fields ar_rhofact,|
|alt_flag_group|,|116|,|ar_radius2, ar_sqi, and ar_thresh are significant.|
|alt_footprint_latitude|,|1|,| The alt_footprint_latitude (VBF85) element provides the|
|alt_footprint_latitude|,|2|,|value of the crust-fixed latitude of the center of the|
|alt_footprint_latitude|,|3|,|altimeter footprint, in the range of -90 (South Pole) to 90|
|alt_footprint_latitude|,|4|,|(North Pole).|
|alt_footprint_longitude|,|1|,| The alt_footprint_longitude (VBF85) element provides the|
|alt_footprint_longitude|,|2|,|value of the crust-fixed longitude of the center of the|
|alt_footprint_longitude|,|3|,|altimeter footprint, in the range of 0 - 360 easterly|
|alt_footprint_longitude|,|4|,|longitude. Periapsis nadir increases in longitude by about|
|alt_footprint_longitude|,|5|,|1.48 deg per day (about 0.2 deg per orbit).|
|alt_footprints|,|1|,| The footprints element provides the value of the number of|
|alt_footprints|,|2|,|Standard Format Data Units  in a specific orbit's altimetry|
|alt_footprints|,|3|,|data file.|
|alt_gain_factor|,|1|,| The alt_gain_factor elements provide the values of the|
|alt_gain_factor|,|2|,|altimeter gain factor taken from the radar burst header.|
|alt_gain_factor|,|3|,|alt_gain_factor[0] pertains to the measurement of|
|alt_gain_factor|,|4|,|raw_rad_antenna_power and alt_gain_factor[1] to|
|alt_gain_factor|,|5|,|raw_rad_load_power.|
|alt_partials_group|,|1|,| The alt_partials_group of the alt_footprint_longitude,|
|alt_partials_group|,|2|,|alt_footprint_latitude, and the derived_planetary_radius|
|alt_partials_group|,|3|,|with respect to the alt_spacecraft_position_vector and|
|alt_partials_group|,|4|,|alt_spacecraft_velocity_vector elements provides the value|
|alt_partials_group|,|5|,|of the partial derivatives of the footprint coordinates|
|alt_partials_group|,|6|,|with respect to changes in the spacecraft position and|
|alt_partials_group|,|7|,|velocity.|
|alt_skip_factor|,|1|,| The alt_skip_factor elements provide the values of the|
|alt_skip_factor|,|2|,|altimeter skip factor taken from the radar burst header.|
|alt_skip_factor|,|3|,|alt_skip_factor[0] pertains to the measurement of|
|alt_skip_factor|,|4|,|raw_rad_antenna_power and alt_skip_factor[1] to|
|alt_skip_factor|,|5|,|raw_rad_load_power.|
|alt_spacecraft_position_vector|,|1|,| The alt_spacecraft_position_vector element provides the|
|alt_spacecraft_position_vector|,|2|,|value of the spacecraft position at|
|alt_spacecraft_position_vector|,|3|,|altimetry_footprint_tdb_time, relative to the Venus center|
|alt_spacecraft_position_vector|,|4|,|of mass, expressed in inertial coordinates in the J2000|
|alt_spacecraft_position_vector|,|5|,|coordinate system.|
|alt_spacecraft_velocity_vector|,|1|,| The alt_spacecraft_velocity_vector element provides the|
|alt_spacecraft_velocity_vector|,|2|,|spacecraft velocity at altimetry_footprint_tdb_time,|
|alt_spacecraft_velocity_vector|,|3|,|relative to the Venus center of mass, expressed in inertial|
|alt_spacecraft_velocity_vector|,|4|,|coordinates in the J2000 coordinate system.|
|altimetry_footprint_tdb_time|,|1|,| The altimetry_footprint_tdb_time element provides the|
|altimetry_footprint_tdb_time|,|2|,|value of the ephemeris time at which the spacecraft passed|
|altimetry_footprint_tdb_time|,|3|,|directly over the center of the footprint. As each|
|altimetry_footprint_tdb_time|,|4|,|footprint is composed of data collected from several|
|altimetry_footprint_tdb_time|,|5|,|altimeter bursts, this epoch doesn't necessarily coincide|
|altimetry_footprint_tdb_time|,|6|,|with a particular burst.|
|altimetry_footprint_tdb_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|antecedent_software_name|,|1|,|The antecedent_software_name element identifies the|
|antecedent_software_name|,|2|,|processing software which is commonly applied to a science|
|antecedent_software_name|,|3|,|data set before processing by the subject software.|
|applicable_start_sclk|,|1|,|The applicable_start_sclk element is an alias within SFOC|
|applicable_start_sclk|,|2|,|for spacecraft_clock_start_count.|
|applicable_start_time|,|1|,|The applicable_start_time element is an alias within SFOC|
|applicable_start_time|,|2|,|for start_time.|
|applicable_start_time|,|501|,|Note: The current SFOC recommendation is to use start_time|
|applicable_start_time|,|502|,|instead.|
|applicable_stop_sclk|,|1|,|The applicable_stop_sclk element is an alias within SFOC for|
|applicable_stop_sclk|,|2|,|spacecraft_clock_stop_count.|
|applicable_stop_time|,|1|,|The applicable_stop_time element is an alias within SFOC for|
|applicable_stop_time|,|2|,|stop_time.|
|applicable_stop_time|,|501|,|Note: Current SFOC recommendation is to use start_time|
|applicable_stop_time|,|502|,|instead.|
|ascending_node_longitude|,|1|,|The ascending_node_longitude element provides the value of|
|ascending_node_longitude|,|2|,|the angle measured eastward along the ecliptic from the|
|ascending_node_longitude|,|3|,|vernal equinox to the ascending node of the orbit.|
|ascending_node_longitude|,|4|,|The ascending node is defined as the point where the body|
|ascending_node_longitude|,|5|,|in its orbit rises north of the ecliptic.|
|assumed_warm_sky_temperature|,|1|,| The assumed_warm_sky_temperature element provides the|
|assumed_warm_sky_temperature|,|2|,|value of the temperature assumed for the dominant portion|
|assumed_warm_sky_temperature|,|3|,|of 'sky' reflected by the radiometer footprint, including|
|assumed_warm_sky_temperature|,|4|,|atmospheric absorption and emission.|
|atmos_correction_to_distance|,|1|,| The atmos_correction_to_distance element provides the|
|atmos_correction_to_distance|,|2|,|value of the correction applied to derived_planetary_radius|
|atmos_correction_to_distance|,|3|,|to allow for the delay of signals passing through the|
|atmos_correction_to_distance|,|4|,|atmosphere, calculated by the MGMOUT phase of the altimetry|
|atmos_correction_to_distance|,|5|,|and radiometry data reduction program.|
|author_full_name|,|1|,|The author_full_name element provides the full_name of an|
|author_full_name|,|2|,|author of a document.  See also:  full_name.|
|availability_id|,|1|,|The availability_identification element is a numeric key|
|availability_id|,|2|,|which identifies the availability of the subject program or|
|availability_id|,|3|,|algorithm (e.g., program permanently on line, user request|
|availability_id|,|4|,|necessary for operator to load program, program undergoing|
|availability_id|,|5|,|development and testing--use at own risk).|
|available_value_type|,|1|,|The available_value_type element indicates whether the|
|available_value_type|,|2|,|available values for a PDS data element consist of a set of|
|available_value_type|,|3|,|literal values or represent example values (i.e. values|
|available_value_type|,|4|,|which must conform to a formation rule).  Example values:|
|available_value_type|,|5|,|L (available values are literal values), or X (available|
|available_value_type|,|6|,|values are example values).|
|average_asc_node_longitude|,|1|,| The average_asc_node_longitude element provides the value|
|average_asc_node_longitude|,|2|,|of the angle in the xy-plane of the J2000 coordinate system|
|average_asc_node_longitude|,|3|,|to the ascending node of the predicted orbit.|
|average_eccentricity|,|1|,| The average_eccentricity element provides the value of the|
|average_eccentricity|,|2|,|eccentricity of the predicted orbit.|
|average_inclination|,|1|,| The average_inclination element provides the value of the|
|average_inclination|,|2|,|angle of inclination of the predicted orbit with respect to|
|average_inclination|,|3|,|the xy-plane of the J2000 coordinate system.|
|average_orbit_peri_tdb_time|,|1|,| The average_orbit_peri_tdb_time element provides the value|
|average_orbit_peri_tdb_time|,|2|,|of the periapsis time of the predicted orbit. This orbit is|
|average_orbit_peri_tdb_time|,|3|,|based on the elements used to generate the uplink commands|
|average_orbit_peri_tdb_time|,|4|,|for the current mapping pass. It represents an average over|
|average_orbit_peri_tdb_time|,|5|,|the entire orbit, and is not the result of post-orbit|
|average_orbit_peri_tdb_time|,|6|,|navigation solutions. The elements should be used for|
|average_orbit_peri_tdb_time|,|7|,|comparison purposes only, since they may involve large|
|average_orbit_peri_tdb_time|,|8|,|errors.  The predicted orbit elements are copied from the|
|average_orbit_peri_tdb_time|,|9|,|orbit header file of the ALT-EDR tape, or, if unavailable,|
|average_orbit_peri_tdb_time|,|10|,|from the orbit header file of the C-BIDR.|
|average_orbit_peri_tdb_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|average_periapsis_argument|,|1|,| The average_periapsis_argument element provides the value|
|average_periapsis_argument|,|2|,|of the angle in the plane of the predicted orbit from the|
|average_periapsis_argument|,|3|,|ascending node in the xy-plane of the J2000 coordinate|
|average_periapsis_argument|,|4|,|system to the periapsis.|
|average_planetary_radius|,|1|,| The average_planetary_radius element provides the value of|
|average_planetary_radius|,|2|,|the planetary radius of the radiometer footprint, used to|
|average_planetary_radius|,|3|,|compute rad_footprint_longitude and rad_footprint_latitude,|
|average_planetary_radius|,|4|,|and also surface_temperature and atmospheric corrections to|
|average_planetary_radius|,|5|,|surface_emissivity.|
|average_semimajor_axis|,|1|,| The average_semimajor_axis element provides the value of|
|average_semimajor_axis|,|2|,|the semi-major axis of the predicted orbit.|
|azimuth|,|1|,|The azimuth element provides the azimuth value of a point|
|azimuth|,|2|,|of interest (for example, the center point of an image of a|
|azimuth|,|3|,|solar system object taken from a lander or a rover).|
|azimuth|,|4|,|Azimuth is an angular distance from a fixed reference|
|azimuth|,|5|,|position.|
|azimuth|,|6|,|Azimuth is measured in a spherical coordinate system, in a|
|azimuth|,|7|,|plane normal to the principal axis.  Azimuth values|
|azimuth|,|8|,|increase according to the right hand rule relative to the|
|azimuth|,|9|,|positive direction of the principal axis of the spherical|
|azimuth|,|10|,|coordinate system.  See elevation.|
|b_axis_radius|,|1|,|The b_axis_radius element provides the value of the b_axis|
|b_axis_radius|,|2|,|of a solar system body.|
|b_axis_radius|,|3|,|The b_axis is the intermediate axis of the ellipsoid which|
|b_axis_radius|,|4|,|defines the approximate shape of the body.|
|band_sequence|,|1|,|The band_sequence element identifies the order in which|
|band_sequence|,|2|,|spectral bands are stored in an image or other object.|
|band_sequence|,|300|,|Note:  In the PDS, this data element is ued to identify|
|band_sequence|,|301|,|the primary colors composing a true color image.  The|
|band_sequence|,|302|,|standard values that appear in sets of three support color|
|band_sequence|,|303|,|image display.  They are not appropriate for describing|
|band_sequence|,|304|,|multi-spectral bands.  For these, it is advisable to use|
|band_sequence|,|305|,|the sampling_parameter keywords defined elsewhere in the|
|band_sequence|,|306|,|PSDD.|
|band_storage_type|,|1|,|The band_storage_type element indicates the storage|
|band_storage_type|,|2|,|sequence of lines, samples and bands in an image.  The|
|band_storage_type|,|3|,|values describe, for example, how different samples are|
|band_storage_type|,|4|,|interleaved in image lines, or how samples from different|
|band_storage_type|,|5|,|bands are arranged sequentially. Example values:|
|band_storage_type|,|6|,|BAND SEQUENTIAL, SAMPLE INTERLEAVED, LINE INTERLEAVED.|
|bands|,|1|,|The bands element indicates the number of spectral bands in|
|bands|,|2|,|image or other object.|
|bandwidth|,|1|,|The bandwidth element provides a measure of the spectral|
|bandwidth|,|2|,|width of a filter or channel.  For a root-mean-square|
|bandwidth|,|3|,|detector this is the effective bandwidth of the filter|
|bandwidth|,|4|,|i.e., the full width of an ideal square filter having a flat|
|bandwidth|,|5|,|response over the bandwidth and zero response elsewhere.|
|best_non_range_sharp_model_tpt|,|1|,| The best_non_range_sharp_model_tpt provides the value of|
|best_non_range_sharp_model_tpt|,|2|,|the theoretical echo profile, at half-baud (0.21|
|best_non_range_sharp_model_tpt|,|3|,|microsecond) intervals, that best approximates the peak of|
|best_non_range_sharp_model_tpt|,|4|,|the non_range_sharp_echo_prof array. The optimal fit is|
|best_non_range_sharp_model_tpt|,|5|,|made by matching best_non_range_sharp_model_tpt[i] with|
|best_non_range_sharp_model_tpt|,|6|,|non_range_sharp_echo_prof[i+non_range_prof_corrs_index],|
|best_non_range_sharp_model_tpt|,|7|,|where i is a value from 0 to 49.|
|best_range_sharp_model_tmplt|,|1|,| The best_range_sharp_model_tmplt element provides the|
|best_range_sharp_model_tmplt|,|2|,|value of the theoretical echo profile, at one-baud (0.21|
|best_range_sharp_model_tmplt|,|3|,|microsecond) intervals, that best approximates the peak of|
|best_range_sharp_model_tmplt|,|4|,|the range_sharp_echo_profile array.  The optimal fit is|
|best_range_sharp_model_tmplt|,|5|,|made by matching the best_range_sharp_model_tmplt[i]|
|best_range_sharp_model_tmplt|,|6|,|element with the|
|best_range_sharp_model_tmplt|,|7|,|range_sharp_echo_profile[i+range_sharp_prof_corrs_index]|
|best_range_sharp_model_tmplt|,|8|,|element, where i is a value from 0 to 49.|
|billing_address_line|,|1|,|This column stores text for the billing address.  The text|
|billing_address_line|,|2|,|may consist of several lines containing up to sixty (60)|
|billing_address_line|,|3|,|characters each.|
|bin_number|,|1|,|The bin_number element provides the number of a bin.|
|bin_number|,|2|,|Bin_number values are dependent upon the associated binning|
|bin_number|,|3|,|scheme.|
|bin_points|,|1|,|The bin_points element identifies the number of data|
|bin_points|,|2|,|samples which fall in a given bin.|
|bin_points|,|300|,|Note:  For radiometry applications, the bin_points value is|
|bin_points|,|301|,|the number of points from a given sequence that are located|
|bin_points|,|302|,|in the given bin.|
|bit_data_type|,|1|,|The bit_data_type element provides the data type for data|
|bit_data_type|,|2|,|values stored in the BIT_COLUMN object.  See also:|
|bit_data_type|,|3|,|data_type.|
|bit_mask|,|1|,|The bit_mask element is a series of binary digits|
|bit_mask|,|2|,|identifying the active bits in a value.|
|bits|,|1|,|The bits element identifies the count of bits, or units of|
|bits|,|2|,|binary information, in a data representation.|
|bl_name|,|1|,|The bl_name element is a unique 12-character name for|
|bl_name|,|2|,|elements used in any PDS database table.  These are only|
|bl_name|,|3|,|elements used in the database.|
|bl_sql_format|,|1|,|This is the format required to generate CREATE statements|
|bl_sql_format|,|2|,|in IDM SQL.|
|bond_albedo|,|1|,|The bond_albedo element provides the value of the ratio of|
|bond_albedo|,|2|,|the total amount of energy reflected from a body to the|
|bond_albedo|,|3|,|total amount of energy (sunlight) incident on the body.|
|brightness_temperature|,|1|,| The brightness_temperature element provides the value of|
|brightness_temperature|,|2|,|the planet brightness temperature, derived from the|
|brightness_temperature|,|3|,|planet_reading_system_temp after correcting for antenna|
|brightness_temperature|,|4|,|efficiency and side-lobe gain.|
|brightness_temperature_id|,|1|,|The brightness_temperature_identification element provides|
|brightness_temperature_id|,|2|,|the designation of the spectral band for which particular|
|brightness_temperature_id|,|3|,|brightness temperature measurements were made.|
|brightness_temperature_id|,|4|,|In the spectral_contrast_range group, the|
|brightness_temperature_id|,|5|,|brightness_temperature_identification designator may refer|
|brightness_temperature_id|,|6|,|to a planetary temperature model.|
|browse_flag|,|1|,|The browse_flag element is a yes-or-no flag which indicates|
|browse_flag|,|2|,|whether browse_format data are available for a given sample|
|browse_flag|,|3|,|interval.|
|build_date|,|1|,|The build_date element provides the date associated with the|
|build_date|,|2|,|completion of the manufacture of an instrument. This date|
|build_date|,|3|,|should reflect the level of technology used in the|
|build_date|,|4|,|construction of the instrument.|
|build_date|,|200|,|Formation rule:  YYYY-MM-DDThh:mm:ss[.fff]|
|bytes|,|1|,|The bytes element indicates the number of bytes allocated|
|bytes|,|2|,|for a particular data representation.|
|c_axis_radius|,|1|,|The c_axis_radius element provides the value of the c_axis|
|c_axis_radius|,|2|,|of a solar system body.|
|c_axis_radius|,|3|,|The c_axis is the semiminor axis of the ellipsoid that|
|c_axis_radius|,|4|,|defines the approximate shape of the body.|
|ccsds_spacecraft_number|,|1|,|The ccsds_spacecraft_number element provides the number|
|ccsds_spacecraft_number|,|2|,|assigned by the CCSDS to a given spacecraft.|
|ccsds_spacecraft_number|,|501|,|Note: Due to conflicting numbering schemes between the DSN|
|ccsds_spacecraft_number|,|502|,|and the CCSDS it is recommended that this element not be|
|ccsds_spacecraft_number|,|503|,|used in SFOC catalog headers.|
|center_filter_wavelength|,|1|,|The center_filter_wavelength element provides the mid_point|
|center_filter_wavelength|,|2|,|wavelength value between the minimum and maximum instrument|
|center_filter_wavelength|,|3|,|filter wavelength values.|
|center_frequency|,|1|,|The center_frequency element provides the frequency of|
|center_frequency|,|2|,|maximum transmittance of a filter or the frequency that|
|center_frequency|,|3|,|corresponds to the geometric center of the passband of a|
|center_frequency|,|4|,|filter or a channel.|
|center_latitude|,|1|,|The center_latitude element provides a reference latitude|
|center_latitude|,|2|,|for certain map projections.  For example, in an|
|center_latitude|,|3|,|Orthographic projection, the center_latitude along with the|
|center_latitude|,|4|,|center_longitude defines the point or tangency between the|
|center_latitude|,|5|,|sphere of the planet and the plane of the projection.  The|
|center_latitude|,|6|,|map_scale (or map_resolution) is typically defined at the|
|center_latitude|,|7|,|center_latitude and center_longitude.|
|center_longitude|,|1|,|The center_longitude element provides a reference longitude|
|center_longitude|,|2|,|for certain map projections.  For example, in an|
|center_longitude|,|3|,|Orthographic projection, the center_longitude along with|
|center_longitude|,|4|,|the  center_latitude defines the point or tangency between|
|center_longitude|,|5|,|the sphere of the planet and the plane of the projection.|
|center_longitude|,|6|,|The map_scale (or map_resolution) is typically defined at|
|center_longitude|,|7|,|the center_latitude and center_longitude.|
|channel_geometric_factor|,|1|,|The channel_geometric_factor element provides the value of G|
|channel_geometric_factor|,|2|,|in the formula:  j = R/((E2-E1)G), where (E2-E1) is the|
|channel_geometric_factor|,|3|,|energy range accepted by the channel.  This formula allows|
|channel_geometric_factor|,|4|,|conversion of a particle detector channel count rate, R,|
|channel_geometric_factor|,|5|,|into a differential intensity, j|
|channel_geometric_factor|,|6|,|(counts/time.area.steradians.energy). G has dimensions of|
|channel_geometric_factor|,|7|,|area.steradians, and here includes the efficiency of|
|channel_geometric_factor|,|8|,|particle counting by the relevant detector.|
|channel_group_name|,|1|,|The channel_group_name element provides the name given to a|
|channel_group_name|,|2|,|group of particle detector channels that are activated or|
|channel_group_name|,|3|,|deactivated as a group in any instrument mode configuration.|
|channel_group_name|,|4|,|The grouping is not tied to the physical groupings of|
|channel_group_name|,|5|,|detectors, and more than one group can be activated during|
|channel_group_name|,|6|,|any one mode.|
|channel_id|,|1|,|The channel_identification element identifies the|
|channel_id|,|2|,|instrument channel through which data were obtained.|
|channel_id|,|3|,|This may refer to a spectral band or to a detector and|
|channel_id|,|4|,|filter combination.|
|channel_integration_duration|,|1|,|The channel_integration_duration element provides the length|
|channel_integration_duration|,|2|,|of time during which charge from incoming particles is|
|channel_integration_duration|,|3|,|counted by the detectors for each channel in a given mode.|
|channels|,|1|,|The channels element provides the number of channels in a|
|channels|,|2|,|particular instrument, section of an instrument, or channel|
|channels|,|3|,|group.|
|checksum|,|1|,|The checksum element represents an unsigned 32-bit sum of|
|checksum|,|2|,|all data values in a data object.|
|clustered_key|,|1|,|The clustered_key element indicates whether a column in a|
|clustered_key|,|2|,|table is part of a unique clustered index.  This index|
|clustered_key|,|3|,|determines uniqueness in the table and the sorting order of|
|clustered_key|,|4|,|the data.|
|cognizant_full_name|,|1|,|The cognizant_full_name element provides the full name of|
|cognizant_full_name|,|2|,|the individual who has either developed the processing|
|cognizant_full_name|,|3|,|software or has current knowledge of its use.  See also:|
|cognizant_full_name|,|4|,|full_name.|
|column_description|,|1|,|This is the description of a element in the database.|
|column_description|,|2|,|There should be a description for every element.|
|column_name|,|1|,|This is the 30 character dictionary name used in|
|column_name|,|2|,|documentation and template objects.  They are unique and|
|column_name|,|3|,|are an alias to the BLNAMEs.|
|column_name_alias|,|1|,|This alias is for isolated screens where the COLNAME|
|column_name_alias|,|2|,|usage may not be clear to the user.|
|column_order|,|1|,|The column_order element represents the sequence number of|
|column_order|,|2|,|columns within a table.  The sequence begins with 1 for the|
|column_order|,|3|,|first column and is incremented by 1 for each subsequent|
|column_order|,|4|,|column in the table.|
|column_required_flag|,|1|,|The column_required_flag element indicates whether an input|
|column_required_flag|,|2|,|parameter to a stored command is required or may be left|
|column_required_flag|,|3|,|blank by the user.|
|column_value|,|1|,|The column value contains a standard ASCII value used in|
|column_value|,|2|,|domain validation.  An element may have many possible|
|column_value|,|3|,|values that are valid.|
|column_value_node_id|,|1|,|The column_value_node_id element indicates a list of one or|
|column_value_node_id|,|2|,|more science nodes for which an available standard value is|
|column_value_node_id|,|3|,|available.  The list of science nodes is represented as a|
|column_value_node_id|,|4|,|concatenation of single-character identifiers in alphabetic|
|column_value_node_id|,|5|,|order.  Allowable identifiers include:  F (Fields and|
|column_value_node_id|,|6|,|Particles), I (Images), N (NAIF), U (unknown - valid only if|
|column_value_node_id|,|7|,|the column_value_type element is 'P' for a possible value|
|column_value_node_id|,|8|,|that was provided but the provider is unknown), A|
|column_value_node_id|,|9|,|(Atmospheres), P (Planetary Rings), R (Radiometry), S|
|column_value_node_id|,|10|,|(Spectroscopy).|
|column_value_type|,|1|,|The column_value_type element indicates whether a standard|
|column_value_type|,|2|,|value is considered to be an available value (the value|
|column_value_type|,|3|,|currently exists in the PDS catalog) or a possible value|
|column_value_type|,|4|,|(the value does not currently exist in the PDS catalog but)|
|column_value_type|,|5|,|may exist in the future).  Example values:  A (available|
|column_value_type|,|6|,|value) or P (possible value).|
|columns|,|1|,|The columns element represents the number of columns in|
|columns|,|2|,|each row of a data object.|
|columns|,|300|,|Note:  In the PDS, the term 'columns' is synonymous with|
|columns|,|301|,|'fields'.|
|committee_member_full_name|,|1|,|The committee_member_full_name element identifies a peer|
|committee_member_full_name|,|2|,|review committee member.  The member does not necessarily|
|committee_member_full_name|,|3|,|have a PDS userid.  See also:  full_name.|
|computer_vendor_name|,|1|,|The computer_vendor_name element identifies the|
|computer_vendor_name|,|2|,|manufacturer of the computer hardware on which the|
|computer_vendor_name|,|3|,|processing software operates.|
|cone_angle|,|1|,|The cone_angle element provides the value of the angle|
|cone_angle|,|2|,|between the primary spacecraft axis and the pointing|
|cone_angle|,|3|,|direction of the instrument.|
|cone_offset_angle|,|1|,|The cone_offset_angle element provides the elevation angle|
|cone_offset_angle|,|2|,|(in the cone direction) between the pointing direction along|
|cone_offset_angle|,|3|,|which an instrument is mounted and the cone axis of the|
|cone_offset_angle|,|4|,|spacecraft.|
|cone_offset_angle|,|5|,|See also cross_cone_offset_angle, twist_offset_angle, and|
|cone_offset_angle|,|6|,|cone_angle.|
|confidence_level_note|,|1|,|The confidence_level_note element is a text field which|
|confidence_level_note|,|2|,|characterizes the reliability of data within a data set or|
|confidence_level_note|,|3|,|the reliability of a particular programming algorithm or|
|confidence_level_note|,|4|,|software component.  Essentially, this note discusses the|
|confidence_level_note|,|5|,|level of confidence in the accuracy of the data or in the|
|confidence_level_note|,|6|,|ability of the software to produce accurate results.|
|contamination_desc|,|1|,|The contamination_description element describes the type of|
|contamination_desc|,|2|,|data contamination which is associated with a particular|
|contamination_desc|,|3|,|contamination_identification value.|
|contamination_desc|,|4|,|The various values of contamination_identification and|
|contamination_desc|,|5|,|contamination_description are instrument_dependent.|
|contamination_id|,|1|,|The contamination_identification element identifies a type|
|contamination_id|,|2|,|of contamination which affected an instrument during a|
|contamination_id|,|3|,|particular period of data acquisition.|
|contamination_id|,|4|,|The associated contamination_description element describes|
|contamination_id|,|5|,|the type of contamination.|
|coordinate_system_center_name|,|1|,|The coordinate_system_center_name element identifies a|
|coordinate_system_center_name|,|2|,|named target, such as the Sun, a planet, a satellite or a|
|coordinate_system_center_name|,|3|,|spacecraft, as being the location of the center of the|
|coordinate_system_center_name|,|4|,|reference coordinate system.|
|coordinate_system_center_name|,|5|,|The coordinate_system_center_name element can also be used|
|coordinate_system_center_name|,|6|,|to identify a barycenter used for a SPICE s_ or p_kernel.|
|coordinate_system_desc|,|1|,|The coordinate_system_description element describes a named|
|coordinate_system_desc|,|2|,|reference coordinate system in terms of the definitions of|
|coordinate_system_desc|,|3|,|the axes and the `handedness' of the system.  It also|
|coordinate_system_desc|,|4|,|provides other necessary descriptive information, such as|
|coordinate_system_desc|,|5|,|the rotation period for rotating coordinate systems.|
|coordinate_system_id|,|1|,|The coordinate_system_identification element provides an|
|coordinate_system_id|,|2|,|alphanumeric identifier for the referenced coordinate|
|coordinate_system_id|,|3|,|system.|
|coordinate_system_name|,|1|,|The coordinate_system_name element provides the full name|
|coordinate_system_name|,|2|,|of the coordinate system to which the state vectors are|
|coordinate_system_name|,|3|,|referenced.|
|coordinate_system_name|,|4|,|Example value:  JUPITER SYSTEM III.|
|coordinate_system_ref_epoch|,|1|,|The coordinate_system_reference_epoch element provides the|
|coordinate_system_ref_epoch|,|2|,|Julian date selected as the reference time for a geometric|
|coordinate_system_ref_epoch|,|3|,|quantity that changes over time.|
|coordinate_system_ref_epoch|,|4|,|For example, the location of a prime meridian may have a|
|coordinate_system_ref_epoch|,|5|,|fixed value at a reference epoch, with additional|
|coordinate_system_ref_epoch|,|6|,|time_dependent terms added.|
|copies|,|1|,|The copies element provides the inventory software with the|
|copies|,|2|,|number of copies of an order that a node is willing to ship|
|copies|,|3|,|using a particular order.|
|create_date|,|1|,|This date is in YYYYMMDD format and is used for storing the|
|create_date|,|2|,|create date of a table or query on the database.|
|criticality|,|1|,|This column stores the criticality code for an attribute.|
|criticality|,|2|,|A criticality id is assigned to each table's attribute so|
|criticality|,|3|,|the criticality can be dependent on the usage within a|
|criticality|,|4|,|table.  This criticality is used by the catalog bulk load|
|criticality|,|5|,|software during a template object validation step.|
|cross_cone_angle|,|1|,|The cross_cone_angle element provides the value of an|
|cross_cone_angle|,|2|,|azimuthal measurement orthogonal to cone_angle.|
|cross_cone_offset_angle|,|1|,|The cross_cone_offset_angle element provides the azimuthal|
|cross_cone_offset_angle|,|2|,|(in the cross-cone direction) between the pointing direction|
|cross_cone_offset_angle|,|3|,|along which an instrument is mounted and the cross_cone axis|
|cross_cone_offset_angle|,|4|,|of the spacecraft.|
|cross_cone_offset_angle|,|5|,|See also cone_offset_angle, twist_offset_angle, and|
|cross_cone_offset_angle|,|6|,|cross_cone_angle.|
|cycle_id|,|1|,|The cycle_id element provides an identification for a|
|cycle_id|,|2|,|particular cycle of the Voyager PLS instrument.  The PLS is|
|cycle_id|,|3|,|programed to execute a sequence of instrument modes at|
|cycle_id|,|4|,|specific time intervals.  These sequences repeat|
|cycle_id|,|5|,|continuously in a given instrument cycle.|
|da_contact_pds_user_id|,|1|,|The da_contact_pds_user_id element provides the pds_user_id|
|da_contact_pds_user_id|,|2|,|of the data administration contact at a node.|
|data_coverage_percentage|,|1|,|The data_coverage_percentage element provides an indication|
|data_coverage_percentage|,|2|,|of the fraction of samples available in a given time period|
|data_coverage_percentage|,|3|,|compared to the maximum possible.|
|data_coverage_percentage|,|4|,|The percentage value is defined as ((Number of samples|
|data_coverage_percentage|,|5|,|available) divided by (total number of samples possible in|
|data_coverage_percentage|,|6|,|the spacecraft time range)) multiplied by 100.|
|data_object_type|,|1|,|The data_object_type element identifies the data object|
|data_object_type|,|2|,|type of a given set of data.|
|data_object_type|,|4|,|Example values:  IMAGE, MAP, SPECTRUM|
|data_object_type|,|300|,|Note:  Within the PDS, data object types are assigned|
|data_object_type|,|301|,|according to the standards outlined in the Data Preparation|
|data_object_type|,|302|,|Workbook, Volume 2.|
|data_object_type|,|501|,|Note: Within SFOC and only for the Magellan catalog, this|
|data_object_type|,|502|,|element is used as an alias for data_set_id.  The use of|
|data_object_type|,|503|,|data_object_type as such provides backward compatibility|
|data_object_type|,|504|,|with earlier SFOC conventions.  The use of this element as|
|data_object_type|,|505|,|an alias for data_set_id is not recommended for any new|
|data_object_type|,|506|,|tables.  See data_set_id.|
|data_path_type|,|1|,|The data_path_description element describes the telemetry|
|data_path_type|,|2|,|path which data traversed from a spacecraft to the ground.|
|data_path_type|,|3|,|Example Values:  REALTIME, RECORDED DATA PLAYBACK.|
|data_quality_desc|,|1|,|The data_quality_description element describes the data|
|data_quality_desc|,|2|,|quality which is associated with a particular|
|data_quality_desc|,|3|,|data_quality_identification value.|
|data_quality_desc|,|4|,|The various values of data_quality_identification and|
|data_quality_desc|,|5|,|data_quality_description are instrument_dependent.|
|data_quality_id|,|1|,|The data_quality_identification element provides a numeric|
|data_quality_id|,|2|,|key which identifies the quality of data available for a|
|data_quality_id|,|3|,|particular time period.|
|data_quality_id|,|4|,|The data quality identification scheme is unique to a given|
|data_quality_id|,|5|,|instrument and is described by the associated|
|data_quality_id|,|6|,|data_quality_description element.|
|data_rate|,|1|,|The data_rate element provides the rate at which data were|
|data_rate|,|2|,|transmitted from a spacecraft to the ground (i.e., the|
|data_rate|,|3|,|telemetry rate).|
|data_set_acceptance_date|,|1|,|Definition TBD.|
|data_set_bytes|,|1|,|The data_set_bytes element is the total size, in bytes, of|
|data_set_bytes|,|2|,|a data set.  This is used by the inventory software to|
|data_set_bytes|,|3|,|determine the portion of a data set that the users has|
|data_set_bytes|,|4|,|ordered.|
|data_set_collection_desc|,|1|,|The data_set_collection_desc element describes the content|
|data_set_collection_desc|,|2|,|and type of the related data sets contained in the|
|data_set_collection_desc|,|3|,|collection.|
|data_set_collection_id|,|1|,|The data_set_collection_id element is a unique alphanumeric|
|data_set_collection_id|,|2|,|identifier for a collection of related data sets or data|
|data_set_collection_id|,|3|,|products.  The data set collection is treated as a single|
|data_set_collection_id|,|4|,|unit, whose components are selected according to a specific|
|data_set_collection_id|,|5|,|scientific purpose.  Components are related by observation|
|data_set_collection_id|,|6|,|type, discipline, target, time, or other classifications.|
|data_set_collection_id|,|8|,|Example value: PREMGN-E/L/H/M/V-4/5-RAD/GRAV-V1.0|
|data_set_collection_id|,|300|,|Note: In the PDS, data set collection ids are constructed|
|data_set_collection_id|,|301|,|according to PDS nomenclature standards outlined in the|
|data_set_collection_id|,|302|,|Data Preparation Workbook, Volume 2.|
|data_set_collection_id_or_name|,|1|,|The data_set_collection_id_or_name provides either the|
|data_set_collection_id_or_name|,|2|,|identification of a given data set collection|
|data_set_collection_id_or_name|,|3|,|(data_set_collection_id), or the full name of a given data|
|data_set_collection_id_or_name|,|4|,|set (data_set_collection_name).|
|data_set_collection_member_flg|,|1|,|The data_set_collection_member_flg element indicates|
|data_set_collection_member_flg|,|2|,|whether or not a data set is a member of a data set|
|data_set_collection_member_flg|,|3|,|collection.|
|data_set_collection_name|,|1|,|The data_set_collection_name element provides the full name|
|data_set_collection_name|,|2|,|given to a collection of related data sets or data products.|
|data_set_collection_name|,|3|,|The data set collection is treated as a single unit, whose|
|data_set_collection_name|,|4|,|components are selected according to a specific scientific|
|data_set_collection_name|,|5|,|purpose.  Components are related by observation type,|
|data_set_collection_name|,|6|,|discipline, target, time, or other classifications.|
|data_set_collection_name|,|8|,|Example value: PRE-MAGELLAN E/L/H/M/V 4/5 RADAR/GRAVITY|
|data_set_collection_name|,|9|,|DATA V1.0|
|data_set_collection_name|,|300|,|Note:  In the PDS, the data set collection name is|
|data_set_collection_name|,|301|,|constructed according to nomenclature standards outlined|
|data_set_collection_name|,|302|,|in the Data Preparation Workbook, Volume 2.|
|data_set_collection_release_dt|,|1|,|The data_set_collection_release_dt element provides the|
|data_set_collection_release_dt|,|2|,|date when the data set collection was released for use.|
|data_set_collection_usage_desc|,|1|,|The data_set_collection_usage_desc element provides|
|data_set_collection_usage_desc|,|2|,|information required to use the data.|
|data_set_cost|,|1|,|The data_set_cost element is the cost per granule of|
|data_set_cost|,|2|,|shipping the data set using a particular medium.|
|data_set_desc|,|1|,|The data_set_description element describes the content and|
|data_set_desc|,|2|,|type of a data set and provides information required to use|
|data_set_desc|,|3|,|the data (such as binning information).|
|data_set_granule_name|,|1|,|The data_set_granule_name element provides the name of the|
|data_set_granule_name|,|2|,|level of granularity for each data set media type a node|
|data_set_granule_name|,|3|,|can deliver.|
|data_set_id|,|1|,|The data_set_identification element is a unique|
|data_set_id|,|2|,|alphanumeric identifier for a data set or a data product.|
|data_set_id|,|3|,|The data_set_identification value for a given data set or|
|data_set_id|,|4|,|product is constructed according to flight project|
|data_set_id|,|5|,|naming conventions.  In most cases the data_set_id is an|
|data_set_id|,|6|,|abbreviation of the data_set_name.|
|data_set_id|,|8|,|Example value: MR9/VO1/VO2-M-ISS/VIS-5-CLOUD-V1.0.|
|data_set_id|,|300|,|Note:  In the PDS, the values for both data_set_id and|
|data_set_id|,|301|,|data_set_name are constructed according to standards|
|data_set_id|,|302|,|outlined in the Data Preparation Workbook, Volume 2.|
|data_set_id_or_name|,|1|,|The data_set_id_or_name element provides either the|
|data_set_id_or_name|,|2|,|identification of a given data set (its data_set_id), or the|
|data_set_id_or_name|,|3|,|name of a given data set (its data_set_name).|
|data_set_id_or_name|,|300|,|Note:  In PDS, the values for both the data_set_id and the|
|data_set_id_or_name|,|301|,|data_set_name are constructed according to standards|
|data_set_id_or_name|,|302|,|outlined in the Data Preparation Workbook, Volume 2.|
|data_set_name|,|1|,|The data_set_name element provides the full name given to a|
|data_set_name|,|2|,|data set or a data product.  The data_set_name typically|
|data_set_name|,|3|,|identifies the instrument that acquired the data, the target|
|data_set_name|,|4|,|of that instrument, and the processing level of the data.|
|data_set_name|,|5|,|Example value:  MR9/VO1/VO2 MARS IMAGING SCIENCE|
|data_set_name|,|6|,|SUBSYSTEM/VIS 5 CLOUD V1.0.  See also:  data_set_id.|
|data_set_name|,|300|,|Note:  In PDS, the data_set_name is constructed according to|
|data_set_name|,|301|,|standards outlined in the Data Preparation Workbook, Vol. 2.|
|data_set_name|,|501|,|Note:  This element is defined in the SFOC Magellan catalog|
|data_set_name|,|502|,|as an alias for file_name to provide backward compatibility|
|data_set_or_inst_parm_desc|,|1|,|The data_set_or_inst_parm_desc element describes either a|
|data_set_or_inst_parm_desc|,|2|,|data set or instrument parameter.|
|data_set_or_instrument_parm_nm|,|1|,|The data_set_or_instrument_parameter_name element provides|
|data_set_or_instrument_parm_nm|,|2|,|either a data_set_parameter_name or an|
|data_set_or_instrument_parm_nm|,|3|,|instrument_parameter_name.  That is, this element may have|
|data_set_or_instrument_parm_nm|,|4|,|values which are either the name of a parameter derived from|
|data_set_or_instrument_parm_nm|,|5|,|measured data (the data_set_parameter_name) or the name of a|
|data_set_or_instrument_parm_nm|,|6|,|parameter measured by an instrument (the|
|data_set_or_instrument_parm_nm|,|7|,|instrument_parameter_name).|
|data_set_parameter_name|,|1|,|The data_set_parameter_name element provides the name of|
|data_set_parameter_name|,|2|,|the scientific parameter or physical quantity that was|
|data_set_parameter_name|,|3|,|derived from measured data.  A description of the dataset|
|data_set_parameter_name|,|4|,|parameter is provided by the data_set_or_inst_parm_desc.|
|data_set_parameter_name|,|5|,|See also instrument_parameter_name.|
|data_set_parameter_name|,|6|,|Example value: MAGNETIC FIELD INTENSITY|
|data_set_parameter_unit|,|1|,|The data_set_parameter_unit element specifies the unit of|
|data_set_parameter_unit|,|2|,|measure of associated data set parameters.|
|data_set_release_date|,|1|,|The data_set_release_date element provides the date when|
|data_set_release_date|,|2|,|a data set was released for use.|
|data_set_release_date|,|200|,|Formation rule:  YYYY-MM-DD|
|data_set_release_date|,|500|,|Note: In SFOC, the data_set_release_date element is used to|
|data_set_release_date|,|501|,|identify the date at which a product may be released to the|
|data_set_release_date|,|502|,|general public from proprietary access.  SFOC-related|
|data_set_release_date|,|503|,|systems should apply this element only to proprietary data.|
|data_set_size_threshold|,|1|,|The data_set_size_threshold element provides the inventory|
|data_set_size_threshold|,|2|,|software with the portions of a data set, in bytes, that a|
|data_set_size_threshold|,|3|,|node is willing to ship on a particular medium.  If a user's|
|data_set_size_threshold|,|4|,|order exceeds this amount for the medium that he has chosen,|
|data_set_size_threshold|,|5|,|then the order will be routed to the NSSDC to be filled.|
|data_sets|,|1|,|The data_sets element identifies the number of data sets|
|data_sets|,|2|,|contained in a data set collection.|
|data_source_desc|,|1|,|The data_source_desc element describes the source of a data|
|data_source_desc|,|2|,|value descriptive of a target body.  The source may be a|
|data_source_desc|,|3|,|document, an individual, or an institution.|
|data_source_desc|,|4|,|See also data_source_identification.|
|data_source_id|,|1|,|The data_source_identification element identifies the source|
|data_source_id|,|2|,|of a data value descriptive of a target body.  The source|
|data_source_id|,|3|,|may be a document, an individual, or an institution, as|
|data_source_id|,|4|,|described by the associated data_source_desc element.|
|data_stream_type|,|1|,|The data_stream_type element identifies a particular type of|
|data_stream_type|,|2|,|data stream to which the given data product is related.|
|data_stream_type|,|501|,|Note: In SFOC this element is used to identify the|
|data_stream_type|,|502|,|particular type of data stream that a given decommutation|
|data_stream_type|,|503|,|map can process.|
|data_type|,|1|,|The data_type element supplies the internal representation|
|data_type|,|2|,|and/or mathematical properties of a value being stored.|
|data_type|,|3|,|See also:  bit_data_type, general_data_type.|
|decal_name|,|1|,|The decal_name element describes the specific decalibration|
|decal_name|,|2|,|data file.  This element is used only in SFOC-Magellan|
|decal_name|,|3|,|mission operations.|
|declination|,|1|,|The declination element provides the value of an angle,|
|declination|,|2|,|corresponding to latitude, used to fix position on the|
|declination|,|3|,|celestial sphere.|
|declination|,|4|,|Declination is measured positive north and negative south|
|declination|,|5|,|of the celestial equator, and is defined relative to a|
|declination|,|6|,|specified reference period or epoch.  See right_ascension.|
|defining_authority_name|,|1|,|The defining_authority_name element identifies the|
|defining_authority_name|,|2|,|Control Authority Office (CAO) responsible for|
|defining_authority_name|,|3|,|maintaining the definition of a particular SFDU format.|
|defining_authority_name|,|4|,|CAOs are officially recognized by the Consultative|
|defining_authority_name|,|5|,|Committee on Space Data Systems (CCSDS).|
|delivery_estimate_date|,|1|,|The delivery_date element identifies the date indicated by|
|delivery_estimate_date|,|2|,|a science node for estimated delivery of ordered data.|
|derived_fresnel_reflect_corr|,|1|,| The derived_fresnel_reflect_corr element provides the|
|derived_fresnel_reflect_corr|,|2|,|value of the derived_fresnel_reflectivity correction factor|
|derived_fresnel_reflect_corr|,|3|,|for diffuse scattering which is a factor by which the|
|derived_fresnel_reflect_corr|,|4|,|derived_fresnel_reflectivity be multiplied by (but only if|
|derived_fresnel_reflect_corr|,|5|,|the derived_fresnel_reflectivity is set in alt_flag_group),|
|derived_fresnel_reflect_corr|,|6|,|to allow for the effect of small-scale surface roughness.|
|derived_fresnel_reflectivity|,|1|,| The derived_fresnel_reflectivity element provides the|
|derived_fresnel_reflectivity|,|2|,|value of the bulk reflectivity of the surface material,|
|derived_fresnel_reflectivity|,|3|,|averaged over the radar footprint, obtained by fitting the|
|derived_fresnel_reflectivity|,|4|,|altimeter echo to a suite of theoretical templates derived|
|derived_fresnel_reflectivity|,|5|,|from the Hagfors scattering model, but ignoring the effect|
|derived_fresnel_reflectivity|,|6|,|of small-scale surface roughness.|
|derived_maximum|,|1|,|The derived_maximum element indicates the largest value|
|derived_maximum|,|2|,|occurring in a given instance of the data object after the|
|derived_maximum|,|3|,|application of a scaling factor and/or offset.|
|derived_minimum|,|1|,|The derived_minimum element indicates the smallest value|
|derived_minimum|,|2|,|occurring in a given instance of the data object after the|
|derived_minimum|,|3|,|application of a scaling factor and/or offset.|
|derived_planetary_radius|,|1|,| The derived_planetary_radius element provides the value of|
|derived_planetary_radius|,|2|,|the mean Venus radius for this radar footprint, obtained by|
|derived_planetary_radius|,|3|,|subtracting (uncorrected_range_to_nadir -|
|derived_planetary_radius|,|4|,|atmospheric_correct_to_range) from the length of the|
|derived_planetary_radius|,|5|,|alt_spacecraft_position_vector element.|
|derived_planetary_thresh_radi|,|1|,| The derived_planetary_thresh_radi element provides the|
|derived_planetary_thresh_radi|,|2|,|value of the threshold Venus radius for this radar|
|derived_planetary_thresh_radi|,|3|,|footprint, obtained from the value of the|
|derived_planetary_thresh_radi|,|4|,|derived_thresh_detector_index element, after correcting for|
|derived_planetary_thresh_radi|,|5|,|atmospheric delay.|
|derived_rms_surface_slope|,|1|,| The derived_rms_surface_slope element provides the value|
|derived_rms_surface_slope|,|2|,|of the root mean square meter-scale surface slope, averaged|
|derived_rms_surface_slope|,|3|,|over the radar footprint, obtained by fitting the altimeter|
|derived_rms_surface_slope|,|4|,|echo to a suite of theoretical templates derived from the|
|derived_rms_surface_slope|,|5|,|Hagfors scattering model.|
|derived_thresh_detector_index|,|1|,| The derived_thresh_detector_index element provides the|
|derived_thresh_detector_index|,|2|,|value of the element in range_sharp_echo_profile that|
|derived_thresh_detector_index|,|3|,|satisfies the altimeter threshold detection algorithm,|
|derived_thresh_detector_index|,|4|,|representing the distance to the nearest object in this|
|derived_thresh_detector_index|,|5|,|radar footprint in units of 33.2 meters, modulus a 10.02|
|derived_thresh_detector_index|,|6|,|kilometer altimeter range ambiguity.|
|description|,|1|,|The description element provides a free-form,|
|description|,|2|,|unlimited-length character string that represents or gives|
|description|,|3|,|an account of something.|
|detailed_catalog_flag|,|1|,|The detailed_catalog_flag element is a yes-or-no flag|
|detailed_catalog_flag|,|2|,|which indicates whether additional information is available|
|detailed_catalog_flag|,|3|,|for this data set in a detailed-level catalog.|
|detector_aspect_ratio|,|1|,|The detector_aspect_ratio element provides the ratio of the|
|detector_aspect_ratio|,|2|,|horizontal to the vertical field of view of a detector.|
|detector_desc|,|1|,|The detector_desc element describes a detector utilized by|
|detector_desc|,|2|,|an instrument.|
|detector_group_name|,|1|,|Definition TBD.|
|detector_groups|,|1|,|Definition TBD.|
|detector_id|,|1|,|The detector_id element identifies a particular instrument|
|detector_id|,|2|,|detector.|
|detector_id|,|3|,|The associated instrument_detector_description element|
|detector_id|,|4|,|describes the detector.|
|detector_type|,|1|,|The detector_type element identifies the type of an|
|detector_type|,|2|,|instrument's detector.|
|detector_type|,|3|,|Example values: SI CCD, INSB, GE, VIDICON, PHOTODIODE.|
|detectors|,|1|,|The detectors element provides the number of detectors of a|
|detectors|,|2|,|specified type contained in the subject instrument.|
|discipline_desc|,|1|,|The discipline_description element describes the discipline|
|discipline_desc|,|2|,|identified by the discipline_name element.|
|discipline_name|,|1|,|The discipline_name element identifies the major academic|
|discipline_name|,|2|,|or scientific domain or specialty of interest to an|
|discipline_name|,|3|,|individual or to a PDS Node.|
|display_format|,|1|,|The display_format element provides display format|
|display_format|,|2|,|information to software that formats data to an output|
|display_format|,|3|,|device.  Valid format types include DATE(x) where X is the|
|display_format|,|4|,|number of digits in a date.  Usually DATE(6) (YYYY-MM) or|
|display_format|,|5|,|DATE(8) (YYYY-MM-DD).  TIME(X) where X is the number of|
|display_format|,|6|,|digits in a time statement.  This is usually represented as|
|display_format|,|7|,|TIME(6) (HH:MM:SS) or TIME(4) (HH:MM)>  DATETIME is used|
|display_format|,|8|,|for UTC date-times (MM-DD-YYYYTHH:MM:SS.HHH).  JUSTLEFT is|
|display_format|,|9|,|used for left-justified character strings, and JUSTRIGHT is|
|display_format|,|10|,|used for right justification.  DIGIT(X) is used where X is|
|display_format|,|11|,|the number of digits in an integer, so 897 would be|
|display_format|,|12|,|DIGIT(3).  SCI(X,Y) is used where X is the number of|
|display_format|,|13|,|significant digits before the decimal in scientific|
|display_format|,|14|,|notation, and Y is the number following the decimal, so|
|display_format|,|15|,|1.293E-2 would be SCI(1,3).  FLOAT(X) is used where X is the|
|display_format|,|16|,|total number of digits in a floating point number, so|
|display_format|,|17|,|33.018746 would be FLOAT(8).  USDOLLAR is used for monetary|
|display_format|,|18|,|amounts in the indicated currency, PHONE is used for|
|display_format|,|19|,|telephone numbers, and FTSPHONE is used for seven-digit|
|display_format|,|20|,|numbers in the Federal Telephone System.|
|distribution_media_desc|,|1|,|The distribution_media_desc element provides the description|
|distribution_media_desc|,|2|,|of the distribution media for an order item.  This|
|distribution_media_desc|,|3|,|description is only associated with an individual order|
|distribution_media_desc|,|4|,|item.|
|distribution_node_id|,|1|,|The distribution_node_id element identifies the node which|
|distribution_node_id|,|2|,|fills and distributes an order.|
|document_topic_type|,|1|,|The document_topic_type element is a keyword which|
|document_topic_type|,|2|,|identifies the major topic of a reference document.|
|dsn_spacecraft_num|,|1|,|The dsn_spacecraft_num element identifies the unique Deep|
|dsn_spacecraft_num|,|2|,|Space Network identification number for a spacecraft or|
|dsn_spacecraft_num|,|3|,|other data source/sink from which a product came or to which|
|dsn_spacecraft_num|,|4|,|the product is to be sent.|
|dsn_station_number|,|1|,|The dsn_station_num identifies the deep space network|
|dsn_station_number|,|2|,|station number through which data were received or to|
|dsn_station_number|,|3|,|which commands are to be sent.|
|earth_base_desc|,|1|,|The earth_base_description element describes the earth base|
|earth_base_desc|,|2|,|from which particular instrument measurements where taken.|
|earth_base_desc|,|3|,|An earth base can be a laboratory, observatory, etc., and is|
|earth_base_desc|,|4|,|identified by the earth_base_id element.|
|earth_base_id|,|1|,|The earth_base_id element provides a unique identifier for|
|earth_base_id|,|2|,|the laboratory, observatory, or other location of an earth-|
|earth_base_id|,|3|,|based instrument.|
|earth_base_institution_name|,|1|,|The earth_base_institution_name element identifies a|
|earth_base_institution_name|,|2|,|university, research center, NASA center or other|
|earth_base_institution_name|,|3|,|institution associated with a laboratory or observatory.|
|earth_base_name|,|1|,|The earth_base_name element identifies the name of the|
|earth_base_name|,|2|,|laboratory, observatory, or other location of a earth-based|
|earth_base_name|,|3|,|instrument.|
|earth_received_time|,|1|,|The earth_received_time element provides the time at which|
|earth_received_time|,|2|,|telemetry was received on earth. This should be|
|earth_received_time|,|3|,|represented in the UTC format. For real time|
|earth_received_time|,|4|,|data, the difference between this time and the|
|earth_received_time|,|5|,|spacecraft_event_time is the signal travel time from the|
|earth_received_time|,|6|,|spacecraft to earth.|
|earth_received_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|edit_mode_id|,|1|,|The edit_mode_id element indicates the amount of data read|
|edit_mode_id|,|2|,|from an imaging instrument's vidicon. '1:1' indicates the|
|edit_mode_id|,|3|,|full-resolution of the vidicon. Example values: (Voyager)|
|edit_mode_id|,|4|,|3:4, 1:2, 1:3, 1:5, and 1:1.|
|edit_routine_name|,|1|,|The edit_routine_name element provides the name of a edit|
|edit_routine_name|,|2|,|routine name that the catalog bulk loading software should|
|edit_routine_name|,|3|,| execute during any validation procedures.|
|effective_time|,|1|,|The effective_time is an alias for start_time used by SFOC-|
|effective_time|,|2|,|MGN ephemeris files to define the time at which the data|
|effective_time|,|3|,|takes effect.|
|electronic_mail_id|,|1|,|The electronic_mail_id element provides an individual's|
|electronic_mail_id|,|2|,|mailbox name on the electronic mail system identified by|
|electronic_mail_id|,|3|,|the electronic_mail_type element (e.g., Telemail).|
|electronic_mail_type|,|1|,|The electronic_mail_type element identifies an electronic|
|electronic_mail_type|,|2|,|mail system by name.|
|electronic_mail_type|,|3|,|Example values:  TELEMAIL, NSI-DECNET.|
|electronics_desc|,|1|,|The electronics_desc element describes the|
|electronics_desc|,|2|,|electronics associated with a given instrument.|
|electronics_id|,|1|,|The electronics_id element identifies the electronics|
|electronics_id|,|2|,|associated with a given instrument.|
|elevation|,|1|,|The elevation element provides the angular elevation of a|
|elevation|,|2|,|point of interest (for example, the center point of an|
|elevation|,|3|,|image of a solar system object taken from a lander or a|
|elevation|,|4|,|rover) above the azimuthal reference plane.|
|elevation|,|5|,|Elevation is measured in a spherical coordinate system.|
|elevation|,|6|,|The zero elevation point lies in the azimuthal reference|
|elevation|,|7|,|plane and positive elevation is measured toward the|
|elevation|,|8|,|positive direction of the principal axis of the spherical|
|elevation|,|9|,|coordinate system.  See azimuth.|
|emission_angle|,|1|,|The emission_angle element provides the value of the angle|
|emission_angle|,|2|,|between the surface normal vector at the intercept point|
|emission_angle|,|3|,|and a vector from the intercept point to the spacecraft.|
|emission_angle|,|4|,|The emission_angle varies from 0 degrees when the|
|emission_angle|,|5|,|spacecraft is viewing the subspacecraft point (nadir|
|emission_angle|,|6|,|viewing) to 90 degrees when the intercept is tangent to the|
|emission_angle|,|7|,|surface of the target body. Thus, higher values of|
|emission_angle|,|8|,|emission_angle indicate more oblique viewing of the target.|
|emission_angle|,|9|,|Values in the range of 90 to 180 degrees are possible for|
|emission_angle|,|10|,|ring data.|
|encoding_type|,|1|,|The encoding_type element indicates the type of compression|
|encoding_type|,|2|,|or encryption used for data storage.|
|ephemeris_latitude_correction|,|1|,| The ephemeris_latitude_correction (VBF85) element provides|
|ephemeris_latitude_correction|,|2|,|the value of the correction applied to the footprint|
|ephemeris_latitude_correction|,|3|,|latitude value by the post-fitting MGMORB phase of the|
|ephemeris_latitude_correction|,|4|,|altimetry and radiometry reduction program.|
|ephemeris_longitude_correction|,|1|,| The ephemeris_longitude_correction (VBF85) element|
|ephemeris_longitude_correction|,|2|,|provides the value of the correction applied to the|
|ephemeris_longitude_correction|,|3|,|footprint longitude value by the post-fitting MGMORB phase|
|ephemeris_longitude_correction|,|4|,|of the altimetry and radiometry reduction program.|
|ephemeris_radius_correction|,|1|,| The ephemeris_radius_correction element provides the value|
|ephemeris_radius_correction|,|2|,|of the correction applied to the length of the|
|ephemeris_radius_correction|,|3|,|alt_spacecraft_position_vector element by the post-fitting|
|ephemeris_radius_correction|,|4|,|MGMORB phase of the altimetry and radiometry reduction|
|ephemeris_radius_correction|,|5|,|program.|
|equatorial_radius|,|1|,|The equatorial_radius element provides the average radius in|
|equatorial_radius|,|2|,|the equatorial plane of the best fit spheroid which|
|equatorial_radius|,|3|,|approximates the target body.|
|event_name|,|1|,|The event_name element identifies an event.  This may be a|
|event_name|,|2|,|spacecraft event, a ground_based event or a system event.|
|event_start_hour|,|1|,|The event_start_hour element provides the date and hour of|
|event_start_hour|,|2|,|the beginning of an event (whether a spacecraft event, a|
|event_start_hour|,|3|,|ground based event or a system event) in the PDS standard|
|event_start_hour|,|4|,|(UTC) format. The values associated with this element are|
|event_start_hour|,|5|,|derived from existing values of  event_start_time and are|
|event_start_hour|,|6|,|used strictly for the PDS catalog performance enhancements.|
|event_type|,|1|,|The event_type element identifies the classification of an|
|event_type|,|2|,|event.|
|event_type|,|3|,|Example values:  MAGNETOPAUSE CROSSING, VOLCANIC ERUPTION,|
|event_type|,|4|,|CLOSEST APPROACH.|
|event_type_desc|,|1|,|The event_type_desc element describes the type of|
|event_type_desc|,|2|,|event identified by the event_type element.|
|expertise_area_desc|,|1|,|The expertise_area_description element describes a|
|expertise_area_desc|,|2|,|particular area of individual expertise.|
|expertise_area_type|,|1|,|The expertise_area_type element identifies an|
|expertise_area_type|,|2|,|individual's area of expertise.|
|expertise_area_type|,|3|,|The corresponding expertise_area_description element|
|expertise_area_type|,|4|,|describes the area of expertise.|
|exposure_duration|,|1|,|The exposure_duration element provides the value of the|
|exposure_duration|,|2|,|time interval between the opening and closing of a camera|
|exposure_duration|,|3|,|shutter.|
|exposure_offset_flag|,|1|,|The exposure_offset_flag element indicates the|
|exposure_offset_flag|,|2|,|(instrument_dependent) mode of the offset state of a|
|exposure_offset_flag|,|3|,|camera.|
|exposure_offset_flag|,|4|,|Offset is a constant value which is added to an|
|exposure_offset_flag|,|5|,|instrument's output signal to increase or decrease the|
|exposure_offset_flag|,|6|,|level of that output.|
|exposure_offset_number|,|1|,|The exposure_offset_number element provides the value of a|
|exposure_offset_number|,|2|,|numerical constant which was added to the exposure duration|
|exposure_offset_number|,|3|,|for a given imaging instrument.|
|feature_name|,|1|,|The feature_name element provides the proper IAU_approved|
|feature_name|,|2|,|name of a feature on a solar system body.|
|feature_name|,|3|,|Example value:  OLYMPUS MONS.|
|feature_type|,|1|,|The feature_type element identifies the type of a|
|feature_type|,|2|,|particular feature, according to IAU standards.|
|feature_type|,|3|,|Example values:  IMPACT CRATER, VOLCANO.|
|feature_type_desc|,|1|,|The feature_type_description element provides the IAU|
|feature_type_desc|,|2|,|standard definition for a particular feature_type.|
|file_name|,|1|,|The file_name element provides the file_name under which|
|file_name|,|2|,|a discrete entity is stored.  To promote portability across|
|file_name|,|3|,|systems the file_name shall exclude directory, path, and|
|file_name|,|4|,|version specification.  The file_name typically identifies|
|file_name|,|5|,|a single component of a data set.|
|file_records|,|1|,|The file_records element indicates the number of physical|
|file_records|,|2|,|file records, including both label records and data|
|file_records|,|3|,|records.|
|file_records|,|300|,|Note:  In the PDS the use of file_records along|
|file_records|,|301|,|with other file-related data elements is fully described in|
|file_records|,|302|,|the Data Preparation Workbook.|
|file_specification_name|,|1|,|The file_specification_name element provides all information|
|file_specification_name|,|2|,| needed to identify a file, including system-specific, full|
|file_specification_name|,|3|,|path information.  See also:  file_name.|
|file_specification_name|,|300|,|Note:  In the PDS, rules for constructing a|
|file_specification_name|,|301|,|file_specification_name are described in the Data|
|file_specification_name|,|302|,|Preparation Workbook.|
|filter_name|,|1|,|The filter_name element provides the commonly-used name of|
|filter_name|,|2|,|the instrument filter through which an image or measurement|
|filter_name|,|3|,|was acquired or which is associated with a given instrument|
|filter_name|,|4|,|mode.|
|filter_name|,|5|,|Example values:  RED, GREEN.|
|filter_name|,|6|,|See also filter_number.|
|filter_number|,|1|,|The filter_number element provides the number of an|
|filter_number|,|2|,|instrument filter through which an image or measurement was|
|filter_number|,|3|,|acquired or which is associated with a given instrument|
|filter_number|,|4|,|mode.|
|filter_number|,|5|,|Note that the filter_number is unique, while the|
|filter_number|,|6|,|filter_name is not.|
|filter_type|,|1|,|The filter_type element identifies the type of a given|
|filter_type|,|2|,|instrument filter.|
|filter_type|,|3|,|Example values:  INTERFERENCE, MESH, BANDPASS, BLOCKING.|
|first_alt_footprint_tdb_time|,|1|,| The first_alt_footprint_tdb_time element provides the|
|first_alt_footprint_tdb_time|,|2|,|value of the spacecraft ephemeris time that represents the|
|first_alt_footprint_tdb_time|,|3|,|first altimeter footprint of this orbit. It is equal to the|
|first_alt_footprint_tdb_time|,|4|,|altimetry_footprint_tdb_time   value in the first record of|
|first_alt_footprint_tdb_time|,|5|,|this orbit's altimetry data file.|
|first_alt_footprint_tdb_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|first_line|,|1|,|The first_line element indicates the line within a source|
|first_line|,|2|,|image that corresponds to the first line in a sub-image.|
|first_line_sample|,|1|,|The first_line_sample element indicates the sample within a|
|first_line_sample|,|2|,|source image that corresponds to the first sample in a|
|first_line_sample|,|3|,|sub-image.|
|first_rad_footprint_tdb_time|,|1|,| The first_rad_footprint_tdb_time element provides the|
|first_rad_footprint_tdb_time|,|2|,|value of the spacecraft ephemeris time of the first|
|first_rad_footprint_tdb_time|,|3|,|radiometer measurement of this orbit. It is equal to the|
|first_rad_footprint_tdb_time|,|4|,|rad_spacecraft_epoch_tdb_time   value in the first record|
|first_rad_footprint_tdb_time|,|5|,|of this orbit's radiometry data file.|
|first_rad_footprint_tdb_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|first_standard_parallel|,|1|,|The first_standard_parallel element  is used in Conic|
|first_standard_parallel|,|2|,|projections.  If a Conic projection has a single standard|
|first_standard_parallel|,|3|,|parallel, then the first_standard_parallel is the point of|
|first_standard_parallel|,|4|,|tangency between the sphere of the planet and the cone of|
|first_standard_parallel|,|5|,|the projection.  If there are two standard parallels|
|first_standard_parallel|,|6|,|(first_standard_parallel, second_standard_parallel), these|
|first_standard_parallel|,|7|,|parallel are the intersection lines  between the sphere of|
|first_standard_parallel|,|8|,|the planet and the cone of the projection.  The map_scale|
|first_standard_parallel|,|9|,|is defined at the standard parallels.|
|flattening|,|1|,|The flattening element provides the value of the geometric|
|flattening|,|2|,|oblateness of a solar system body, defined as the ratio of|
|flattening|,|3|,|the difference between the body's equatorial and polar|
|flattening|,|4|,|radii to the equatorial radii ((a-c) divided by (a)).|
|footprint_number|,|1|,| The footprint_number element provides a signed integer|
|footprint_number|,|2|,|value. The altimetry and radiometry processing program|
|footprint_number|,|3|,|assigns footprint 0 to that observed at nadir at periapsis.|
|footprint_number|,|4|,|The remaining footprints are located along the spacecraft|
|footprint_number|,|5|,|nadir track, with a separation that depends on the doppler|
|footprint_number|,|6|,|resolution of the altimeter at the epoch at which that|
|footprint_number|,|7|,|footprint is observed. Pre-periapsis footprints will be|
|footprint_number|,|8|,|assigned negative numbers, post-periapsis footprints will|
|footprint_number|,|9|,|be assigned positive ones. A loss of several consecutive|
|footprint_number|,|10|,|burst records from the ALT-EDR will result in missing|
|footprint_number|,|11|,|footprint numbers.|
|formal_correlations_group|,|1|,| The formal_correlations_group provides the formal|
|formal_correlations_group|,|2|,|correlations between the derived_planetary_radius and the|
|formal_correlations_group|,|3|,|derived_rms_surface_fresnel_reflect elements, and between|
|formal_correlations_group|,|4|,|the derived_fresnel_reflectivity and the|
|formal_correlations_group|,|5|,|derived_planetary_radius elements, respectively. As the|
|formal_correlations_group|,|6|,|profile fitting algorithm is non-linear, the correlations|
|formal_correlations_group|,|7|,|may not be symmetric.|
|formal_errors_group|,|1|,| The formal_errors_group element provides the value of the|
|formal_errors_group|,|2|,|1-sigma statistical errors expected in the determination of|
|formal_errors_group|,|3|,|the derived_planetary_radius, the|
|formal_errors_group|,|4|,|derived_rms_surface_slope, and the|
|formal_errors_group|,|5|,|derived_fresnel_reflectivity elements, respectively.|
|format|,|1|,|A specified or predetermined arrangement of data within a|
|format|,|2|,|file or on a storage medium.|
|format|,|300|,|Note:  In the PDS, the format element indicates the display|
|format|,|301|,|specification for a collection of data.  It is equivalent|
|format|,|302|,|to the FORTRAN language format specification.  Example|
|format|,|303|,|values:  'Ew.deEXP', A6, I5.|
|format_desc|,|1|,|The format_desc element provides a textual description of|
|format_desc|,|2|,|the format of the subject data.|
|fov_shape_name|,|1|,|The field_of_view_shape_name element identifies the|
|fov_shape_name|,|2|,|geometric shape of the field of view of an instrument.|
|fovs|,|1|,|The fovs (fields-of-view) element indicates the number of|
|fovs|,|2|,|fields of view associated with a single fov shape within a|
|fovs|,|3|,|section of an instrument.|
|frame_duration|,|1|,|The frame_duration element provides the value of the length|
|frame_duration|,|2|,|of time required to measure one frame of data.  The|
|frame_duration|,|3|,|frame_duration is constant within a given instrument cycle,|
|frame_duration|,|4|,|which is identified by the cycle_id element.|
|frame_id|,|1|,|The frame_id element provides an identification for a|
|frame_id|,|2|,|particular instrument measurement frame.  A frame consists|
|frame_id|,|3|,|of a sequence of measurements made over a specified time|
|frame_id|,|4|,|interval, and may include measurements from different|
|frame_id|,|5|,|instrument modes.  These sequences repeat from cycle to|
|frame_id|,|6|,|cycle and sometimes within a cycle.|
|frame_sequence_number|,|1|,|The frame_sequence_number element indicates the location|
|frame_sequence_number|,|2|,|within a cycle at which a specific frame occurs.  Frames are|
|frame_sequence_number|,|3|,|repeated in a specific order within each cycle.|
|frames|,|1|,|The frames element provides the number of frames within a|
|frames|,|2|,|particular cycle, which is identified by the cycle_id|
|frames|,|3|,|element.|
|fts_number|,|1|,|The fts_number element provides the Federal|
|fts_number|,|2|,|Telecommunications System (FTS) telephone number of an|
|fts_number|,|3|,|individual.|
|full_name|,|1|,|The full_name element provides the complete name of an|
|full_name|,|2|,|individual, including titles and suffixes (such as 'Jr.' or|
|full_name|,|3|,|'III').  Example value: DR. J. THOMAS RENFROW.|
|gain_mode_id|,|1|,|The gain_mode_id element identifies the gain|
|gain_mode_id|,|2|,|state of an instrument.|
|gain_mode_id|,|3|,|Gain is a constant value which is multiplied with an|
|gain_mode_id|,|4|,|instrument's output signal to increase or decrease the|
|gain_mode_id|,|5|,|level of that output.|
|gain_modes|,|1|,|The gain_modes element provides the number of gain states of|
|gain_modes|,|2|,|a particular instrument or section of an instrument.|
|granule_sequence_number|,|1|,|The granule_sequence_number element identifies the sequence|
|granule_sequence_number|,|2|,|of data granules within an order item.|
|granule_start|,|1|,|The granule_start element identifies the first or start|
|granule_start|,|2|,|value in a range of granules associated with a particular|
|granule_start|,|3|,|order item.|
|help_id|,|1|,|The help_id element identifies a PDS topic for which help|
|help_id|,|2|,|text is available.|
|help_name|,|1|,|The help_name element provides the key to help text used in|
|help_name|,|2|,|the Inspect Data function.|
|help_text|,|1|,|The help_text element provides the ascii help text used for|
|help_text|,|2|,| online help in the Inspect Data function.|
|horizontal_fov|,|1|,|The horizontal_field_of_view element provides the angular|
|horizontal_fov|,|2|,|measure of the horizontal field of view of an instrument.|
|horizontal_pixel_fov|,|1|,|The horizontal_pixel_field_of_view element provides the|
|horizontal_pixel_fov|,|2|,|angular measure of the horizontal field of view of a single|
|horizontal_pixel_fov|,|3|,|pixel.|
|host_id|,|1|,|The host_id element provides the name or identification of|
|host_id|,|2|,|the particular computer on which the product was generated.|
|image_id|,|1|,|The image_id element is used to identify an image and|
|image_id|,|2|,|typically consists of a sequence of characters representing|
|image_id|,|3|,|1) a routinely occurring measure, such as revolution number,|
|image_id|,|4|,|2) a letter identifying the spacecraft, target, or camera,|
|image_id|,|5|,|and 3) a representation of a count within the measure, such|
|image_id|,|6|,|as picture number within a given revolution.|
|image_id|,|8|,|Example:|
|image_id|,|10|,|Mariner 9 - Levanthal Identifier - (orbit, camera, pic #,|
|image_id|,|12|,|            total # of pics in orbit)|
|image_id|,|14|,|Viking Orbiter - (orbit #, sc, pic # (FSC/16)),|
|image_id|,|16|,|Viking Lander - (sc, camera, mars doy, diode (filter),|
|image_id|,|18|,|                 pic # for that day),|
|image_id|,|20|,|Voyager - (pic # for encounter, FDS for cruise)|
|image_key_id|,|1|,|The image_key_id element provides a shorthand|
|image_key_id|,|2|,|identifier for an image which is unique for a given|
|image_key_id|,|3|,|spacecraft. The image_key_id and spacecraft_id together|
|image_key_id|,|4|,|provide a unique identifier for any image.  The|
|image_key_id|,|5|,|contents of image_key_id may be any common identifier|
|image_key_id|,|6|,|of an image, but it is suggested that one of the|
|image_key_id|,|7|,|following be used:  1) image_id (pic_no), 2)|
|image_key_id|,|8|,|image_number (FSC), 3) spacecraft_clock_count (FDS).|
|image_key_id|,|300|,|Note:   Guaranteeing uniqueness may require|
|image_key_id|,|301|,|modification of the selected common identifier and is|
|image_key_id|,|302|,|the responsibility of the  data supplier. For example,|
|image_key_id|,|303|,|in the case where an image was retransmitted, an|
|image_key_id|,|304|,|alphabetic character could be appended. When unique|
|image_key_id|,|305|,|identifiers are not supplied, PDS will assign a simple|
|image_key_id|,|306|,|numeric identifier as the image_key_id. This identifier|
|image_key_id|,|307|,|will range from 1 to the number of images associated|
|image_key_id|,|308|,|with the specified spacecraft.|
|image_number|,|1|,|The image_number element is a value obtained from the|
|image_number|,|2|,|spacecraft_clock_start_count. The image number is another|
|image_number|,|3|,|commonly used identifier for an image.|
|image_number|,|5|,|Example:|
|image_number|,|7|,|Viking - Frame Start Count (FSC)|
|image_number|,|9|,|Voyager - Flight Data Subsystem (FDS) clock count|
|image_number|,|11|,|          (integer 7 digit)|
|image_observation_type|,|1|,|The image_observation_type element identifies the type or|
|image_observation_type|,|2|,|purpose of an observation that may be associated with an|
|image_observation_type|,|3|,|image. Image observation types include limb, black sky,|
|image_observation_type|,|4|,|spacecraft calibration, or other image attribute that may be|
|image_observation_type|,|5|,|used for identification. Observation types should  not|
|image_observation_type|,|6|,|include features, regions, or standard target names.|
|image_time|,|1|,|The image_time element provides the spacecraft event time at|
|image_time|,|2|,|the time of frame acquisition. This should be represented in|
|image_time|,|3|,|UTC format.|
|image_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|important_instrument_parms|,|1|,|The important_instrument_parameters element provides the|
|important_instrument_parms|,|2|,|number of instrument parameters which are required to derive|
|important_instrument_parms|,|3|,|a particular data set parameter.  This value depends partly|
|important_instrument_parms|,|4|,|on the particular characteristics of the instruments|
|important_instrument_parms|,|5|,|providing the instrument parameters.  For example, in the|
|important_instrument_parms|,|6|,|case of Voyager instruments, the data set parameter PLASMA|
|important_instrument_parms|,|7|,|BETA may be derived from the following set of instrument|
|important_instrument_parms|,|8|,|parameters:  ELECTRON RATE, ION RATE, MAGNETIC FIELD|
|important_instrument_parms|,|9|,|COMPONENT.  In that case, the value of the|
|important_instrument_parms|,|10|,|important_instrument_parameters element is 3.|
|incidence_angle|,|1|,|The incidence_angle element provides a measure of the|
|incidence_angle|,|2|,|lighting condition at the intercept point.  Incidence angle|
|incidence_angle|,|3|,|is the angle between the local vertical at the intercept|
|incidence_angle|,|4|,|point (surface) and a vector from the intercept point to|
|incidence_angle|,|5|,|the sun.|
|incidence_angle|,|6|,|The incidence_angle varies from 0 degrees when the|
|incidence_angle|,|7|,|intercept point coincides with the sub_solar point to 90|
|incidence_angle|,|8|,|degrees when the intercept point is at the terminator|
|incidence_angle|,|9|,|(i.e., in the shadowed or dark portion of the target body).|
|incidence_angle|,|10|,| Thus, higher values of incidence_angle indicate the|
|incidence_angle|,|11|,|existence of a greater number of surface shadows.|
|incidence_angle*|,|1|,|The incidence_angle* element provides the value of the|
|incidence_angle*|,|2|,|angle between the local vertical and the spacecraft|
|incidence_angle*|,|3|,|direction, measured at the center of the radiometer|
|incidence_angle*|,|4|,|footprint at rad_spacecraft_epoch_event_time.|
|incidence_angle*|,|300|,|Note:  Incidence_angle* is marked with an asterix because|
|incidence_angle*|,|301|,|it duplicates an already-existing element in the common|
|incidence_angle*|,|302|,|list of data element names.  This situation will be|
|incidence_angle*|,|303|,|rectified in the next edition of the PSDD.|
|initiating_node_id|,|1|,|The initiating_node_id element identifies the node from|
|initiating_node_id|,|2|,|which a user placed an order.|
|instrument_calibration_desc|,|1|,|The instrument_calibration_description element explains the|
|instrument_calibration_desc|,|2|,|method of calibrating an instrument and identifies|
|instrument_calibration_desc|,|3|,|reference documents which explain in detail the calibration|
|instrument_calibration_desc|,|4|,|of the instrument.|
|instrument_calibration_desc|,|5|,|As an example, this element would explain whether the|
|instrument_calibration_desc|,|6|,|calibration was time_independent (i.e., a single algorithm|
|instrument_calibration_desc|,|7|,|was used) or time_dependent and whether the calibration was|
|instrument_calibration_desc|,|8|,|performed in_flight or in a laboratory.|
|instrument_desc|,|1|,|The instrument_description element describes a given|
|instrument_desc|,|2|,|instrument.|
|instrument_height|,|1|,|The instrument_height element provides the physical height|
|instrument_height|,|2|,|of an instrument.|
|instrument_host_id|,|1|,|The instrument_host_id element provides a unique identifier|
|instrument_host_id|,|2|,|for the host on which an instrument is based.  This host can|
|instrument_host_id|,|3|,|be either a spacecraft or an earth base.  Thus, the|
|instrument_host_id|,|4|,|instrument_host_id element can contain values which are|
|instrument_host_id|,|5|,|either spacecraft_id values or earth_base_id values.|
|instrument_host_id_or_name|,|1|,|The instrument_host_id_or_name element provides either an|
|instrument_host_id_or_name|,|2|,|instrument_host_id or an instrument_host_name.  That is,|
|instrument_host_id_or_name|,|3|,|this element may have values which are either the|
|instrument_host_id_or_name|,|4|,|identification of an instrument host (the|
|instrument_host_id_or_name|,|5|,|instrument_host_id) or the name of an instrument host (the|
|instrument_host_id_or_name|,|6|,|instrument_host_name).|
|instrument_host_name|,|1|,|The instrument_host_name element provides the full name of|
|instrument_host_name|,|2|,|the host on which an instrument is based.  This host can be|
|instrument_host_name|,|3|,|either a spacecraft or an earth base.  Thus, the|
|instrument_host_name|,|4|,|instrument_host_name element can contain values which are|
|instrument_host_name|,|5|,|either spacecraft_name values or earth_base_name values.|
|instrument_host_type|,|1|,|The instrument_host_type element provides the type of host|
|instrument_host_type|,|2|,|on which an instrument is based.  For example, if the|
|instrument_host_type|,|3|,|instrument is located on a spacecraft, the|
|instrument_host_type|,|4|,|instrument_host_type element would have the value|
|instrument_host_type|,|5|,|SPACECRAFT.|
|instrument_id|,|1|,|The instrument_identification element provides an|
|instrument_id|,|2|,|abbreviated name or acronym which identifies an instrument.|
|instrument_id|,|3|,|Note that the instrument_identification is not a unique|
|instrument_id|,|4|,|identifier for a given instrument.  Note also that the|
|instrument_id|,|5|,|associated instrument_name element provides the full name|
|instrument_id|,|6|,|of the instrument.|
|instrument_id|,|7|,|Example values:  IRTM (for Viking Infrared Thermal Mapper),|
|instrument_id|,|8|,|PWS (for plasma wave spectrometer).|
|instrument_id_or_name|,|1|,|The instrument_id_or_name element provides either an|
|instrument_id_or_name|,|2|,|instrument_id or an instrument_name.  That is, this element|
|instrument_id_or_name|,|3|,|may have values which are either the identification of an|
|instrument_id_or_name|,|4|,|instrument (the instrument_id) or the name of an instrument|
|instrument_id_or_name|,|5|,|(the instrument_name).|
|instrument_length|,|1|,|The instrument_length element provides the physical length|
|instrument_length|,|2|,|of an instrument.|
|instrument_manufacturer_name|,|1|,|The instrument_manufacturer_name element identifies the|
|instrument_manufacturer_name|,|2|,|manufacturer of an instrument.|
|instrument_mass|,|1|,|The instrument_mass element provides the mass of an|
|instrument_mass|,|2|,|instrument.|
|instrument_mode_desc|,|1|,|The instrument_mode_description element describes the|
|instrument_mode_desc|,|2|,|instrument mode which is identified by the|
|instrument_mode_desc|,|3|,|instrument_mode_id element.|
|instrument_mode_id|,|1|,|The instrument_mode_identification element provides an|
|instrument_mode_id|,|2|,|instrument-dependent designation of operating mode.  This|
|instrument_mode_id|,|3|,|may be simply a number, letter or code, or a word such as|
|instrument_mode_id|,|4|,|`normal,' `full resolution,' `near encounter,' or|
|instrument_mode_id|,|5|,|`fixed grating.'|
|instrument_mounting_desc|,|1|,|The instrument_mounting_description element describes the|
|instrument_mounting_desc|,|2|,|mounting of an instrument (on a platform on spacecraft or|
|instrument_mounting_desc|,|3|,|a mounting at a lab) and the orientation of the|
|instrument_mounting_desc|,|4|,|instrument with respect to the platform.|
|instrument_name|,|1|,|The instrument_name element provides the full name of an|
|instrument_name|,|2|,|instrument.|
|instrument_name|,|3|,|Note that the associated instrument_identification element|
|instrument_name|,|4|,|provides an abbreviated name or acronym for the instrument.|
|instrument_name|,|5|,|Example values:  FLUXGATE MAGNETOMETER, NEAR_INFRARED|
|instrument_name|,|6|,|MAPPING SPECTROMETER.|
|instrument_parameter_name|,|1|,|The instrument_parameter_name element provides the name of|
|instrument_parameter_name|,|2|,|the data parameter which was measured by an instrument.|
|instrument_parameter_name|,|3|,|As an example, the instrument_parameter_name value could be|
|instrument_parameter_name|,|4|,|ELECTRIC FIELD COMPONENT.  It is intended that the|
|instrument_parameter_name|,|5|,|instrument_parameter_name element provide the name of the|
|instrument_parameter_name|,|6|,|rawest measured value which has some physical significance.|
|instrument_parameter_name|,|7|,| Thus, for example, while the detector of an instrument may|
|instrument_parameter_name|,|8|,|actually record voltage differences, the electric field|
|instrument_parameter_name|,|9|,|component which is proportional to those differences is|
|instrument_parameter_name|,|10|,|considered to be the instrument parameter.|
|instrument_parameter_name|,|11|,|Note that the associated|
|instrument_parameter_name|,|12|,|dataset_or_instrument_parameter_description element|
|instrument_parameter_name|,|13|,|describes the measured parameter.|
|instrument_parameter_ranges|,|1|,|The instrument_parameter_ranges element provides the number|
|instrument_parameter_ranges|,|2|,|of instrument parameter ranges for a given magnetometer|
|instrument_parameter_ranges|,|3|,|detector. The magnetometer can measure in one of these|
|instrument_parameter_ranges|,|4|,|ranges at a time. The actual range (minimum and maximum|
|instrument_parameter_ranges|,|5|,|values) varies with the quantization of the instrument,|
|instrument_parameter_ranges|,|6|,|which is expressed in the quantization_resolution element.|
|instrument_parameter_unit|,|1|,|The instrument_parameter_unit element specifies the unit of|
|instrument_parameter_unit|,|2|,|measure of associated instrument parameters.|
|instrument_power_consumption|,|1|,|The instrument_power_consumption element provides power|
|instrument_power_consumption|,|2|,|consumption information for an instrument.|
|instrument_power_consumption|,|3|,|Note that instrument_power_consumption may vary with|
|instrument_power_consumption|,|4|,|different modes of instrument operation.|
|instrument_serial_number|,|1|,|The instrument serial number element provides the|
|instrument_serial_number|,|2|,|manufacturer's serial number assigned to an instrument.|
|instrument_serial_number|,|3|,|This number may be used to uniquely identify a particular|
|instrument_serial_number|,|4|,|instrument for tracing its components or determining its|
|instrument_serial_number|,|5|,|calibration history, for example.|
|instrument_type|,|1|,|The instrument_type element identifies the type of an|
|instrument_type|,|2|,|instrument.|
|instrument_type|,|3|,|Example values:  POLARIMETER, RADIOMETER, REFLECTANCE|
|instrument_type|,|4|,|SPECTROMETER, VIDICON CAMERA.|
|instrument_width|,|1|,|The instrument_width element provides the physical width of|
|instrument_width|,|2|,|an instrument.|
|interchange_format|,|1|,|The interchange_format element represent the manner in|
|interchange_format|,|2|,|which data items are stored.  Example values: BINARY,|
|interchange_format|,|3|,|ASCII.|
|invalid|,|1|,|The INVALID element supplies the value used when the|
|invalid|,|2|,|received data were out of the legitimate range of values.|
|items|,|1|,|The items element defines the number of multiple, identical|
|items|,|2|,|occurrences of an object.|
|journal_name|,|1|,|The journal_name element identifies, where applicable, the|
|journal_name|,|2|,|published work (e.g., journal or report) which contains a|
|journal_name|,|3|,|reference document.|
|jpl_press_release_id|,|1|,|This element describes the JPL press release id for a data|
|jpl_press_release_id|,|2|,|product associated with the given data product.|
|keyword_default_value|,|1|,|The keyword_default_value element is used to initialize a|
|keyword_default_value|,|2|,|template keyword value to a default value during|
|keyword_default_value|,|3|,|construction of templates.  When filling out template, the|
|keyword_default_value|,|4|,|data supplier provides a value for all keywords except|
|keyword_default_value|,|5|,|those which have a default value.|
|keyword_value_help_text|,|1|,|The keyword_value_help_text element provides text which|
|keyword_value_help_text|,|2|,|describes the information required from the data supplier|
|keyword_value_help_text|,|3|,|to assign a value to a template keyword.|
|label_records|,|1|,|The label_records element indicates the number of physical|
|label_records|,|2|,|file records that contain only label information.   The|
|label_records|,|3|,|number of data records in a file is determined by|
|label_records|,|4|,|subtracting the value of label_records from the value of|
|label_records|,|5|,|file_records.|
|label_records|,|300|,|Note:  In the PDS, the use of label_records along|
|label_records|,|301|,|with other file-related data elements is fully|
|label_records|,|302|,|described in the Data Preparation Workbook.|
|last_alt_footprint_tdb_time|,|1|,| The last_alt_footprint_tdb_time element provides the value|
|last_alt_footprint_tdb_time|,|2|,|of the spacecraft ephemeris time that represents the last|
|last_alt_footprint_tdb_time|,|3|,|altimeter footprint of this orbit. It is equal to the|
|last_alt_footprint_tdb_time|,|4|,|altimetry_footprint_tdb_time   value in the last record of|
|last_alt_footprint_tdb_time|,|5|,|this orbit's altimetry data file.|
|last_alt_footprint_tdb_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|last_name|,|1|,|The last_name element provides the last name (surname) of an|
|last_name|,|2|,|individual.|
|last_rad_footprint_tdb_time|,|1|,| The last_rad_footprint_tdb_time element provides the value|
|last_rad_footprint_tdb_time|,|2|,|of the spacecraft ephemeris time of the last radiometer|
|last_rad_footprint_tdb_time|,|3|,|measurement of this orbit. It is equal to the|
|last_rad_footprint_tdb_time|,|4|,|rad_spacecraft_epoch_tdb_time value in the last record of|
|last_rad_footprint_tdb_time|,|5|,|this orbit's radiometry data file.|
|last_rad_footprint_tdb_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|latitude|,|1|,|The latitude element provides the value, in a spherical|
|latitude|,|2|,|coordinate system, of the angular distance from the plane|
|latitude|,|3|,|orthogonal to the axis of symmetry.|
|latitude|,|300|,|Note:  The PDS standard for latitude on planets and|
|latitude|,|301|,|satellites is the Cartographic latitude, defined for a|
|latitude|,|302|,|vector from the body center-of-figure to the surface.|
|latitude|,|303|,|Certain exceptions apply.  See 'Cartographic Standards' in|
|latitude|,|304|,|the PDS Data Preparation Workbook.|
|launch_date|,|1|,|The launch_date element identifies the date of launch of a|
|launch_date|,|2|,|spacecraft or a spacecraft_carrying vehicle.|
|launch_date|,|200|,|Formation rule:  YYYY-MM-DD|
|light_flood_state_flag|,|1|,|The light_flood_state_flag element indicates the mode (on|
|light_flood_state_flag|,|2|,|or off) of light flooding for a camera.|
|limb_angle|,|1|,|The limb_angle element provides the value of the angle|
|limb_angle|,|2|,|between the center of an instrument's field of view and the|
|limb_angle|,|3|,|nearest point on the lit limb of the target body.|
|limb_angle|,|4|,|Limb_angle values are positive off_planet and negative|
|limb_angle|,|5|,|on_planet.|
|line_prefix_bytes|,|1|,|The line_prefix_bytes element indicates the number of|
|line_prefix_bytes|,|2|,|non-image bytes at the beginning of each line. The value|
|line_prefix_bytes|,|3|,|must represent an integral number of bytes.|
|line_prefix_structure|,|1|,|The line_prefix_structure element indicates a pointer to a|
|line_prefix_structure|,|2|,|file containing a definition of the structure of the|
|line_prefix_structure|,|3|,|line prefix bytes.|
|line_prefix_structure|,|300|,|Note:  In ODL convention the circumflex|
|line_prefix_structure|,|301|,|(^) indicates a pointer, therefore the circumflex must|
|line_prefix_structure|,|302|,|precede the data element name to indicate that it is a|
|line_prefix_structure|,|303|,|pointer to a file.  Example: ^LINE_PREFIX_STRUCTURE =|
|line_prefix_structure|,|304|,|'myfile.fmt'.|
|line_samples|,|1|,|The line_samples element indicates the total number of data|
|line_samples|,|2|,|instances along the horizontal axis of an image.|
|line_suffix_bytes|,|1|,|The line_suffix_bytes element indicates the number of|
|line_suffix_bytes|,|2|,|non-image bytes at the end of each line. This value must be|
|line_suffix_bytes|,|3|,|an integral number of bytes.|
|line_suffix_structure|,|1|,|The line_suffix_structure element indicates a pointer to a|
|line_suffix_structure|,|2|,|file containing a definition of the structure of the|
|line_suffix_structure|,|3|,|line suffix bytes.|
|line_suffix_structure|,|300|,|Note:  In ODL convention the circumflex|
|line_suffix_structure|,|301|,|(^) indicates a pointer, therefore the circumflex must|
|line_suffix_structure|,|302|,|precede the data element name to indicate that it is a|
|line_suffix_structure|,|303|,|pointer to a file.  Example: ^LINE_SUFFIX_STRUCTURE =|
|line_suffix_structure|,|304|,|'myfile.fmt'.|
|lines|,|1|,|The lines element indicates the total number of data|
|lines|,|2|,|instances along the vertical axis of an image.|
|lines|,|300|,|Note:  In PDS label convention, the number of lines is|
|lines|,|301|,|stored in a 32-bit integer field.  The minimum value of 0|
|lines|,|302|,|indicates no data received.|
|local_hour_angle|,|1|,|The local_hour_angle element provides a measure of the|
|local_hour_angle|,|2|,|instantaneous apparent sun position at the subspacecraft|
|local_hour_angle|,|3|,|point.  The local_hour_angle is the angle between the|
|local_hour_angle|,|4|,|extension of the vector from the Sun to the target body and|
|local_hour_angle|,|5|,|the vector projection on the target body's ecliptic plane|
|local_hour_angle|,|6|,|of a vector from the target body's planetocentric center to|
|local_hour_angle|,|7|,|the observer (usually, the spacecraft).|
|local_hour_angle|,|8|,|This angle is measured in a counterclockwise direction when|
|local_hour_angle|,|9|,|viewed from north of the ecliptic plane.  It may be|
|local_hour_angle|,|10|,|converted from an angle in degrees to a local time, using|
|local_hour_angle|,|11|,|the conversion of 15 degrees per hour, for those planets|
|local_hour_angle|,|12|,|for which the rotational direction corresponds with the|
|local_hour_angle|,|13|,|direction of measure of the angle.|
|local_time|,|1|,|The local_time element provides the local time of day at|
|local_time|,|2|,|the center of the field of view of an instrument, measured|
|local_time|,|3|,|in local hours from midnight.|
|local_time|,|4|,|A local hour is defined as one twenty_fourth of a local|
|local_time|,|5|,|solar day.|
|longitude|,|1|,|The longitude element provides the value, in a spherical|
|longitude|,|2|,|coordinate system, of the angular distance from a standard|
|longitude|,|3|,|origin line, measured in the plane orthogonal to the axis of|
|longitude|,|4|,|symmetry.|
|longitude|,|300|,|Note:  The PDS standard for longitude on planets and|
|longitude|,|301|,|satellites is the Cartographic longitude, defined for a|
|longitude|,|302|,|vector from the body center-of-figure to the surface.|
|longitude|,|303|,|For a full description of the standard, please refer to the|
|longitude|,|304|,|cartographic standards section in the PDS Data Preparation|
|longitude|,|305|,|Workbook.|
|magnetic_moment|,|1|,|The magnetic_moment element provides the value of the|
|magnetic_moment|,|2|,|magnetic moment of a target body.|
|mailing_address_line|,|1|,|The mailing_address_line element provides one line|
|mailing_address_line|,|2|,|of the mailing address of an individual or institution.|
|mailing_address_line|,|3|,|The ordering of the mailing address lines is provided by|
|mailing_address_line|,|4|,|the associated tuple_sequence_number.|
|mandatory_column|,|1|,|The mandatory_column element denotes whether an attribute|
|mandatory_column|,|2|,|may be set to a null value.  Example:  Y or N|
|map_desc|,|1|,|The map_description element describes the contents and|
|map_desc|,|2|,|processing history of a given map.|
|map_name|,|1|,|The map_name element provides the name assigned to a map,|
|map_name|,|2|,|and typically corresponds to the name of a prominent|
|map_name|,|3|,|feature which appears on the map.|
|map_name|,|501|,|Note: This element is also used within SFOC as a unique|
|map_name|,|502|,|identifier for decommutation maps.|
|map_number|,|1|,|The map_number element provides a numeric identifier for a|
|map_number|,|2|,|given map.|
|map_projection_desc|,|1|,|The map_projection_description element describes the|
|map_projection_desc|,|2|,|map_projection_type unambiguously.  It shall contain the|
|map_projection_desc|,|3|,|mathematical expressions (it may even contain the source|
|map_projection_desc|,|4|,|code or pseudo code, with comments) and any assumptions|
|map_projection_desc|,|5|,|(e.g. the  planet is assumed spherical).  Additionally it|
|map_projection_desc|,|6|,|shall describe the  planet eccentricity, the treatment of|
|map_projection_desc|,|7|,|the a_axis_radius, b_axis_radius,  and c_axis_radius when|
|map_projection_desc|,|8|,|the projection was created, and where the  map_scale (or|
|map_projection_desc|,|9|,|map_resolution) is defined.|
|map_projection_rotation|,|1|,|The map_projection_rotation element provides the clockwise|
|map_projection_rotation|,|2|,|rotation, in degrees, of the line and sample coordinates|
|map_projection_rotation|,|3|,|with respect to the map projection origin|
|map_projection_rotation|,|4|,|(x_axis_projection_offset, y_axis_projection_offset). This|
|map_projection_rotation|,|5|,|parameter is used to indicate where 'up' is in the|
|map_projection_rotation|,|6|,|projection.  For example, in a polar stereographic|
|map_projection_rotation|,|7|,|projection does the zero meridian go center to bottom,|
|map_projection_rotation|,|8|,|center to top, center to left, or center to right?  The|
|map_projection_rotation|,|9|,|polar projection is defined such that the zero meridian|
|map_projection_rotation|,|10|,|goes center to bottom. However, by rotating the map|
|map_projection_rotation|,|11|,|projection, the zero meridian can go in any direction.|
|map_projection_rotation|,|12|,|Note that 180 degrees is at the top of the North Pole and 0|
|map_projection_rotation|,|13|,|degrees is at the top of the South Pole.  For example, if 0|
|map_projection_rotation|,|14|,|degrees  is at the top of the North Pole than the|
|map_projection_rotation|,|15|,|map_projection_rotation would be 180 degrees.|
|map_projection_type|,|1|,|The map_projection_type element identifies the type of|
|map_projection_type|,|2|,|projection characteristic of a given map.|
|map_projection_type|,|3|,|Example value:  ORTHOGRAPHIC.|
|map_resolution|,|1|,|The map_resolution element identifies the scale of a given|
|map_resolution|,|2|,|map.  Please refer to the definition for map_scale for a|
|map_resolution|,|3|,|more complete definition.  Note that map_resolution and|
|map_resolution|,|4|,|map_scale both define the scale of a map except that they|
|map_resolution|,|5|,|are expressed in different units:  map_resolution is in|
|map_resolution|,|6|,|PIXEL/DEGREE and map_scale is in KM/PIXEL.|
|map_scale|,|1|,|The map_scale element identifies the scale of a given map.|
|map_scale|,|2|,|The scale is defined as the ratio of the actual distance|
|map_scale|,|3|,|between two points on the surface of the target body to the|
|map_scale|,|4|,|distance between the corresponding points on the map.|
|map_scale|,|5|,|The map_scale references the scale of a map at a certain|
|map_scale|,|6|,|reference point or line.  Certain map projections|
|map_scale|,|7|,|vary in scale throughout the map.  For example, in a|
|map_scale|,|8|,|Mercator projection, the map_scale refers to the scale of|
|map_scale|,|9|,|the map at the equator.  For Conic projections, the|
|map_scale|,|10|,|map_scale refers to the scale at the standard parallels.|
|map_scale|,|11|,|For an Orthographic point, the map_scale refers to the scale|
|map_scale|,|12|,|at the center latitude and longitude.  The relationship|
|map_scale|,|13|,|between map_scale and the map_resolution element is that|
|map_scale|,|14|,|they both define the scale of a given map, except they are|
|map_scale|,|15|,|expressed in different units:  map_scale is in KM/PIXEL|
|map_scale|,|16|,|and map_resolution is in PIXEL/DEGREE.  Also note that one|
|map_scale|,|17|,|is the inverse of the other and that kilometers and degrees|
|map_scale|,|18|,|can be related given the radius of the planet:  1 degree =|
|map_scale|,|19|,|(2 * RADIUS * PI) / 360 kilometers.|
|map_sequence_number|,|1|,|The map_sequence_number element identiies the sequence|
|map_sequence_number|,|2|,|number of a particular series of decommutation maps.|
|map_series_id|,|1|,|The map_series_identification element identifies a map|
|map_series_id|,|2|,|series (as specified by the agency which issued the map).|
|map_sheet_number|,|1|,|The map_sheet_number element provides the sequence number|
|map_sheet_number|,|2|,|of a map which comprises multiple sheets.|
|map_type|,|1|,|The map_type element identifies the general type of|
|map_type|,|2|,|information depicted on a given map.|
|map_type|,|3|,|Example values:  GEOLOGIC, TOPOGRAPHIC, SHADED_RELIEF.|
|mapping_start_time|,|1|,|The mapping_start_time element is an alias for start_time|
|mapping_start_time|,|2|,|used exclusively by SFOC-MGN ephemeris files.|
|mapping_stop_time|,|1|,|The mapping_stop_time element is an alias for stop_time used|
|mapping_stop_time|,|2|,|exclusively by SFOC-MGN ephemeris files.|
|mass|,|1|,|The mass element provides the estimated mass of a target|
|mass|,|2|,|body.|
|mass_density|,|1|,|The mass_density element provides the bulk density (mass|
|mass_density|,|2|,|per unit volume) of a target body.  Bulk density is defined|
|mass_density|,|3|,|as the ratio of total mass to total volume.|
|maximum|,|1|,|The maximum element indicates the largest value occurring|
|maximum|,|2|,|in a given instance of the data object.|
|maximum_brightness_temperature|,|1|,|The maximum_brightness_temperature element provides the|
|maximum_brightness_temperature|,|2|,|maximum brightness temperature value measured within a given|
|maximum_brightness_temperature|,|3|,| set of data or a given sequence.|
|maximum_brightness_temperature|,|4|,|Brightness temperature is the temperature of aideal|
|maximum_brightness_temperature|,|5|,|blackbody whose radiant energy in a particular wavelength|
|maximum_brightness_temperature|,|6|,|range is the same as that of an observed object or feature.|
|maximum_channel_id|,|1|,|The maximum_channel_id element provides an identification of|
|maximum_channel_id|,|2|,|the highest energy channel from which PLS instrument data is|
|maximum_channel_id|,|3|,|telemetered to Earth while the instrument is operating in a|
|maximum_channel_id|,|4|,|particular mode in a given frame.  Each mode consists of a|
|maximum_channel_id|,|5|,|specific number of energy/charge channels which sequentially|
|maximum_channel_id|,|6|,|measure current, but information from all measured channels|
|maximum_channel_id|,|7|,|may not be telemetered to Earth.|
|maximum_column_value|,|1|,|The maximum_column_value element provides the maximum real|
|maximum_column_value|,|2|,|value currently allowed by the PDS catalog for a given table|
|maximum_column_value|,|3|,|element.  This value is updated when new limits are|
|maximum_column_value|,|4|,|discovered.  Note that these elements are unique to a table|
|maximum_column_value|,|5|,|and may have different values depending on which table the|
|maximum_column_value|,|6|,|element is associated with.|
|maximum_emission_angle|,|1|,|The maximum_emission_angle element provides the maximum|
|maximum_emission_angle|,|2|,|emission angle value.  See emission_angle.|
|maximum_incidence_angle|,|1|,|The maximum_incidence_angle element provides the maximum|
|maximum_incidence_angle|,|2|,|incidence angle value.  See incidence_angle.|
|maximum_instrument_exposr_dur|,|1|,|The maximum_instrument_exposure_duration element provides|
|maximum_instrument_exposr_dur|,|2|,|the maximum possible exposure time for the instrument mode|
|maximum_instrument_exposr_dur|,|3|,|identified by the instrument_mode_identification element.|
|maximum_instrument_exposr_dur|,|4|,|See instrument_exposure_duration.|
|maximum_instrument_parameter|,|1|,|The maximum_instrument_parameter element provides an|
|maximum_instrument_parameter|,|2|,|instrument's maximum usefully detectable signal level for|
|maximum_instrument_parameter|,|3|,|a given instrument parameter.  This value indicates the|
|maximum_instrument_parameter|,|4|,|physical value corresponding to the maximum digital output|
|maximum_instrument_parameter|,|5|,|of an instrument.|
|maximum_instrument_parameter|,|6|,|by the instrument_parameter_name element.|
|maximum_latitude|,|1|,|The maximum_latitude element specifies the northernmost|
|maximum_latitude|,|2|,|latitude of a spatial area, such as a map, mosaic, bin,|
|maximum_latitude|,|3|,|feature, or region.  See latitude.|
|maximum_limb_angle|,|1|,|The maximum_limb_angle element provides the maximum value|
|maximum_limb_angle|,|2|,|of the limb angle within a given set of data.  See|
|maximum_limb_angle|,|3|,|limb_angle.|
|maximum_local_time|,|1|,|The maximum_local_time element provides the maximum|
|maximum_local_time|,|2|,|local time of day on the target body, measured in hours|
|maximum_local_time|,|3|,|from local midnight.|
|maximum_longitude|,|1|,|The maximum_longitude element specifies the westernmost|
|maximum_longitude|,|2|,|(left_most) longitude of a spatial area, such as a map,|
|maximum_longitude|,|3|,|mosaic, bin, feature, or region.  See longitude.|
|maximum_longitude|,|300|,|Note:  For areas that cross the prime meridian, the maximum|
|maximum_longitude|,|301|,|longitude will have an ordinal value less than the minimum|
|maximum_longitude|,|302|,|value.|
|maximum_parameter|,|1|,|The maximum_parameter element specifies the maximum|
|maximum_parameter|,|2|,|allowable value for a parameter input to a given data|
|maximum_parameter|,|3|,|processing program.|
|maximum_parameter|,|4|,|The parameter constrained by this value is identified by|
|maximum_parameter|,|5|,|the parameter_name element.|
|maximum_phase_angle|,|1|,|The maximum_phase_angle element provides the maximum phase|
|maximum_phase_angle|,|2|,|angle value.  See phase_angle.|
|maximum_sampling_parameter|,|1|,|The maximum_sampling_parameter element identifies the|
|maximum_sampling_parameter|,|2|,|maximum value at which a given data item was sampled.|
|maximum_sampling_parameter|,|3|,|For example, a spectrum that was measured in the 0.4 to 3.5|
|maximum_sampling_parameter|,|4|,|micrometer spectral region would have a|
|maximum_sampling_parameter|,|5|,|maximum_sampling_parameter value of 3.5.|
|maximum_sampling_parameter|,|6|,|The sampling parameter constrained by this value is|
|maximum_sampling_parameter|,|7|,|identified by the sampling_parameter_name element.  Note|
|maximum_sampling_parameter|,|8|,|that the unit of measure for the sampling parameter is|
|maximum_sampling_parameter|,|9|,|provided by the unit element.|
|maximum_slant_distance|,|1|,|The maximum_slant_distance element provides the maximum|
|maximum_slant_distance|,|2|,|slant distance value.  See slant_distance.|
|maximum_solar_band_albedo|,|1|,|The maximum_solar_band_albedo element provides the maximum|
|maximum_solar_band_albedo|,|2|,|solar band albedo value measured within a given set of data|
|maximum_solar_band_albedo|,|3|,|or a given sequence.|
|maximum_spectral_contrast|,|1|,|The maximum_spectral_contrast element provides the maximum|
|maximum_spectral_contrast|,|2|,|value of spectral contrast within a given set of data.  See|
|maximum_spectral_contrast|,|3|,|spectral_contrast_range.|
|maximum_surface_pressure|,|1|,|The maximum_surface_pressure element provides the maximum|
|maximum_surface_pressure|,|2|,|surface pressure value for the atmosphere of a given body.|
|maximum_surface_temperature|,|1|,|The maximum_surface_temperature element provides the maximum|
|maximum_surface_temperature|,|2|,|equatorial surface temperature value for a given body during|
|maximum_surface_temperature|,|3|,|its year.|
|maximum_wavelength|,|1|,|The maximum_wavelength element identifies the maximum|
|maximum_wavelength|,|2|,|wavelength to which an instrument detector or filter is|
|maximum_wavelength|,|3|,|sensitive.|
|mean_orbital_radius|,|1|,|The mean_orbital_radius element provides the mean distance|
|mean_orbital_radius|,|2|,|between the center of a solar system object and the center|
|mean_orbital_radius|,|3|,|of its primary (e.g., the primary body for a planet is the|
|mean_orbital_radius|,|4|,|Sun, while the primary body for a satellite is the planet|
|mean_orbital_radius|,|5|,|about which it orbits).|
|mean_orbital_radius|,|6|,|As the radius of an elliptical orbit varies with time, the|
|mean_orbital_radius|,|7|,|notion of mean radius allows for general, time-independent|
|mean_orbital_radius|,|8|,|comparisons between the sizes of different bodies' orbits.|
|mean_radius|,|1|,|The mean_radius element is measured or derived using a|
|mean_radius|,|2|,|variety of methods. It provides, approximately, an average|
|mean_radius|,|3|,|of the equatorial and polar radii of the best fit spheroid|
|mean_radius|,|4|,|(for planets) or ellipsoid (for satellites).|
|mean_solar_day|,|1|,|The mean_solar_day element provides the average interval|
|mean_solar_day|,|2|,|required for successive transits of the Sun.  This is|
|mean_solar_day|,|3|,|computed as if planets and satellites move in circular|
|mean_solar_day|,|4|,|orbits about their primaries with periods as specified by|
|mean_solar_day|,|5|,|the revolution_period element, and as if planets and|
|mean_solar_day|,|6|,|satellites have spin axes which are perpendicular to their|
|mean_solar_day|,|7|,|orbit planes.|
|mean_surface_pressure|,|1|,|The mean_surface_pressure element provides the|
|mean_surface_pressure|,|2|,|mean equatorial atmospheric pressure value at the mean|
|mean_surface_pressure|,|3|,|equatorial surface of a body, averaged over the body's|
|mean_surface_pressure|,|4|,|year.|
|mean_surface_temperature|,|1|,|The mean_surface_temperature element provides the mean|
|mean_surface_temperature|,|2|,|equatorial surface temperature of a body, averaged over the|
|mean_surface_temperature|,|3|,|body's year.|
|measured_quantity_name|,|1|,|The measured_quantity_name element indicates the physical|
|measured_quantity_name|,|2|,|phenomenon measured by a declared unit of measure.|
|measured_quantity_name|,|3|,|For example, the measured quantity name for the unit|
|measured_quantity_name|,|4|,|AMPERE is ELECTRIC CURRENT.|
|measured_quantity_name|,|300|,|NOTE:  A table of standard units, unit ids, and measured|
|measured_quantity_name|,|301|,|quantities based on those published by the Systeme|
|measured_quantity_name|,|302|,|Internationale appears in the 'Units of Measurement' section|
|measured_quantity_name|,|303|,|of the PSDD.  (Please refer to the table of contents for its|
|measured_quantity_name|,|304|,|location.)  The values in this table's 'Measured Quantity'|
|measured_quantity_name|,|305|,|column constitute the standard values for the data element|
|measured_quantity_name|,|306|,|measured_quantity_name.|
|measurement_atmosphere_desc|,|1|,|The measurement_atmosphere_description element describes|
|measurement_atmosphere_desc|,|2|,|the atmospheric conditions through which ground data were|
|measurement_atmosphere_desc|,|3|,|taken.|
|measurement_source_desc|,|1|,|The measurement_source_description element describes the|
|measurement_source_desc|,|2|,|source of light used in a laboratory-generated data set,|
|measurement_source_desc|,|3|,|or the radar transmitter in the case of radar astronomy|
|measurement_source_desc|,|4|,|experiments.|
|measurement_standard_desc|,|1|,|The measurement_standard_description element identifies the|
|measurement_standard_desc|,|2|,|standard object on which observations are performed in|
|measurement_standard_desc|,|3|,|order to calibrate an instrument.|
|measurement_wave_calbrt_desc|,|1|,|The measurement_wavelength_calibration_description element|
|measurement_wave_calbrt_desc|,|2|,|identifies the technique and procedure used to calibrate|
|measurement_wave_calbrt_desc|,|3|,|wavelength.|
|medium_count|,|1|,|The medium_count element indicates the number of units|
|medium_count|,|2|,|(for example, the number of reels of magnetic tape) included|
|medium_count|,|3|,|in the delivery of a data set or data set collection.|
|medium_desc|,|1|,|The medium_desc element provides the textual description for|
|medium_desc|,|2|,| the medium used in the distribution of an ordered data set.|
|medium_type|,|1|,|The medium_type element identifies the physical storage|
|medium_type|,|2|,|medium for a data volume.  Examples:  CD-ROM, CARTRIDGE|
|medium_type|,|3|,|TAPE.|
|method_desc|,|1|,|The method_desc element describes the method used to perform|
|method_desc|,|2|,|a particular observation.|
|midnight_longitude|,|1|,|The midnight_longitude element identifies the longitude on|
|midnight_longitude|,|2|,|the target body at which midnight was occurring at the time|
|midnight_longitude|,|3|,|of the start of an observation sequence.|
|midnight_longitude|,|4|,|Midnight_longitude is used to assist in geometry|
|midnight_longitude|,|5|,|calculations.|
|minimum|,|1|,|The minimum element indicates the smallest value occurring|
|minimum|,|2|,|in a given instance of the data object.|
|minimum_available_sampling_int|,|1|,|The minimum_available_sampling_interval element identifies|
|minimum_available_sampling_int|,|2|,|the finest sampling at which a particular set of data is|
|minimum_available_sampling_int|,|3|,|available.|
|minimum_available_sampling_int|,|4|,|For example, magnetometer data are available in various|
|minimum_available_sampling_int|,|5|,|sampling intervals ranging from 1.92 seconds to 96 seconds.|
|minimum_available_sampling_int|,|6|,| Thus, for magnetometer data the value of the|
|minimum_available_sampling_int|,|7|,|minimum_available_sampling_interval would be 1.92.|
|minimum_available_sampling_int|,|8|,|Note that the unit of measure for the sampling interval is|
|minimum_available_sampling_int|,|9|,|provided by the unit element.|
|minimum_brightness_temperature|,|1|,|The minimum_brightness_temperature element provides the|
|minimum_brightness_temperature|,|2|,|minimum brightness temperature value measured within a|
|minimum_brightness_temperature|,|3|,|given set of data or a given sequence.|
|minimum_brightness_temperature|,|4|,|Brightness temperature is the temperature of an ideal|
|minimum_brightness_temperature|,|5|,|blackbody whose radiant energy in a particular wavelength|
|minimum_brightness_temperature|,|6|,|range is the same as that of an observed object or feature.|
|minimum_channel_id|,|1|,|The minimum_channel_id element provides an identification of|
|minimum_channel_id|,|2|,|the lowest energy channel from which PLS instrument data is|
|minimum_channel_id|,|3|,|telemetered to Earth while the instrument is operating in a|
|minimum_channel_id|,|4|,|particular mode in a given frame.  Each mode consists of a|
|minimum_channel_id|,|5|,|specific number of energy/charge channels which sequentially|
|minimum_channel_id|,|6|,|measure current, but information from all measured channels|
|minimum_channel_id|,|7|,|may not be telemetered to Earth.|
|minimum_column_value|,|1|,|The minimum_column_value provides the minimum real value|
|minimum_column_value|,|2|,|currently allowed by the PDS catalog for a given table|
|minimum_column_value|,|3|,|element.  This value is updated when new limits are|
|minimum_column_value|,|4|,|discovered.  Note that these elements are unique to a table|
|minimum_column_value|,|5|,|and may have different values depending on which table the|
|minimum_column_value|,|6|,| element is associated with.|
|minimum_emission_angle|,|1|,|The minimum_emission_angle element provides the minimum|
|minimum_emission_angle|,|2|,|emission angle value.  See emission_angle.|
|minimum_incidence_angle|,|1|,|The minimum_incidence_angle element provides the minimum|
|minimum_incidence_angle|,|2|,|incidence angle value.  See incidence_angle.|
|minimum_instrument_exposr_dur|,|1|,|The minimum_instrument_exposure_duration element provides|
|minimum_instrument_exposr_dur|,|2|,|the minimum possible exposure time for the instrument mode|
|minimum_instrument_exposr_dur|,|3|,|identified by the instrument_mode_identification element.|
|minimum_instrument_exposr_dur|,|4|,|See instrument_exposure_duration.|
|minimum_instrument_parameter|,|1|,|The minimum_instrument_parameter element provides an|
|minimum_instrument_parameter|,|2|,|instrument's minimum usefully detectable signal level for a|
|minimum_instrument_parameter|,|3|,|given instrument parameter.  This value indicates the|
|minimum_instrument_parameter|,|4|,|physical value corresponding to the minimum digital output|
|minimum_instrument_parameter|,|5|,|of an instrument.|
|minimum_instrument_parameter|,|6|,|The instrument parameter to which this relates is identified|
|minimum_instrument_parameter|,|7|,|by the instrument_parameter_name element.|
|minimum_latitude|,|1|,|The minimum_latitude element specifies the southernmost|
|minimum_latitude|,|2|,|latitude of a spatial area, such as a map, mosaic, bin,|
|minimum_latitude|,|3|,|feature, or region.  See latitude.|
|minimum_limb_angle|,|1|,|The minimum_limb_angle element provides the minimum value|
|minimum_limb_angle|,|2|,|of the limb angle within a given set of data.  See|
|minimum_limb_angle|,|3|,|limb_angle.|
|minimum_local_time|,|1|,|The minimum_local_time element provides the minimum|
|minimum_local_time|,|2|,|local time of day on the target body, measured in hours|
|minimum_local_time|,|3|,|from local midnight.|
|minimum_longitude|,|1|,|The minimum_longitude element specifies the easternmost|
|minimum_longitude|,|2|,|(right_most) longitude of a spatial area, such as a map,|
|minimum_longitude|,|3|,|mosaic, bin, feature, or region.  See longitude.|
|minimum_longitude|,|300|,|Note:  For areas that cross the prime meridian, the minimum|
|minimum_longitude|,|301|,|longitude will have an ordinal value greater than the|
|minimum_longitude|,|302|,|maximum value.|
|minimum_longitude|,|303|,|Note:  Longitudes are measured in the direction of rotation|
|minimum_longitude|,|304|,|for all planetary rings.|
|minimum_parameter|,|1|,|The minimum_parameter element specifies the minimum|
|minimum_parameter|,|2|,|allowable value for a parameter input to a given data|
|minimum_parameter|,|3|,|processing program.|
|minimum_parameter|,|4|,|The parameter constrained by this value is identified by|
|minimum_parameter|,|5|,|the parameter_name element.|
|minimum_phase_angle|,|1|,|The minimum_phase_angle element provides the minimum phase|
|minimum_phase_angle|,|2|,|angle value.  See phase_angle.|
|minimum_sampling_parameter|,|1|,|The minimum_sampling_parameter element identifies the|
|minimum_sampling_parameter|,|2|,|minimum value at which a given data item was sampled.|
|minimum_sampling_parameter|,|3|,|For example, a spectrum that was measured in the 0.4 to 3.5|
|minimum_sampling_parameter|,|4|,|micrometer spectral region would have a|
|minimum_sampling_parameter|,|5|,|minimum_sampling_parameter value of 0.4.|
|minimum_sampling_parameter|,|6|,|The sampling parameter constrained by this value is|
|minimum_sampling_parameter|,|7|,|identified by the sampling_parameter_name element.  Note|
|minimum_sampling_parameter|,|8|,|that the unit of measure for the sampling parameter is|
|minimum_sampling_parameter|,|9|,|provided by the unit element.|
|minimum_slant_distance|,|1|,|The minimum_slant_distance element provides the minimum|
|minimum_slant_distance|,|2|,|slant distance value.  See slant_distance.|
|minimum_solar_band_albedo|,|1|,|The minimum_solar_band_albedo element provides the minimum|
|minimum_solar_band_albedo|,|2|,|solar band albedo value measured within a given set of data|
|minimum_solar_band_albedo|,|3|,|or a given sequence.|
|minimum_spectral_contrast|,|1|,|The minimum_spectral_contrast element provides the minimum|
|minimum_spectral_contrast|,|2|,|value of spectral contrast within a given set of data.  See|
|minimum_spectral_contrast|,|3|,|spectral_contrast_ range.|
|minimum_surface_pressure|,|1|,|The minimum_surface_pressure element provides the minimum|
|minimum_surface_pressure|,|2|,|surface pressure value for the atmosphere of a given body.|
|minimum_surface_temperature|,|1|,|The minimum_surface_temperature element provides the minimum|
|minimum_surface_temperature|,|2|,|equatorial surface temperature value for a given body during|
|minimum_surface_temperature|,|3|,|its year.|
|minimum_wavelength|,|1|,|The minimum_wavelength element identifies the minimum|
|minimum_wavelength|,|2|,|wavelength to which an instrument detector or filter is|
|minimum_wavelength|,|3|,|sensitive.|
|missing|,|1|,|The missing element supplies the value used when no science|
|missing|,|2|,|data were available.|
|mission_alias_name|,|1|,|The mission_alias_name element provides an official name of|
|mission_alias_name|,|2|,|a mission  used during the initial design, implementation,|
|mission_alias_name|,|3|,|or prelaunch phases. Example values: mission_name:MAGELLAN,|
|mission_alias_name|,|4|,|mission_alias_name:VENUS RADAR MAPPER.|
|mission_desc|,|1|,|The mission_description element summarizes major aspects of|
|mission_desc|,|2|,|a planetary mission or project, including the number and|
|mission_desc|,|3|,|type of spacecraft, the target body or bodies and major|
|mission_desc|,|4|,|accomplishments.|
|mission_id|,|1|,|The mission_id element provides a synonym or mnemonic for|
|mission_id|,|2|,|the mission_name element.|
|mission_id|,|501|,|Note: Within SFOC this may also be a numeric value which is|
|mission_id|,|502|,|the DSN mission number.|
|mission_name|,|1|,|The mission_name element identifies a major planetary|
|mission_name|,|2|,|mission or project.|
|mission_name|,|3|,|A given planetary mission may be associated with one or|
|mission_name|,|4|,|more spacecraft.|
|mission_name_or_alias|,|1|,|The mission_name_or_alias element provides the capability to|
|mission_name_or_alias|,|2|,|enter either a mission name or a mission alias name in a|
|mission_name_or_alias|,|3|,|single input parameter field of a user view.|
|mission_objectives_summary|,|1|,|The mission_objectives_summary element describes the major|
|mission_objectives_summary|,|2|,|scientific objectives of a planetary mission or project.|
|mission_phase_desc|,|1|,|The mission_phase_description element summarizes key|
|mission_phase_desc|,|2|,|aspects of a mission phase.|
|mission_phase_start_time|,|1|,|The mission_phase_start_time element provides the date and|
|mission_phase_start_time|,|2|,|time of the beginning of a mission phase in UTC format.|
|mission_phase_start_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|mission_phase_stop_time|,|1|,|The mission_phase_stop_time element provides the date and|
|mission_phase_stop_time|,|2|,|time of the end of a mission phase in UTC format.|
|mission_phase_stop_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|mission_phase_type|,|1|,|The mission_phase_type element identifies the type of a|
|mission_phase_type|,|2|,|major segment or 'phase' of a spacecraft mission.  Example|
|mission_phase_type|,|3|,|values: LAUNCH, CRUISE, ENCOUNTER.|
|mission_phase_type|,|300|,|Note:  The concept of a mission phase name exists only|
|mission_phase_type|,|301|,|implicitly in the PDS via the combination of spacecraft_id,|
|mission_phase_type|,|302|,|target name, mission_phase_type.|
|mission_start_date|,|1|,|The mission_start_date element provides the date of the|
|mission_start_date|,|2|,|beginning of a mission in UTC format.|
|mission_start_date|,|200|,|Formation rule:  YYYY-MM-DDThh:mm:ss[.fff]|
|mission_stop_date|,|1|,|The mission_stop_date element provides the date of the end|
|mission_stop_date|,|2|,|of a mission in UTC format.|
|mission_stop_date|,|200|,|Formation rule:  YYYY-MM-DDThh:mm:ss[.fff]|
|mode_continuation_flag|,|1|,|The mode_continuation_flag element is a yes-or-no flag which|
|mode_continuation_flag|,|2|,|indicates if the first mode in a frame is a continuation of|
|mode_continuation_flag|,|3|,|a measurement from the previous frame.  Some modes require|
|mode_continuation_flag|,|4|,|longer than one frame to make a measurement, resulting in|
|mode_continuation_flag|,|5|,|their continuation to a subsequent frame.  In that case, the|
|mode_continuation_flag|,|6|,|mode_ continuation_flag element would have the value YES.|
|mode_integration_duration|,|1|,|The mode_integration_duration element provides the length of|
|mode_integration_duration|,|2|,|time required to measure all the channels which are sampled|
|mode_integration_duration|,|3|,|when the instrument is operating in a given mode.|
|mosaic_desc|,|1|,|The mosaic_description element provides a brief textual|
|mosaic_desc|,|2|,|description of a mosaic.|
|mosaic_images|,|1|,|The mosaic_images element identifies the number of images|
|mosaic_images|,|2|,|which are contained in a given mosaic.|
|mosaic_production_parameter|,|1|,|The mosaic_production_parameter element identifies the|
|mosaic_production_parameter|,|2|,|method of production of a mosaic product (e.g., manual vs.|
|mosaic_production_parameter|,|3|,|digital).|
|mosaic_sequence_number|,|1|,|The mosaic_sequence_number element is a numeric identifier|
|mosaic_sequence_number|,|2|,|which defines a group of related images on a single mosaic.|
|mosaic_sequence_number|,|3|,|The mosaic_sequence_number is necessary when several groups|
|mosaic_sequence_number|,|4|,|of images covering different regions are printed on one|
|mosaic_sequence_number|,|5|,|photo_product.|
|mosaic_series_id|,|1|,|The mosaic_series_identification element is an alphanumeric|
|mosaic_series_id|,|2|,|identifier for mosaics from a given mission.|
|mosaic_sheet_number|,|1|,|The mosaic_sheet_number element is a numeric identifier for|
|mosaic_sheet_number|,|2|,|a mosaic series or for a mosaic within a mosaic series.|
|mult_peak_fresnel_reflect_corr|,|1|,| The mult_peak_fresnel_reflect_corr element provides the|
|mult_peak_fresnel_reflect_corr|,|2|,|correction factor that has been applied to|
|mult_peak_fresnel_reflect_corr|,|3|,|derived_fresnel_reflectivity to allow for radar echoes|
|mult_peak_fresnel_reflect_corr|,|4|,|possessing more than an single peak.|
|naif_data_set_id|,|1|,|The naif_data_set_id element provides the data_set_id which|
|naif_data_set_id|,|2|,|contains the position information for the instrument.|
|name|,|1|,|The name data element indicates a literal value|
|name|,|2|,|representing the common term used to identify an element or|
|name|,|3|,|object.  See also: 'id'.|
|native_start_time|,|1|,|The native_start_time element provides a time value at the|
|native_start_time|,|2|,|beginning of a time period of interest. Native time is|
|native_start_time|,|3|,|'native to' (that is, resident within) a given set of data,|
|native_start_time|,|4|,|in those cases in which the native time field is in a format|
|native_start_time|,|5|,|other than the standard UTC format. For example, the|
|native_start_time|,|6|,|spacecraft clock count could be a native time value.|
|native_stop_time|,|1|,|The native_stop_time element provides a time value at the|
|native_stop_time|,|2|,|end of a time period of interest. Native time is 'native to'|
|native_stop_time|,|3|,|(that is, resident within) a given set of data, in those|
|native_stop_time|,|4|,|cases in which the native time field is in a format other|
|native_stop_time|,|5|,|than the standard UTC format. For example, the|
|native_stop_time|,|6|,|spacecraft clock count could be a native time value.|
|nav_unique_id|,|1|,|This element is a SFOC-MGN unique element used to express a|
|nav_unique_id|,|2|,|NAV-unique identifier for the file.|
|node_desc|,|1|,|The node_desc element describes a PDS Node.|
|node_id|,|1|,|The node_id element provides the node id assigned to a|
|node_id|,|2|,| science community node.|
|node_institution_name|,|1|,|The node_institution_name element identifies a university,|
|node_institution_name|,|2|,|research center, NASA center or other institution associated|
|node_institution_name|,|3|,|with a PDS node.|
|node_manager_pds_user_id|,|1|,|The node_manager_pds_user_id element provides the|
|node_manager_pds_user_id|,|2|,|pds_user_id of the node manager.|
|node_name|,|1|,|The node_name element provides the officially recognized|
|node_name|,|2|,|name of a PDS Node.|
|node_order_item_id|,|1|,|The node_order_item_desc provides a node's order item|
|node_order_item_id|,|2|,|reference number and is not controlled by the Central Node|
|node_order_item_id|,|3|,|order function but is allowed for tracking to the node's|
|node_order_item_id|,|4|,|system.|
|noise_level|,|1|,|The noise_level element identifies the threshold at which|
|noise_level|,|2|,|signal is separable from noise in a given data set or for|
|noise_level|,|3|,|measurements performed by a particular instrument.|
|noise_level|,|4|,|For instruments the noise level is a function primarily of|
|noise_level|,|5|,|the instrument characteristics, while for data sets or data|
|noise_level|,|6|,|products the noise level can also be a function of the data|
|noise_level|,|7|,|processing history.|
|nominal_energy_resolution|,|1|,|The nominal_energy_resolution element provides an|
|nominal_energy_resolution|,|2|,|approximation of the energy resolution obtained during a|
|nominal_energy_resolution|,|3|,|particular instrument mode.  Energy resolution is defined as|
|nominal_energy_resolution|,|4|,|the width of an energy channel divided by the average energy|
|nominal_energy_resolution|,|5|,|of that channel.  A nominal value is given as this quantity|
|nominal_energy_resolution|,|6|,|varies between channels.|
|nominal_operating_temperature|,|1|,|The nominal_operating_temperature element identifies the|
|nominal_operating_temperature|,|2|,|operating temperature as given in the specifications for an|
|nominal_operating_temperature|,|3|,|instrument detector.|
|non_clustered_key|,|1|,|The non_clustered_key element indicates whether a column in|
|non_clustered_key|,|2|,|a table has a nonclustered index.  This index is not unique|
|non_clustered_key|,|3|,|does not determines the sorting order of the data, but is|
|non_clustered_key|,|4|,|intended purely for query performance optimization.|
|non_range_prof_corrs_index|,|1|,| The non_range_prof_corrs_index element provides the value|
|non_range_prof_corrs_index|,|2|,|of the index of the element in non_range_sharp_echo_prof|
|non_range_prof_corrs_index|,|3|,|that corresponds to the first element in|
|non_range_prof_corrs_index|,|4|,|best_non_range_sharp_model_tpt[0]. The indices start at|
|non_range_prof_corrs_index|,|5|,|zero.|
|non_range_sharp_echo_prof|,|1|,| The non_range_sharp_echo_prof element provides the value|
|non_range_sharp_echo_prof|,|2|,|of the power vs. time echo profile, at half-baud (0.21|
|non_range_sharp_echo_prof|,|3|,|microsecond) intervals, assembled from up to 16 frequency|
|non_range_sharp_echo_prof|,|4|,|components, without shifting their time origins (see|
|non_range_sharp_echo_prof|,|5|,|range_sharp_echo_profile element). This profile yields the|
|non_range_sharp_echo_prof|,|6|,|best estimate of the time dispersion of the echo, and hence|
|non_range_sharp_echo_prof|,|7|,|the value of the derived_rms_surface_slope and|
|non_range_sharp_echo_prof|,|8|,|derived_fresnel_reflectivity element.|
|non_range_sharp_fit|,|1|,| The non_range_sharp_fit element provides the value of the|
|non_range_sharp_fit|,|2|,|'goodness of fit' measuring the correlation between the|
|non_range_sharp_fit|,|3|,|observed profile non_range_sharp_echo_prof and the|
|non_range_sharp_fit|,|4|,|theoretical template best_non_range_sharp_model_tpt|
|non_range_sharp_fit|,|5|,|elements. Scaling_factors for the|
|non_range_sharp_fit|,|6|,|best_non_range_sharp_model_tpt and the|
|non_range_sharp_fit|,|7|,|non_range_sharp_echo_prof elements provide the value of the|
|non_range_sharp_fit|,|8|,|conversion factor that multiplies the integer array|
|non_range_sharp_fit|,|9|,|elements of the best_non_range_sharp_model_tpt and|
|non_range_sharp_fit|,|10|,|non_range_sharp_echo_prof elements to yield their physical|
|non_range_sharp_fit|,|11|,|values, expressed as equivalent radar cross-sections in|
|non_range_sharp_fit|,|12|,|units of km**2.|
|non_range_sharp_looks|,|1|,| The non_range_sharp_looks element provides the value of|
|non_range_sharp_looks|,|2|,|the number of statistically independent measurements of|
|non_range_sharp_looks|,|3|,|echo profile that were summed to produce the value for the|
|non_range_sharp_looks|,|4|,|profile non_range_sharp_echo_prof element.|
|north_azimuth|,|1|,|The north_azimuth element provides the value of the angle|
|north_azimuth|,|2|,|between a line from the image center to the north pole and|
|north_azimuth|,|3|,|a reference line in the image plane.  The reference line is|
|north_azimuth|,|4|,|a horizontal line from the image center to the middle right|
|north_azimuth|,|5|,|edge of the image.|
|north_azimuth|,|6|,|This angle increases in a clockwise direction.|
|note|,|1|,|The note element is a text field which provides|
|note|,|2|,|miscellaneous notes or comments (for example, concerning a|
|note|,|3|,|given data set or a given data processing program).|
|notebook_entry_time|,|1|,|The notebook_entry_time element provides the date and time|
|notebook_entry_time|,|2|,|at which an experimenter made a particular entry in the|
|notebook_entry_time|,|3|,|experimenter notebook.|
|notebook_entry_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|object|,|1|,|The object_name element provides the template object name|
|object|,|2|,|assigned by the Central Node data administrator to a logical|
|object|,|3|,|template used in the PDS.|
|object_attribute_value|,|1|,|The object_attribute_value element is the supplier's input|
|object_attribute_value|,|2|,|he/she assigned to a catalog template keyword.  This value|
|object_attribute_value|,|3|,|may represent any type of data (i.e. text, integer, real).|
|object_attribute_value|,|4|,|The values are ultimately copied into the PDS catalog.|
|obliquity|,|1|,|The obliquity element provides the value of the angle|
|obliquity|,|2|,|between the plane of the equator and the orbital plane of a|
|obliquity|,|3|,|target body.|
|observation_id|,|1|,|The observation_id element identifies a specific observation|
|observation_id|,|2|,|sequence.|
|observation_type|,|1|,|The observation_type element identifies the general type of|
|observation_type|,|2|,|an observation.|
|offset|,|1|,|The offset element indicates a shift or displacement of a|
|offset|,|2|,|data value.  See also: scaling_factor.|
|offset|,|300|,|Note:  Expressed as an equation:  true value = offset value|
|offset|,|301|,|+ (scaling factor x stored value).|
|operational_consid_desc|,|1|,|The operational_considerations_description element provides|
|operational_consid_desc|,|2|,|a brief description of operational characteristics which|
|operational_consid_desc|,|3|,|affect the measurements made by an instrument.|
|operations_contact_pds_user_id|,|1|,|The operations_contact_pds_user_id element provides the|
|operations_contact_pds_user_id|,|2|,|pds_user_id of the operations contact at a node.|
|optics_desc|,|1|,|The optics_description element provides a textual|
|optics_desc|,|2|,|description of the physical and operational characteristics|
|optics_desc|,|3|,|of the optics of an instrument.|
|orbit_direction|,|1|,|The orbit_direction element provides the direction of|
|orbit_direction|,|2|,|movement along the orbit about the primary as seen from the|
|orbit_direction|,|3|,|north pole of the 'invariable plane of the solar system',|
|orbit_direction|,|4|,|which is the plane passing through the center of mass of the|
|orbit_direction|,|5|,|solar system and perpendicular to the angular momentum|
|orbit_direction|,|6|,|vector of the solar system orbit motion, RETROGRADE for|
|orbit_direction|,|7|,|clockwise orbit motion.|
|orbit_number|,|1|,|The orbit_number element identifies the number of the|
|orbit_number|,|2|,|orbital revolution of the spacecraft, counted since orbit|
|orbit_number|,|3|,|insertion.|
|orbit_number*|,|1|,|The orbit_number* element provides the Magellan orbit|
|orbit_number*|,|2|,|number corresponding to the following three files|
|orbit_number*|,|3|,|(ephemeris, altimetry, and radiometry).|
|orbit_number*|,|300|,|Note:  Orbit_number* is marked with an asterix because it|
|orbit_number*|,|301|,|duplicates an already-existing element in the common list|
|orbit_number*|,|302|,|of data element names.  This situation will be rectified|
|orbit_number*|,|303|,|in the next edition of the PSDD.|
|orbit_start_number|,|1|,|The orbit_start_number is an alias for start_orbit_number|
|orbit_start_number|,|2|,|used exclusively by the SFOC-MGN KEY_TIMES file.|
|orbit_start_time|,|1|,|The orbit_start_time element is an alias for start_time used|
|orbit_start_time|,|2|,|exclusively by SFOC-MGN ephemeris files.|
|orbit_stop_number|,|1|,|The orbit_stop_number is an alias for stop_orbit_number used|
|orbit_stop_number|,|2|,|exclusively by the SFOC-MGN KEY_TIMES data file.|
|orbit_stop_time|,|1|,|The orbit_stop_time element is an alias for stop_time used|
|orbit_stop_time|,|2|,|exclusively by SFOC-MGN ephemeris files.|
|orbital_eccentricity|,|1|,|The orbital_eccentricity element provides a measure of the|
|orbital_eccentricity|,|2|,|non_circularity or flattening of the orbit of a planetary|
|orbital_eccentricity|,|3|,|body.  The orbit of a comet, for example, could be either|
|orbital_eccentricity|,|4|,|parabolic or hyperbolic.|
|orbital_eccentricity|,|5|,|Circular orbits are defined as having an eccentricity of 0,|
|orbital_eccentricity|,|6|,|and the eccentricity value is greater than 0 for|
|orbital_eccentricity|,|7|,|non_circular orbits. Elliptical orbits have eccentricities|
|orbital_eccentricity|,|8|,|between (but not equal to) 0 and 1. Parabolic orbits have|
|orbital_eccentricity|,|9|,|an eccentricity of 1, while hyperbolic orbits have|
|orbital_eccentricity|,|10|,|eccentricities greater than 1.|
|orbital_inclination|,|1|,|The orbital_inclination element provides the value of the|
|orbital_inclination|,|2|,|angle between the orbital plane of a target body and the|
|orbital_inclination|,|3|,|ecliptic.|
|orbital_semimajor_axis|,|1|,|The orbital_semimajor_axis element provides the value of|
|orbital_semimajor_axis|,|2|,|the semimajor axis of the orbit of a target body.  The|
|orbital_semimajor_axis|,|3|,|semimajor axis is one_half of the maximum dimension of an|
|orbital_semimajor_axis|,|4|,|orbit.|
|order_date|,|1|,|The order_date element provides the date of when an order|
|order_date|,|2|,|was placed for a data set.|
|order_initiator|,|1|,|The order_initiator element identifies the initiator of a|
|order_initiator|,|2|,|PDS order which is associated with a specific order number.|
|order_item_bytes|,|1|,|The order_item_bytes element provides the total number of|
|order_item_bytes|,|2|,|bytes that an order item requires for storage.|
|order_item_desc|,|1|,|The order_item_desc element provides a textual description|
|order_item_desc|,|2|,|of an order item accepted by the PDS.|
|order_item_media_cost|,|1|,|The order_item_media_cost element provides the total cost|
|order_item_media_cost|,|2|,|associated with an order item.|
|order_item_number|,|1|,|The order_item_number element provides a sequential computer|
|order_item_number|,|2|,|generated number for each item within an order number.|
|order_item_processing_cost|,|1|,|The order_item_processing_cost element identifies the total|
|order_item_processing_cost|,|2|,|cost associated with processing a data order.|
|order_item_quantity|,|1|,|The order_item_quantity element provides the order item|
|order_item_quantity|,|2|,|quantity ordered.|
|order_item_ship_quantity|,|1|,|The order_item_shipping_quantity element provides the|
|order_item_ship_quantity|,|2|,|quantity shipped per status change of an order item.|
|order_item_shipping_cost|,|2|,|cost in shipping a data order, including packing and mailing|
|order_item_shipping_instr|,|1|,|The order_item_shipping_instructions element provides any|
|order_item_shipping_instr|,|2|,|special shipping instructions for an order item.|
|order_item_special_instr|,|1|,|The order_item_special_instructions element provides any|
|order_item_special_instr|,|2|,|special instructions for an order item, allowing the person|
|order_item_special_instr|,|3|,|placing the order to indicate any special processing|
|order_item_special_instr|,|4|,|request.|
|order_item_status|,|1|,|The order_item_status element provides the status associated|
|order_item_status|,|2|,|with PDS order items accepted by the PDS order function.|
|order_item_status_date|,|1|,|The order_item_status_date element provides the date of an|
|order_item_status_date|,|2|,|order item status change.|
|order_item_status_desc|,|1|,|The order_item_status_desc element provides the status|
|order_item_status_desc|,|2|,|description for an order item accepted by the PDS order|
|order_item_status_desc|,|3|,|function. This is an optional function provided by the|
|order_item_status_desc|,|4|,|system to help fully describe any reasons for an order item|
|order_item_status_desc|,|5|,|status change.|
|order_item_status_sequence_num|,|1|,|The order_item_status_sequence_num element identifies the|
|order_item_status_sequence_num|,|2|,|sequence of tuples used to describe the status of order|
|order_item_status_sequence_num|,|3|,|items.|
|order_number|,|1|,|The order_number element is a unique system_generated|
|order_number|,|2|,|number which is used to identify an order.|
|order_preference_id|,|1|,|The order_preference_id element indicates a user's|
|order_preference_id|,|2|,|preference for one of a set of alternatives for electronic|
|order_preference_id|,|3|,|distribution of an order.|
|order_ship_carrier_name|,|1|,|The order_ship_carrier_name element provides the shipping|
|order_ship_carrier_name|,|2|,|carrier name associated with an order item.|
|order_status|,|1|,|The order_status element provides the status associated with|
|order_status|,|2|,| orders and order items accepted by the PDS order function.|
|order_status_date|,|1|,|The order_status_date element provides the effective date|
|order_status_date|,|2|,|of an order status change.|
|order_status_desc|,|1|,|The order_status_desc element details the status of an|
|order_status_desc|,|2|,|order.|
|order_status_id|,|1|,|The order_status_id element identifies the status of an|
|order_status_id|,|2|,|order.|
|order_status_sequence_number|,|1|,|The order_status_sequence_number element provides an integer|
|order_status_sequence_number|,|2|,|which indicates the sequence of status changes within an|
|order_status_sequence_number|,|3|,|order.|
|order_status_staff_name|,|1|,|The order_item_staff element provides the name of the|
|order_status_staff_name|,|2|,|person filling an order item for a PDS order.|
|order_status_time|,|1|,|The order_status_time element gives the date (and time,|
|order_status_time|,|2|,|where applicable) as of which the status of an order was|
|order_status_time|,|3|,|changed.|
|order_status_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|output_flag|,|1|,|The output_flag element indicates whether standard values|
|output_flag|,|2|,|shall be output for hardcopy display.|
|parameter_desc|,|1|,|The parameter_desc element defines the input or output|
|parameter_desc|,|2|,|parameter identified by the parameter_name element,|
|parameter_desc|,|3|,|including units, derivation (where applicable), and|
|parameter_desc|,|4|,|associated parameters.|
|parameter_sequence_number|,|1|,|The parameter_sequence_number element provides an ordering|
|parameter_sequence_number|,|2|,|sequence number for parameters used in user views and|
|parameter_sequence_number|,|3|,|associated queries.|
|parameter_type|,|1|,|The parameter_type element provides the type of parameter|
|parameter_type|,|2|,|(input or output) used in user views and associated queries.|
|parent_template|,|1|,|The parent_template element contains the name of the|
|parent_template|,|2|,|template which provides the loader software with a keyword|
|parent_template|,|3|,|value which occurred elsewhere in the same or a different|
|parent_template|,|4|,|template.  For example:  the value for the data_set_id|
|parent_template|,|5|,|keyword is required in several templates to map the|
|parent_template|,|6|,|template information to the proper dataset, yet to avoid|
|parent_template|,|7|,|redundant data supplier effort it appears only on the|
|parent_template|,|8|,|DATASET template.  For these templates, the parenttmplt|
|parent_template|,|9|,|provides the source of the data_set_id value, i.e. the|
|parent_template|,|10|,|DATASET template.|
|particle_species_name|,|1|,|The particle_species_name element provides the name of a|
|particle_species_name|,|2|,|particle detected by a given instrument.  Example values:|
|particle_species_name|,|3|,|ELECTRON, ION, PROTON, HYDROGEN, HELIUM, OXYGEN, etc.  For|
|particle_species_name|,|4|,|ions, the specific atomic number designation may be used|
|particle_species_name|,|5|,|(e.g., Z=1, Z=2, Z=8, etc.).|
|pds_supplier_name|,|1|,|The pds_supplier_name element provides the name of a person|
|pds_supplier_name|,|2|,|who supplied a completed catalog template.  This person is|
|pds_supplier_name|,|3|,|the primary contact for any questions on the contents of|
|pds_supplier_name|,|4|,|the catalog template.|
|pds_user_id|,|1|,|The pds_user_id element provides a unique identifier for|
|pds_user_id|,|2|,|each individual who is allowed access to the PDS. The system|
|pds_user_id|,|3|,|manager at the Central Node assigns this identifier at the|
|pds_user_id|,|4|,|time of user registration.|
|peer_review_data_set_status|,|1|,|The peer_review_data_set_status element provides status for|
|peer_review_data_set_status|,|2|,|data sets which have been peer reviewed.|
|peer_review_id|,|1|,|The peer_review_id element provides a unique identifier|
|peer_review_id|,|2|,|assigned by the bulk loading software to each peer review|
|peer_review_id|,|3|,|information set saved in the PDS database.|
|peer_review_results_desc|,|1|,|The peer_review_results element provides the textual|
|peer_review_results_desc|,|2|,|description of the results of a peer review.|
|peer_review_role|,|1|,|The peer_review_role element provides the role of a member|
|peer_review_role|,|2|,|of a peer review committee.|
|peer_review_start_date|,|1|,|The peer_review_start_date element provides the beginning|
|peer_review_start_date|,|2|,|date for a peer review in YYYYMMDD format.|
|peer_review_stop_date|,|1|,|The peer_review_stop_date element provides the final date|
|peer_review_stop_date|,|2|,|for a peer review in YYYYMMDD format.|
|periapsis_argument_angle|,|1|,|The periapsis_argument_angle element provides the value of|
|periapsis_argument_angle|,|2|,|the periapsis argument angle, which is defined as the angle|
|periapsis_argument_angle|,|3|,|measured from the ascending node of the orbit of a target|
|periapsis_argument_angle|,|4|,|body (relative to the reference plane) to the point in the|
|periapsis_argument_angle|,|5|,|orbit at which the target body obtains its closest approach|
|periapsis_argument_angle|,|6|,|to the primary body.|
|periapsis_argument_angle|,|7|,|See also: ascending_node_longitude.|
|person_institution_name|,|1|,|The person_institution_name element identifies a university,|
|person_institution_name|,|2|,|research center, NASA center or other institution associated|
|person_institution_name|,|3|,|with an individual involved with the PDS.|
|personnel_shipping_account_num|,|1|,|The personnel_shipping_account_num element identifies the|
|personnel_shipping_account_num|,|2|,|shipping carrier account number for a PDS user.|
|personnel_shipping_carrier_nam|,|1|,|The personnel_shipping_carrier_name element provides the|
|personnel_shipping_carrier_nam|,|2|,|name of the user's default shipping carrier.|
|personnel_shipping_instruction|,|1|,|The personnel_shipping_instruction element identifies|
|personnel_shipping_instruction|,|2|,|default shipping instructions.|
|phase_angle|,|1|,|The phase_angle element provides a measure of the|
|phase_angle|,|2|,|relationship between the spacecraft viewing position and|
|phase_angle|,|3|,|incident solar light. Phase_angle is defined as the angle|
|phase_angle|,|4|,|between a vector from the intercept point to the sun and a|
|phase_angle|,|5|,|vector from the intercept point to the spacecraft.|
|phase_angle|,|6|,|Low values of phase angle indicate lighting from behind the|
|phase_angle|,|7|,|spacecraft.  Phase angle varies from 0 degrees, when the|
|phase_angle|,|8|,|sun is directly behind the spacecraft, to 180 degrees, when|
|phase_angle|,|9|,|the sun is opposite the spacecraft.|
|pi_pds_user_id|,|1|,|The pi_pds_user_id element provides the pds_user_id of the|
|pi_pds_user_id|,|2|,|principal investigator associated with an instrument.|
|pin_software_id|,|1|,|The pin_software_id element identifies a partially|
|pin_software_id|,|2|,|integrated node (PIN) software package available through|
|pin_software_id|,|3|,|a science node.|
|planet_day_number|,|1|,|The planet_day_number element indicates the number of days|
|planet_day_number|,|2|,|elapsed since the landing day (landing day number is zero)|
|planet_day_number|,|3|,|for data obtained by a lander or a rover.|
|planet_reading_system_temp|,|1|,| The planet_reading_system_temp element provides the value|
|planet_reading_system_temp|,|2|,|of the raw radiometer reading, when switched into the SAR|
|planet_reading_system_temp|,|3|,|antenna, converted to equivalent noise temperature.|
|platform_or_mounting_desc|,|1|,|The platform_or_mounting_description element describes the|
|platform_or_mounting_desc|,|2|,|spacecraft platform or laboratory mounting frame on which|
|platform_or_mounting_desc|,|3|,|an instrument is mounted.|
|platform_or_mounting_name|,|1|,|The platform_or_mounting_name element identifies the|
|platform_or_mounting_name|,|2|,|spacecraft platform or the laboratory mounting frame on|
|platform_or_mounting_name|,|3|,|which an instrument is mounted.|
|platform_or_mounting_name|,|4|,|Example values:  SCAN_PLATFORM, PROBE, MAGNETOMETER_BOOM.|
|pole_declination|,|1|,|The pole_declination element provides the value of the|
|pole_declination|,|2|,|declination of the polar axis of a target body.  See|
|pole_declination|,|3|,|declination.|
|pole_right_ascension|,|1|,|The pole_right_ascension element provides the value of the|
|pole_right_ascension|,|2|,|right_ascension of the polar axis of a target body.  See|
|pole_right_ascension|,|3|,|right_ascension.|
|position_time|,|1|,|The position_time element provides the time when the|
|position_time|,|2|,|location information of an event is derived, in the|
|position_time|,|3|,|UTC format.|
|position_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|positive_longitude_direction|,|1|,|The positive_longitude_direction element identifies the|
|positive_longitude_direction|,|2|,|direction of longitude (e.g. EAST, WEST) for a planet.  The|
|positive_longitude_direction|,|3|,|IAU definition for direction of positive longitude is|
|positive_longitude_direction|,|4|,|adopted.  Typically, for planets with prograde rotations,|
|positive_longitude_direction|,|5|,|positive longitude direction is to the WEST.  For planets|
|positive_longitude_direction|,|6|,|with retrograde rotations, positive longitude direction is|
|positive_longitude_direction|,|7|,|to the EAST.|
|preference_id|,|1|,|The preference_identification element indicates a user's|
|preference_id|,|2|,|degree of preference for one of a set of alternatives (for|
|preference_id|,|3|,|example, preference for a particular electronic mail system|
|preference_id|,|4|,|such as Telemail).|
|preference_id|,|5|,|Values range from 1 to 4, with 1 indicating the highest|
|preference_id|,|6|,|preference.|
|primary_body_name|,|1|,|The primary_body_name element identifies the primary body|
|primary_body_name|,|2|,|with which a given target body is associated as a secondary|
|primary_body_name|,|3|,|body.|
|process_time|,|1|,|Alias within SFOC for product_creation_time.|
|process_time|,|501|,|Note: This element is retained for use by Magellan SFOC data|
|process_time|,|502|,|products only.  New products should use|
|process_time|,|503|,|product_creation_time.|
|process_version_id|,|1|,|The process_version_id element identifies the version (e.g.,|
|process_version_id|,|2|,|the method of processing) of a mosaic.|
|processing_control_parm_name|,|1|,|The processing_control_parm_name element identifies a|
|processing_control_parm_name|,|2|,|parameter which allows a user to tailor a program or an|
|processing_control_parm_name|,|3|,|algorithm to specific needs, such as outputting planetary|
|processing_control_parm_name|,|4|,|surface coordinates in planetocentric or planetographic|
|processing_control_parm_name|,|5|,|coordinates, specifying the units of the parameters to be|
|processing_control_parm_name|,|6|,|plotted or specifying the scale of a map to be output.|
|processing_level_desc|,|1|,|The processing_level_description element provides the|
|processing_level_desc|,|2|,|CODMAC standard definition corresponding to a particular|
|processing_level_desc|,|3|,|processing_level_id value.|
|processing_level_desc|,|300|,|Note:  For a fuller definition of CODMAC processing levels,|
|processing_level_desc|,|301|,|please refer to the PDS Data Preparation Workbook, Vol. 2.|
|processing_level_id|,|1|,|The processing_level_identification element identifies the|
|processing_level_id|,|2|,|processing level of a set of data according to the|
|processing_level_id|,|3|,|eight_level CODMAC standard.|
|processing_start_time|,|1|,|The processing_start_time element gives the beginning date|
|processing_start_time|,|2|,|(and time, where appropriate) of processing for a particular|
|processing_start_time|,|3|,|set of data.|
|processing_start_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|processing_stop_time|,|1|,|The processing_stop_time element gives the ending date (and|
|processing_stop_time|,|2|,|time, where appropriate) of processing for a particular set|
|processing_stop_time|,|3|,|of data.|
|processing_stop_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|producer_full_name|,|1|,|The producer_full_name element provides the full_name of the|
|producer_full_name|,|2|,|individual mainly responsible for the production of a data|
|producer_full_name|,|3|,|set.  See also:  full_name.|
|producer_full_name|,|300|,|Note:  This individual does not have to be registered with|
|producer_full_name|,|301|,|the PDS.|
|producer_id|,|1|,|The producer_id element provides a short name or acronym for|
|producer_id|,|2|,|the producer or producing team/group of a dataset.|
|producer_institution_name|,|1|,|The producer_institution_name element identifies a|
|producer_institution_name|,|2|,|university, research center, NASA center or other|
|producer_institution_name|,|3|,|institution associated with the production of a data set.|
|producer_institution_name|,|4|,|This would generally be an institution associated with the|
|producer_institution_name|,|5|,|element producer_full_name.|
|product_creation_time|,|1|,|The product_creation_time defines the UTC time when a|
|product_creation_time|,|2|,|product was created.|
|product_creation_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|product_data_set_id|,|1|,|The product_data_set_id element provides the data_set_id  of|
|product_data_set_id|,|2|,|a cataloged data set that resulted from the|
|product_data_set_id|,|3|,|application of the processing software to the source data|
|product_data_set_id|,|4|,|sets. The data set name associated with the product data set|
|product_data_set_id|,|5|,|is provided by the data_set_name element.|
|product_version_id|,|1|,|The product_version_id element identifies the version|
|product_version_id|,|2|,|of an individual product within a data set.  Example:|
|product_version_id|,|3|,|1.0, 2A, 1.2.3C.|
|product_version_id|,|501|,|Note: This is not the same as the data set version that is|
|product_version_id|,|502|,|an element of the data_set_id value.  Product_version_id is|
|product_version_id|,|503|,|intended for use within SFOC to identify separate iterations|
|product_version_id|,|504|,|of a given product, which will also have a unique file_name.|
|product_version_type|,|1|,|The product_version_type element identifies the version of|
|product_version_type|,|2|,|an individual data product.  It can be applied to any type|
|product_version_type|,|3|,|of data that might appear in several incarnations, including|
|product_version_type|,|4|,|ephemeris files, sequence files, or software.  Example|
|product_version_type|,|5|,|values:  VERSION 1, PREDICT, ACTUAL, DRAFT, PRELIMINARY,|
|product_version_type|,|6|,|FINAL, REVISION A.|
|programming_language_name|,|1|,|The programming_language_name element identifies the major|
|programming_language_name|,|2|,|programming language in which a given data processing|
|programming_language_name|,|3|,|program or algorithm is written.|
|publication_date|,|1|,|The publication_date element provides the date when a|
|publication_date|,|2|,|published item, such as a document or a compact disc, was|
|publication_date|,|3|,|issued.|
|publication_date|,|200|,|Formation rule:  YYYY-MM-DD|
|quantization_resolution|,|1|,|The quantization_resolution element provides the value of|
|quantization_resolution|,|2|,|the magnetic field which corresponds to a single count from|
|quantization_resolution|,|3|,|the magnetometer.|
|query_context|,|1|,|The query_context element identifies the context of|
|query_context|,|2|,|a query for the purpose of identifying an appropriate set|
|query_context|,|3|,|of standard values.  Example values: H (High Level),|
|query_context|,|4|,|F (Fields and Particles), I (Images).|
|query_desc|,|1|,|The query_desc element provides the ascii text description|
|query_desc|,|2|,|of a query used in the PDS.  These queries are also known|
|query_desc|,|3|,|as stored commands.|
|query_name|,|1|,|The query_name element provides a unique name assigned to a|
|query_name|,|2|,|pre-defined query used in the PDS.|
|rad_along_track_footprint_size|,|1|,| The rad_along_track_footprint_size provides the value of|
|rad_along_track_footprint_size|,|2|,|the along track dimension of the intersection of the SAR|
|rad_along_track_footprint_size|,|3|,|antenna (3dB one-way attenuation) cone with a sphere of|
|rad_along_track_footprint_size|,|4|,|radius average_planetary_radius.|
|rad_cross_track_footprint_size|,|1|,| The rad_cross_track_footprint_size element provides the|
|rad_cross_track_footprint_size|,|2|,|value of the cross track dimension of the intersection of|
|rad_cross_track_footprint_size|,|3|,|the SAR antenna (3dB one-way attenuation) cone with a|
|rad_cross_track_footprint_size|,|4|,|sphere of radius average_planetary_radius.|
|rad_emissivity_partial|,|1|,| The rad_emissivity_partial element provides the value of|
|rad_emissivity_partial|,|2|,|the partial derivative of surface_emissivity with respect|
|rad_emissivity_partial|,|3|,|to average_planetary_radius.|
|rad_flag2_group|,|1|,| Additional flag fields (unused).|
|rad_flag_group|,|1|,| The RAD_FLAG_GROUP element identifies the following flag|
|rad_flag_group|,|2|,|fields.|
|rad_flag_group|,|4|,|RR_GEOC=0x0001|
|rad_flag_group|,|6|,|Geometry values have been corrected|
|rad_flag_group|,|8|,|for ephemeris errors in the phase.|
|rad_flag_group|,|10|,|RR_RADC=0x0002|
|rad_flag_group|,|12|,|The average_planetary_radius value has been|
|rad_flag_group|,|14|,|corrected by altimeter radius values.|
|rad_flag_group|,|16|,|RR_NOS1=0x0004|
|rad_flag_group|,|18|,|sar_average_backscatter[0] value missing.|
|rad_flag_group|,|20|,|RR_NOS2=0x0008|
|rad_flag_group|,|22|,|sar_average_backscatter[1] value missing.|
|rad_flag_group|,|24|,|RR_BAD=0x0010|
|rad_flag_group|,|26|,|The elements brightness_temperature,|
|rad_flag_group|,|28|,|average_planetary_radius, planet_reading_system_temp,|
|rad_flag_group|,|30|,|assumed_warm_sky_temperature, rad_receiver_system_temp,|
|rad_flag_group|,|32|,|surface_emission_temperature, and surface_emissivity, and|
|rad_flag_group|,|34|,|surface_temperature should be ignored.|
|rad_flag_group|,|36|,|RR_CAL=0x0020|
|rad_flag_group|,|38|,|The spacecraft is operating in its 'radiometric|
|rad_flag_group|,|40|,|calibration' mode, in which the SAR boresight is pointed|
|rad_flag_group|,|42|,|away from the planet. The rad_footprint_latitude and|
|rad_flag_group|,|44|,|rad_footprint_longitude fields contain the boresight|
|rad_flag_group|,|46|,|latitude and longitude in the inertial (J2000) coordinate|
|rad_flag_group|,|48|,|system, not in VBF85.|
|rad_flag_group|,|50|,|RR_NRAD=0x0040|
|rad_flag_group|,|52|,|The average_planetary_radius value could not be estimated|
|rad_flag_group|,|54|,|from the topography model.|
|rad_flag_group|,|56|,|RR_RAD2=0x0080|
|rad_flag_group|,|58|,|This record was created under software version 2 or|
|rad_flag_group|,|60|,|higher, in which elements rad_emissivity_partial,|
|rad_flag_group|,|62|,|surface_temperature, raw_rad_antenna_power,|
|rad_flag_group|,|64|,|raw_rad_load_power, alt_skip_factor, alt_gain_factor,|
|rad_flag_group|,|68|,|and alt_coarse_resolution are significant.|
|rad_footprint_latitude|,|1|,| The rad_footprint_latitude (VBF85) element provides the|
|rad_footprint_latitude|,|2|,|value of the crust-fixed latitude, at|
|rad_footprint_latitude|,|3|,|rad_spacecraft_epoch_tdb_time, of the intersection of the|
|rad_footprint_latitude|,|4|,|antenna boresight and the planetary surface (a sphere of|
|rad_footprint_latitude|,|5|,|radius average_planetary_radius element).|
|rad_footprint_longitude|,|1|,| The rad_footprint_longitude (VBF85) element provides the|
|rad_footprint_longitude|,|2|,|crust-fixed longitude, at rad_spacecraft_epoch_tdb_time, of|
|rad_footprint_longitude|,|3|,|the intersection of the antenna boresight and the planetary|
|rad_footprint_longitude|,|4|,|surface (a sphere of radius average_planetary_radius).|
|rad_footprints|,|1|,| The footprints element provides the value of the number of|
|rad_footprints|,|2|,|Standard Format Data Units  in a specific orbit's|
|rad_footprints|,|3|,|radiometry data file.|
|rad_number|,|1|,| The rad_number element provides the value of the number|
|rad_number|,|2|,|assigned by the MSPF (Multimission SAR Processing Facility)|
|rad_number|,|3|,|SAR processor (from C-BIDR) to the burst header that|
|rad_number|,|4|,|contains the radiometer measurement referenced by this|
|rad_number|,|5|,|element. This is performed on every other burst, so|
|rad_number|,|6|,|rad_number will usually increase by 2 between records.|
|rad_partials_group|,|1|,| The rad_partials_group element provides the value of the|
|rad_partials_group|,|2|,|partials of the rad_footprint_latitude, the|
|rad_partials_group|,|3|,|rad_footprint_longitude, and the average_planetary_radius|
|rad_partials_group|,|4|,|elements with respect to the rad_spacecraft_position_vector|
|rad_partials_group|,|5|,|and rad_spacecraft_velocity_vector elements.|
|rad_receiver_system_temp|,|1|,| The rad_receiver_system_temp element provides the value of|
|rad_receiver_system_temp|,|2|,|the receiver input radiometer reading, converted to|
|rad_receiver_system_temp|,|3|,|equivalent noise temperature.  This is the difference|
|rad_receiver_system_temp|,|4|,|between raw_rad_antenna_power and raw_rad_load_power,|
|rad_receiver_system_temp|,|5|,|converted to equivalent noise temperature and compensated|
|rad_receiver_system_temp|,|6|,|for changes in receiver gain and temperature.|
|rad_spacecraft_epoch_tdb_time|,|1|,| The rad_spacecraft_epoch_tdb_time element provides the|
|rad_spacecraft_epoch_tdb_time|,|2|,|value of the ephemeris time at which the radiometry|
|rad_spacecraft_epoch_tdb_time|,|3|,|measurement was made.|
|rad_spacecraft_epoch_tdb_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|rad_spacecraft_position_vector|,|1|,| The rad_spacecraft_position_vector element provides the|
|rad_spacecraft_position_vector|,|2|,|value of the spacecraft position at|
|rad_spacecraft_position_vector|,|3|,|rad_spacecraft_epoch_tdb_time, relative to the Venus center|
|rad_spacecraft_position_vector|,|4|,|of mass, expressed in inertial coordinates in the J2000|
|rad_spacecraft_position_vector|,|5|,|coordinate system.|
|rad_spacecraft_velocity_vector|,|1|,| The rad_spacecraft_velocity_vector element provides the|
|rad_spacecraft_velocity_vector|,|2|,|value of the spacecraft velocity at|
|rad_spacecraft_velocity_vector|,|3|,|rad_spacecraft_epoch_tdb_time, relative to the Venus center|
|rad_spacecraft_velocity_vector|,|4|,|of mass, expressed in inertial coordinates in the J2000|
|rad_spacecraft_velocity_vector|,|5|,|coordinate system.|
|range_sharp_echo_profile|,|1|,| The range_sharp_echo_profile element provides the value of|
|range_sharp_echo_profile|,|2|,|the power vs. time echo profile, at half-baud (0.21|
|range_sharp_echo_profile|,|3|,|microsecond) intervals, assembled from up to 16 frequency|
|range_sharp_echo_profile|,|4|,|components, each shifted in time so as to align their|
|range_sharp_echo_profile|,|5|,|rising edges. This profile yields the best estimate of the|
|range_sharp_echo_profile|,|6|,|two-way echo time, and hence the value of the|
|range_sharp_echo_profile|,|7|,|derived_planetary_radius element.|
|range_sharp_fit|,|1|,| The range_sharp_fit element provides the value of the|
|range_sharp_fit|,|2|,|parameter which measures the correlation between the|
|range_sharp_fit|,|3|,|observed range_sharp_echo_profile and the theoretical|
|range_sharp_fit|,|4|,|template best_range_sharp_model_tmplt elements.|
|range_sharp_looks|,|1|,| The range_sharp_looks element provides the value of the|
|range_sharp_looks|,|2|,|number of equivalent looks of statistically independent|
|range_sharp_looks|,|3|,|measurements of echo profile that were summed to produce|
|range_sharp_looks|,|4|,|the values for the range_sharp_echo_profile element.|
|range_sharp_prof_corrs_index|,|1|,| The range_sharp_prof_corrs_index element provides the|
|range_sharp_prof_corrs_index|,|2|,|value of the index of the element in|
|range_sharp_prof_corrs_index|,|3|,|range_sharp_echo_profile that corresponds to the first|
|range_sharp_prof_corrs_index|,|4|,|element in best_range_sharp_model_tmplt[0]. The indices|
|range_sharp_prof_corrs_index|,|5|,|start at zero.|
|range_sharp_scaling_factor|,|1|,| The range_sharp_scaling_factor element provides the value|
|range_sharp_scaling_factor|,|2|,|of the conversion factor for the best_range_model_tmplt and|
|range_sharp_scaling_factor|,|3|,|the range_sharp_echo_profile element that multiplies the|
|range_sharp_scaling_factor|,|4|,|integer array of the best_range_model_tmplt and|
|range_sharp_scaling_factor|,|5|,|range_sharp_echo_profile elements to yield their physical|
|range_sharp_scaling_factor|,|6|,|values, expressed as specific radar cross-sections in units|
|range_sharp_scaling_factor|,|7|,|of km**2.|
|rationale_desc|,|1|,|The rationale_desc element describes the rationale for|
|rationale_desc|,|2|,|performing a particular observation.|
|raw_rad_antenna_power|,|1|,| The raw_rad_antenna_power element provides the value of|
|raw_rad_antenna_power|,|2|,|the radiometer noise power when the receiver is connected|
|raw_rad_antenna_power|,|3|,|to the SAR antenna. It is corrected for systematic errors|
|raw_rad_antenna_power|,|4|,|resulting from leakage of the altimeter signal.|
|raw_rad_load_power|,|1|,| The raw_rad_load_power element provides the value of the|
|raw_rad_load_power|,|2|,|radiometer noise power when the receiver is connected to a|
|raw_rad_load_power|,|3|,|load at a known temperature. It is averaged over as many as|
|raw_rad_load_power|,|4|,|10 successive measurements and corrected for systematic|
|raw_rad_load_power|,|5|,|errors resulting from leakage of the altimeter signal.|
|receiver_noise_calibration|,|1|,| The receiver_noise_calibration element provides the value|
|receiver_noise_calibration|,|2|,|of a measure of the altimeter noise background, obtained|
|receiver_noise_calibration|,|3|,|from the pulse- compressed altimeter signals by the mgmtac|
|receiver_noise_calibration|,|4|,|phase of the altimetry and radiometry data reduction|
|receiver_noise_calibration|,|5|,|program.|
|record_bytes|,|1|,|The record_bytes element indicates the number of bytes in a|
|record_bytes|,|2|,|physical file record, including record terminators and|
|record_bytes|,|3|,|separators.|
|record_bytes|,|300|,|Note:  In the PDS, the use of record_bytes, along|
|record_bytes|,|301|,|with other file-related data elements is fully described in|
|record_bytes|,|302|,|the Data Preparation Workbook.|
|record_type|,|1|,|The record_type element indicates the record format of a|
|record_type|,|2|,|file.|
|record_type|,|300|,|Note:  In the PDS, when record_type is used in a|
|record_type|,|301|,|detached label file it always describes its corresponding|
|record_type|,|302|,|detached data file, not the label file itself.|
|record_type|,|303|,|The use of record_type along with other file-related data|
|record_type|,|304|,|elements is fully described in the Data Preparation|
|record_type|,|305|,|Workbook.|
|reference_desc|,|1|,|The reference_description element provides a standard|
|reference_desc|,|2|,|reference citation in the format used by the Journal of|
|reference_desc|,|3|,|Geophysical Research.  In the case where the reference has|
|reference_desc|,|4|,|more than one author, all authors should be listed. This|
|reference_desc|,|5|,|element enables material such as articles, books, JPL|
|reference_desc|,|6|,|documents, etc. to be completely referenced so that they may|
|reference_desc|,|7|,|be used to provide more detailed information than may be|
|reference_desc|,|8|,|available elsewhere.|
|reference_key_id|,|1|,|The reference_key_id element provides the catalog with|
|reference_key_id|,|2|,|an identifier for a reference document.  Additionally, it|
|reference_key_id|,|3|,|may be used in various catalog descriptions, for example|
|reference_key_id|,|4|,|in data_set_desc, as a shorthand notation of a document|
|reference_key_id|,|5|,|reference.|
|reference_key_id|,|8|,|The reference_key_id element is composed according to the|
|reference_key_id|,|9|,|following guidelines:|
|reference_key_id|,|12|,|1.  if there is an author for the publication, the general|
|reference_key_id|,|13|,|rule is:|
|reference_key_id|,|16|,|  REFERENCE_KEY_ID = <author's last name><year><letter>,|
|reference_key_id|,|19|,|     where|
|reference_key_id|,|21|,|     <author's last name> is a maximum of 15 characters,|
|reference_key_id|,|23|,|          and may need to be truncated.|
|reference_key_id|,|26|,|     <year> is 4 characters for the year published.|
|reference_key_id|,|29|,|     <letter> is optional and consist of one character|
|reference_key_id|,|31|,|           used to distinguish multiple papers by the|
|reference_key_id|,|33|,|           same author(s) in the same year.|
|reference_key_id|,|38|,|   The following variations apply:|
|reference_key_id|,|41|,|   a.  If there is one author:|
|reference_key_id|,|43|,|    <author's last name><year>|
|reference_key_id|,|46|,|    Example value:  SCARF1980|
|reference_key_id|,|49|,|   b.  If there are two authors:|
|reference_key_id|,|51|,|    <first author's last name>&<second author's last name>|
|reference_key_id|,|53|,|    <year>|
|reference_key_id|,|56|,|    Example value:  SCARF&GURNETT1977|
|reference_key_id|,|59|,|  c . If there are three or more authors:|
|reference_key_id|,|61|,|    <first author's last name>ETAL<year>|
|reference_key_id|,|64|,|    Example value:  GURNETTETAL1979|
|reference_key_id|,|67|,|   d.  If one author has the same last name as another:|
|reference_key_id|,|69|,|    <author's last name>,<author's first initial>|
|reference_key_id|,|71|,|    <year published>|
|reference_key_id|,|74|,|    Example value:  FREUD,A1935|
|reference_key_id|,|77|,|   e.  If the same author(s) published more than one paper|
|reference_key_id|,|79|,|    in the same year:|
|reference_key_id|,|82|,|      <author's last name><year><letter>|
|reference_key_id|,|84|,|      or|
|reference_key_id|,|86|,|      <first author's last name>&<second author's last name>|
|reference_key_id|,|88|,|      <year><letter>|
|reference_key_id|,|90|,|      or|
|reference_key_id|,|92|,|      <first author's last name>ETAL<year><letter>|
|reference_key_id|,|95|,|    Example values:  SCARF1980A|
|reference_key_id|,|97|,|                     SCARF&GURNETT1977B|
|reference_key_id|,|100|,|2.  If there is no author for the publication, the general|
|reference_key_id|,|102|,|rule is:|
|reference_key_id|,|105|,| REFERENCE_KEY_ID = <journal name><document identification>|
|reference_key_id|,|108|,| where|
|reference_key_id|,|110|,| <journal name> is a maximum of 10 characters, and|
|reference_key_id|,|112|,|      may need to be abbreviated|
|reference_key_id|,|114|,| <document identification> is a maximum of 10|
|reference_key_id|,|116|,|      characters.  This id may consist of a volume number,|
|reference_key_id|,|118|,|      and/or document or issue number, and/or year of|
|reference_key_id|,|120|,|      publication.|
|reference_key_id|,|123|,|     Example values:  SCIENCEV215N4532|
|reference_key_id|,|125|,|                      JGRV88|
|reference_key_id|,|127|,|                      JPLD-2468|
|reference_latitude|,|1|,|The reference_latitude element provides the new zero|
|reference_latitude|,|2|,|latitude in a rotated spherical coordinate system that was|
|reference_latitude|,|3|,|used in a given map_projection_type.|
|reference_longitude|,|1|,|The reference_longitude element defines the zero longitude|
|reference_longitude|,|2|,|in a rotated spherical coordinate system that was used in a|
|reference_longitude|,|3|,|given map_projection_type.|
|reference_object_name|,|1|,|The reference_object_name element identifies the point,|
|reference_object_name|,|2|,|vector, or plane used as the origin from which an angle or|
|reference_object_name|,|3|,|a distance is measured.|
|reference_object_name|,|4|,|As an example, the reference object could be the center of|
|reference_object_name|,|5|,|a given planet (a point), the spacecraft z_axis (a vector)|
|reference_object_name|,|6|,|or the equatorial plane.|
|reference_target_name|,|1|,|The reference_target_name element provides the name of the|
|reference_target_name|,|2|,|target body being used as the reference to help define a|
|reference_target_name|,|3|,|particular vector_component_identification.|
|reference_target_name|,|4|,|For example, the RJ\$ vector component is defined with the|
|reference_target_name|,|5|,|spacecraft as the reference target.|
|region_desc|,|1|,|The region_description element describes a particular|
|region_desc|,|2|,|region of a planetary surface, indicating its historical|
|region_desc|,|3|,|significance, identifying major geological features and|
|region_desc|,|4|,|providing other descriptive information.|
|region_name|,|1|,|The region_name element identifies a region of a planetary|
|region_name|,|2|,|surface.  In many cases, the name of a region derives from|
|region_name|,|3|,|the major geologic features found within the region.|
|registration_date|,|1|,|The registration_date element provides the date as of which|
|registration_date|,|2|,|an individual is registered as an authorized user of the PDS|
|registration_date|,|3|,|system.|
|registration_date|,|200|,|Formation rule:  YYYY-MM-DD|
|remote_node_privileges_id|,|1|,|The remote_node_priviledges_id element identifies the|
|remote_node_privileges_id|,|2|,|systems at a remote node (or nodes) which a user is|
|remote_node_privileges_id|,|3|,|priviledged to access.|
|request_desc|,|1|,|The request_desc element describes a user's request for|
|request_desc|,|2|,|support.|
|request_time|,|1|,|The request_time element provides the date (and time, where|
|request_time|,|2|,|appropriate) at which a user's request was received by the|
|request_time|,|3|,|Customer Support function.|
|required_memory_bytes|,|1|,|The required_memory_bytes element indicates the amount of|
|required_memory_bytes|,|2|,|memory, in bytes, required to run the subject software.|
|research_topic_desc|,|1|,|The research_topic_desc element describes the topic of|
|research_topic_desc|,|2|,|scientific research identified by the research_topic_name|
|research_topic_desc|,|3|,|element.|
|research_topic_name|,|1|,|The research_topic_name element provides the name of a topic|
|research_topic_name|,|2|,|of scientific research.|
|resolution_desc|,|1|,|The resolution_desc element describes the resolution of and|
|resolution_desc|,|2|,|the approach used to resolve a user's request for support.|
|resolution_time|,|1|,|The resolution_time element provides the date (and time,|
|resolution_time|,|2|,|where appropriate) as of which a user's request is resolved.|
|reticle_point_number|,|1|,|The reticle_point_number element provides the number of an|
|reticle_point_number|,|2|,|image reticle point, as follows:  1  upper left, 3 - upper|
|reticle_point_number|,|3|,|right, 5 - middle, 7 - lower left, 9 - lower right.|
|revolution_period|,|1|,|The revolution_period element provides the time period of|
|revolution_period|,|2|,|revolution of a solar system object about its spin axis.|
|right_ascension|,|1|,|The right_ascension element provides the right ascension|
|right_ascension|,|2|,|value. Right_ascension is defined as the arc of the|
|right_ascension|,|3|,|celestial equator between the vernal equinox and the point|
|right_ascension|,|4|,|where the hour circle through the given body intersects the|
|right_ascension|,|5|,|Earth's mean equator (reckoned eastward).  See declination.|
|ring_system_summary|,|1|,|The ring_system_summary element provides a brief and|
|ring_system_summary|,|2|,|general description of the rings or ring_like features|
|ring_system_summary|,|3|,|associated with a particular solar system body.|
|role_desc|,|1|,|The role_desc element describes the role of an individual|
|role_desc|,|2|,|during his or her association with a particular institution.|
|role_desc|,|3|,|Note that the term 'role' is a more specific|
|role_desc|,|4|,|characterization of the individual's activities than is|
|role_desc|,|5|,|'specialty' (see the specialty_name element).|
|rotation_direction|,|1|,|The rotation_direction element provides the direction|
|rotation_direction|,|2|,|of rotation as viewed from the north pole of the 'invariable|
|rotation_direction|,|3|,|plane of the solar system', which is the plane passing|
|rotation_direction|,|4|,|through the center of mass of the solar system and|
|rotation_direction|,|5|,|perpendicular to the angular momentum vector of the solar|
|rotation_direction|,|6|,|system for clockwise rotation, and SYNCHRONOUS for|
|rotation_direction|,|7|,|satellites which are tidally locked with the primary.|
|rotation_direction|,|8|,|Sidereal_rotation_ period and rotation_direction_type are|
|rotation_direction|,|9|,|unknown for a number of satellites, and are Not Applicable|
|rotation_direction|,|10|,|(N/A) for satellites which are tumbling.|
|rotational_element_desc|,|1|,|The rotational_element_description element describes the|
|rotational_element_desc|,|2|,|standard used for the definition of a planet's pole|
|rotational_element_desc|,|3|,|orientation and prime meridian.  The description defines|
|rotational_element_desc|,|4|,|the right ascension and the declination values used to|
|rotational_element_desc|,|5|,|define the planet pole, and the spin angle value of the|
|rotational_element_desc|,|6|,|planet referenced to a standard time (typically EME1950 or|
|rotational_element_desc|,|7|,|J2000 time is used).  Periodically, the right ascension,|
|rotational_element_desc|,|8|,|declination, and spin values of the planets are updated by|
|rotational_element_desc|,|9|,|the IAU/IAG/COOSPAR Working Group On Cartographic|
|rotational_element_desc|,|10|,|Coordinates and Rotational Elements because an unambiguous|
|rotational_element_desc|,|11|,|definition of a planet's coordinate system requires these|
|rotational_element_desc|,|12|,|values.|
|row_bytes|,|1|,|The row_bytes element represents the number of bytes in|
|row_bytes|,|2|,|each data object row.|
|row_bytes|,|300|,|Note:  In the PDS, if no value for|
|row_bytes|,|301|,|this element is supplied, the ODL parsing system will|
|row_bytes|,|302|,|substitute the value of the RECORD_BYTES specified in the|
|row_bytes|,|303|,|FILE object.|
|row_prefix_bytes|,|1|,|The row_prefix_bytes element indicates the number of bytes|
|row_prefix_bytes|,|2|,|prior to the start of the data content of each row of a|
|row_prefix_bytes|,|3|,|table. The value must represent an integral number of|
|row_prefix_bytes|,|4|,|bytes.|
|row_prefix_structure|,|1|,|The row_prefix_structure element indicates a pointer to a|
|row_prefix_structure|,|2|,|file that defines the structure of the row prefix bytes.|
|row_prefix_structure|,|3|,|See also:  file_name|
|row_prefix_structure|,|300|,|Note:  In ODL convention the|
|row_prefix_structure|,|301|,|circumflex (^) indicates a pointer, therefore the|
|row_prefix_structure|,|302|,|circumflex must precede the data element name to indicate|
|row_prefix_structure|,|303|,|that it is a pointer to a file. Example:|
|row_prefix_structure|,|304|,|^ROW_PREFIX_STRUCTURE = 'myfile.fmt'.|
|row_suffix_bytes|,|1|,|The row_suffix_bytes element indicates the number of bytes|
|row_suffix_bytes|,|2|,|following the data at the end of each row. The value must|
|row_suffix_bytes|,|3|,|be an integral number of bytes.|
|row_suffix_structure|,|1|,|The row_suffix_structure element indicates a pointer to a|
|row_suffix_structure|,|2|,|file that defines the structure of the ROW_SUFFIX_BYTES.|
|row_suffix_structure|,|3|,|See also: file_name|
|row_suffix_structure|,|300|,|Note:  In ODL convention the|
|row_suffix_structure|,|301|,|circumflex (^) indicates a pointer, therefore the|
|row_suffix_structure|,|302|,|circumflex must precede the data element name to indicate|
|row_suffix_structure|,|303|,|that it is a pointer to a file.  Example:|
|row_suffix_structure|,|304|,|^ROW_SUFFIX_STRUCTURE = 'myfile.fmt'.|
|rows|,|1|,|The rows element represents the number of rows in a data|
|rows|,|2|,|object.|
|rows|,|300|,|Note:  In PDS, the term 'rows' is synonymous with|
|rows|,|301|,|'records'.  In PDS attached labels, the number of rows is|
|rows|,|302|,|equivalent to the number of file_records minus the number|
|rows|,|303|,|of label_records, as indicated in the file_object|
|rows|,|304|,|definition.|
|sample_bit_mask|,|1|,|The sample_bit_mask element identifies the active bits in a|
|sample_bit_mask|,|2|,|sample.|
|sample_bit_mask|,|300|,|Note:  In the PDS, the domain of sample_bit_mask is|
|sample_bit_mask|,|301|,|dependent upon the currently-described value in the|
|sample_bit_mask|,|302|,|sample_bits element and only applies to integer values.|
|sample_bit_mask|,|303|,|For an 8-bit sample where all bits are active the|
|sample_bit_mask|,|304|,|sample_bit_mask would be 2#11111111#.|
|sample_bits|,|1|,|The sample_bits element indicates the stored number of|
|sample_bits|,|2|,|bits, or units of binary information, contained in a|
|sample_bits|,|3|,|line_sample value.|
|sample_type|,|1|,|The sample_type element indicates the data storage|
|sample_type|,|2|,|representation of sample value.|
|sampling_desc|,|1|,|The sampling_description element describes how instrument|
|sampling_desc|,|2|,|parameters are sampled within an instrument or a section of|
|sampling_desc|,|3|,|an instrument.  Generally, this includes information on the|
|sampling_desc|,|4|,|timing of samples and how they are taken as a function of|
|sampling_desc|,|5|,|energy, frequency, wavelength, position, etc.|
|sampling_factor|,|1|,|The sampling_factor element provides the value N, where|
|sampling_factor|,|2|,|every Nth data point was kept from the original data set by|
|sampling_factor|,|3|,|selection, averaging, or taking the median.|
|sampling_factor|,|300|,|Note:  When applied to an image object, the single value|
|sampling_factor|,|301|,|represented in sampling_factor applies to both the lines|
|sampling_factor|,|302|,|and the samples.  When applied to a table object, the value|
|sampling_factor|,|303|,|applies only to the rows.|
|sampling_parameter_interval|,|1|,|The sampling_parameter_interval element identifies the|
|sampling_parameter_interval|,|2|,|spacing of points at which data are sampled and at which a|
|sampling_parameter_interval|,|3|,|value for an instrument or dataset parameter is available.|
|sampling_parameter_interval|,|4|,|This sampling interval can be either the original (raw)|
|sampling_parameter_interval|,|5|,|sampling or the result of some resampling process.|
|sampling_parameter_interval|,|6|,|For example, in 48-second magnetometer data the sampling|
|sampling_parameter_interval|,|7|,|interval is 48.|
|sampling_parameter_interval|,|8|,|The sampling parameter (time, in the example) is identified|
|sampling_parameter_interval|,|9|,|by the sampling_parameter_name element.|
|sampling_parameter_name|,|1|,|The sampling_parameter_name element provides the name of|
|sampling_parameter_name|,|2|,|the parameter which determines the sampling interval of a|
|sampling_parameter_name|,|3|,|particular instrument or dataset parameter.|
|sampling_parameter_name|,|4|,|For example, magnetic field intensity is sampled in time|
|sampling_parameter_name|,|5|,|increments, and a spectrum is sampled in wavelength or|
|sampling_parameter_name|,|6|,|frequency.|
|sampling_parameter_resolution|,|1|,|The sampling_parameter_resolution element identifies the|
|sampling_parameter_resolution|,|2|,|resolution along the sampling parameter axis.|
|sampling_parameter_resolution|,|3|,|For example, spectral data may be sampled every 0.0005 cm|
|sampling_parameter_resolution|,|4|,|in wavelength, but the smallest resolvable width of a|
|sampling_parameter_resolution|,|5|,|feature could be 0.001 cm.  In this example, the sampling|
|sampling_parameter_resolution|,|6|,|parameter resolution would be 0.001.|
|sampling_parameter_resolution|,|7|,|Note that the unit element identifies the unit of measure|
|sampling_parameter_resolution|,|8|,|of the sampling parameter resolution.|
|sampling_parameter_unit|,|1|,|The sampling_parameter_unit element specifies the unit of|
|sampling_parameter_unit|,|2|,|measure of associated data sampling parameters.|
|sar_average_backscatter|,|1|,| The sar_average_backscatter element provides the values of|
|sar_average_backscatter|,|2|,|a pair of running averages of SAR image pixel values,|
|sar_average_backscatter|,|3|,|sar_average_backscatter[0] taken from pixels lying westward|
|sar_average_backscatter|,|4|,|of the antenna boresight, and sar_average_backscatter[1]|
|sar_average_backscatter|,|5|,|taken from pixels lying to the east of it.|
|sar_footprint_size|,|1|,| The sar_footprint_size element provides the value of the|
|sar_footprint_size|,|2|,|approximate diameter of the surface footprint represented|
|sar_footprint_size|,|3|,|by the SAR backscatter values which are provided by the|
|sar_footprint_size|,|4|,|sar_average_backscatter element.|
|scaled_image_height|,|1|,|The scaled_image_height element provides the height on the|
|scaled_image_height|,|2|,|target surface of the projection of an image onto the|
|scaled_image_height|,|3|,|surface.|
|scaled_image_height|,|4|,|This is the distance on the surface between intercept|
|scaled_image_height|,|5|,|points 2 (upper middle) and 8 (lower middle).|
|scaled_image_width|,|1|,|The scaled_image_width element provides the width on the|
|scaled_image_width|,|2|,|target surface of the projection of an image onto the|
|scaled_image_width|,|3|,|surface.|
|scaled_image_width|,|4|,|This is the distance on the surface between intercept|
|scaled_image_width|,|5|,|points 4 (middle left) and 6 (middle right).|
|scaled_pixel_height|,|1|,|The scaled_pixel_height element provides the scaled height|
|scaled_pixel_height|,|2|,|of a pixel at a given reticle point within an image.|
|scaled_pixel_height|,|3|,|Scaled pixel height is defined as the height on the surface|
|scaled_pixel_height|,|4|,|of the target of the projection of a pixel onto the surface.|
|scaled_pixel_width|,|1|,|The scaled_pixel_width element provides the scaled width|
|scaled_pixel_width|,|2|,|of a pixel at a given reticle point within an image.|
|scaled_pixel_width|,|3|,|Scaled pixel width is defined as the width on the surface|
|scaled_pixel_width|,|4|,|of the target of the projection of a pixel onto the surface.|
|scaling_factor|,|1|,|The scaling factor element provides the constant value by|
|scaling_factor|,|2|,|which the stored value is multiplied. See also: offset.|
|scaling_factor|,|300|,|Note:  Expressed as an equation: true value = offset value|
|scaling_factor|,|301|,|+ (scaling factor x stored value).|
|scaling_factor*|,|1|,| The scaling_factor element provides the value of the|
|scaling_factor*|,|2|,|conversion factor for the best_non_range_sharp_model_tpt|
|scaling_factor*|,|3|,|and the non_range_sharp_echo_prof element that multiplies|
|scaling_factor*|,|4|,|the integer array elements of the|
|scaling_factor*|,|5|,|best_non_range_sharp_model_tpt and the|
|scaling_factor*|,|6|,|non_range_sharp_echo_prof to yield their physical values,|
|scaling_factor*|,|7|,|expressed as equivalent radar cross-sections in units of|
|scaling_factor*|,|8|,|km**2.|
|scaling_factor*|,|300|,|Note:  Scaling_factor* is marked with an asterix because it|
|scaling_factor*|,|301|,|duplicates an already-existing keyword in the common list|
|scaling_factor*|,|302|,|of data elements.|
|scan_mode_id|,|1|,|The scan_mode_id element provides the identification of|
|scan_mode_id|,|2|,|different internal rates of acquiring data for an|
|scan_mode_id|,|3|,|instrument.  For example, the rate at which an imaging|
|scan_mode_id|,|4|,|instrument acquires an image, scan_rate, is typically|
|scan_mode_id|,|5|,|expressed as a ratio, and is not to be confused with the|
|scan_mode_id|,|6|,|rate at which a spacecraft scan platform moves. Example|
|scan_mode_id|,|7|,|values:  1:1, 2:1.|
|scet_start_time|,|1|,|The scet_start_time element is defined as an alias for|
|scet_start_time|,|2|,|start_time for Magellan mission operations files in SFOC.|
|scet_stop_time|,|1|,|The scet_stop_time element is defined as an alias for|
|scet_stop_time|,|2|,|stop_time for Magellan mission operations files only.|
|scientific_objectives_summary|,|1|,|The scientific_objectives_summary element explains the|
|scientific_objectives_summary|,|2|,|science data_gathering purposes for a particular type of|
|scientific_objectives_summary|,|3|,|observation, for a particular observation sequence or for|
|scientific_objectives_summary|,|4|,|which an instrument was designed.|
|scientist_funding_id|,|1|,|The scientist_funding_id is the NASA code which supplies|
|scientist_funding_id|,|2|,|funding to the scientist.|
|sclk_start_value|,|1|,|The sclk_start_value element is an alias for spacecraft_|
|sclk_start_value|,|2|,|clock_start_count which is used only by SFOC-Magellan|
|sclk_start_value|,|3|,|mission operations data files.|
|sclk_stop_value|,|1|,|The sclk_stop_value element is an alias for spacecraft_|
|sclk_stop_value|,|2|,|clock_stop_count which is used only in SFOC-Magellan|
|sclk_stop_value|,|3|,|mission operations files.|
|screen_id|,|1|,|The screen_id element is a unique identifier assigned to a|
|screen_id|,|2|,|screen which is used by software in building a screen for a|
|screen_id|,|3|,|display device.|
|second_standard_parallel|,|1|,|Please refer to the definition for first_standard_parallel|
|second_standard_parallel|,|2|,|element to see how second_standard_parallel is defined.|
|section_id|,|1|,|The section_id element provides a unique identifier for a|
|section_id|,|2|,|section of an instrument.  An instrument section is a|
|section_id|,|3|,|logical view of an instrument's operating functions, and is|
|section_id|,|4|,|distinct from the instrument's physical composition.|
|section_id|,|5|,|Essentially, instrument sections are a device to describe|
|section_id|,|6|,|the instrument's functioning in terms of a set of 'black|
|section_id|,|7|,|boxes', which are themselves described parametrically by the|
|section_id|,|8|,|data which are produced.  Various operational parts of the|
|section_id|,|9|,|instrument, such as detectors, filters, and electronics, are|
|section_id|,|10|,|considered to participate by providing data from a section,|
|section_id|,|11|,|but have no direct physical relationship with the section,|
|section_id|,|12|,|since the section is not a physical object.  Instrument|
|section_id|,|13|,|modes consist of sets of sections, and the physical|
|section_id|,|14|,|implementation of a mode is the union of those physical|
|section_id|,|15|,|units which are processing data for each section|
|section_id|,|16|,|participating in the mode.|
|sef_creation_time|,|1|,|This element is unique to the SFOC-MGN KEY_TIMES data file.|
|sef_creation_time|,|2|,|It defines the time of creation of the source sequence file.|
|selection_query_desc|,|1|,|The selection_query_description element provides a query|
|selection_query_desc|,|2|,|statement, in Standard Query Language (SQL) or another|
|selection_query_desc|,|3|,|query language, which constrains the set of items|
|selection_query_desc|,|4|,|requested in an order.|
|sensitivity_desc|,|1|,|The sensitivity_description element provides a textual|
|sensitivity_desc|,|2|,|description of the minimum response threshold of a|
|sensitivity_desc|,|3|,|detector.|
|seq_id|,|1|,|The seq_id element provides an identification of the|
|seq_id|,|2|,|spacecraft sequence associated with the given product.|
|sequence_number|,|1|,|The sequence_number element identifies a particular|
|sequence_number|,|2|,|sequence within a revolution.|
|sequence_number|,|3|,|The first sequence in each revolution is numbered 1.|
|sequence_number|,|4|,|Subsequent sequences in a revolution--through the last|
|sequence_number|,|5|,|sequence which began in that revolution--are numbered|
|sequence_number|,|6|,|consecutively.|
|sequence_samples|,|1|,|The sequence_samples element specifies the number of|
|sequence_samples|,|2|,|samples in a given observation sequence.|
|sequence_title|,|1|,|The sequence_title element provides the title assigned to a|
|sequence_title|,|2|,|particular observation sequence during planning or data|
|sequence_title|,|3|,|processing.|
|sfdu_format_id|,|1|,|The sfdu_format_id element provides the 12-character|
|sfdu_format_id|,|2|,|Standard Format Data Unit (SFDU) identification for a|
|sfdu_format_id|,|3|,|particular set of data.|
|sfdu_label_and_length|,|1|,| The SFDU_label_and_length element identifies the label and|
|sfdu_label_and_length|,|2|,|length of the Standard Format Data Unit (SFDU).|
|shipping_address_line|,|1|,|The shipping_address_line element indicates the address to|
|shipping_address_line|,|2|,|which a PDS client has requested PDS data set orders be|
|shipping_address_line|,|3|,|sent.  The address may consist of many sixty (60) character|
|shipping_address_line|,|4|,|lines.|
|shipping_carrier_name|,|1|,|The shipping_carrier_name element identifies a shipping|
|shipping_carrier_name|,|2|,|carrier for use in distributing data.|
|shutter_mode_id|,|1|,|The shutter_mode_id element identifies the state of an|
|shutter_mode_id|,|2|,|imaging instrument's shutter during image acquisition. Note:|
|shutter_mode_id|,|3|,|the instrument shutter mode affects the radiometric|
|shutter_mode_id|,|4|,|properties of the camera. Example values: (VOYAGER) NAONLY -|
|shutter_mode_id|,|5|,|narrow angle camera shuttered only, WAONLY - wide angle|
|shutter_mode_id|,|6|,|camera shuttered only, BOTSIM - both cameras shuttered|
|shutter_mode_id|,|7|,|simultaneously, BSIMAN - BOTSIM mode followed by NAONLY,|
|shutter_mode_id|,|8|,|BODARK - shutter remained closed for narrow and wide angle|
|shutter_mode_id|,|9|,|camera, NADARK - narrow angle read out without shuttering,|
|shutter_mode_id|,|10|,|WADARK - wide angle read out without shuttering.|
|sidereal_rotation_period|,|1|,|The sidereal_rotation_period element provides the time|
|sidereal_rotation_period|,|2|,|period required for a solar system object to complete one|
|sidereal_rotation_period|,|3|,|full rotation about its primary, with respect to the|
|sidereal_rotation_period|,|4|,|stars.|
|signal_quality_indicator|,|1|,| The signal_quality_indicator element provides a measure of|
|signal_quality_indicator|,|2|,|the signal-to- noise-ratio of the measurement of the|
|signal_quality_indicator|,|3|,|derived_thresh_detector_index value. It is the ratio|
|signal_quality_indicator|,|4|,|between the sum of the 10 successive values of|
|signal_quality_indicator|,|5|,|range_sharp_echo_profile, starting 10 values after the|
|signal_quality_indicator|,|6|,|element numbered by the derived_thresh_detector_index|
|signal_quality_indicator|,|7|,|element value, to the 10 successive values of|
|signal_quality_indicator|,|8|,|range_sharp_echo_profile, starting 20 values before the|
|signal_quality_indicator|,|9|,|element numbered by the derived_thresh_detector_index|
|signal_quality_indicator|,|10|,|element value. This ratio is expressed in decibels.|
|site_id|,|1|,|Short identifier for each CMD site.  See CMD Subsystem doc.|
|site_name|,|1|,|The site_name element is used to describe the spacecraft|
|site_name|,|2|,|commanding site for the SFOC CMD subsystem.  Values include|
|site_name|,|3|,|MASTER, MCCC, SEQTRAN, GSOC.|
|slant_distance|,|1|,|The slant_distance element provides a measure of the|
|slant_distance|,|2|,|distance from the spacecraft to the intercept point on the|
|slant_distance|,|3|,|body surface.|
|software_accessibility_desc|,|1|,|The software_access_desc element provides a description of|
|software_accessibility_desc|,|2|,|the software's accessibility related to the software_type|
|software_accessibility_desc|,|3|,|element. For example, software with a software_type of PIN|
|software_accessibility_desc|,|4|,|implies that the software accessibility is 'accessible|
|software_accessibility_desc|,|5|,|through the PDS catalog system.' Software with a|
|software_accessibility_desc|,|6|,|software_type of NIN implies that the software accessibility|
|software_accessibility_desc|,|7|,|is 'not accessible through the PDS catalog system  - Contact|
|software_accessibility_desc|,|8|,|Node.'|
|software_desc|,|1|,|The software_desc element describes the functions performed|
|software_desc|,|2|,|by the data processing software.  If the subject software is|
|software_desc|,|3|,|a program library, this element may provide a list of the|
|software_desc|,|4|,|contents of the library.|
|software_flag|,|1|,|The software_flag element is a yes-or-no flag which|
|software_flag|,|2|,|indicates whether documented software exists which can be|
|software_flag|,|3|,|used to process this data set. (Currently this software may|
|software_flag|,|4|,|be either partially-integrated (PIN) or non-integrated|
|software_flag|,|5|,|(NIN) software).|
|software_name|,|1|,|The software_name element identifies data processing|
|software_name|,|2|,|software such as a program or a program library.|
|software_release_date|,|1|,|The software_release_date element provides the date as of|
|software_release_date|,|2|,|which a program was released for use.|
|software_release_date|,|200|,|Formation rule:  YYYY-MM-DD|
|software_type|,|1|,|The software_type element associates a PDS software type|
|software_type|,|2|,|with the processing software. This type can be either PIN|
|software_type|,|3|,|(partially integrated) or NIN (non integrated) software.|
|software_version_id|,|1|,|The software_version_id element indicates the version|
|software_version_id|,|2|,|(development level) of a program or a program library.|
|solar_distance|,|1|,|The solar_distance element provides the distance from the|
|solar_distance|,|2|,|center of the sun to the center of a target body.|
|solar_latitude|,|1|,|The solar_latitude element provides the subsolar latitude|
|solar_latitude|,|2|,|value.|
|solar_latitude|,|3|,|Subsolar latitude is defined as the latitude of the point|
|solar_latitude|,|4|,|on the target body surface that would be intersected by a|
|solar_latitude|,|5|,|straight line from the center of the sun to the center of|
|solar_latitude|,|6|,|the target body.|
|solar_longitude|,|1|,|The solar_longitude element provides the value of the angle|
|solar_longitude|,|2|,|between the body_Sun line at the time of interest and the|
|solar_longitude|,|3|,|body_Sun line at the vernal equinox.|
|solar_longitude|,|4|,|This provides a measure of season on a target body, with|
|solar_longitude|,|5|,|values of 0 to 90 degrees representing northern spring, 90|
|solar_longitude|,|6|,|to 180 degrees representing northern summer, 180 to 270|
|solar_longitude|,|7|,|degrees representing northern autumn and 270 to 360 degrees|
|solar_longitude|,|8|,|representing northern winter.|
|source_data_set_id|,|1|,|The source_data_set_identification element identifies a set|
|source_data_set_id|,|2|,|of data which was used to produce the subject data set,|
|source_data_set_id|,|3|,|data product or SPICE kernel.|
|source_file_name|,|1|,|The source_file_name element indicates the file containing|
|source_file_name|,|2|,|the image from which a sub-image was extracted.|
|source_file_name|,|500|,|Note:  In the SFOC, the source_file_name element provides|
|source_file_name|,|501|,|the name of a specific file that contributed data to a given|
|source_file_name|,|502|,|product.|
|source_line_samples|,|1|,|The source_line_samples element indicates the total number|
|source_line_samples|,|2|,|of samples in the image from which a rectangular sub-image|
|source_line_samples|,|3|,|has been derived.|
|source_line_samples|,|300|,|Note:  In the PDS, if source_line_samples appears in|
|source_line_samples|,|301|,|the image object, it should be greater than the value of|
|source_line_samples|,|302|,|line_samples, to indicate that the image described by lines|
|source_line_samples|,|303|,|and line_samples is a sub-image of the original (source)|
|source_line_samples|,|304|,|image.|
|source_lines|,|1|,|The source_lines element indicates the total number of|
|source_lines|,|2|,|lines in the image from which a rectangular sub-image has|
|source_lines|,|3|,|been derived.|
|source_lines|,|300|,|Note:  If source_lines appears in the image|
|source_lines|,|301|,|object, it should be greater than the value of lines, to|
|source_lines|,|302|,|indicate that the image described by lines and line_samples|
|source_lines|,|303|,|is a sub-image of the original (source) image.|
|source_sample_bits|,|1|,|The source_sample_bits element indicates the number of|
|source_sample_bits|,|2|,|bits, or units of binary information, that make up a sample|
|source_sample_bits|,|3|,|value in the source file used to produce a sub-image.|
|spacecraft_altitude|,|1|,|The spacecraft_altitude element provides the distance from|
|spacecraft_altitude|,|2|,|the spacecraft to the sub_spacecraft point on the surface|
|spacecraft_altitude|,|3|,|of the target body.|
|spacecraft_clock_start_count|,|1|,|The spacecraft_clock_start_count element provides the value|
|spacecraft_clock_start_count|,|2|,|of the spacecraft clock at the time of frame acquisition.|
|spacecraft_clock_start_count|,|300|,|Note:  In the PDS, sclk_start_counts have been represented|
|spacecraft_clock_start_count|,|301|,|in the following ways:|
|spacecraft_clock_start_count|,|303|,|Voyager - Flight Data Subsystem (FDS) clock count|
|spacecraft_clock_start_count|,|305|,|          (floating point 7.2)|
|spacecraft_clock_start_count|,|307|,|Mariner 9 - Data Automation Subsystem,|
|spacecraft_clock_start_count|,|309|,|Mariner 10 - FDS - spacecraft_clock|
|spacecraft_clock_stop_count|,|1|,|The spacecraft_clock_stop_count element provides the value|
|spacecraft_clock_stop_count|,|2|,|of the spacecraft clock  at the end of a time period of|
|spacecraft_clock_stop_count|,|3|,|interest.|
|spacecraft_desc|,|1|,|The spacecraft_description element describes the|
|spacecraft_desc|,|2|,|characteristics of a particular spacecraft.  This|
|spacecraft_desc|,|3|,|description addresses the complement of instruments|
|spacecraft_desc|,|4|,|carried, the onboard communications and data processing|
|spacecraft_desc|,|5|,|equipment, the method of stabilization, the source of power|
|spacecraft_desc|,|6|,|and the capabilities or limitations of the spacecraft|
|spacecraft_desc|,|7|,|design which are related to data_taking activities.  The|
|spacecraft_desc|,|8|,|description may be a synopsis of available mission|
|spacecraft_desc|,|9|,|documentation.|
|spacecraft_id|,|1|,|The spacecraft_identification element provides a synonym or|
|spacecraft_id|,|2|,|mnemonic for the name of a spacecraft which is uniquely|
|spacecraft_id|,|3|,|associable with the spacecraft name.|
|spacecraft_id|,|501|,|Note: Within SFOC only this element is also an alias for|
|spacecraft_id|,|502|,|dsn_spacecraft_num.  This interpretation is not portable to|
|spacecraft_id|,|503|,|the PDS.|
|spacecraft_id_or_name|,|1|,|The spacecraft_id_or_name element provides either a|
|spacecraft_id_or_name|,|2|,|spacecraft_id or a spacecraft_name.  That is, this element|
|spacecraft_id_or_name|,|3|,|may have values which are either the identification of a|
|spacecraft_id_or_name|,|4|,|spacecraft (the spacecraft_id) or the name of a spacecraft|
|spacecraft_id_or_name|,|5|,|(the spacecraft_name).|
|spacecraft_name|,|1|,|The spacecraft_name element provides the full, unabbreviated|
|spacecraft_name|,|2|,|name of a spacecraft.  See also: spacecraft_id,|
|spacecraft_name|,|3|,|instrument_host_id.|
|spacecraft_operating_mode_id|,|1|,|The spacecraft_operating_mode_id element identifies a|
|spacecraft_operating_mode_id|,|2|,|particular configuration in which the spacecraft takes and|
|spacecraft_operating_mode_id|,|3|,|returns data.|
|spacecraft_operations_type|,|1|,|The spacecraft_operation_type element|
|spacecraft_operations_type|,|2|,|provides the type of mode of operation of a spacecraft.|
|spacecraft_operations_type|,|3|,|Example values:  SUN-SYNCHRONOUS, GEOSTATIONARY, LANDER,|
|spacecraft_operations_type|,|4|,|ROVER, FLYBY.|
|spacecraft_solar_distance|,|1|,|The spacecraft_solar_distance element provides the distance|
|spacecraft_solar_distance|,|2|,|from the spacecraft to the center of the sun.  See also:|
|spacecraft_solar_distance|,|3|,|solar distance.|
|specialty_desc|,|1|,|The specialty_desc element describes an individual's area|
|specialty_desc|,|2|,|of specialization during his or her association with a|
|specialty_desc|,|3|,|particular institution.|
|specialty_desc|,|4|,|Note that `specialty' is a more general characterization|
|specialty_desc|,|5|,|of the individual's activities than is `role.'  See|
|specialty_desc|,|6|,|role_description.|
|spectrum_integrated_radiance|,|1|,|The spectrum_integrated_radiance element provides the|
|spectrum_integrated_radiance|,|2|,|radiance value derived from integration across an entire|
|spectrum_integrated_radiance|,|3|,|spectrum.|
|spectrum_number|,|1|,|The spectrum_number element provides the number which|
|spectrum_number|,|2|,|identifies a particular spectrum.|
|spectrum_samples|,|1|,|The spectrum_samples element provides the number of samples|
|spectrum_samples|,|2|,|which form a given spectrum.|
|sql_format|,|1|,|The sql_format element provides the Standard Query Language|
|sql_format|,|2|,|(SQL) data type and is used as an alias to the Britton Lee|
|sql_format|,|3|,|SQL type.  This element is used primarily for documentation.|
|standard_value_type|,|1|,|The standard_value_type element indicates the type of|
|standard_value_type|,|2|,|standard value which exists for a PDS data element.  Example|
|standard_value_type|,|3|,|values: static - values for the data element exist in a|
|standard_value_type|,|4|,|defined and fixed set of standard values, dynamic -|
|standard_value_type|,|5|,|values for the data element must either exist in a set of|
|standard_value_type|,|6|,|defined standard values or be approved by peer review for|
|standard_value_type|,|7|,|inclusion to the set of standard values, suggest -|
|standard_value_type|,|8|,|values for the data element must exist in a set of defined|
|standard_value_type|,|9|,|standard values or may be added to the set of standard|
|standard_value_type|,|10|,|values with no requirement for peer review, range -|
|standard_value_type|,|11|,|values for the data element must fall within a default range|
|standard_value_type|,|12|,|specified with the minimum_column_value and|
|standard_value_type|,|13|,|maximum_column_value elements, formation - values for|
|standard_value_type|,|14|,|the data element must conform to a formation rule.|
|start_bit|,|1|,|The start_bit element identifies the location of the first|
|start_bit|,|2|,|bit in a value, counting from 1.|
|start_byte|,|1|,|The start_byte element indicates the location of the first|
|start_byte|,|2|,|byte, counting from 1, within a particular data|
|start_byte|,|3|,|representation.|
|start_delimiting_parameter|,|1|,|The start_delimiting_parameter element provides the|
|start_delimiting_parameter|,|2|,|beginning parameter value which, together with the|
|start_delimiting_parameter|,|3|,|stop_delimiting_parameter value, delimits a subset of data.|
|start_julian_date|,|1|,|The start_julian_date element provides the julian date of|
|start_julian_date|,|2|,|the start of a time period of interest.  Julian date is|
|start_julian_date|,|3|,|defined as an integer count of days elapsed since noon,|
|start_julian_date|,|4|,|January 1, 4713 B.C.  Thus, the julian date of January 1,|
|start_julian_date|,|5|,|1960 (A.D.) is 2436935.|
|start_orbit_number|,|1|,|The start_orbit_number data element provides the the lowest|
|start_orbit_number|,|2|,|revolution orbit number that contributed data to a given|
|start_orbit_number|,|3|,|data product.|
|start_page_number|,|1|,|The start_page_number element identifies the beginning page|
|start_page_number|,|2|,|number of a reference document which appears (as an|
|start_page_number|,|3|,|article, for example) in a journal, report or other|
|start_page_number|,|4|,|published work.|
|start_sample_number|,|1|,|The start_sample_number element identifies the lowest of|
|start_sample_number|,|2|,|the sample numbers which define the orbit sequence portion|
|start_sample_number|,|3|,|located within a given bin.|
|start_sequence_number|,|1|,|The start_sequence_number element provides the number of|
|start_sequence_number|,|2|,|the first sequence in a revolution.  See sequence_number.|
|start_time|,|1|,|The start_time element provides the date and time of|
|start_time|,|2|,|the beginning of an occurrence or observation (whether it|
|start_time|,|3|,|be a spacecraft, ground-based, or system event) in|
|start_time|,|4|,|UTC format.|
|start_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|start_time_base|,|1|,|The start_time_base element provides the elapsed time from|
|start_time_base|,|2|,|the beginning of each frame to the beginning of a particular|
|start_time_base|,|3|,|mode.|
|start_time_from_closest_aprch|,|1|,|The start_time_from_closest_approach element provides the|
|start_time_from_closest_aprch|,|2|,|time from spacecraft periapsis at the beginning of a|
|start_time_from_closest_aprch|,|3|,|sequence.  See time_from_closest_approach.|
|stop_delimiting_parameter|,|1|,|The stop_delimiting_parameter element provides the ending|
|stop_delimiting_parameter|,|2|,|parameter value which, together with the|
|stop_delimiting_parameter|,|3|,|start_delimiting_parameter value, delimits a subset of|
|stop_delimiting_parameter|,|4|,|data.|
|stop_orbit_number|,|1|,|The stop_orbit_number data element provides the the highest|
|stop_orbit_number|,|2|,|revolution orbit number that contributed data to a given|
|stop_orbit_number|,|3|,|data product.|
|stop_sample_number|,|1|,|The stop_sample_number element identifies the highest of|
|stop_sample_number|,|2|,|the sample numbers which define the orbit sequence portion|
|stop_sample_number|,|3|,|located within a given bin.|
|stop_sequence_number|,|1|,|The stop_sequence_number element provides the number of the|
|stop_sequence_number|,|2|,|last sequence in a revolution.  See sequence_number.|
|stop_time|,|1|,|The stop_time element provides the date and time of the end|
|stop_time|,|2|,|of an observation or occurrence (whether it be a spacecraft,|
|stop_time|,|3|,|ground-based, or system event) in UTC format.|
|stop_time|,|200|,|Formation rule: YYYY-MM-DDThh:mm:ss[.fff]|
|stop_time_from_closest_aprch|,|1|,|The stop_time_from_closest_approach element provides the|
|stop_time_from_closest_aprch|,|2|,|time from spacecraft periapsis at the end of a sequence.|
|stop_time_from_closest_aprch|,|3|,|See time_from_closest_approach.|
|storage_level_id|,|1|,|The storage_level_id element identifies a particular storage|
|storage_level_id|,|2|,|level.|
|storage_level_id|,|3|,|For example, if the complete pathname for a stored data file|
|storage_level_id|,|4|,|is 'JPLPDS::DISK$USER1:[JJEANS.UNIVERSE]DESCRPTR.LIS' then|
|storage_level_id|,|5|,|the storage_level_identification element value will be one|
|storage_level_id|,|6|,|of the following:  JPLPDS, DISK$USER1, JJEANS, UNIVERSE,|
|storage_level_id|,|7|,|DESCRPTR.LIS.|
|storage_level_number|,|1|,|The storage_level_number element describes the position of a|
|storage_level_number|,|2|,|given storage level within the overall storage hierarchy of|
|storage_level_number|,|3|,|an entire data set, data product, or SPICE kernel.|
|storage_level_number|,|4|,|As many storage levels are documented as are necessary to|
|storage_level_number|,|5|,|identify the data.  Level 0 indicates the highest storage|
|storage_level_number|,|6|,|level, which successively higher level numbers indicate|
|storage_level_number|,|7|,|successively lower levels in the storage hierarchy.|
|storage_level_type|,|1|,|The storage_level_type element identifies the type of|
|storage_level_type|,|2|,|storage structure to which a given storage_level_number|
|storage_level_type|,|3|,|refers.|
|storage_level_type|,|4|,|Example values: DATABASE, PHOTOGRAPHIC FRAME NUMBER, TAPE|
|storage_level_type|,|5|,|REEL NUMBER, VAX COMPUTER, VAX DIRECTORY, VAX FILE, VAX|
|storage_level_type|,|6|,|SUBDIRECTORY.|
|sub_object_name|,|1|,|The sub_object_name element provides the template object|
|sub_object_name|,|2|,|name for a child object name subordinate to a parent object|
|sub_object_name|,|3|,|name.  This object name is used by the catalog bulk loading|
|sub_object_name|,|4|,|software to establish a hierarchy between template objects.|
|sub_object_name|,|5|,|For full definitions of the terms object and sub-object,|
|sub_object_name|,|6|,|please refer to PDS standards documentation.|
|sub_solar_azimuth|,|1|,|The sub_solar_azimuth element provides the value of the|
|sub_solar_azimuth|,|2|,|angle between the line from the center of an image to the|
|sub_solar_azimuth|,|3|,|subsolar point and a horizontal reference line (in the|
|sub_solar_azimuth|,|4|,|image plane) extending from the image center to the middle|
|sub_solar_azimuth|,|5|,|right edge of the image.|
|sub_solar_azimuth|,|6|,|The values of this angle increase in a clockwise direction.|
|sub_solar_latitude|,|1|,|The sub_solar_latitude element provides the latitude of|
|sub_solar_latitude|,|2|,|the subsolar point.  The subsolar point is that point on a|
|sub_solar_latitude|,|3|,|body which lies directly beneath the sun.|
|sub_solar_longitude|,|1|,|The sub_solar_longitude element provides the longitude of|
|sub_solar_longitude|,|2|,|the subsolar point.  The subsolar point is that point on a|
|sub_solar_longitude|,|3|,|body which lies directly beneath the sun.|
|sub_spacecraft_azimuth|,|1|,|The sub_spacecraft_azimuth element provides the value of|
|sub_spacecraft_azimuth|,|2|,|the angle between the line from the center of an image to|
|sub_spacecraft_azimuth|,|3|,|the subspacecraft point and a horizontal reference line (in|
|sub_spacecraft_azimuth|,|4|,|the image plane) extending from the image center to the|
|sub_spacecraft_azimuth|,|5|,|middle right edge of the image.|
|sub_spacecraft_azimuth|,|6|,|The values of this angle increase in a clockwise direction.|
|sub_spacecraft_latitude|,|1|,|The sub_spacecraft_latitude element provides the latitude of|
|sub_spacecraft_latitude|,|2|,|the subspacecraft point.  The subspacecraft point is that|
|sub_spacecraft_latitude|,|3|,|point on a body which lies directly beneath the spacecraft.|
|sub_spacecraft_longitude|,|1|,|The sub_spacecraft_longitude element provides the longitude|
|sub_spacecraft_longitude|,|2|,|of the subspacecraft point.  The subspacecraft point is that|
|sub_spacecraft_longitude|,|3|,|point on a body which lies directly beneath the spacecraft.|
|support_request_date|,|1|,|The support_request_date element provides the date that a|
|support_request_date|,|2|,|support request was taken by the PDS operator.|
|support_request_desc|,|1|,|The support_request_desc element provides a textual|
|support_request_desc|,|2|,|description of an official PDS support request as recorded|
|support_request_desc|,|3|,|by the PDS operator after talking with a PDS user about a|
|support_request_desc|,|4|,|problem with the PDS.|
|support_request_no|,|1|,|The support_request_number provides a computer assigned|
|support_request_no|,|2|,|unique number given to each support request recorded by the|
|support_request_no|,|3|,|Central Node PDS operator.|
|support_resolution|,|1|,|The support_resolution element provides the textual|
|support_resolution|,|2|,|description of the resolution to a problem recorded by the|
|support_resolution|,|3|,|PDS operator.|
|support_resolution_date|,|1|,|The support_resolution_date element provides the date that|
|support_resolution_date|,|2|,|a support request was resolved by the PDS.|
|support_staff_full_name|,|1|,|The support_staff_name element provides the full name of the|
|support_staff_full_name|,|2|,|PDS person entering the support request information into|
|support_staff_full_name|,|3|,|the PDS.  See also:  full_name.|
|surface_clarity_percentage|,|1|,|The surface_clarity_percentage element provides an estimate|
|surface_clarity_percentage|,|2|,|of the fraction of an image or observation of a surface|
|surface_clarity_percentage|,|3|,|which is unobscured (as by clouds).|
|surface_clarity_percentage|,|4|,|Surface_clarity_percentage is defined as the ratio of the|
|surface_clarity_percentage|,|5|,|unobscured area to the total observed area.|
|surface_clarity_percentage|,|6|,|See also surface_clarity_description.|
|surface_emission_temperature|,|1|,| The surface_emission_temperature element provides the|
|surface_emission_temperature|,|2|,|value of the temperature assumed for the planetary surface|
|surface_emission_temperature|,|3|,|covered by the radiometer footprint, derived by correcting|
|surface_emission_temperature|,|4|,|brightness_temperature for atmospheric emission and|
|surface_emission_temperature|,|5|,|absorption.|
|surface_emissivity|,|1|,| The surface_emissivity element provides the value of|
|surface_emissivity|,|2|,|surface microwave emissivity, calculated by dividing|
|surface_emissivity|,|3|,|(surface_emission_temperature -|
|surface_emissivity|,|4|,|assumed_warm_sky_temperature) by|
|surface_emissivity|,|5|,|(physical_surface_temperature -|
|surface_emissivity|,|6|,|assumed_warm_sky_temperature).|
|surface_gravity|,|1|,|The surface_gravity element provides the average|
|surface_gravity|,|2|,|gravitational acceleration at the surface of a target body.|
|surface_gravity|,|3|,|Surface_gravity is computed from the mass and mean radius|
|surface_gravity|,|4|,|of the target body.|
|surface_temperature|,|1|,| The surface_temperature element provides the value of the|
|surface_temperature|,|2|,|physical surface temperature of the radiometer footprint,|
|surface_temperature|,|3|,|calculated from average_planetary_radius and the|
|surface_temperature|,|4|,|project-adopted atmospheric model.|
|synodic_rotation_period|,|1|,|The synodic_rotation_period element provides the time|
|synodic_rotation_period|,|2|,|period required for a solar system object to complete one|
|synodic_rotation_period|,|3|,|full rotation about its primary, returning to the same|
|synodic_rotation_period|,|4|,|position in space relative to its primary.|
|system_bulletin_date|,|1|,|The system_bulletin_date element is the date and time|
|system_bulletin_date|,|2|,|when the PDS operator logged a PDS system bulletin.|
|system_bulletin_desc|,|1|,|The system_bulletin_desc element is the text of a PDS|
|system_bulletin_desc|,|2|,|system bulletin.|
|system_bulletin_id|,|1|,|The system_bulletin_id element is a unique integer that|
|system_bulletin_id|,|2|,|identifies a PDS system bulletin.|
|system_bulletin_type|,|1|,|The system_bulletin_type element is a keyword that|
|system_bulletin_type|,|2|,|describes the type of bulletin displayed.|
|system_event_date|,|1|,|The system_event_date element provides the beginning date|
|system_event_date|,|2|,|of a PDS scheduled event.|
|system_event_user_note|,|1|,|The system_event_user_note element provides information|
|system_event_user_note|,|2|,|about a system event.|
|system_event_user_note|,|3|,|Example value:  THE SYSTEM WILL BE DOWN FOR PREVENTATIVE|
|system_event_user_note|,|4|,|MAINTENANCE FROM NOON UNTIL MIDNIGHT.|
|system_expertise_level|,|1|,|The system_expertise_level element identifies an|
|system_expertise_level|,|2|,|individual's level of expertise in the use of the PDS|
|system_expertise_level|,|3|,|capabilities.|
|table_bl_name|,|1|,|The table_bl_name element represents the database tersename|
|table_bl_name|,|2|,|used by the loader software to map a template value to a|
|table_bl_name|,|3|,|column in a table.  There exists a unique mapping for each|
|table_bl_name|,|4|,|template keyword=value occurrence|
|table_bl_name|,|5|,|identifies the database column.  The formulation of the|
|table_bl_name|,|6|,|tblblname is governed by rules and abbreviations as defined|
|table_bl_name|,|7|,|in the PDS Data Administration Plan document.|
|table_desc|,|1|,|The table_desc element provides the ascii text description|
|table_desc|,|2|,| for a table in the PDS database.|
|table_name|,|1|,|The table_name element provides a unique name for a table|
|table_name|,|2|,|in the PDS database.  All tables in the database will have|
|table_name|,|3|,|a name and a description.|
|table_storage_type|,|1|,|The table_storage_type element indicates the order of|
|table_storage_type|,|2|,|storage for entries in a table.|
|table_type|,|1|,|The table_type element denotes whether the table contains|
|table_type|,|2|,|High Level Catalog data, Detailed Level Catalog Data|
|table_type|,|3|,|(Image), Detailed Level Catalog (Fields and Particles) data,|
|table_type|,|4|,| or system data.  Examples:  H, F, I, or S|
|target_center_distance|,|1|,|The target_center_distance element provides the distance|
|target_center_distance|,|2|,|between a spacecraft and the center of the named target.|
|target_name|,|1|,|The  target_name element identifies a target.  The target|
|target_name|,|2|,|may be a planetary body, satellite, ring, region, feature,|
|target_name|,|3|,|asteroid or comet. See target_type.|
|target_parameter_epoch|,|1|,|The target_parameter_epoch element provides the reference|
|target_parameter_epoch|,|2|,|epoch for the value associated with a particular target|
|target_parameter_epoch|,|3|,|parameter, whose name is provided in the|
|target_parameter_epoch|,|4|,|target_parameter_name element. The reference epoch is the|
|target_parameter_epoch|,|5|,|date and time associated with measurement of a quantity|
|target_parameter_epoch|,|6|,|which may vary with time.  For example, the value provided|
|target_parameter_epoch|,|7|,|for the obliquity of a planet will be given for a|
|target_parameter_epoch|,|8|,|measurement taken at a specified time.  That time will be|
|target_parameter_epoch|,|9|,|referenced in the target_parameter_epoch element.  See also|
|target_parameter_epoch|,|10|,|target_parameter_value.|
|target_parameter_name|,|1|,|The target_parameter_name element provides the name of|
|target_parameter_name|,|2|,|a dynamic or physical parameter associated with a given|
|target_parameter_name|,|3|,|target.  This element may take as values only those|
|target_parameter_name|,|4|,|names that are proper element names for the various|
|target_parameter_name|,|5|,|dynamic and physical parameters cataloged as part of|
|target_parameter_name|,|6|,|target information.  Example values:  BOND_ALBEDO,|
|target_parameter_name|,|7|,|MEAN_SURFACE_TEMPERATURE, OBLIQUITY,|
|target_parameter_name|,|8|,|ORBITAL_INCLINATION.|
|target_parameter_uncertainty|,|1|,|The target_parameter_uncertainty element provides the|
|target_parameter_uncertainty|,|2|,|numeric value of the uncertainty associated with the value|
|target_parameter_uncertainty|,|3|,|given for a particular target parameter, whose name is|
|target_parameter_uncertainty|,|4|,|provided in the associated target_parameter_name element.|
|target_parameter_uncertainty|,|5|,|The uncertainty is expressed in the same units as the value|
|target_parameter_uncertainty|,|6|,|of the parameter itself, and gives some measure of the|
|target_parameter_uncertainty|,|7|,|provider's estimate of the reliability of a particular value|
|target_parameter_uncertainty|,|8|,|stored in the catalog. See also target_parameter_value.|
|target_parameter_value|,|1|,|The target_parameter_value element provides the numeric|
|target_parameter_value|,|2|,|value associated with a particular target parameter, whose|
|target_parameter_value|,|3|,|name is provided in the associated target_parameter_name|
|target_parameter_value|,|4|,|element.  Each value provided is associated with a|
|target_parameter_value|,|5|,|particular source, which is completely referenced in the|
|target_parameter_value|,|6|,|associated data_source_description. See also|
|target_parameter_value|,|7|,|target_parameter_uncertainty, target_parameter_epoch.|
|target_type|,|1|,|The target_type element identifies the type of a named|
|target_type|,|2|,|target.|
|target_type|,|3|,|Example values:  PLANET, SATELLITE, RING, REGION, FEATURE,|
|target_type|,|4|,|ASTEROID, COMET.|
|task_name|,|1|,|The task_name element identifies the task with which an|
|task_name|,|2|,|individual is or was affiliated during his or her|
|task_name|,|3|,|association with a particular institution.|
|task_name|,|4|,|Note that `task' affiliations are distinct from|
|task_name|,|5|,|`mission' affiliations.|
|telephone_number|,|1|,|The telephone_number element provides the area code,|
|telephone_number|,|2|,|telephone number and extension (if any) of an individual or|
|telephone_number|,|3|,|node.|
|telephone_number|,|4|,|See also fts_number and home_telephone_number.|
|telescope_diameter|,|1|,|The telescope_diameter element provides the diameter of the|
|telescope_diameter|,|2|,|primary mirror of a telescope.|
|telescope_f_number|,|1|,|The telescope_f_number element provides the value of the|
|telescope_f_number|,|2|,|ratio of the focal length to the aperture of a telescope.|
|telescope_focal_length|,|1|,|The telescope_focal_length element provides the total|
|telescope_focal_length|,|2|,|optical path distance from the first element of the optics|
|telescope_focal_length|,|3|,|to the focal point of a telescope.|
|telescope_id|,|1|,|The telescope_id element uniquely identifies a particular|
|telescope_id|,|2|,|telescope.|
|telescope_resolution|,|1|,|The telescope_resolution element provides the achievable|
|telescope_resolution|,|2|,|angular resolution of a telescope.|
|telescope_serial_number|,|1|,|The telescope_serial_number element provides the serial|
|telescope_serial_number|,|2|,|number of a telescope.|
|telescope_t_number|,|1|,|The telescope_t_number element provides the effective|
|telescope_t_number|,|2|,|f_number of a telescope.|
|telescope_t_number|,|3|,|Note that the t_number differs from the f_number due to|
|telescope_t_number|,|4|,|losses in the optical system.|
|telescope_t_number_error|,|1|,|The telescope_t_number_error element indicates the error|
|telescope_t_number_error|,|2|,|associated with the t_number value for a particular|
|telescope_t_number_error|,|3|,|telescope.|
|telescope_transmittance|,|1|,|The telescope_transmittance element provides the|
|telescope_transmittance|,|2|,|transmittance value for a telescope.  Transmittance is|
|telescope_transmittance|,|3|,|defined as the ratio of transmitted to incident flux|
|telescope_transmittance|,|4|,|through the telescope.|
|temperature_translation_desc|,|1|,|The temperature_translation_description element provides|
|temperature_translation_desc|,|2|,|the conversion necessary to translate an instrument's|
|temperature_translation_desc|,|3|,|transmitted temperature reading to a value which is|
|temperature_translation_desc|,|4|,|relative to a standard temperature scale.|
|template_bl_name|,|1|,|The template_bl_name element represents the database terse|
|template_bl_name|,|2|,|name associated with a template keyword.  This tersename is|
|template_bl_name|,|3|,|used during construction of templates to provide a reference|
|template_bl_name|,|4|,|to the keyword|
|template_bl_name|,|5|,|a full data element name rather than the terse|
|template_bl_name|,|6|,|representation.  The formulation of the tmpltblname is|
|template_bl_name|,|7|,|governed by rules and abbreviations as defined in the PDS|
|template_bl_name|,|8|,| Data Administration Plan document.|
|template_load_date|,|1|,|The template_load_date element provides the current date the|
|template_load_date|,|2|,|loader program is run.  This date is supplied by the host|
|template_load_date|,|3|,|operating system.|
|template_load_time|,|1|,|The template_load_time provides the current time the loader|
|template_load_time|,|2|,|program is run.  This time indicates the host operating|
|template_load_time|,|3|,|system time at the beginning of the catalog template|
|template_load_time|,|4|,|parsing.|
|template_name|,|1|,|The template_name element provides the name of a template|
|template_name|,|2|,|object used in the PDS system and the bulk loading software.|
|template_note|,|1|,|The template_note element provides the textual description|
|template_note|,|2|,|of the purpose for a template object as related to the data|
|template_note|,|3|,|supplier.  This description is distributed whenever a|
|template_note|,|4|,|template is sent to a data supplier.|
|template_revision_date|,|1|,|The template_revision_date element indicates the latest|
|template_revision_date|,|2|,|revision date for a template (i.e. 11/22/88).|
|template_status|,|1|,|The template_status element is updated by the loader|
|template_status|,|2|,|software after certain events in the catalog loading|
|template_status|,|3|,|process.  The value of this field indicates the current|
|template_status|,|4|,|status of a template or sub-template in the load process.|
|template_type|,|1|,|The template_type element provides a type or class of|
|template_type|,|2|,|template object.|
|template_use_indicator|,|1|,|The template_use_indicator element indicates whether or not|
|template_use_indicator|,|2|,|template may recur within a set of templates.|
|terse_name|,|1|,|The terse_name element represents the name of a column in a|
|terse_name|,|2|,|database table, specifically the DBMS implementation name of|
|terse_name|,|3|,|that column.  Thus, the tersename is the physical database|
|terse_name|,|4|,|identifier for a particular data element.  The formulation|
|terse_name|,|5|,|of the tersename is governed by rules and abbreviations as|
|terse_name|,|6|,|defined in PDS standards documentation.|
|text_flag|,|1|,|The text_flag element indicates whether or not a data|
|text_flag|,|2|,|element contains variable-length textual information (i.e.,|
|text_flag|,|3|,|a description, a note, or a summary).|
|threshold_cost|,|1|,|The threshold_cost element provides the maximum cost which|
|threshold_cost|,|2|,|is compared to the order item's calculated cost.  When the|
|threshold_cost|,|3|,|threshold cost is exceeded, the order item is not accepted|
|threshold_cost|,|4|,|by the PDS order function.|
|time_from_closest_approach|,|1|,|The time_from_closest_approach element provides the time|
|time_from_closest_approach|,|2|,|from spacecraft periapsis.|
|time_from_closest_approach|,|3|,|The time values are negative prior to periapsis and|
|time_from_closest_approach|,|4|,|positive after periapsis.|
|time_range_number|,|1|,|The time_range number is unique to SFOC-MGN ephemeris files|
|time_range_number|,|2|,|and identifies groups of time ranges in the catalog object.|
|total_data_set_granules|,|1|,|The total_data_set_granule element is the total number of|
|total_data_set_granules|,|2|,|granules contained in a data set.  A granule is the smallest|
|total_data_set_granules|,|3|,|orderable unit of a data set, so the total data set granules|
|total_data_set_granules|,|4|,|might be the total number of images, or the total number of|
|total_data_set_granules|,|5|,|hours of data, depending on the data set.|
|total_fovs|,|1|,|The total_fovs (fields-of-view) element indicates the total|
|total_fovs|,|2|,|number of fields of view associated with a single section of|
|total_fovs|,|3|,|an instrument.|
|true_anomaly_angle|,|1|,|The true_anomaly_angle element provides the value of the|
|true_anomaly_angle|,|2|,|angle between the line connecting an orbiting spacecraft|
|true_anomaly_angle|,|3|,|and the body around which it is orbiting and the line|
|true_anomaly_angle|,|4|,|connecting the periapsis position and the target.|
|true_anomaly_angle|,|5|,|True_anomaly_angle is measured in the spacecraft's orbital|
|true_anomaly_angle|,|6|,|plane counterclockwise from periapsis.|
|tuple_sequence_number|,|1|,|The tuple_sequence_number element is used in all text|
|tuple_sequence_number|,|2|,|tables where the ordering of the ASCII text rows is|
|tuple_sequence_number|,|3|,|required.  This element is used in all text type tables in|
|tuple_sequence_number|,|4|,|the PDS database.|
|twist_offset_angle|,|1|,|The twist_offset_angle element provides the angle at which|
|twist_offset_angle|,|2|,|an instrument is mounted, measured perpendicular to the|
|twist_offset_angle|,|3|,|plane defined by the cone and cross-cone axes.|
|twist_offset_angle|,|4|,|See also cone_offset_angle and cross_cone_offset_angle.|
|uncorrected_distance_to_nadir|,|1|,| The uncorrected_distance_to_nadir element provides the|
|uncorrected_distance_to_nadir|,|2|,|`raw' measurement of range-to-surface, obtained from the|
|uncorrected_distance_to_nadir|,|3|,|pulse-compressed altimeter signals by the MGMTAC phase of|
|uncorrected_distance_to_nadir|,|4|,|the altimetry and radiometry data reduction program.|
|unit|,|1|,|The unit element provides the full name or standard|
|unit|,|2|,|abbreviation of a unit of measurement in which a value is|
|unit|,|3|,|expressed.  Example values: square meter, meter per second.|
|unit|,|4|,||
|unit|,|5|,|Note:  A table of standard units representing those|
|unit|,|6|,|published by the Systeme Internationale appears in the|
|unit|,|7|,|'Units of Measurement' section of the PSDD.  (Please refer|
|unit|,|8|,|to the table of contents for its location.)  The values|
|unit|,|9|,|in this table's 'Unit Name' column constitute the standard|
|unit|,|10|,|values for the data element UNIT.|
|unit_id|,|1|,|The unit_id element indicates the common abbreviation or|
|unit_id|,|2|,|symbol for a unit of measure.  Example:  The unit KILOGRAM|
|unit_id|,|3|,|has the unit_id 'kg'.|
|unit_id|,|300|,|Note:  A table of standard units, unit ids, and measured|
|unit_id|,|301|,|quantities including those published by the Systeme|
|unit_id|,|302|,|Internationale appears in the 'Units of Measurement'|
|unit_id|,|303|,|section of the PSDD.  (Please refer to the table of contents|
|unit_id|,|304|,|for its location.)  The values in this table's 'Symbol'|
|unit_id|,|305|,|column constitue the standard values for the data element|
|unit_id|,|306|,|unit_id.|
|upload_id|,|1|,|The upload_id element describes a spacecraft command set|
|upload_id|,|2|,|that is associated with the given data product.|
|user_product_id|,|1|,|The user_product_identification element provides an|
|user_product_id|,|2|,|alternate logical file name constructed according to a|
|user_product_id|,|3|,|producer-defined naming convention.|
|user_view_category_full_name|,|1|,|The user_view_category_full_name element identifies a|
|user_view_category_full_name|,|2|,|user view category by a text-like name.|
|user_view_category_full_name|,|3|,|Example:  DATASET AND PRODUCT INFORMATION|
|user_view_category_name|,|1|,|The user_view_category_name element identifies a|
|user_view_category_name|,|2|,|category of user views.  A user view category groups a|
|user_view_category_name|,|3|,|set of user views by related function.  This name is|
|user_view_category_name|,|4|,|a terse version of a text-like user view name which is|
|user_view_category_name|,|5|,|contained in the user_view_full_name element.  The|
|user_view_category_name|,|6|,|formulation of the user_view_category_name is governed|
|user_view_category_name|,|7|,|by rules and abbreviations as defined in the PDS|
|user_view_category_name|,|8|,|Catalog Design Document.|
|user_view_desc|,|1|,|The user_view_desc element provides a high-level functional|
|user_view_desc|,|2|,|description of a specific user view.  The user view inputs a|
|user_view_desc|,|3|,|outputs are described in general terms.|
|user_view_full_name|,|1|,|The user_view_full_name element identifies a specific|
|user_view_full_name|,|2|,|user view by a text-like name.|
|user_view_full_name|,|3|,|Example:  General Data Set Information|
|user_view_name|,|1|,|The user_view_name element identifies a specific user view.|
|user_view_name|,|2|,|This name is a terse version of a text-like user view name|
|user_view_name|,|3|,|which is contained in the user_view_full_name element.  The|
|user_view_name|,|4|,|formulation of the user_view_name is governed by rules and|
|user_view_name|,|5|,|abbreviations as defined in the PDS Catalog Design Document.|
|user_view_type|,|1|,|The user_view_type element indicates whether a specific user|
|user_view_type|,|2|,|view is logically associated with the PDS High Level|
|user_view_type|,|3|,|catalog, the Detail Level catalog, or with system data.|
|user_view_warning|,|1|,|The user_view_warning element provides a single line of text|
|user_view_warning|,|2|,|that may warn or comment on some aspect of either the user|
|user_view_warning|,|3|,|view or the data displayed. For example, a user view|
|user_view_warning|,|4|,|displaying target data may suggest that a user contact the|
|user_view_warning|,|5|,|NAIF node if values with more precision are required.|
|vector_component_1|,|1|,|The vector_component_1 element provides the magnitude of|
|vector_component_1|,|2|,|the first component of a vector.|
|vector_component_1|,|3|,|The particular vector component being measured is|
|vector_component_1|,|4|,|identified by the vector_component_identification_1|
|vector_component_1|,|5|,|element.|
|vector_component_2|,|1|,|The vector_component_2 element provides the magnitude of|
|vector_component_2|,|2|,|the second component of a vector.|
|vector_component_2|,|3|,|The particular vector component being measured is|
|vector_component_2|,|4|,|identified by the vector_component_identification_2|
|vector_component_2|,|5|,|element.|
|vector_component_3|,|1|,|The vector_component_3 element provides the magnitude of|
|vector_component_3|,|2|,|the third component of a vector.|
|vector_component_3|,|3|,|The particular vector component being measured is|
|vector_component_3|,|4|,|identified by the vector_component_identification_3|
|vector_component_3|,|5|,|element.|
|vector_component_id|,|1|,|The vector_component_identification element identifies a|
|vector_component_id|,|2|,|vector component without reference to a particular vector|
|vector_component_id|,|3|,|component value.|
|vector_component_id_1|,|1|,|The vector_component_identification_1 element identifies|
|vector_component_id_1|,|2|,|the first component of a vector.|
|vector_component_id_1|,|3|,|The magnitude of the first component of the vector is|
|vector_component_id_1|,|4|,|provided by the vector_component_1 element.|
|vector_component_id_1|,|5|,|Example value:  RJ\$ (a radial distance).|
|vector_component_id_2|,|1|,|The vector_component_identification_2 element identifies|
|vector_component_id_2|,|2|,|the second component of a vector.|
|vector_component_id_2|,|3|,|The magnitude of the second component of the vector is|
|vector_component_id_2|,|4|,|provided by the vector_component_2 element.|
|vector_component_id_2|,|5|,|Example value:  LATJ\$S3 (a latitude).|
|vector_component_id_3|,|1|,|The vector_component_identification_3 element identifies|
|vector_component_id_3|,|2|,|the third component of a vector.|
|vector_component_id_3|,|3|,|The magnitude of the third component of the vector is|
|vector_component_id_3|,|4|,|provided by the vector_component_3 element.|
|vector_component_id_3|,|5|,|Example value:  LONJ\$S3 (a longitude).|
|vector_component_type|,|1|,|The vector_component_type element identifies the type of|
|vector_component_type|,|2|,|information which is provided by a particular vector|
|vector_component_type|,|3|,|component identification element.|
|vector_component_type|,|4|,|Example values:  LATITUDE, LONGITUDE, VELOCITY.|
|vector_component_type_desc|,|1|,|The vector component type description provides a|
|vector_component_type_desc|,|2|,|general description of a particular vector component|
|vector_component_type_desc|,|3|,|type.|
|vector_component_unit|,|1|,|The vector_component_unit element specifies the unit of|
|vector_component_unit|,|2|,|measure of associated dataset or sampling parameters.|
|vector_component_unit|,|3|,|For example, in the ring information entity the unit|
|vector_component_unit|,|4|,|element specifies that a given set of ring radii are|
|vector_component_unit|,|5|,|measured in kilometers.|
|version_id|,|1|,|This element is an alias for product_version_id used only by|
|version_id|,|2|,|SFOC-MGN ephemeris files.|
|version_number|,|1|,|The version_number element is defined as an alias for|
|version_number|,|2|,|product_version_id and is avaliable only for SFOC-Magellan|
|version_number|,|3|,|mission operations products.|
|vertical_fov|,|1|,|The vertical_field_of_view element provides the angular|
|vertical_fov|,|2|,|measure of the vertical field of view of an instrument.|
|vertical_pixel_fov|,|1|,|The vertical_pixel_field_of_view element provides the|
|vertical_pixel_fov|,|2|,|angular measure of the vertical field of view of a single|
|vertical_pixel_fov|,|3|,|pixel.|
|volume_version_id|,|1|,|The volume_version_id element identifies the version of a|
|volume_version_id|,|2|,|particular volume within a volume set.  Example value:|
|volume_version_id|,|3|,|VERSION 2.|
|volumes|,|1|,|The volumes element provides the count of a particular|
|volumes|,|2|,|medium to be provided in a data set delivery.  For example:|
|volumes|,|3|,|if the medium_type of a data set is CD-ROM, the value of|
|volumes|,|4|,|volumes would be the total number of CDs in that delivery.|
|x_axis_first_pixel|,|1|,|The x_axis_first_pixel element provides the x-dimension|
|x_axis_first_pixel|,|2|,|index to be assigned the first pixel that was physically|
|x_axis_first_pixel|,|3|,|recorded at the beginning of the image array.|
|x_axis_framelet_offset|,|1|,|The x_axis_framelet_offset provides the row number of a|
|x_axis_framelet_offset|,|2|,|framelet within a tiled image.|
|x_axis_last_pixel|,|1|,|The x_axis_last_pixel element provides the x-dimension|
|x_axis_last_pixel|,|2|,|index to be assigned the last pixel that was physically|
|x_axis_last_pixel|,|3|,|recorded at the end of the image array.|
|x_axis_projection_offset|,|1|,|The x_axis_projection_offset element provides the line|
|x_axis_projection_offset|,|2|,|offset value of the map projection origin position from|
|x_axis_projection_offset|,|3|,|line and sample 1,1 (line and sample 1,1 is considered the|
|x_axis_projection_offset|,|4|,|upper left corner of the digital array).  Note that the|
|x_axis_projection_offset|,|5|,|positive direction is to the right and down.|
|y_axis_first_pixel|,|1|,|The y_axis_first_pixel element provides the y-dimension|
|y_axis_first_pixel|,|2|,|index to be assigned the first pixel that was physically|
|y_axis_first_pixel|,|3|,|recorded at the beginning of the image array.|
|y_axis_framelet_offset|,|1|,|The y_axis_framelet_offset element provides the column|
|y_axis_framelet_offset|,|2|,|number of a framelet within a tiled image.|
|y_axis_last_pixel|,|1|,|The y_axis_last_pixel element provides the y-dimension|
|y_axis_last_pixel|,|2|,|index to be assigned the last pixel that was physically|
|y_axis_last_pixel|,|3|,|recorded at the end of the image array.|
|y_axis_projection_offset|,|1|,|The y_axis_projection_offset element provides the sample|
|y_axis_projection_offset|,|2|,|offset value of the map projection origin position from|
|y_axis_projection_offset|,|3|,|line and sample 1,1 (line and sample 1,1 is considered the|
|y_axis_projection_offset|,|4|,|upper left corner of the digital array).  Note that the|
|y_axis_projection_offset|,|5|,|positive direction is to the right and down.|