Property talk:P1444

Documentation

destination point
destination for this route (journey, flight, sailing, exploration, migration, etc.)
Representsdestination point or location (Q23458944)
Data typeItem
Template parameter|destination= in en:template:infobox Airliner accident
Domain
According to this template: geographic location (Q2221906)
According to statements in the property:
occurrence (Q1190554), itinerary (Q1322323), vehicle (Q42889), fictional occurrence (Q14136353) or expedition (Q2401485)
When possible, data should only be stored as statements
Allowed valuesany geographic location, e.g. airport, city, island, etc. (note: this should be moved to the property statements)
Example2013 Vuelta a España, Stage 12 (Q14702221)Tarragona (Q15088)
sinking of the MV Sewol (Q16338015)Port of Jeju (Q12616503)
Magellan’s expedition (Q1225170)Seville (Q8717)
Sourceinfoboxes (note: this information should be moved to a property statement; use property source website for the property (P1896))
Robot and gadget jobsBots can fill in from infoboxes.
Tracking: usageCategory:Pages using Wikidata property P1444 (Q20990035)
Tracking: local yes, WD nono label (Q101363837)
<complementary property>start point (P1427)
See alsovia (P2825), terminus (P559), primary destinations (P1302), terminus location (P609)
Lists
Proposal discussionProposal discussion
Current uses
Total34,015
Main statement32,81096.5% of uses
Qualifier1,1993.5% of uses
Reference6<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P1444#Value type Q17334923, Q618123, Q2169973, Q41176, Q6999, 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/P1444#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P1444#Scope, SPARQL
 
Value requires "country" (P17)
add value or define exception (Help)
Violations query: SELECT DISTINCT ?item ?itemLabel ?itemDescription ?value ?valueLabel ?valueDescription { ?item wdt:P1444 ?value . MINUS { ?value p:P17 [] } MINUS { ?value p:P376 [] } MINUS { ?value p:P397 [] } MINUS { ?value wdt:P31 wd:Q5107 } MINUS { ?value wdt:P31 wd:Q2098155 } FILTER( !isBlank(?value) && ?value not in ( wd:Q29876 , wd:Q41872 , wd:Q7204 ) ) SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } }
List of this constraint violations: Database reports/Complex constraint violations/P1444#Value requires "country" (P17)
 
This property is being used by:

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

Opposite edit

I do not know how to mention it, but this property seems to be the opposite of start point (P1427).

Kvardek du (talk) 09:50, 14 November 2014 (UTC)Reply

I think we should attempt to complete the missing essential information for the items listed there. There are few exceptions there, but these can be dealt with afterwards.
--- Jura 08:42, 6 May 2018 (UTC)Reply

Value requires statement constraint: country? edit

@Jura1: You re-added "country" (P17) as a "property" (P2306) for "value requires statement constraint" (Q21510864). But an astronomical body, which can be the "destination point" (P1444) of a spaceflight, does not have property "country". And even many locations on Earth, such as Antarctica and North Pole, do not belong to any country. It is not a good idea to list (infinite) exceptions here. --Neo-Jay (talk) 08:49, 6 May 2018 (UTC)Reply

There might be a dozen for several thousands of items. See previous section. Places on Antarctica should have P17.
--- Jura 08:54, 6 May 2018 (UTC)Reply
@Jura1: Only a "dozen"? Just en:List of missions to Mars has 47 missions already. And the number of missions to Mars (not mention the missions to other astronomical bodies) will surely grow significantly in the near future. It is not acceptable to list too many exceptions here. --Neo-Jay (talk) 09:09, 6 May 2018 (UTC)Reply
I will keep an eye on the exceptions. Currently there are 59 violations. Most can be fixed. Just don't set the constraint to mandatory.
--- Jura 09:12, 6 May 2018 (UTC)Reply
@Jura1: Do you mean that you want to list (at least) 47 exceptions? That will be a bad idea and I cannot agree. Your edit should be reverted.--Neo-Jay (talk) 09:13, 6 May 2018 (UTC)Reply
@Jura1: Your last edit 20 days ago was reverted by me. It was you who added this Q21510864 ("value requires statement constraint") in the first place (on 3 August 2017). Please don't change the status quo before a consensus is achieved. Thanks. --Neo-Jay (talk) 09:45, 26 May 2018 (UTC)Reply
Status quo is that there is such a constraint. Please don't change it until a new one is formed.
--- Jura 09:47, 26 May 2018 (UTC)Reply
@Jura1: No. You changed the status quo unilaterally on 3 August 2017 without any discussion. My reverting is simply restoring the status quo ante. --Neo-Jay (talk) 09:55, 26 May 2018 (UTC)Reply
We don't delete the wiki just because you weren't around to discuss it when it was started. Sorry about that.
--- Jura 10:19, 26 May 2018 (UTC)Reply
@Jura1: Well, it's fine for an editor to edit Wikidata without discussion. But if someone else opposes that edit and gives serious reasons, it is appropriate to restore the status quo ante until a consensus is reached. --Neo-Jay (talk) 11:15, 26 May 2018 (UTC)Reply

change subclasses allowed for items with this property edit

Folllowing a discussion on start point (P1427), I update subject type constraint (Q21503250) with trail (Q628179) as a vàlid subclasse, because it's not only valid for the journey (occurrence (Q1190554)), but also the via where the journey is done by. Amadalvarez (talk) 05:22, 7 August 2018 (UTC)Reply

@Amadalvarez: I think that, for the linear feature where a journey occurs, P559 (terminus) or P609 (terminus location), not P1427 (start point) or P1444 (destination point), should be used. Relevant type constraints have been removed. For more discussion, please see here on Property talk:P1427. Thank you. --Neo-Jay (talk) 15:11, 8 June 2021 (UTC)Reply
Given the above, I've just removed pilgrims' way (Q337912) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:08, 11 July 2023 (UTC)Reply
Return to "P1444" page.