Property talk:P1083
Documentation
number of people allowed for a venue or vehicle
| Represents | seating capacity (Q16685058), individual seat (Q44666669) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Has quality | maximum (Q10578722) | ||||||||||||
| Data type | Quantity | ||||||||||||
| Template parameter | |capacity= in en:template:Infobox stadium | ||||||||||||
| Domain | architectural structure (Q811979), vehicle (Q42889), fictional building (Q15720793), fictional vehicle (Q20871196), fixed construction (Q811430), aircraft class (Q1875621), festival (Q132241), attraction (Q2800000), venue (Q17350442) or eating or drinking establishment (Q88985865) | ||||||||||||
| Allowed values | According to this template:
range between 1 and 400000
According to statements in the property:
When possible, data should only be stored as statements0 ≤ 𝓧 ≤ 900,000 | ||||||||||||
| Allowed units | not applicable, individual seat (Q44666669), bed (Q42177), human (Q5), passenger (Q319604), prisoner (Q1862087), student (Q48282), adult human (Q9584157) or hotel room (Q2948144) | ||||||||||||
| Example | Lang Park (Q643328) → 52,500 | ||||||||||||
| Source | External reference, Wikipedia list article (note: this information should be moved to a property statement; use property source website for the property (P1896)) | ||||||||||||
| Robot and gadget jobs | they should be allowed | ||||||||||||
| Tracking: usage | Category:Pages using Wikidata property P1083 (Q27826989) | ||||||||||||
| See also | throughput (P2957) | ||||||||||||
| Lists |
| ||||||||||||
| Proposal discussion | Proposal discussion | ||||||||||||
| Current uses |
|
List of violations of this constraint: Database reports/Constraint violations/P1083#Units
List of violations of this constraint: Database reports/Constraint violations/P1083#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1083#No Bounds, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1083#Type Q811979, Q42889, Q15720793, Q20871196, Q811430, Q1875621, Q132241, Q2800000, Q17350442, Q88985865, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1083#Entity types
(Help)
Violations query:
SELECT ?item ?capacity { ?item wdt:P31/wdt:P279* wd:Q483110; wdt:P1083 ?capacity. FILTER (?capacity < 100) }List of this constraint violations: Database reports/Complex constraint violations/P1083#Detect some mistakes
(Help)
Violations query:
SELECT ?item ?capacity ?nbStatements ?ratio { ?item wdt:P31/wdt:P279* wd:Q483110; wdt:P1083 ?capacity; wikibase:statements ?nbStatements. BIND (?capacity / ?nbStatements AS ?ratio) FILTER (?ratio < 10) }List of this constraint violations: Database reports/Complex constraint violations/P1083#Detect some mistakes # 2
| ||||||
Discussion edit
What about standing room of a venue? edit
I think I get the idea behind this property, but at least for some venues I know it would be more applicable to talk of capacity. Often the seating capacity is not known, only the full capacity (seating capacity plus standing room) is known. I guess for some venues (like theaters) we want to know the seating capacity (as normally people sit there during a stage performance). For stadiums (sports venues in general) we want to know the "total capacity", so the number of people that are allowed in a venue during a sports event (seating capacity plus standing room). Maybe this could be reflected in the label/description in some way, not sure how. In the end the correct term for sports venues with standing room would probably be "maximum number of tickets that are be sold for this venue" as we don't really know what the maximum legal capacity is, we (usually) only know how many tickets are sold for sports events in such a venue. E.g. a sports club could sell less tickets for the standing room in this venue than are allowed by law (legal capacity) as they think this would be too uncomfortable for the spectators (just a made up example, not sure if this is realistic :) --Bthfan (talk) 17:04, 13 July 2014 (UTC)
- I agree, the English label and description should be changed. In all other languages, the label already implies the total capacity. --Pasleim (talk) 10:48, 28 October 2014 (UTC)
- Changed. --Denny (talk) 16:00, 17 September 2015 (UTC)
From the new label it's not clear that it's meant for venues. Now it's used (and erronousely did so myself) for vehicles with units such as "aircraft pilot (Q2095549)" and "passenger (Q319604)". Should we add "venue" into the label? --- Jura 14:44, 7 October 2015 (UTC)
- I think it's okay to use this property also for vehicles but I really don't like the units aircraft pilot (Q2095549) and passenger (Q319604). metre (Q11573), millennium (Q36507) etc. are units but not aircraft pilot (Q2095549). --Pasleim (talk) 16:07, 7 October 2015 (UTC)
Standing room again: if we use the total capacity (which is useful since often there is no other number available), the allowed unit still only is "seat", which gives a wrong impression. "Person" (possibly Q215627?) should be allowed, too. --Anvilaquarius (talk) 08:38, 14 December 2018 (UTC)
Why limit to people? edit
Given that we can specify units, should we broaden this property to be able to talk about the number of containers on a container ship, or the number of bullets in a gun? Bovlb (talk) 00:02, 26 October 2015 (UTC)
- Option: Object has characteristic (P1552) +capacity (Q28443346)+numeric value (P1181) --Fractaler (talk) 10:24, 8 June 2017 (UTC)
Conflicts with instances of statements for architectural structures and organizations edit
As observed in the WikiProject Performing Arts:
Many Wikidata items confound architectural structures (buildings, venues) and organizations. This is a problem when we add statements that may apply to either of them, such as inception (P571).
Further to discussions with members of this Wikiproject – as an attempt to reduce the occurrence of conflicting instance of (P31) statements for architectural structure (Q811979) and organization (Q43229) on the same item – we decided to implement a conflicts-with constraint (Q21502838) on this property.
Users encountering this constraint are encouraged to create distinct items for the architectural structure and the organization.
Comments on this constraint and/or the issue of organization/building conflation are welcome, of course. --Fjjulien (talk) 23:45, 26 November 2020 (UTC)
- Monitoring of the effectiveness of this constraint
- When this constraint was initially implemented, there were 857 organization items with a maximum capacity statement. As of July 15, 2021, the same query (https://w.wiki/oJ9) rendered 2888 results (many of which are actually restaurants or prisons). This constraint did not have the intended effect. In fact, the constraint was initially set as a suggested constraint and it did not prompt constraint warnings on items violating this constraint. As of July 15, 2021, after consultation with members of the WikiProject Performing arts, the constraint status (P2316) value was changed from suggestion constraint (Q62026391) to mandatory constraint (Q21502408). Fjjulien (talk) 15:32, 15 July 2021 (UTC)
- As of November 29, 2021, this query found 1843 organization items with a maximum capacity statement. Another query was written to monitor the most frequently used properties on items conflating a performing arts building (Q57660343) and a performing arts group (Q105815710) (https://w.wiki/4UEb). This other query found 29 performing arts group items with a maximum capacity statement. Fjjulien (talk) 15:25, 29 November 2021 (UTC)
Add crew unit? edit
"Complement" is a synonym for this property. "23 crew" might be a more sensible ship's complement than "23 human". BucketOfSquirrels (talk) 22:14, 24 October 2022 (UTC)