Property talk:P1101
Documentation
above ground floor count of a building (ground floor and attic included)
List of violations of this constraint: Database reports/Constraint violations/P1101#Type Q811979, Q15720793, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1101#No Bounds, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1101#integer, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1101#Entity types
List of violations of this constraint: Database reports/Constraint violations/P1101#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.) |
Ground floor included
editI added "ground floor" included. Some cultures include it and some dont, but we have to settle on a definition. --Zolo (talk) 13:39, 31 January 2014 (UTC)
- @Zolo: - I think that is reasonable as a building with only the ground floor would otherwise have 0 as the number of floors. Maybe we should also mention if cellar floors are counted or if that needs a separate property. And I think we should also discuss if this can be used for the number of decks on a ship @Danrok:. --Tobias1984 (talk) 16:59, 31 January 2014 (UTC)
- I would personnally say that we should not include floors below ground, at least not for the "preferred" value with this property. If we want to have data about them I would say that we should either create a new property or add another statement with this property ranked as "normal" and using excluding (P1011). I am fine with using this property for ship decks. --Zolo (talk) 19:10, 31 January 2014 (UTC)
- It may be best to follow this example: Taipei 101 So, two properties floors above ground and floors below ground. That could mean no need for storing the absolute total number of floors, because it's just the sum of those two numbers. Danrok (talk) 19:14, 31 January 2014 (UTC)
- @Danrok: I think it would be good idea to add to this property that it is above ground and create a second one for below ground. --Tobias1984 (talk) 23:13, 31 January 2014 (UTC)
- I already changed the name to floors above ground, just making a proposal for the other. Danrok (talk) 23:19, 31 January 2014 (UTC)
- @Danrok: I think it would be good idea to add to this property that it is above ground and create a second one for below ground. --Tobias1984 (talk) 23:13, 31 January 2014 (UTC)
- It may be best to follow this example: Taipei 101 So, two properties floors above ground and floors below ground. That could mean no need for storing the absolute total number of floors, because it's just the sum of those two numbers. Danrok (talk) 19:14, 31 January 2014 (UTC)
Constraint changes
editI increased the maximum value to 500 floors, due to floors above ground (P1101) of Sky Mile Tower (Q22704279) (it's still being planned only, but this property is meant to deal with fictional buildings as well). Since the range is a mandatory constraint (Q21502408), the exception to constraint (P2303) thing doesn't work there.
I also limited this property to Wikibase item (Q29934200) and scope as main value (Q54828448). There are 17,000 main value cases, but only 24 uses as a qualifier right now, some of them with location (P276) to indicate which floor an item is found on. --SM5POR (talk) 14:24, 15 January 2023 (UTC)
Mechanical floors included?
editWhat is the normal practice - exclude or include uninhabited mechanical floors? if yes, should they be explicitly marked in any way? Retired electrician (talk) 18:09, 28 April 2023 (UTC)