HiRISE Home
Last updated:
(none)
|
-
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: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.
| Field |
Description |
Type |
Null |
Limits |
Size |
Key |
Default |
Authority |
Source |
| ID |
A unique integer ID assocated with each tag assignment.
|
INT(10) unsigned auto_increment |
Not Null |
|
|
Primary Key |
|
|
db server |
| OBSERVATION_ID |
The Observation ID of the product associated with this tag.
|
VARCHAR(20) |
Not Null |
|
|
|
|
|
Downlink tools |
| PRODUCT_ID |
The Product ID of the product associated with this tag.
|
VARCHAR(35) |
|
|
|
|
|
|
Downlink tools |
| VERSION |
The version id of the product this tag is associated with.
|
VARCHAR(255) |
Not Null |
|
|
|
|
|
Downlink tools |
| TAG_PATH |
The unique path within the TAG configuration file that uniquely
identifies the position of the TAG_NAME in the taggine hierarchy.
|
TEXT |
Not Null |
|
|
|
|
|
Tagsonomy configuration file |
| TAG_NAME |
The tag to be associated with the given product/observation.
|
VARCHAR(255) |
Not Null |
|
|
|
|
|
Downlink tools |
| USERNAME |
The system username of the user that assigned the tag to the product.
|
VARCHAR(25) |
Not Null |
|
|
|
|
|
Downlink tools |
| COMMENT |
A note from the user applying the tag to indicate why the tag was applied,
or any other relevant information relating to the tag application.
|
TEXT |
|
|
|
|
|
|
Downlink tools |
| RELATED_TAG_ID |
Some tags may require an action that must be completed, which will
result in another tag being applied to indicate the resolution.
The originating tag_id should be entered here to indicate what tag
is being referred to.
|
INT(10) unsigned |
|
|
|
Foreign Key which references Tags (ID) ON DELETE CASCADE |
|
|
Downlink tools |
| LAST_UPDATE |
This column records the last time that a record was updated.
|
TIMESTAMP |
|
|
|
|
|
|
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:
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.
|
