Property talk:P2659

Latest comment: 5 years ago by Lucas Werkmeister (WMDE) in topic Range constraint

Documentation

topographic isolation
minimum distance to a point of higher elevation
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “mountain (Q8502), summit (Q207326), hill (Q54050): item must contain property “instance of (P31)” with classes “mountain (Q8502), summit (Q207326), hill (Q54050)” 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/P2659#Type Q8502, Q207326, Q54050, SPARQL
Units: “kilometre (Q828224): 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/P2659#Units
Range from “0” to “16520”: values should be in the range from “0” to “16520”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Mount Everest (Q513)
List of violations of this constraint: Database reports/Constraint violations/P2659#Range
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2659#Scope, hourly updated report, 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/P2659#Entity types
value < distance to parent peak
TODO: correct value or coordinates, adjust ranks, define exceptions (Help)
Violations query: SELECT ?item ?itemLabel ?parentpeak ?parentpeakLabel ?topo_dist ?dist { ?item wdt:P3137 ?parentpeak . ?item p:P2659 / psn:P2659 / wikibase:quantityAmount ?topo_dist . ?item wdt:P625 ?coor . ?parentpeak wdt:P625 ?parentpeak_coor . BIND( ROUND(geof:distance(?coor, ?parentpeak_coor)*1000) as ?dist) FILTER( ?topo_dist >= ?dist && (?topo_dist / ?dist) > 1.05 # 3% tolerance && ?topo_dist >= (?dist + 1000) # 1000 m tolerance ) FILTER( ?item not in ( wd:Q15397819 , wd:Q4115189 ) ) SERVICE wikibase:label { bd:serviceParam wikibase:language "en,en" } } LIMIT 100
List of this constraint violations: Database reports/Complex constraint violations/P2659#value < distance to parent peak
This property is being used by:

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

Statistics edit

Discussion edit

Range constraint edit

Why 961 km is regarded at Q739484 as a violation? --Infovarius (talk) 14:16, 21 June 2018 (UTC)Reply

@Lucas Werkmeister (WMDE):

  • Somehow it fails when you add "km". Maybe the check is in metres. It passes now that I increased the limit *1000. Is it a bug or do we need to add units to the constraint? Maybe Lucas Werkmeister can help.
    --- Jura 14:30, 21 June 2018 (UTC)Reply
@Infovarius, Jura1: WikibaseQualityConstraints applies unit conversions when checking “range” and “difference within range”. Since the constraint didn’t specify a range, it was interpreted as “metres” (the default unit for lengths). See also phabricator:T193870 :/ --Lucas Werkmeister (WMDE) (talk) 17:22, 21 June 2018 (UTC)Reply
Return to "P2659" page.