Property talk:P1145
Latest comment: 10 years ago by Paperoastro in topic Minor planets
Documentation
Lagrangian point
libration point of an object (default: object-sun-earth)
libration point of an object (default: object-sun-earth)
| Description | The libration point at which a space craft or astronomical object is | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Represents | Lagrangian point (Q190463) | |||||||||
| Data type | Item | |||||||||
| Template parameter | Infobox space flight: orbit_reference? | |||||||||
| Domain | According to this template:
space craft - artificial satellite (Q26540) or astronomical object (Q6999)
According to statements in the property:
When possible, data should only be stored as statementsphysical object (Q223557) or asteroid classification (Q15101896) | |||||||||
| Allowed values | Lagrangian point / libration point: Lagrangian point (Q190463) - L1 to L5 (note: this should be moved to the property statements) | |||||||||
| Example | Gaia (Q767805) → L2-Earth-Sun (Q15725510) 13185 Agasthenes (Q679982) → L4-Jupiter-Sun (Q15726288) | |||||||||
| Source | technical sources (note: this information should be moved to a property statement; use property source website for the property (P1896)) | |||||||||
| Lists |
| |||||||||
| Proposal discussion | Proposal discussion | |||||||||
| Current uses |
| |||||||||
| Search for values |
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1145#Single value, hourly updated report, SPARQL
Type “physical object (Q223557), asteroid classification (Q15101896)”: item must contain property “instance of (P31)” with classes “physical object (Q223557), asteroid classification (Q15101896)” or their subclasses (defined using subclass of (P279)). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1145#Type Q223557, Q15101896, hourly updated report, SPARQL
Value type “Lagrangian point (Q190463)”: This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value Lagrangian point (Q190463) (or a subclass thereof). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1145#Value type Q190463, hourly updated report, SPARQL
Subclass/Instance edit
I think the lagrangian points should have a subclass of (P279) relationship to Lagrangian point (Q190463):
Specific lagrange points (e.g. L1 for Earth) can probably be an instance of (P31) relationship:
- L1-Earth --> instance of (P31) = L1 (general)
The items are not created yet. --Tobias1984 (talk) 14:44, 10 February 2014 (UTC)
Documentation edit
Minor planets edit
Minor planets are also related to Lagrangian points. Would it do any good to add them here? -- Lavallen (talk) 15:37, 17 February 2014 (UTC)
- Yes. And if you create any additional lagrange points, please add them to the list. --Tobias1984 (talk) 18:09, 17 February 2014 (UTC)
- Or the alternative would be to use other properties. The Jupiter-trojans can be divided by Trojan and Greek camp (if I rememeber correctly). Maybe would be better to use "part of" Trojan camp, who is a part of the LX Jupiter?
- But the Martian, Neptun etc trojans do not have "camps"... -- Lavallen (talk) 18:23, 17 February 2014 (UTC)
- I think both camp and minor planet should get this property as a statement. The "minor planet - part of - camp"-relationship sounds good too. @Paperoastro: - What do you think? --Tobias1984 (talk) 18:33, 17 February 2014 (UTC)
- Hi, Tobias1984 and Lavallen, thanks to ping me :-) . Your proposal is very interesting and I support it. In general, trojan asteroids can be distinguish from the others using property minor planet group (P196) and values Earth trojan (Q2658049), Mars trojan (Q1902545), Jupiter trojan (Q8101032), and Neptune trojan (Q336004), subclasses of trojan (Q19635). I'm trying to make a hierarchy also for this property.
- I suggest to not distinguish, if possible, between Greek and Trojan camps for these reasons:
- this division exists only for Jupiter (it seems to me);
- a reference of this article explains that some of trojans of Jupiter are in the wrong camp, so it is difficult to choose the right camp using the name;
- the JPL Small-Body Database (Q4026990) does not distinguish between Greek and Trojans camps of Jupiter, but, if exists another source, it will be welcome.
- --Paperoastro (talk) 22:15, 17 February 2014 (UTC)
- This source, tells which "camp". I think there are simliar sources for the Mars and Neptun trojans.
- And I think Saturn also have two trojan Moons. -- Lavallen (talk) 08:20, 18 February 2014 (UTC)
- Good, we can use certainly these information with this property! Imho Trojan and Greek camps can be considered synonyms of L4 and L5, at least on Jupiter (I don't know if astronomers use different words than L4 and L5 for other planets), so I would use only L4 and L5. --Paperoastro (talk) 10:03, 18 February 2014 (UTC) P.S.: yes, Saturn has trojan moons, but not in L4 and L5 of the orbit Saturn-Sun, but in L4 and L5 of the orbits Tethys-Saturn and Dione-Saturn! For this reason I suggest the creation of items for L1, L2, L3, L4 and L5 as generic Lagrangian points and use a qualifier to specify the pair of bodies involved (the e.g. Sun and Jupiter, Saturn and Tethys...)
- I think L4/L5-Jupiter-Sun can de facto be used as synonyms for Greek/Trojan camps, at least when it comes to minor planets. I'm not so sure if it would be applied to other kinds of objects. -- Lavallen (talk) 10:23, 18 February 2014 (UTC)
- The problem with qualifiers is that we can't query them yet, control constraint violations, and they are less compatible with SemanticWeb. An additional problem is that there is quite a lot of controversy about the naming of qualifiers. --Tobias1984 (talk) 10:10, 18 February 2014 (UTC)
- You are right, it is better not to use qualifiers, at now. --Paperoastro (talk) 12:37, 18 February 2014 (UTC)
- Good, we can use certainly these information with this property! Imho Trojan and Greek camps can be considered synonyms of L4 and L5, at least on Jupiter (I don't know if astronomers use different words than L4 and L5 for other planets), so I would use only L4 and L5. --Paperoastro (talk) 10:03, 18 February 2014 (UTC) P.S.: yes, Saturn has trojan moons, but not in L4 and L5 of the orbit Saturn-Sun, but in L4 and L5 of the orbits Tethys-Saturn and Dione-Saturn! For this reason I suggest the creation of items for L1, L2, L3, L4 and L5 as generic Lagrangian points and use a qualifier to specify the pair of bodies involved (the e.g. Sun and Jupiter, Saturn and Tethys...)
- I think both camp and minor planet should get this property as a statement. The "minor planet - part of - camp"-relationship sounds good too. @Paperoastro: - What do you think? --Tobias1984 (talk) 18:33, 17 February 2014 (UTC)