Property talk:P247
Documentation
international satellite designation, administered by the UN Committee on Space Research (COSPAR), similar but not synonymous with the NSSDCA ID (P8913)
Description | International Designator (Q54228), administered by the Committee on Space Research (COSPAR) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type | External identifier | ||||||||||||
Domain | According to this template:
spacecraft (Q40218)
According to statements in the property:
When possible, data should only be stored as statementsspacecraft (Q40218), spaceflight (Q5916), space station module (Q18812508), rocket (Q41291), rover (Q643962) or space debris (Q275450) | ||||||||||||
Allowed values | (19[5-9]|20[0-2])\d-[012]\d\d[A-Z]{1,2} | ||||||||||||
Example | Venera 7 (Q152800) → 1970-060A Mars 2MV-3 No.1 (Q18775) → 1962-062A | ||||||||||||
Formatter URL | https://nssdc.gsfc.nasa.gov/nmc/spacecraft/display.action?id=$1 | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P247 (Q41443728) | ||||||||||||
Related to country | United Nations (Q1065) (See 3 others) | ||||||||||||
See also | SCN (P377), NSSDCA ID (P8913) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | [not applicable Proposal discussion] | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
(19[5-9]|20[0-2])\d-[012]\d\d[A-Z]{1,2}
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P247#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P247#Item P377, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P247#Item P619, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P247#Item P1427, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P247#Item P375, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P247#Type Q40218, Q5916, Q18812508, Q41291, Q643962, Q275450, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P247#Entity types
Constraints built from templates (actual)
[edit]Other property info
[edit]
|
Usage and ambiguity with mission
[edit]I want to make sure I understand the best way to use this. Sometimes the mission can be confused with the spacecraft that is being identified with the COSPAR ID. A case where that is clear and generates an error is Apollo 11 (Q43653), which shares a COSPAR ID with Apollo 11 Command and Service Module (Q28101301). I think the most accurate/proper way in this case is:
- Apollo 11 (Q43653), no COSPAR ID (P247)
- Apollo 11 Command and Service Module (Q28101301), COSPAR ID (P247) of 1969-059A
- New instance of S-IVB (Q257161) named Apollo 11 SIVB, COSPAR ID (P247) of 1969-059B
- Eagle (Q28101302), COSPAR ID (P247) of 1969-059C
A less clear case is for Sputnik 1 (Q80811). The satellite and the upper stage of the rocket were both assigned COSPAR IDs. Sputnik 1 (Q80811) refers to both the mission and satellite. So is the following correct?
- space launch vehicle (P375) in Sputnik 1 (Q80811) with property COSPAR ID (P247) defined as 1957-001A (though technically not true as 1957-001A is for only a part of Sputnik (Q1393751)
- Sputnik 1 (Q80811) with statement COSPAR ID (P247) defined as 1957-001B
This same logic would apply for most if not all cases of SCN (P377) and Harvard designation (P5049).
I am new to Wikidata, let know if I did not clarify the ambiguity well or if I misused terminology, or if I need to advertise this question at other venues. Thanks for any assistance. Kees08 (talk) 21:58, 6 April 2020 (UTC)
Confusion with NSSDCA ID
[edit]There seems to be some confusion about how the COSPAR ID is related to the NSSDCA ID. These are two separate catalogs maintained by separate organizations. Most of the time the NSSDCA equals the COSPAR ID for a given object. However, many times the two ID numbers are different for the same object. For example: Lemur-2 https://nssdc.gsfc.nasa.gov/nmc/spacecraft/display.action?id=LEMUR2105, AESP-14 https://nssdc.gsfc.nasa.gov/nmc/spacecraft/display.action?id=1998067FM, Lightsail-2 https://nssdc.gsfc.nasa.gov/nmc/spacecraft/display.action?id=2019036AC
I have received confirmation from a NASA representative about this. The above examples are not errors. Any time the COSPAR ID is longer than 9 characters, the NSSDCA ID will be different due to their internal system limitations.
I would like to propose that a new property be created called NSSDCA ID to account for these differences. Item Q96142561 (Lightsail 2) technically has the wrong COSPAR ID due to this issue.Spacepat o (talk) 19:41, 19 October 2020 (UTC)
- Agreed. Benrem (talk) 16:53, 6 July 2024 (UTC)
COSPAR IDs for space launches (as opposed to spacecraft)
[edit]Hi,
The current formatter does not allow the COSPAR ID (P247) property to be defined for instances of space launch (Q7572593) or launch vehicle (Q697175).
As you know, spacecraft COSPAR IDs have the yyyy-nnnXXX
(e.g. 1969-059A
) syntax,
but it is also possible to use the yyyy-nnn
syntax without letter (e.g. 1969-059
) syntax for launch COSPAR IDs.
Extending the example provided by Kees08 above, for the launch of Apollo 11 (Q43653), the items would have the following COSPAR ID (P247) values:
1969-059
for Apollo 11 (Q43653)'s launch (and/or Saturn V launch vehicle)1969-059A
for Apollo 11 Command and Service Module (Q28101301)1969-059B
for the SIVB instance (to be created)1969-059C
for Eagle (Q28101302)
N.B.: It must be noted that the launcher can be designated as yyyy-nnn
during launch, but may become one or several space objects afterwards and then be designated as yyyy-nnnXXX
(such as 1969-059B
in this case).
I am thus hesitating between defining a new property for this identifier OR modifying the formatter of the present one to allow the absence of any letter.
- A new property would clearly separate both concepts, and each would have its own formatter (it would prevent using
1969-059A
to describe a space launch (Q7572593), or1969-059
to be used to describe a spacecraft (Q40218)). But it is unclear which one should be proposed for launch vehicle (Q697175). - On the other hand, I don't think it would be an issue to mix both, as it is clear that the absence of a letter corresponds to a launch, and not to a space object.
What do you think is best? Benrem (talk) 16:44, 6 July 2024 (UTC)
- I would not think the yyyy-nnn would ever apply to the launch vehicle itself; that's reserved for the mission/launch attempt in general. Components that reached orbit, yes, but not the launch vehicle as a whole. I don't really see a need for an entirely new property. — Huntster (t @ c) 17:24, 6 July 2024 (UTC)
- United Nations-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with format constraints
- Properties with unique value constraints
- Properties with single value constraints
- Properties with conflicts with constraints
- Properties with constraints on items using them
- Properties with constraints on type
- Properties with scope constraints
- Properties with entity type constraints