Difference between revisions of "Standard Values Quick Reference"
(→<type>: Added target types) |
|||
Line 647: | Line 647: | ||
* Other Investigation | * Other Investigation | ||
|} | |} | ||
+ | |||
+ | === In <Observation_Area> (or <Context_Area>)/<Target_Identification> === | ||
+ | |||
+ | {| | ||
+ | |- | ||
+ | | valign="top" | | ||
+ | * Asteroid | ||
+ | * Calibration ''(see note below)'' | ||
+ | * Comet | ||
+ | * Dust | ||
+ | * Dwarf Planet | ||
+ | * Galaxy | ||
+ | * Globular Cluster | ||
+ | * Meteorite | ||
+ | * Meteroid | ||
+ | * Meteroid Stream | ||
+ | * Nebula | ||
+ | * Open Cluster | ||
+ | |||
+ | | valign="top" | | ||
+ | * Planet | ||
+ | * Planetary Nebula | ||
+ | * Planetary System | ||
+ | * Plasma Cloud | ||
+ | * Ring | ||
+ | * Satellite | ||
+ | * Star | ||
+ | * Star Cluster | ||
+ | * Sun | ||
+ | * Terrestrial_Sample | ||
+ | * Trans-Neptunian Object | ||
+ | |} | ||
+ | |||
+ | {| class="wikitable" style="background-color:yellow" | ||
+ | | '''Note:''' ''Do not use '''Calibration''' as a target ''<type>'' value in data labels submitted to the SBN. "Calibration" is a reason to take an observation, and is noted in the ''<Primary_Result_Summary>''. | ||
+ | |} | ||
+ | |||
+ | Some targets, particularly small body targets, correspond to more than one of the listed ''type'' values. The <code><type></code> attribute may be repeated in these cases. If you have observed something that does not have a reasonable, corresponding ''type'' value in the above list, please contact your PDS node consultant as soon as possible with details. | ||
+ | |||
=== In <Observing_System_Component> === | === In <Observing_System_Component> === |
Revision as of 15:55, 4 August 2015
A number of attributes in the PDS common classes have standard value lists. You can look the standard values up in either the Data Dictionary - Abridged document or the Schematron file that comes with the PDS4 master schema. Both can be rather tedious to sort through.
Following are the most commonly used standard value lists for quick reference. They're sorted first by the attribute name, then by the context in which it appears. Many of these appear in several different classes, and the standard value lists depend on which class the attribute appears in, and sometimes - as in the case of <reference_type> - it depends on the containing class one or two levels above that. We'll try to keep these updated as changes and additions propagate to the master schema.
Note that spelling counts - including capitalization and use of underscores vs. blanks. Type these values exactly as they're shown below or you will get a validation error from the Schematron file.
As of 2014-04-29, these have been updated to reflect the Release 1.4.0.0 schemas.
Contents
- 1 <bundle_type>
- 2 <collection_type>
- 3 <coordinate_source>
- 4 <data_type>
- 5 <discipline_name>
- 6 <document_standard_id>
- 7 <domain>
- 8 <facetN>
- 9 <field_delimiter>
- 10 <local_reference_type>
- 11 <member_status>
- 12 <parsing_standard_id>
- 13 <processing_level>
- 14 <purpose>
- 15 <record_delimiter>
- 16 <reference_type>
- 16.1 In <Bundle_Member_Entry>
- 16.2 In <Inventory>
- 16.3 In <Investigation_Area>/<Internal_Reference>
- 16.4 In <Observing_System_Component>/<Internal_Reference>
- 16.5 In <Reference_List>/<Internal_Reference> in Bundles
- 16.6 In <Reference_List>/<Internal_Reference> in Collections
- 16.7 In <Reference_List>/<Internal_Reference> in Context Products
- 16.8 In <Reference_List>/<Internal_Reference> in Document Products
- 16.9 In <Reference_List>/<Internal_Reference> in Observational Products
- 17 <type>
- 17.1 In <Investigation_Area>
- 17.2 In <Observation_Area> (or <Context_Area>)/<Target_Identification>
- 17.3 In <Observing_System_Component>
- 17.4 In <Product_Context>/<Facility>
- 17.5 In <Product_Context>/<Instrument>
- 17.6 In <Product_Context>/<Instrument_Host>
- 17.7 In <Product_Context>/<Investigation>
- 17.8 In <Product_Context>/<Target>
- 18 <wavelength_range>
<bundle_type>
In <Bundle>
|
<collection_type>
In <Collection>
|
<coordinate_source>
NOTE: As of this writing, this attribute is required to contain one of the following values, but all of these values are also deprecated. Here's what SBN recommends:
In any event, you'll have to ignore either an error or a warning about this field. |
In <Telescope>
|
<data_type>
Follow the links below for a thumbnail description of each data type.
In character table fields (fixed width or delimited)
In binary table fields
In array elements
<discipline_name>
In <Primary_Result_Summary>/<Science_Facets>
|
|
<document_standard_id>
In <Document_File>
|
|
<domain>
In <Primary_Result_Summary>/<Science_Facets>
|
|
<facetN>
In <Primary_Result_Summary>/<Science_Facets>
The allowed values for <facet1> and <facet2> depend on the value of <discipline_name>, but are independent of each other. Not all disciplines have a facet2 value list, and there is no requirement to use these values if they are not applicable to your data. This table shows the discipline_name/facet correspondences:
discipline_name | facet1 | facet2 |
---|---|---|
Atmospheres |
|
not used |
Fields |
|
|
Flux Measurements |
|
not used |
Imaging |
|
not used |
Particles |
|
|
Ring-Moon Systems |
|
not used |
Small Bodies |
|
not used |
Spectroscopy |
|
not used |
If you have suggestions for additional facet values, please contact your PDS node representative.
<field_delimiter>
- Comma
- Horizontal Tab
- Semicolon
- Vertical Bar
<local_reference_type>
This attribute, defined in the core PDS4 namespace, will be assigned enumerated value lists in discipline and mission dictionaries. The contexts listed below refer to these namespaces by their PDS-assigned prefixes:
In <disp:Display_Settings>
- display_settings_to_array
<member_status>
In <Bundle_Member_Entry>
|
<parsing_standard_id>
In <Header>
|
|
In <Inventory>
|
In <Table_Delimited>
|
<processing_level>
In <Primary_Result_Summary>
|
<purpose>
In <Primary_Result_Summary>
|
<record_delimiter>
- Carriage-Return Line-Feed
<reference_type>
In <Bundle_Member_Entry>
|
|
In <Inventory>
|
In <Investigation_Area>/<Internal_Reference>
|
In <Observing_System_Component>/<Internal_Reference>
|
Use is_facility for ground-based observatories and labs. Use is_other for anything that doesn't clearly fit in one of the other categories.
In <Reference_List>/<Internal_Reference> in Bundles
|
In <Reference_List>/<Internal_Reference> in Collections
|
|
In <Reference_List>/<Internal_Reference> in Context Products
|
|
|
In <Reference_List>/<Internal_Reference> in Document Products
|
In <Reference_List>/<Internal_Reference> in Observational Products
|
|
<type>
In <Investigation_Area>
|
In <Observation_Area> (or <Context_Area>)/<Target_Identification>
|
|
Note: Do not use Calibration as a target <type> value in data labels submitted to the SBN. "Calibration" is a reason to take an observation, and is noted in the <Primary_Result_Summary>. |
Some targets, particularly small body targets, correspond to more than one of the listed type values. The <type>
attribute may be repeated in these cases. If you have observed something that does not have a reasonable, corresponding type value in the above list, please contact your PDS node consultant as soon as possible with details.
In <Observing_System_Component>
|
In <Product_Context>/<Facility>
|
In <Product_Context>/<Instrument>
|
|
|
In <Product_Context>/<Instrument_Host>
|
In <Product_Context>/<Investigation>
|
In <Product_Context>/<Target>
|
|
<wavelength_range>
In <Primary_Result_Summary>/<Science_Facets>
|
|