HiCat Data Dictionary
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.
- Group:Suggested and Planned Observations
- 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.
- Table:Suggested_Observations_GIS
-
This table stores suggestion geometry information using MySQL's geospatial
datatypes. This data must be kept in a table separate from the rest of the
suggestion information due to certian limitations on how these datatypes
are stored in the database.
- Table:Suggestion_Relations
-
This table defines relations between suggestions. The table specifies
a relation type, and an optional hypothesis field which can be used to
store a hypothesis for an imaging program.
- Table:Related_Suggestions_map
-
This table relates individual suggestion id's to a relation id in
the Suggestion_Relations table.
- Table:Special_Target_Categories
-
A table listing the types of special target requests.
- Table:Special_Target_Requests
-
This table holds the "want-to-have" suggestion list by cycle and user.
- Table:Special_Target_Categories_map
- Table:Suggested_Observations_Science_Themes_map
-
This table connects Suggested Observations with Science Themes.
- Table:Planned_Observations
-
Holds information about parameters of planned observations.
The parameters in this table are organized at the observation
level. Parameters at the CCD level are stored in the
Planned_CCD table. The values of these two tables will be
manipulated (insert, update, and delete) by HiPlan, and
HiCommand will retrieve the parameter values in these two
tables to generate command files. HiCommand will also input
some flag values back into this table, such as the various
COMMAND_FILE_* fields. HiDOG will also input observation
SUCCESS_ACQUIRED_TIME back into this table. This table is
related to the Suggested_Observations table by the mapping
table Suggested_Observations_Planned_Observations_map, and
is related to the Sequence_Plan table by the mapping table
?, and related to most of other tables by Observation_ID.
- Table:Suggested_Observations_Planned_Observations_map
-
A mapping table used to relate the Planned_Observations table
and the Suggested_Observations table together, based on the
many to many relationship between these two tables.
- Table:Planned_CCD_Parameters
-
Stores information about planned parameters per CCD, generated
by HiPlan and edited by a Co-I.
- Table:Planned_ADC_Settings
-
Stores the planned Analog-to-Digital Converter (ADC) settings for each CCD
used in an observation.
- Table:Sequence_Plan
- Table:Orbits
-
This table holds MRO orbital information related to specific orbits. These
generally take the form of times (eg. the light-to-dark terminator
crossing time, etc).
- Group:Acquired Observation and Products
- Table:EDR_Products
-
Store metadata about EDR products. Keeps track of product
identification information,EDR product header data (based
on EDR SIS), product processing history information, product
related files information. Also allows scientists to input
product statistical analysis results. For example mean image
pixel value or the standard deviation of pixel values. Most of
the values in this table will be input/updated by EDRgen
application.
- Table:Calibration_Data
-
This table holds the calibration data generated from calibration EDRs. A
number fields in this table are redundant with fields already in the
EDR_Products table, and should possibly be merged together.
- Table:Raw_Products_map
-
This table maps channelized raw data files (DAT's) to the parent .out files, if
a parent .out file was used to produce the DAT file.
- Table:Raw_Products
-
This table stores metadata about raw products downloaded from the RSDS.
- Table:Data_Summary
- Ad hoc Data Summary table
- Table:Observation_Geometry
- This table holds shared geometry parameters that apply to
an entire observation. Parameters that may be specific
to a product will be stored in the proper product table.
- Table:Frost_Statistics
-
This table stores frost/ice statistics for observations. The information
in this table can be used to monitor frost/ice found in observations, or
to locate observations that may have frost or ice. The statistics are
also used for refining the stretch algorithm in the HiMosMerge pipeline
(and probably the color nomap pipelines, eventually).
- Table:RDR_Products
-
Store metadata about RDR products. Keeps track of product
identification information,RDR product header data, product
processing history information, product related files
information. Most of the values in this table will be
input/updated by RDRgen application.
- Table:RDR_Products_GIS
-
This table holds the center and footprint information for RDR_Products as
indexed OpenGIS geometry objects. Geometric based searches will be much
faster when run against this table.
- Table:RDR_Products_Archive
-
Holds metadata about old versions of RDR products that have been removed
from the system.
- Table:Anaglyph_Products
-
Stores metadata about anaglyph products.
- Table:RDR_Products_EDR_Products_map
-
A table for mapping which specific EDR products a given RDR product has
been derived from.
- Table:Extras_Products
-
Track and store information about extras products.
- Table:DTM_Products
-
Store metadata about DTM products. Keeps track of product
identification information,DTM product header data, product
processing history information, product related files
information. Most of the values in this table will be
input/updated by DTMgen application.
- Table:DTM_Extras_Products
-
Track and store information about extras products.
- Table:HiPrecision_Products
-
Track and stores information about high precision geometry products.
- Table:CCD_Processing_Statistics
-
Stores statistics on the corrections made to the data to match the channels
in each CCD and to match the CCDs radiometrically.
- Table:Color_Processing_Statistics
-
Stores statistics on the corrections made to the data during color
processing.
- Table:Jitter_Statistics
-
Stores statitics from the jitter analysis.
- Group:Other
- Table:Extras_File_Types
-
This table lists the different types of Extras Products and indicates
if the specific product type should be released to the Planetary
Data System.
- Table:DTM_Extras_File_Types
-
This table lists the different types of Extras Products and indicates
if the specific product type should be released to the Planetary
Data System.
- Table:Anaglyph_File_Types
-
This table lists the different types of Anaglyph Products and indicates
if the specific product type should be released to the Planetary
Data System.
- Table:Engineering_Data
- Table:Science_Themes
-
This is a very simple list of the different science themes for
HiRISE.
- Table:People
-
Keeps track of information about people who will access the
HiCat database. People can belong to different groups, such
as Co-I, team, validater, suggestor, with different HiCat
access privileges.
- Table:Classrooms
-
Keeps track of information about classroom activities and
group educational projects. People can belong to different
classrooms via the People_Classrooms_map table.
- Table:Suggested_Observations_People_map
-
This table connects People with the Suggested Observations that they
have made.
- Table:Suggested_Observations_Classrooms_map
-
This table connects Classrooms with the Suggested Observations that they
have made.
- Table:People_Science_Themes_map
-
This table connects People with Science Themes. This is mostly
for team members, most records in the People table will not have
a connection to a Science Theme.
- Table:People_Classrooms_map
-
This table connects People to Classrooms.
- Table:Proffered_EDR_Products
-
This table maps a given PRODUCT_ID to the most current or best
version of a product in the EDR_Products table.
- Table:Proffered_RDR_Products
-
This table maps a given PRODUCT_ID to the most current or best
version of a product in the RDR_Products table.
- Table:Proffered_DTM_Products
-
This table maps a given PRODUCT_ID to the most current or best
version of a product in the DTM_Products table.
- Table:Proffered_HiPrecision_Products
-
This table maps a given PRODUCT_ID to the most current or best
version of a product in the HiPrecision_Products table.
- Table:Proffered_Extras_Products
-
This table maps a given Extras ID to the most current or best
version of a product in the Extras_Products table.
- Table:Proffered_DTM_Extras_Products
-
This table maps a given DTM Extras ID to the most current or best
version of a product in the Extras_Products table.
- Table:Proffered_Anaglyph_Products
-
This table maps a given Anaglyph ID to the most current or best
version of a product in the Anaglyph_Products table.
- Table:Web_Publications
-
Stores information about images release on the website, including
who released the image, when it was released, and the
location to which the image was released.
- Table:Web_Publications_Science_Themes_map
-
Stores the mappings between the web release and the science
theme(s) associated with it.
- Table:Web_Datebook
-
A table for storing information about HiRISE related events.
- Table:Publications
-
Stores information about HiRISE related publications, including
who released the image, when it was released, and the
location to which the image was released.
- Table:Publications_Observations_map
-
A mapping table that maps publications to observations. This allows us to link
observations and publications in a standard way, and allow quick lookups of
observations referenced within a publication.
- Table:SPICE
- Table:Product_Status
-
A table for assigning status tags to products. The tags in this table should
be exclusively status related. In order to enforce a single status value
in this table, a uniqueness constraint has been placed on the PRODUCT_ID and
VERSION columns. The tag definitions are stored in
a PVL style configuration file located at /HiRISE/?????? in the HiRISE logical
file system.
- Table:Tags
-
A table for assigning informational tags to products. These tags may be related
to status, special processing requirements, geologic feature information, or
any other use that we might put them to. The tag definitions are stored in
a PVL style configuration file located at /HiRISE/?????? in the HiRISE logical
file system. Note: This table definition is only a draft at this time, it is
not currently available in HiCat.
- Table:Feature_Locations
-
A table for storing the coordinates of potentially interesting features found
in HiRISE observations. These may be a single coordinate or multiple coordinate
sets defining an area, or even a center and radius (for example). Only line
and sample coordinates are currently supported.
- Table:Observation_Retirement_Status
-
This table tracks the date and time that observations were processed through
the different retirement stages. The first stage normally occurs in HiPlan
during the planning. The second stage occurs after the geometry processing
has completed.
- Table:Cycle_map
-
This table maps cycle identifiers to various other time related ranges such
as orbit ranges, dates, or LS. Note: This table is
currently a stop gap measure to allow some automated procedures to gather
cycle information. It is likely that the structure of this table may change
in the future and some fields will probably be moved/removed. It is
highly likely that the LS range will be removed.
- Table:Mars_Feature_Types
-
This table stores the feature names and codes as defined by the USGS
nomenclature service. The ID field is a foreign key in the
Mars_Nomenclature table.
- Table:Mars_Nomenclature
-
This table contain nomenclature for various regions on Mars.
- Table:Mars_Year
- A table mapping Mars years to UTC Earth dates
- Table:Pipeline_Configuration
- A table for storing some pipeline configuration parameters.
- Table:Footprints
-
A table for storing footprint information for variety of different mission
observations.
- Table:Suggested_Observations_Footprints_map
-
A mapping table between Suggested_Observations and the Footprints table.
- Table:RDR_Products_Footprints_map
-
A mapping table between RDR_Products and the Footprints table.
- Table:CTX_Footprints_map
-
A mapping table between CTX and the Footprints table.
- Table:CRISM_Footprints_map
-
A mapping table between CRISM and the Footprints table.
- Table:MOC_Footprints_map
-
A mapping table between MOC and the Footprints table.
- Group:Planetary Data System
- Table:EDR_Datasets
-
A table describing the PDS Datasets available for EDR's. There are several
columns in this table for which there is no clear description. These are
likely things that are used by the Planetary Image Atlas but are not
directly applicable to our local PDS node.
- Table:EDR_Inventory
-
This table contains additional metadata information needed by the PDS
Profile Server to construct paths and URLs to the released data products.
There are several seemingly redundant fields in this table, they are
required by the PDS profile server.
- Table:RDR_Datasets
-
A table describing the PDS Datasets available for RDR's. There are several
columns in this table for which there is no clear description. These are
likely things that are used by the Planetary Image Atlas but are not
directly applicable to our local PDS node.
- Table:RDR_Inventory
-
This table contains additional metadata information needed by the PDS
Profile Server to construct paths and URLs to the released data products.
There are several seemingly redundant fields in this table, they are
required by the PDS profile server.
Copyright (C) 2005-2022 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.
HEAD
Contact
Please send comments to:
HiCat@pirlmail.lpl.arizona.edu.