Shortcut: WD:PP/SPACE

Wikidata:Property proposal/Space

From Wikidata
Jump to: navigation, search


See also:
Wikidata:Property proposal/Pending - Properties which have been approved but which are on hold waiting for the appropriate datatype to be made available.
Wikidata:Properties for deletion - proposals for the deletion of properties.


This page is for the proposal of new properties.

Before proposing a property
  1. Check if the property already exists by looking at Wikidata:List of properties (manual list) and Special:AllPages.
  2. Check if the property is already pending or has been rejected.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically. See WD:WikiProject Infoboxes for suggestions.
  4. Select the right datatype for the Property.
  5. Start writing the documentation based on the preload form below and add it in the appropriate section.

Creating the property

  1. Creation can be done after 1 week by a property creator or an administrator.
  2. See steps when creating properties.

Add a request

This page is archived, currently at Archive 31.

To add a request, you should use this form:

=== {{TranslateThis | anchor = en
| en = PROPERTY NAME IN ENGLISH
| de = <!-- PROPERTY NAME IN German (optional) -->
| fr = <!-- PROPERTY NAME IN French (optional) -->
<!-- |xx = property names in some other languages -->
}} ===
{{Property documentation
|status                 = <!--leave this empty-->
|description            = {{TranslateThis
  | en = ...
  }}
|subject item           = <!-- item corresponding to the concept represented by the property, if applicable; example: item ORCID (Q51044) for property ORCID (P496) -->
|infobox parameter      = Wikipedia infobox parameters, if any; ex: "population" in [[:en:template:infobox settlement]]
|datatype               = put datatype here (item, string, media, coordinate, monolingual text, multilingual text, time, URL, number)
|domain                 = types of items that may bear this property
|allowed values         = type of linked items (Q template or text), list or range of allowed values, string pattern...
|source                 = external reference, Wikipedia list article, etc.
|example                = {{Q|1}} → {{Q|2}}
|formatter URL          = 
|filter                 = (sample: 7 digit number can be validated with edit filter [[Special:AbuseFilter/17]])
|robot and gadget jobs  = Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
}}

;Motivation

(Add your motivation for this property here.) ~~~~

;{{int:Talk}}

For a list of infobox parameters, you might want to use table format:

{{List of properties/Header}}

{{List of properties/Row|id=
|title          = audio
|type           = media
|qualifier      =
|description    = Commons sound file
|example-subject= Q187 <!-- Il Canto degli Italiani -->
|example-object = Inno di Mameli instrumental.ogg
}}

</table>

For blank forms, see Property documentation and List of properties/Row


Space / Космос[edit]

Expedition Missions[edit]

   In progress
Description Expeditions an astronaut has participated in
Data type Item
Example STS-124 (Q217550) -> Expedition 25, Expedition 26, Expedition 43, Expedition 44
Source Nasa web site, other
Proposed by --Adert (talk) 12:33, 6 May 2015 (UTC)
Discussion

Number spaceflight[edit]

   In progress
Description Number of space flights made by astronaut including this (qualifiers)
Data type Number
Example

STS-124 (Q217550) -> Crew -> Mark Kelly -> Number spaceflight (qualifiers) -> 3

Soyuz TMA-15M (Q610681) -> Crew -> Samantha Cristoforetti -> Number spaceflight (qualifiers) -> 1
Source Nasa web site, other
Proposed by --Adert (talk) 12:33, 6 May 2015 (UTC)
Discussion

Spacecraft code[edit]

   In progress
Description Code for this spacecraft (qualifiers)
Data type String
Example

Apollo 8 (Q184201) -> spacecraft -> Apollo Command/Service Module -> Spacecraft code (qualifiers) -> 103

Soyuz TMA-15M (Q610681) -> spacecraft -> Sojuz-TMA -> Spacecraft code (qualifiers) -> 11F732A47 No.715
Source Nasa web site, other
Proposed by --Adert (talk) 12:24, 6 May 2015 (UTC)
Discussion

The spacecraft for Apollo 8 (Q184201) (for example) should not be "Apollo Command/Service Module", but an item for the specific instance of that craft. The code should then be a property of that item. Someone at Wikidata:Project chat will probably tell you where to get help making the relevant queries. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:47, 6 May 2015 (UTC)

I do not know ... In this case we have an item for any spacecraft that has flown in space ... I'm not sure it's a good idea --Adert (talk) 16:47, 6 May 2015 (UTC)
No, we have an item for any craft that has flown a notable mission. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:01, 6 May 2015 (UTC)

Astronomical objects[edit]

See also Wikidata:WikiProject Astronomy/Properties for proposal and discussion about properties.
See also Wikidata:Property proposal/Pending for approved items awaiting the deployment of currently unavailable datatypes.

Recently Pending:

  • Apparent magnitude / Scheinbare Helligkeit / Magnitude apparente
  • Absolute magnitude / Absolute Helligkeit / Magnitude absolue
  • Distance / Entfernung
  • Redshift / Rotverschiebung / Décalage vers le rouge
  • Rotation period / Rotationsperiode / Période de rotation
  • Orbital period / Siderische Periode / Période orbitale
  • Semi-major axis / Große Halbachse / Grand axe
  • Proper motion / Eigenbewegung / Mouvement propre
  • Parallax / Parallaxe / Parallaxe
  • Radius
  • Flattening / / Aplatissement
  • Orbital inclination
  • Orbital eccentricity
  • M sin i
  • Color index
  • Flux
  • Observed separation
  • Orbit apsis
  • Radial velocity
  • Luminosity
  • Metallicity
  • Angular distance
  • Position angle

Eclipse properties[edit]

Various properties required for storing data related to lunar eclipses. Some of these might be relevant to other celestial events.

Contact times of eclipses[edit]

   In progress
Description Contact times of eclipses: P1, U1, U2, U3, U4, P4
Data type Time
Domain lunar and solar eclipses
Allowed values time in UTC
Example 6 April 2015, 03:22 UTC. qualifier <applies to part:U4>
Source Wikipedia list article, e.g. en:List of 21st-century lunar eclipses
I have amended the example as I understand it should be used. Please check I got it right.
Can this property be extended so it can be used on solar eclipses as well? Creating a property that can only be used on lunar eclipses seems a bit narrow. Filceolaire (talk) 00:10, 29 April 2015 (UTC)
Yes, I believe this is correct (see en:Solar eclipse of August 11, 1999#Notable times and coordinates for example. I will ask someone more knowledgeable to comment here. MSGJ (talk) 09:52, 29 April 2015 (UTC)
P1-4 and U1-4 apply to solar and lunar eclipses, but differently. A solar eclipse is a en:Transit (astronomy) so the timing is based on the viewing location INSIDE a shadow, while a lunar eclipse has viewers looking at an object INSIDE a shadow, so everyone sees the same appearance at the same universal time. So knowing the P1-4,U1-4 times for a solar eclipse are less useful for any given observer. Tomruen (talk) 01:08, 30 April 2015 (UTC)
If U4 for a solar eclipse is different from U4 for a lunar eclipse then we should have separate items for these with the "applies to part" qualifier linking to the appropriate item in each case. This means this property could be used for solar eclipses if we just change the label. I would Symbol support vote.svg Support this property if you made this change to the property label and description. Filceolaire (talk) 03:04, 30 April 2015 (UTC)
Could you explain what you mean by "This means this property could be used for solar eclipses if we just change the label." Does that mean that properties can have more than one label? Or do you mean that you could have two statements for "subject item of this property"? Or do you mean something else? MSGJ (talk) 12:24, 30 April 2015 (UTC)
Rename the property as "Contact time for eclipses". Change the description to "Contact time for lunar and solar eclipses (U1, U2 etc. lunar and U1, U2 etc. solar)". Filceolaire (talk) 16:41, 30 April 2015 (UTC)
✓ Done, although no corresponding items created yet MSGJ (talk) 09:22, 5 June 2015 (UTC)

Gamma of eclipse[edit]

   Ready
Represents gamma (Q827951)
Data type Number
Domain lunar eclipses
Allowed values a decimal number between approximately -1.5 and +1.5, specified to 3 decimal places
Example -1.057
Source Wikipedia list article, e.g. en:List of 21st-century lunar eclipses

Magnitude of eclipse[edit]

   In progress
Represents magnitude of eclipse (Q1268559)
Data type Number
Domain lunar eclipses
Allowed values a decimal number between approximately -3 and +3, specified to 3 decimal places
Example -1.057
Source Wikipedia list article, e.g. en:List of 21st-century lunar eclipses

Saros cycle of eclipse[edit]

   In progress
Represents Saros cycle (Q220397)
Data type Number
Domain lunar eclipses
Allowed values a whole number between -20 and 183
Example 130
Source Wikipedia list article, e.g. en:List of 21st-century lunar eclipses
Discussion

These properties are for describing lunar eclipses. I understand that times are not yet possible, so these can be put on hold if approved.

Proposed by: MSGJ (talk)

@MSGJ: please provide labels for each proposal individually. Josh Baumgartner (talk) 23:02, 20 April 2015 (UTC)
@Joshbaumgartner: Hi Josh, do you have any comments on the merits of this proposal? MSGJ (talk) 11:51, 28 April 2015 (UTC)
@MSGJ: On the surface they seem appropriate, but my concern was more administrative in nature. A nice clear label and description for each of the requested properties makes it much easier for a property creator to do the actual creation of your request once consensus is gained. Josh Baumgartner (talk) 20:27, 28 April 2015 (UTC)
Symbol support vote.svg Support useful to describe lunar (and solar) eclipses. --Pasleim (talk) 07:52, 26 April 2015 (UTC)

Periapsis_date[edit]

   In progress
Description The date of periapsis of anything in any kind of orbit. (Planets, Comets, Satellites etc)
Data type Time
Template parameter nästa_perihelium and förra_perihelium in sv:Mall:Infobox planet
Domain astronomical objects or artificial satellites
Allowed values time for perihelim/perigeum/periwhatever in each orbit
Example 1986-02-05 => Halley's Comet (Q23054)
Format and edit filter validation no
Source JPL Small-Body Database (Q4026990)
Robot and gadget jobs yes
Discussion

Especially useful for Comets, but can be applied to any kind of object.

Proposed by: Innocent bystander (talk)

Instead of having one property for perihelium and one for perigeum etc, I choose one periapsis-property for them all. Separating last/next_periapsis can be solved with software, when you compare with current date. One potential problem is satellites with short orbit, which can have hundreds of periapsis for one single year. -- Innocent bystander (talk) 11:20, 22 March 2015 (UTC)

Symbol oppose vote.svg Oppose use significant event (P793) --Pasleim (talk) 22:42, 20 May 2015 (UTC)