Difference between revisions of "Filling out the SPICE Kernel Files Class"

From The SBN Wiki
Jump to navigation Jump to search
(Creation)
(: Update for 1.4.0.1)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
The SPICE_Kernel_Files class is used to cite the specific SPICE kernel files used in calculating the associated geometry.  Since SPICE kernels are also archivable products, they will usually be referenced by their PDS logical identifier and version ID by the time (i.e., ''LIDVID'') by the time the associated data are archived.  If referencing by LIDVID presents a problem, you should let PDS node consultant know ASAP, and use the various names and IDs that are included optionally in this class to help link early mission data to its final SPICE kernels after the fact.
+
The SPICE_Kernel_Files class is used to cite the specific SPICE kernel files used in calculating the associated geometry.  Since SPICE kernels are also archivable products, they will usually be referenced by their PDS logical identifier and version ID (i.e., ''LIDVID'') by the time the associated data are archived.  If referencing by LIDVID presents a problem, you should let PDS node consultant know ASAP, and use the various names and IDs that are included optionally in this class to help link early mission data to its final SPICE kernels after the fact.
  
 
== <SPICE_Kernel_Identification> ==
 
== <SPICE_Kernel_Identification> ==
Line 11: Line 11:
 
'''''Usage Note'''''
 
'''''Usage Note'''''
  
In an ideal world, you would only ever need to provide the ''&lt;kernel_type&gt;'' and ''&lt;Internal_Reference&gt;'' attributes of this class to link directly to the URI of the SPICE kernel product on which the geometry is based.  But if the SPICE kernel products do not exist yet, you will need to use the other, optional attributes of this class to provide enough information for future users to find the corresponding kernels by these other parameters.
+
Always use ''&lt;Internal_Reference&gt;'' to identify any SPICE kernel that has a LIDVID, and always use the version ID (the "VID" part) when you do.
  
 
=== <kernel_type> ===
 
=== <kernel_type> ===
  
''REQUIRED ''
+
''OPTIONAL''
  
This is the standard NAIF/SPICE abbreviation used to identify kernels in that toolkit.  It must have one of the following values:
+
This is the standard NAIF/SPICE abbreviation used to identify kernels in that toolkit.  If it is used, it must have one of the following values:
  
 
{|
 
{|
Line 36: Line 36:
 
|}
 
|}
  
=== <file_name> ===
+
=== <spice_kernel_file_name> ===
  
''OPTIONAL''
+
''REQUIRED''
  
This is the name of the file containing the SPICE kernel, as assigned by NAIF.  Do not include path information (it is unlikely to be correct in the archive),  but do include the correct extension.
+
This is the name of the file containing the SPICE kernel.  Do not include path information (it is unlikely to be correct in the archive),  but do include the correct extension.
  
=== <frame_spice_id> ===
+
=== <kernel_provenance> ===
  
 
''OPTIONAL''
 
''OPTIONAL''
  
This attribute contains the numeric identifier assigned by NAIF to the reference frame associated with the data.
+
This attribute indicates whether the data in the kernel cited is a prediction, a reconstruction, a combination of those two, or if that distinction is not relevant (as in the case of a leap second kernel). It must contain one of the following values:
  
=== <frame_spice_name> ===
+
::*'''Mixed'''
 +
::*'''Predicted'''
 +
::*'''Provenance Not Applicable'''
 +
::*'''Reconstructed'''
  
''OPTIONAL''
+
{| class="wikitable" style="background-color: lightcyan"
 
+
|
This attribute provides the specific name string assigned by NAIF to the reference frame corresponding to the ''frame_spice_id'' value.
+
'''Note:''' ''While this attribute is technically optional, you should ''always'' use it to indicate at least at a coarse level the quality of the geometric values provided wherever that makes sense.''
 
+
|}
=== <body_spice_id> ===
 
 
 
''OPTIONAL''
 
 
 
This attribute contains the numeric identifier assigned by NAIF to some physical entity - a planet, a spacecraft, a system barycenter, etc.
 
 
 
=== <body_spice_name> ===
 
 
 
''OPTIONAL''
 
 
 
This attribute contains the name string assigned by NAIF to correspond to the ''body_spice_id''.
 
  
=== <local_spice_kernel_name> ===
+
=== <pds:Internal_Reference> ===
 
 
''OPTIONAL''
 
 
 
This attribute contains the name of the kernel file as it was identified in the local mission disk space.
 
 
 
=== <Internal_Reference> ===
 
  
 
''OPTIONAL''
 
''OPTIONAL''
Line 78: Line 64:
 
Use this class to identify your SPICE kernels by their PDS URI (LIDVID, in particular). This allows the kernels to be programmatically linked to this data product.
 
Use this class to identify your SPICE kernels by their PDS URI (LIDVID, in particular). This allows the kernels to be programmatically linked to this data product.
  
Note, however, that the elements in this class are considered to be in the PDS4 core namespace, '''''not''''' the geometry dictionary namespace.  So you will need to provide the PDS4 core namespace reference when using the elements. There are two ways to do that: by using a pre-defined namespace prefix, or by specifying the PDS4 core namespace URI via an ''xmlns'' XML-attribute in each of the tags.  For this page, we're using the namespace abbreviation as a prefix on the tag.
+
Note that this class is actually in the PDS namespace, as are all its elements, so you will need to indicate that namespace for this class and its elements. There are two ways to do that: by using a pre-defined namespace prefix, or by specifying the PDS4 core namespace URI via an ''xmlns'' XML-attribute in each of the tags.  For this page, we're using the namespace abbreviation as a prefix on the tag.
  
 
If that all sounds like gibberish to you, you might want to check the [[Schema_Referencing_in_PDS4_Labels#Namespace_References|Namespace Reference]] topic on the ''"Schema Referencing"'' page on this wiki.
 
If that all sounds like gibberish to you, you might want to check the [[Schema_Referencing_in_PDS4_Labels#Namespace_References|Namespace Reference]] topic on the ''"Schema Referencing"'' page on this wiki.
Line 92: Line 78:
 
''REQUIRED''
 
''REQUIRED''
  
This ''must'' have a value of '''data_to_spice_kernel'''.
+
This ''must'' have a value of '''geometry_to_SPICE_kernel'''.
 
 
{| class="wikitable" style="background-color: yellow"
 
|
 
'''''Note:''' Type carefully, this value is not currently being validated.
 
|}
 
  
 
==== <pds:comment> ====
 
==== <pds:comment> ====
Line 110: Line 91:
  
 
If you have any additional comments to make about the SPICE kernels you've referenced as a group, this is the place to do it.
 
If you have any additional comments to make about the SPICE kernels you've referenced as a group, this is the place to do it.
 +
 +
{| class="wikitable" style="background-color: yellow"
 +
|
 +
'''''Note:''' This attribute is currently repeatable, but it probably shouldn't be. Don't repeat it.
 +
|}

Latest revision as of 19:13, 17 January 2017

The SPICE_Kernel_Files class is used to cite the specific SPICE kernel files used in calculating the associated geometry. Since SPICE kernels are also archivable products, they will usually be referenced by their PDS logical identifier and version ID (i.e., LIDVID) by the time the associated data are archived. If referencing by LIDVID presents a problem, you should let PDS node consultant know ASAP, and use the various names and IDs that are included optionally in this class to help link early mission data to its final SPICE kernels after the fact.

<SPICE_Kernel_Identification>

REQUIRED

You are required to identify at least one SPICE kernel in your <SPICE_Kernel_Files> class. You will repeat this class for each kernel file you need to reference.

Note that if you reference a meta-kernel, you do not need to reference all the kernel files that the meta-kernel references. Make sure you include the appropriate version ID in the kernel reference, though.

Usage Note

Always use <Internal_Reference> to identify any SPICE kernel that has a LIDVID, and always use the version ID (the "VID" part) when you do.

<kernel_type>

OPTIONAL

This is the standard NAIF/SPICE abbreviation used to identify kernels in that toolkit. If it is used, it must have one of the following values:

  • CK
  • DBK
  • DSK
  • EK
  • FK
  • IK
  • LSK
  • MK
  • PCK
  • SCLK
  • SPK

<spice_kernel_file_name>

REQUIRED

This is the name of the file containing the SPICE kernel. Do not include path information (it is unlikely to be correct in the archive), but do include the correct extension.

<kernel_provenance>

OPTIONAL

This attribute indicates whether the data in the kernel cited is a prediction, a reconstruction, a combination of those two, or if that distinction is not relevant (as in the case of a leap second kernel). It must contain one of the following values:

  • Mixed
  • Predicted
  • Provenance Not Applicable
  • Reconstructed

Note: While this attribute is technically optional, you should always use it to indicate at least at a coarse level the quality of the geometric values provided wherever that makes sense.

<pds:Internal_Reference>

OPTIONAL

Use this class to identify your SPICE kernels by their PDS URI (LIDVID, in particular). This allows the kernels to be programmatically linked to this data product.

Note that this class is actually in the PDS namespace, as are all its elements, so you will need to indicate that namespace for this class and its elements. There are two ways to do that: by using a pre-defined namespace prefix, or by specifying the PDS4 core namespace URI via an xmlns XML-attribute in each of the tags. For this page, we're using the namespace abbreviation as a prefix on the tag.

If that all sounds like gibberish to you, you might want to check the Namespace Reference topic on the "Schema Referencing" page on this wiki.

<pds:lid_reference> or <pds:livid_reference>

REQUIRED

One or the other of these is required to be present. In most cases, version matters and you should reference your SPICE kernel products by LIDVID rather than just LID.

<pds:reference_type>

REQUIRED

This must have a value of geometry_to_SPICE_kernel.

<pds:comment>

OPTIONAL

If you have anything else you'd like to say about the particular kernel product being referenced, here would be the place to do it.

<comment>

OPTIONAL

If you have any additional comments to make about the SPICE kernels you've referenced as a group, this is the place to do it.

Note: This attribute is currently repeatable, but it probably shouldn't be. Don't repeat it.