HiCat Data Dictionary

Catalog: HiRISE
The main HiRISE catalog contains all the information used in operating the HiRISE camera after it is attached to the MRO spacecraft. The information is divided into those related to suggesting, planning, commanding, retrieving, processing, validating, and distributing the observations. The tag that follows an observation through all these catalogs (and from Earth to Mars and back) is the unique Observation_ID. This ID is available in both a 32-bit binary code and a user-friendly text representation. This text representation also forms the core of the product names. The HiRISE catalog also contains ancillary information needed in various uplink and downlink activities, such as the people making image suggestions, MRO project uplink files, SPICE and engineering data, and public image releases.
Table:Suggested_Observations
Stores information about the suggested locations to image. Includes all desired parameters specified by suggestors, such as the geographic position, the minimum image area, the desired viewing geometry, the need for color and/or stereo observations, and seasonal constraints. Also includes suggestion history information such as who, when, and why the suggestion was made, and includes a suggestion priority level specified by a Co-I.

Field Description Type Null Limits Size Key Default Authority Source
ID This is the unique ID for each Suggested Observation. The values here should not be assigned by external programs. Instead it can either be ignored, or NULL can be inserted, and the database will automatically assign the next ID. INT(10) unsigned auto_increment Not Null Primary Key
CENTER_LATITUDE This is the center planetocentric latitude of the suggested observation. FLOAT
CENTER_LONGITUDE This is the center east longitude of the suggested observation. FLOAT
MAX_LATITUDE This is the maximum bound of planetocentric latitude covered by this suggestion. FLOAT
MIN_LATITUDE This is the minimum bound of planetocentric latitude covered by this suggestion. FLOAT
MAX_LONGITUDE This is the maximum bound of east longitude covered by this suggestion. FLOAT
MIN_LONGITUDE This is the minimum bound of east longitude covered by this suggestion. FLOAT
NEED_STEREO This indicates whether this suggestion requires stereo to achieve its goals. TINYINT
NEED_COLOR This indicates whether this suggestion requires color to achieve its goals. TINYINT
MAX_BINNING The maximum binning allowable for this suggestion. The binning value may be less than this value (i.e. not binned as much), but won't be more. Allowable values are 1, 2, 3, 4, 8, and 16. TINYINT(2) unsigned
MAX_LSUBS The maximum allowable LS value for this suggestion. FLOAT
MIN_LSUBS The minimum allowable LS value for this suggestion. FLOAT
MAX_PHASE_ANGLE The maximum allowable phase angle for this suggestion in degrees. FLOAT
MIN_PHASE_ANGLE The minimum allowable phase angle for this suggestion in degrees. FLOAT
MAX_INCIDENCE_ANGLE The maximum allowable incidence angle for this suggestion in degrees. FLOAT
MIN_INCIDENCE_ANGLE The minimum allowable incidence angle for this suggestion in degrees. FLOAT
MAX_EMISSION_ANGLE The maximum allowable emission angle for this suggestion in degrees. FLOAT
MIN_EMISSION_ANGLE The minimum allowable emission angle for this suggestion in degrees. FLOAT
PRIORITY The priority for this suggestion. Is this ordinal or cardinal? Who sets this, the suggestor? What do the different values mean? Laz: None of this has been decided... The most likely will be an integer between 1 and 15, which is what the MRO project is using. The Co-I's are supposed to do this, but all very fuzzy-wuzzy... TINYINT(2) unsigned
DATE_PRIORITIZED The UTC date that this suggestion was given a priority. By whom? The suggestor, the team, related to above. DATETIME
SCIENCE_RATIONALE The scientific rationale for why this suggestion should be acquired. TEXT Not Null
SEASONAL_CONSTRAINTS This specifies whether there are seasonal constraints for this suggestion. Where are these seasonal constraints detailed? Just in the SPECIAL_NOTES or LSUBS fields?? Laz: LSUBS type fields and notes. Unclear if we need this? TINYINT
SUGGESTION_DATE The date and time the suggestion was made. DATETIME
SUCCESS This indicates whether the science goal for this suggestion has been achieved. TINYINT
SUCCESS_VALIDATOR_ID The ID of the person (from the People table) that validated that this suggestion was successful. I kind of want to break this out into a mapping table. INT(10) unsigned Foreign Key which references People (ID)
DATE_SUCCESS The date upon which this suggestion was validated as successful. This was a timestamp field, but that would get updated anytime any of the fields were changed, not just this one. So this field must be updated by whatever software marks SUCCESS. DATETIME
SPECIAL_NOTES This field contains any notes that are specific to details of this suggestion. TEXT
TARGET_NAME The name of the target for this suggestion. ENUM("MARS", "STARS", "PHOBOS", "DEIMOS", "SKY", "CAL", "LUNA") MARS
REPEAT_TARGET Does the suggested target need to be repeatedly imaged to fulfull the suggestion? TINYINT
NUMBER_OF_OBSERVATIONS Is this the number of observations that the suggestor needs for this suggestion. TINYINT(3) unsigned
LAST_UPDATE This column records the last time that a record was updated. TIMESTAMP

Table Options:

Copyright (C) 2004 Arizona Board of Regents on behalf of the Planetary Image Research Laboratory, Lunar and Planetary Laboratory at the University of Arizona.

This page was generated from the XML HiCat Data Dictionary. $Name: $

Contact

Please send comments to: HiCat@pirlmail.lpl.arizona.edu .