Property talk:P6710

From Wikidata
Jump to navigation Jump to search

Documentation

linear reference
nominal distance commonly used to describe location along a route. Defined by operator/authority, it might not reflect physical distance
Representslinear referencing (Q1741425)
Data typeQuantity
Template parameteren:Template:Routemap
Domainbridge (Q12280), lock (Q105731) or port (Q44782)
Allowed valuesmile ≤ 𝓧 ≤ 10,000 mile
Allowed unitskilometre (Q828224), metre (Q11573) or mile (Q253276)
Example
According to this template:
According to statements in the property:
MKAD–Volgogradsky Prospekt interchange (Q112080196) → 11 kilometre
Bushey railway station (Q19817) → 16.05 mile
When possible, data should only be stored as statements
See alsodistance from river mouth (P2148), located on linear feature (P795), connecting line (P81)
Lists
Proposal discussionProposal discussion
Current uses
Total29,772
Main statement2290.8% of uses
Qualifier29,54399.2% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
No bounds: values can't have any bounds (e.g. 1 not 1±0) (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/P6710#No Bounds, SPARQL
Units: “kilometre (Q828224), metre (Q11573), mile (Q253276): value unit must be one of listed. (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/P6710#Units
Range from “0” to “10000”: values should be in the range from “0” to “10000”. (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/P6710#Range
Type “bridge (Q12280), lock (Q105731), port (Q44782): item must contain property “instance of (P31)” with classes “bridge (Q12280), lock (Q105731), port (Q44782)” or their subclasses (defined using subclass of (P279)). (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/P6710#Type Q12280, Q105731, Q44782, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): 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/P6710#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/P6710#Scope, SPARQL

Additional queries[edit]

@Jura1, DeltaIndiaRomeoKilo--, ArthurPSmith, Sabas88, GPSLeo, Sfan00 IMG: I struggle to differentiate between located on linear feature (P795) and linear reference (P6710). The intended use-case of both properties is the same; the implementation is a bit different. The former property is used >1000 times, the latter property is used <5 times (as of writing). Should we focus on the established property located on linear feature (P795) and remove/deprecate the property linear reference (P6710), or is it too late anyways? Thanks! --Simon04 (talk) 20:13, 29 October 2019 (UTC)[reply]