Difference between revisions of "Standard Values Quick Reference"
Jump to navigation
Jump to search
m (1 revision: Extracted from "Questions") |
(Extracted from Questions page) |
||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
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. We'll try to keep these updated. | 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. We'll try to keep these updated. | ||
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. | 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. | ||
| − | + | == In ''<Primary_Result_Summary>'' == | |
| − | + | === <data_regime> === | |
{| | {| | ||
|- | |- | ||
| Line 62: | Line 30: | ||
|} | |} | ||
| − | + | === <type> === | |
{| | {| | ||
|- | |- | ||
| Line 85: | Line 53: | ||
|} | |} | ||
| − | + | === <purpose> === | |
{| | {| | ||
|- | |- | ||
| Line 96: | Line 64: | ||
|} | |} | ||
| − | + | === <processing_level_id> === | |
{| | {| | ||
|- | |- | ||
| Line 106: | Line 74: | ||
|} | |} | ||
| − | + | == In <Observing_System_Component> == | |
| − | + | === <observing_system_component_type> === | |
{| | {| | ||
|- | |- | ||
| Line 123: | Line 91: | ||
|} | |} | ||
| − | + | === <reference_type> === | |
{| | {| | ||
|- | |- | ||
| Line 141: | Line 109: | ||
Let me know if you run across anything else that doesn't fit. | Let me know if you run across anything else that doesn't fit. | ||
| − | + | == In <Target_Identification> == | |
| − | + | === <type> === | |
{| | {| | ||
| Line 176: | Line 144: | ||
Clearly this list is not sufficient for small bodies, but at the moment a target is only allowed to have one ''<type>'' designation anyway, which is also problematic. So if you have an issue with target types, contact your PDS node consultant. | Clearly this list is not sufficient for small bodies, but at the moment a target is only allowed to have one ''<type>'' designation anyway, which is also problematic. So if you have an issue with target types, contact your PDS node consultant. | ||
| − | == | + | == <data_type> in ... == |
| − | === | + | === In character table fields (fixed width or delimited) === |
{| | {| | ||
|- | |- | ||
| Line 215: | Line 183: | ||
| − | === | + | === In binary table fields === |
{| | {| | ||
|- | |- | ||
| valign="top" | | | valign="top" | | ||
* IEEE754LSBDouble | * IEEE754LSBDouble | ||
| − | |||
* IEEE754LSBSingle | * IEEE754LSBSingle | ||
* IEEE754MSBDouble | * IEEE754MSBDouble | ||
* IEEE754MSBSingle | * IEEE754MSBSingle | ||
* ComplexLSB16 | * ComplexLSB16 | ||
| − | |||
* ComplexLSB8 | * ComplexLSB8 | ||
* ComplexMSB16 | * ComplexMSB16 | ||
| − | |||
* ComplexMSB8 | * ComplexMSB8 | ||
| valign="top" | | | valign="top" | | ||
* SignedBitString | * SignedBitString | ||
| − | |||
* SignedByte | * SignedByte | ||
* SignedLSB2 | * SignedLSB2 | ||
| − | |||
* SignedLSB4 | * SignedLSB4 | ||
* SignedLSB8 | * SignedLSB8 | ||
| − | |||
* SignedMSB2 | * SignedMSB2 | ||
| − | |||
* SignedMSB4 | * SignedMSB4 | ||
| − | |||
* SignedMSB8 | * SignedMSB8 | ||
| − | |||
* UnsignedBitString | * UnsignedBitString | ||
| − | |||
* UnsignedByte | * UnsignedByte | ||
| − | |||
* UnsignedLSB2 | * UnsignedLSB2 | ||
| − | |||
* UnsignedLSB4 | * UnsignedLSB4 | ||
| − | |||
* UnsignedLSB8 | * UnsignedLSB8 | ||
| − | |||
* UnsignedMSB2 | * UnsignedMSB2 | ||
| − | |||
* UnsignedMSB4 | * UnsignedMSB4 | ||
| − | |||
* UnsignedMSB8 | * UnsignedMSB8 | ||
| valign="top" | | | valign="top" | | ||
* ASCII_AnyURI | * ASCII_AnyURI | ||
| − | |||
* ASCII_Boolean | * ASCII_Boolean | ||
| − | |||
* ASCII_DOI | * ASCII_DOI | ||
| − | |||
* ASCII_Date | * ASCII_Date | ||
| − | |||
* ASCII_Date_DOY | * ASCII_Date_DOY | ||
| − | |||
* ASCII_Date_Time | * ASCII_Date_Time | ||
* ASCII_Date_Time_DOY | * ASCII_Date_Time_DOY | ||
| Line 278: | Line 225: | ||
* ASCII_Directory_Path_Name | * ASCII_Directory_Path_Name | ||
* ASCII_File_Name | * ASCII_File_Name | ||
| − | |||
* ASCII_File_Specification_Name | * ASCII_File_Specification_Name | ||
* ASCII_Integer | * ASCII_Integer | ||
| Line 284: | Line 230: | ||
* ASCII_LID | * ASCII_LID | ||
* ASCII_LIDVID | * ASCII_LIDVID | ||
| − | |||
* ASCII_LIDVID_LID | * ASCII_LIDVID_LID | ||
| − | |||
* ASCII_MD5_Checksum | * ASCII_MD5_Checksum | ||
* ASCII_NonNegative_Integer | * ASCII_NonNegative_Integer | ||
| − | |||
* ASCII_Numeric_Base16 | * ASCII_Numeric_Base16 | ||
* ASCII_Numeric_Base2 | * ASCII_Numeric_Base2 | ||
| − | |||
* ASCII_Numeric_Base8 | * ASCII_Numeric_Base8 | ||
| − | |||
* ASCII_Real | * ASCII_Real | ||
* ASCII_String | * ASCII_String | ||
* ASCII_Time | * ASCII_Time | ||
| − | |||
* ASCII_VID | * ASCII_VID | ||
* UTF8_String | * UTF8_String | ||
|} | |} | ||
| − | + | === In array elements === | |
| − | |||
{| | {| | ||
|- | |- | ||
| Line 313: | Line 252: | ||
* IEEE754MSBDouble | * IEEE754MSBDouble | ||
* IEEE754MSBSingle | * IEEE754MSBSingle | ||
| − | |||
* ComplexLSB16 | * ComplexLSB16 | ||
| − | |||
* ComplexLSB8 | * ComplexLSB8 | ||
* ComplexMSB16 | * ComplexMSB16 | ||
| Line 323: | Line 260: | ||
* SignedBitString | * SignedBitString | ||
* SignedByte | * SignedByte | ||
| − | |||
* SignedLSB2 | * SignedLSB2 | ||
* SignedLSB4 | * SignedLSB4 | ||
| Line 341: | Line 277: | ||
|} | |} | ||
| − | + | == <reference_type> in... == | |
| − | + | === <Observing_System_Component>/<Internal_Reference> === | |
{| | {| | ||
| Line 356: | Line 292: | ||
|} | |} | ||
| − | + | === <Reference_List>/<Internal_Reference> in Bundles === | |
{| | {| | ||
| Line 365: | Line 301: | ||
|} | |} | ||
| − | + | === <Reference_List>/<Internal_Reference> in Collections === | |
{| | {| | ||
| Line 387: | Line 323: | ||
|} | |} | ||
| − | + | === <Reference_List>/<Internal_Reference> in Document Products === | |
{| | {| | ||
| Line 399: | Line 335: | ||
|} | |} | ||
| − | + | === <Reference_list>/<Internal_Reference> in Observational Products === | |
{| | {| | ||
| Line 418: | Line 354: | ||
| − | + | == <external_standard_id> in...== | |
| − | + | === <Document_File> === | |
{| | {| | ||
| Line 442: | Line 378: | ||
|} | |} | ||
| − | + | == <collection_type> == | |
{| | {| | ||
Revision as of 00:29, 24 January 2013
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. We'll try to keep these updated.
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.
Contents
In <Primary_Result_Summary>
<data_regime>
|
|
|
<type>
|
|
|
<purpose>
|
<processing_level_id>
|
In <Observing_System_Component>
<observing_system_component_type>
|
<reference_type>
|
Note: Clearly these values are not sufficient for groundbased data, or indeed anything other than a spacecraft-mounted instrument. Following are some additional fake values we'll use until the above problem is fixed. These values will generate validation errors:
|
Let me know if you run across anything else that doesn't fit.
In <Target_Identification>
<type>
|
|
|
Clearly this list is not sufficient for small bodies, but at the moment a target is only allowed to have one <type> designation anyway, which is also problematic. So if you have an issue with target types, contact your PDS node consultant.
<data_type> in ...
In character table fields (fixed width or delimited)
|
|
|
|
In binary table fields
|
|
|
|
In array elements
|
|
|
<reference_type> in...
<Observing_System_Component>/<Internal_Reference>
|
| Note: Clearly these values are not sufficient for this context in SBN data (there are no values for ground-based observing, for a start). |
<Reference_List>/<Internal_Reference> in Bundles
|
<Reference_List>/<Internal_Reference> in Collections
|
|
<Reference_List>/<Internal_Reference> in Document Products
|
<Reference_list>/<Internal_Reference> in Observational Products
|
<external_standard_id> in...
<Document_File>
|
|
<collection_type>
|
