Property talk:P247

From Wikidata
Jump to navigation Jump to search

Documentation

COSPAR ID
international satellite designation, administered by the UN Committee on Space Research (COSPAR), similar but not synonymous with the NSSDCA ID (P8913)
DescriptionInternational Designator (Q54228), administered by the Committee on Space Research (COSPAR)
Data typeExternal identifier
Domain
According to this template: spacecraft (Q40218)
According to statements in the property:
spacecraft (Q40218), spaceflight (Q5916), space station module (Q18812508), rocket (Q41291), rover (Q643962) or space debris (Q275450)
When possible, data should only be stored as statements
Allowed values(19[5-9]|20[0-2])\d-[012]\d\d[A-Z]{1,2}
ExampleVenera 7 (Q152800)1970-060A
Mars 2MV-3 No.1 (Q18775)1962-062A
Formatter URLhttps://nssdc.gsfc.nasa.gov/nmc/spacecraft/display.action?id=$1
Tracking: usageCategory:Pages using Wikidata property P247 (Q41443728)
Related to country United Nations (Q1065) (See 3 others)
See alsoSCN (P377), NSSDCA ID (P8913)
Lists
Proposal discussion[not applicable Proposal discussion]
Current uses
Total7,159
Main statement7,154>99.9% of uses
Qualifier3<0.1% of uses
Reference2<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “(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#Format, hourly updated report, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Hiscock Radiation Belt Explorer (Q127976929), M-Cubed (Q6712042)
List of violations of this constraint: Database reports/Constraint violations/P247#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P247#Single value, hourly updated report, SPARQL
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P247#Conflicts with P31, hourly updated report, search, SPARQL
Item “SCN (P377): Items with this property should also have “SCN (P377)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Prowler (Q14940655), LICIACube (Q109650148)
List of violations of this constraint: Database reports/Constraint violations/P247#Item P377, search, SPARQL
Item “UTC date of spacecraft launch (P619): Items with this property should also have “UTC date of spacecraft launch (P619)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P247#Item P619, SPARQL
Item “start point (P1427): Items with this property should also have “start point (P1427)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P247#Item P1427, search, SPARQL
Item “space launch vehicle (P375): Items with this property should also have “space launch vehicle (P375)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P247#Item P375, search, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P247#Scope, hourly updated report, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P247#Entity types

Constraints built from templates (actual)

[edit]

Other property info

[edit]
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

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:

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?

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)[reply]

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)[reply]

Agreed. Benrem (talk) 16:53, 6 July 2024 (UTC)[reply]

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:

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), or 1969-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)[reply]

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)[reply]