Difference between revisions of "Target Names"
m (Creation - Safety Save) |
(Creation - Safety Save) |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | Names for small bodies are tricky. Many minor planets have multiple designations, and it is common for new names to be added or existing names changed or modified sometimes long after they were initially assigned. There are also numerous name collision between small bodies of various types - there are comets that share names with asteroids, asteroids with the same name as meteorites, and planetary moons with the same names as asteroids. So when identifying observational targets in your PDS data products, it is vitally important that the target be uniquely identified by the < | + | Names for small bodies are tricky. Many minor planets have multiple designations, and it is common for new names to be added or existing names changed or modified sometimes long after they were initially assigned. There are also numerous name collision between small bodies of various types - there are comets that share names with asteroids, asteroids with the same name as meteorites, and planetary moons with the same names as asteroids. So when identifying observational targets in your PDS data products, it is vitally important that the target be uniquely identified by the <tt><name></tt> in its <tt><Target_Identification></tt> class. |
== Unambiguous Identification == | == Unambiguous Identification == | ||
| − | The make sure a target object is uniquely identified, you should formulate the | + | The make sure a target object is uniquely identified, you should formulate the ''<name>'' value so that the following is true: |
| − | # The < | + | # The <tt>name</tt> string contains at least one identifier that can only be associated with a single physical object. |
| − | # The < | + | # The <tt>name</tt> string contains at least two different identifiers for each object wherever possible. |
| − | The first rule ensures that there is only a single object that could possibly be intended; the second provides a cross-check on that identification, in case the identity of the target object is questioned. To help with parsing < | + | The first rule ensures that there is only a single object that could possibly be intended; the second provides a cross-check on that identification, in case the identity of the target object is questioned. To help with parsing <tt>name</tt> strings for use in database searches, the SBN has developed the following style sheet for formulating target names. '''''You must use this format for all target names in products archived with the Small Bodies Node.''''' |
If you have any questions about the correct name string to use, please contact the Small Bodies Node and we will happily convert whatever ID you have to a unique name string for your labels. | If you have any questions about the correct name string to use, please contact the Small Bodies Node and we will happily convert whatever ID you have to a unique name string for your labels. | ||
| Line 15: | Line 15: | ||
== SBN Target Name Strings == | == SBN Target Name Strings == | ||
| − | Following are the rules for formulating values of the < | + | Following are the rules for formulating values of the <tt><name></tt> attribute in your <tt><Target_Identification></tt> classes for any and all data coming in to the SBN archives. |
=== Major Planets === | === Major Planets === | ||
| + | |||
| + | '''Format:''' ''<tt>Name</tt>'' | ||
| + | |||
| + | For the eight major planets (and the sun), the name string is just the properly capitalized English name - so "<tt>Jupiter</tt>", not "<tt>JUPITER</tt>" or "<tt>jupiter</tt>". | ||
| + | |||
| + | '''Examples:''' | ||
| + | * <tt>Earth</tt> | ||
| + | * <tt>Jupiter</tt> | ||
| + | * <tt>Sun</tt> | ||
| + | |||
| + | === Dwarf Planets === | ||
| + | |||
| + | '''Format:''' <tt>(''Minor_Planet_Number'') ''Name''</tt> | ||
| + | |||
| + | Dwarf planets should be identified by both Minor Planet Number in parentheses followed by their properly capitalized English name. | ||
| + | |||
| + | '''Examples:''' | ||
| + | * <tt>(1) Ceres</tt> | ||
| + | * <tt>(134340) Pluto</tt> | ||
| + | * <tt>(136199) Eris</tt> | ||
Revision as of 18:39, 15 July 2015
Contents
Introduction
Names for small bodies are tricky. Many minor planets have multiple designations, and it is common for new names to be added or existing names changed or modified sometimes long after they were initially assigned. There are also numerous name collision between small bodies of various types - there are comets that share names with asteroids, asteroids with the same name as meteorites, and planetary moons with the same names as asteroids. So when identifying observational targets in your PDS data products, it is vitally important that the target be uniquely identified by the <name> in its <Target_Identification> class.
Unambiguous Identification
The make sure a target object is uniquely identified, you should formulate the <name> value so that the following is true:
- The name string contains at least one identifier that can only be associated with a single physical object.
- The name string contains at least two different identifiers for each object wherever possible.
The first rule ensures that there is only a single object that could possibly be intended; the second provides a cross-check on that identification, in case the identity of the target object is questioned. To help with parsing name strings for use in database searches, the SBN has developed the following style sheet for formulating target names. You must use this format for all target names in products archived with the Small Bodies Node.
If you have any questions about the correct name string to use, please contact the Small Bodies Node and we will happily convert whatever ID you have to a unique name string for your labels.
SBN Target Name Strings
Following are the rules for formulating values of the <name> attribute in your <Target_Identification> classes for any and all data coming in to the SBN archives.
Major Planets
Format: Name
For the eight major planets (and the sun), the name string is just the properly capitalized English name - so "Jupiter", not "JUPITER" or "jupiter".
Examples:
- Earth
- Jupiter
- Sun
Dwarf Planets
Format: (Minor_Planet_Number) Name
Dwarf planets should be identified by both Minor Planet Number in parentheses followed by their properly capitalized English name.
Examples:
- (1) Ceres
- (134340) Pluto
- (136199) Eris
