-
Notifications
You must be signed in to change notification settings - Fork 169
The ISIS3 Attached Spice Format
Running the spiceinit application with attach=true
will attach all of the SPICE data required by the camera model directly to the cube. There are 6 locations information is added to the cube:
- The
Kernels
group - The
NaifKeywords
group - The
InstrumentPointing
Table - The
InstrumentPosition
Table - The
BodyRotation
Table - The
SunPosition
Table
The following sections outline what is stored in each of these locations. The spiceinit application documentation shows what textual information is added to these locations.
The Kernels
group is already a part of the Cube label after ingestion (it is nested under the IsisCube
object). Usually, the only information it contains after ingestion is the NaifFrameCode
keyword and possibly the NaifCkCode
keyword. The NaifFrameCode
keyword contains the NAIF code for the instrument. So, information about the instrument will be stored as INS{NaifFrameCode}_{Some property}
in the NAIF kernels. For example the NaifFrameCode
for Kaguya Terrain Camera 2 is -131371
. So, the focal length for Kaguya Terrain Camera 2 is stored as INS-131371_FOCAL_LENGTH
. Usually, the NAIF ID for the instrument is also the NAIF ID for the sensor reference frame. If this is not the case, then the NaifCkCode
keyword contains the NAIF ID for the sensor reference frame.
- Building
- Writing Tests
- Test Data
- Start Contributing
- Public Release Process
- Continuous Integration
- Updating Application Documentation
- Deprecating Functionality
- LTS Release Process and Support
- RFC1 - Documentation Delivery
- RFC2 - ISIS3 Release Policy
- RFC3 - SPICE Modularization
- RFC3 - Impact on Application Users
- RFC4 - Migration of ISIS Data to GitHub - Updated Information 2020-03-16
- RFC5 - Remove old LRO LOLA/GRAIL SPK files
- RFC6 - BLOB Redesign
- Introduction to ISIS
- Locating and Ingesting Image Data
- ISIS Cube Format
- Understanding Bit Types
- Core Base and Multiplier
- Special Pixels
- FAQ