Property talk:P609
Documentation
location of the terminus of a linear feature
Description | The geographical location (city, town, administrative unit, census-designated place, etc.) at the terminus of a linear feature. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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 statementsthoroughfare (Q83620), road (Q34442), canal (Q12284), piping (Q3679502), ferry route (Q18984099) or route section in a geographic region (Q120367839) | ||||||||||||
Allowed values | any (note: this should be moved to the property statements) | ||||||||||||
Usage notes | Use direction{P560} as a qualifier to identify which location is at which terminus. Use terminus{P559} to identify the feature at each terminus. | ||||||||||||
Example | Oklahoma State Highway 325 (Q2174691) → Boise City (Q833668) A501 road (Q89030335) → Finsbury (Q1817328) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P609 (Q38537793) | ||||||||||||
See also | terminus (P559), direction (P560), destination point (P1444) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P609#Type Q83620, Q34442, Q12284, Q3679502, Q18984099, Q120367839, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P609#Value type Q56061, Q486972, Q6671777, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P609#mandatory qualifier, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P609#Item P17, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P609#Entity types
List of violations of this constraint: Database reports/Constraint violations/P609#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.) |
Which value should be used if a road is ring road (Q510662), or a railway line is Circle Line (Q4228983)[edit]
--Liuxinyu970226 (talk) 23:47, 22 September 2016 (UTC)
Request[edit]
Could the value-type constraint (Q21510865) of this property be "expanded" in order to allow instance of (P31) border (Q133346) as valid terminus locations aside from just instance of (P31) administrative territorial entity (Q56061)? Regards.--Asqueladd (talk) 14:05, 27 August 2018 (UTC)
- The value type constraint is just plain daft. First, administrative territorial entity (Q56061) is a very poor choice for a terminus. Administrative territorial entities are areas - normally large in relation to the terminus of a linear feature - and normally contrain within them features or items that are the actual terminus location of the linear feature. Second, and whoever wrote the type constraint might want to sit themelves down for this, not all linear features such as roads terminate at human settlements. Some, for instance, terminate at junctions with other roads, miles from the nearest human settlement.
- In the absence of any analysis of the values for the large set of things at which features can terminate, I think the appropriate thing to do right now would be to remove the constraint fullstop. --Tagishsimon (talk) 18:57, 17 October 2019 (UTC)
Adding cycling routes to subject type constraint[edit]
Can we allow this property to be used with long-distance cycling route (Q353027), they are functionally the same as cycling route (Q102307360) and long-distance cycling route (Q353027) is subclass of (P279)? They can have well defined terminus locations
In my case, it's for Route Verte 6 (Q3444019) which is a province-wide route composed of different long distance routes in order to form the route
- All Properties
- Properties with wikibase-item-datatype
- Properties used on 10000+ items
- Properties with constraints on type
- Properties with conflicts with constraints
- Properties with required qualifiers constraints
- Properties with constraints on items using them
- Properties with entity type constraints
- Properties with scope constraints