Property talk:P2243

From Wikidata
Jump to navigation Jump to search

Documentation

apoapsis
distance, at which a celestial body is the farthest to the object it orbits
Representsapoapsis distance (Q98875099)
Data typeQuantity
Domain
According to statements in the property:
astronomical object type (Q17444909), planetary system (Q206717), astronomical object (Q6999), spaceflight (Q5916), fictional astronomical object (Q15831598) or spacecraft (Q40218)
When possible, data should only be stored as statements
Allowed unitskilometre (Q828224) or astronomical unit (Q1811)
ExampleEarth (Q2) → 151,930,000 kilometre
1I/ʻOumuamua (Q42313338) → not applicable
Tracking: usageCategory:Pages using Wikidata property P2243 (Q26905049)
<complementary property>periapsis (P2244)
See alsosemi-major axis of an orbit (P2233)
Lists
Proposal discussionProposal discussion
Current uses
Total89,559
Main statement89,533>99.9% of uses
Qualifier26<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Units: “kilometre (Q828224), astronomical unit (Q1811): value unit must be one of listed. (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/P2243#Units
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/P2243#allowed qualifiers, SPARQL
Item “parent astronomical body (P397): Items with this property should also have “parent astronomical body (P397)”. (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/P2243#Item P397, SPARQL
Item “orbital eccentricity (P1096): Items with this property should also have “orbital eccentricity (P1096)”. (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/P2243#Item P1096, SPARQL
Item “periapsis (P2244): Items with this property should also have “periapsis (P2244)”. (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/P2243#Item P2244, 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/P2243#Entity types
Scope is as main value (Q54828448): the property must be used by specified way only (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/P2243#Scope, SPARQL
This property is being used by:

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

More general[edit]

@Tobias1984, Sjoerddebruin, Mbch331, Pikolas: This property looks too solarsentric. It's not useful for any moon, articifical satellite, or anything orbiting anything but the sun. Apoapsis looks to me like a more general property. This property is young, it is not to late to change. There are maybe some examples of objects where it is not obvious what it is related to, like objects in the Pluto-Charon system and other objects in binary/trinary systems. For those we can use properties like relative to (P2210) as a qualifier. -- Innocent bystander (talk) 15:22, 18 October 2015 (UTC)[reply]

This was proposed by Yair rand and nobody suggested it on the proposal page. I don't see any problems in changing it. Mbch331 (talk) 15:59, 18 October 2015 (UTC)[reply]
@Innocent bystander: Good idea. Aphelion can still be an alias. Can you also review the other properties on Wikidata:Property proposal/Space. --Tobias1984 (talk) 16:27, 18 October 2015 (UTC)[reply]
Please also review my proposal of "Periapsis_date". I am not fully pleased with the "significant event"-solution. -- Innocent bystander (talk) 20:11, 18 October 2015 (UTC)[reply]

Parent astronomical body[edit]

I don't think it should be needed to add the parent astronomical body (P397) property, at least when we talk about man made satellites. Since doing that requires to add the child astronomical body (P398) property to Earth (Q2), I found it rather impractical since we would need to that to 4000 satellites that are currently orbiting the Earth.--BugWarp (talk) 19:31, 24 November 2019 (UTC)[reply]

Change of orbits / Unicity[edit]

This property is meant to have a unique value. But then how can we document the changes of orbit? This is now mandatory that artifical satellites get their orbit changed at their end of life to minimize the risk of new space debris. I tried to document the deorbitation of Q3459966 and faced the unicity warning. --Don-vip (talk) 21:43, 4 April 2021 (UTC)[reply]

@Don-vip: I adjusted the unicity constraint to allow several values (as long as they have qualifiers to distinguish them) : Special:Diff/1396290560. I think it's good now. Notifying Notified participants of WikiProject Astronomy. Cheers, VIGNERON (talk) 11:24, 5 April 2021 (UTC)[reply]
We can also add a qualifier with the date of when the orbit has certain value of apoapsid. --Paperoastro (talk) 14:21, 5 April 2021 (UTC)[reply]
Note that there may be several different values for astronomical objects due to different measurements over the years. I'm not sure that a unique value constraint is appropriate here. Thanks. Mike Peel (talk) 18:52, 10 April 2021 (UTC)[reply]