Property talk:P247

Active discussions

Documentation

COSPAR ID
international satellite designation, administered by the UN Committee on Space Research (COSPAR) and the US National Space Science Data Center (NSSDC)
DescriptionInternational Designator (Q54228), administered by the UN Committee on Space Research (COSPAR) and the US National Space Science Data Center (NSSDC)
RepresentsInternational Designator (Q54228)
Data typeExternal identifier
Domain
According to this template: spacecraft (Q40218)
According to statements in the property:
spacecraft (Q40218), spaceflight (Q5916) or space station module (Q18812508)
When possible, data should only be stored as statements
Allowed values(19[5-9]|20[0-2])\d-[01]\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 States of America (Q30) (See 433 others)
Lists
Proposal discussion[not applicable Proposal discussion]
Current uses
Total6,081
Main statement6,079>99.9% of uses
Qualifier2<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-[01]\d\d[A-Z]{1,2}: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P247#Format, SPARQL, SPARQL (new)
  Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P247#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
  Single value: this property generally contains a single value. (Help)
List of this constraint violations: Database reports/Constraint violations/P247#Single value, hourly updated report, SPARQL, SPARQL (new)
  Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P247#Conflicts with P31, hourly updated report, search, SPARQL, SPARQL (new)
  Conflicts with “coordinate location (P625): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P247#Conflicts with P625, hourly updated report, SPARQL, SPARQL (new)
  Item “SCN (P377): Items with this property should also have “SCN (P377)”. (Help)
Exceptions are possible as rare values may exist. Known exceptions: Prowler (Q14940655)
List of this constraint violations: Database reports/Constraint violations/P247#Item P377, search, SPARQL, SPARQL (new)
  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.
List of this constraint violations: Database reports/Constraint violations/P247#Item P619, SPARQL, SPARQL (new)
  Item “start point (P1427): Items with this property should also have “start point (P1427)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P247#Item P1427, search, SPARQL, SPARQL (new)
  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.
List of this constraint violations: Database reports/Constraint violations/P247#Item P375, search, SPARQL, SPARQL (new)
  Type “spacecraft (Q40218), spaceflight (Q5916), space station module (Q18812508): element must contain property “instance of (P31)” with classes “spacecraft (Q40218), spaceflight (Q5916), space station module (Q18812508)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P247#type Q40218, Q5916, Q18812508, SPARQL, SPARQL (new)
  Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of this constraint violations: Database reports/Constraint violations/P247#scope, hourly updated report, SPARQL, SPARQL (new)
  Format “\d\d\d\d.*: value must be formatted using this pattern (PCRE syntax). (Help)
List of this constraint violations: Database reports/Constraint violations/P247#Format, hourly updated report, SPARQL, SPARQL (new)
  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.
List of this constraint violations: Database reports/Constraint violations/P247#allowed entity types, SPARQL (new)

Constraints built from templates (actual)Edit

Other property infoEdit

 
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 missionEdit

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)

Confusion with NSSDCA IDEdit

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)

Return to "P247" page.