Property talk:P559
Documentation
the feature (intersecting road, train station, etc.) at the end of a linear feature
Description | The feature (intersecting road, train station, etc.) at the terminus of a linear feature. Use direction (P560) as a qualifier to identify which feature is at which terminus. Use terminus location (P609) to identify the geographical location of each terminus. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Represents | terminus (Q20202072) | ||||||||||||
Data type | Item | ||||||||||||
Domain | According to this template:
Linear features, especially man-made, like roads and rail lines
According to statements in the property:
When possible, data should only be stored as statementsgeographic location (Q2221906), public transport (Q178512), itinerary (Q1322323), aerial tramway (Q498002), thoroughfare (Q83620) or transport service itinerary (Q1067164) | ||||||||||||
Allowed values | any place (note: this should be moved to the property statements) | ||||||||||||
Example | Oklahoma State Highway 74 (Q2172683) → Interstate 35 in Oklahoma (Q2171631) Oklahoma State Highway 7 (Q2171857) Boucan Canot Beach (Q3390839) → cap Boucan Canot (Q26205063) Cap Homard (Q2937047) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P559 (Q26205053) | ||||||||||||
See also | terminus location (P609), connects with (P2789), towards (P5051) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P559#Value type Q27096213, Q178512, Q12819564, Q44782, Q228332, Q728937, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P559#Type Q2221906, Q178512, Q1322323, Q498002, Q83620, Q1067164, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P559#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P559#Entity types
Multi-value constraint
[edit]I doubt the multi-value constraint (Q21510857) is useful here. Often there is only one value one can add, e.g. in case there is only one end point of a street (a dead end street) that has and should have a Wikidata item. --Leit (talk) 20:20, 8 February 2020 (UTC) Removed.--Leit (talk) 05:27, 29 March 2020 (UTC)
Subject constraint
[edit]I'm not sure what changed where, but the size of Wikidata:Database reports/Constraint violations/P559 doubled on December 20, and every railway service that I've spot-checked that defines its termini is on it (see for example Carolinian (Q283663) or S1 (Q115689931). I think transport service itinerary (Q1067164) ought to be a valid subject. Mackensen (talk) 13:28, 24 December 2022 (UTC)
Recent (2023-08-16) changes to property constraint (P2302): subject type constraint
[edit]It appears that roads, streets, alleys etc. (including the Q2172683 example) are now red-flagged - they are not on whitelist. Thoroughfare is, but street is not. Is there a way around it? What's the proper top-level entry that will cover these instances? Retired electrician (talk) 00:13, 22 August 2023 (UTC)