Property talk:P2595

From Wikidata
Jump to navigation Jump to search

Documentation

maximum gradient
maximum gradient on a route, expressed as a percentage
Representsgrade (Q1139344)
Has qualitymaximum (Q10578722)
Data typeQuantity
Template parameterw:de:Template:BS-daten, parameter "NEIGUNG"
Domainitinerary (Q2450078) (note: this should be moved to the property statements)
Allowed values
According to this template: 0-100 (percent) or positive numbers for 1 in n
According to statements in the property:
0 ≤ 𝓧 ≤ 1,000 per mille
When possible, data should only be stored as statements
Allowed unitsper mille (Q181011) or percent (Q11229)
ExampleSnowdon Mountain Railway (Q1798093) → 18.18 percent
Ffordd Pen Llech (Q16992125) → 37.45 percent
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
SourceWikipedia articles, external references (note: this information should be moved to a property statement; use property source website for the property (P1896))
Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
See alsoaverage gradient (P2198)
Lists
Proposal discussionProposal discussion
Current uses
Total2,178
Main statement2,176>99.9% of uses
Qualifier2<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P2595#Scope, hourly updated report, SPARQL
Units: “per mille (Q181011), percent (Q11229): 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/P2595#Units
Range from “0” to “1000”: values should be in the range from “0” to “1000”. (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/P2595#Range
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/P2595#Entity types
This property is being used by:

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

Units[edit]

This was originally expressed as a fraction of 1 with no units, e.g. 0.64. However Pasleim has now changed at least some instances of this to express it as hundredths with unit percent (Q11229) e.g. 64 percent (Q11229). The related average gradient (P2198) is still used in the first manner, and has constraints set to restrict it to that manner (which this property never seems to have had). I feel the two properties should use the same structure and so propose to return this to using fractions of 1 and set constraints accordingly. Thryduulf (talk) 12:34, 6 October 2016 (UTC)[reply]

Well, this property is used on 4 items. 2 values were in percentage and used unit percent (Q11229), 1 value was in percentage but without unit and 1 value was expressed as a fraction of 1. Not sure if returning to this mess is beneficial. --Pasleim (talk) 12:42, 6 October 2016 (UTC)[reply]
average gradient (P2198) is used on two items. One value is a fraction of 1, the other value is percentage value without unit. --Pasleim (talk) 12:47, 6 October 2016 (UTC)[reply]
No, I certainly don;t intend to return to a mess, so that was poor phrasing. I do though think we need consistency and fractions of 1 is what the constraints on average gradient (P2198) use and how I understood the intention to use both properties was in the proposals. Thryduulf (talk) 16:03, 6 October 2016 (UTC)[reply]