HiRISE Home


Last updated:
(none)

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 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:Web_Datebook
A table for storing information about HiRISE related events.

Field Description Type Null Limits Size Key Default Authority Source
ID This is the unique ID for each event. 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 db server
EVENT_TITLE The title of the event. VARCHAR(255) Not Null Date Book Editor
DESCRIPTION A short description of the event. VARCHAR(255) Date Book Editor
ENTRY_DATE The date the event was entered into the catalog. DATE Not Null Date Book Editor
START_DATE The starting date of the event. DATE Not Null Date Book Editor
START_TIME The start time of the event. TIME Date Book Editor
END_DATE The ending date of the event. DATE Not Null Date Book Editor
PUBLIC Is the even public? If yes, the event will be on the website, if no, then the even will be in the BackOffice. ENUM("YES","NO") Date Book Editor
STATUS The status of the event. TINYINT(1) Date Book Editor
LAST_UPDATE This column records when this record was last updated. TIMESTAMP Not Null db server

  • Field: the field name within the table.
  • Description: the definition for the field.
  • Type: the data type of the field.
  • Null: whether the field is allowed to be null.
  • Limits: the acceptable data range for the field.
  • Size: the upper limit data storage size for the field.
  • Default: the default value for the field.
  • Authority: the agency responsible for definition of the field.
  • Source: the most frequent source of data for this field.

Table Options:

  • type=InnoDB

Copyright (C) 2005-2020 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.