Property talk:P1110

From Wikidata
Jump to navigation Jump to search

Documentation

attendance
number of people (spectators, ticket holders) at an event or exhibition
Descriptionnumber of people who (passively) follow an event. For permanent locations like museum (Q33506), rather use visitors per year (P1174).
Representsattendance (Q659779)
Data typeQuantity
Template parameter"attendance" in en:template:Infobox International Football Competition
Domain
According to this template: all kinds of event (Q1656682)
According to statements in the property:
event (Q1656682) or work (Q386724)
When possible, data should only be stored as statements
Allowed values
According to this template: Positive integers
According to statements in the property:
0 ≤ 𝓧 ≤ 450,000,000,000
When possible, data should only be stored as statements
Allowed unitsnot applicable
Example1982 FIFA World Cup (Q46934) → 2,109,723
Tracking: usageCategory:Pages using Wikidata property P1110 (Q26250059)
See alsonumber of participants (P1132), population (P1082), patronage (P3872), number of viewers/listeners (P5436)
Lists
Proposal discussionProposal discussion
Current uses
Total34,998
Main statement34,69599.1% of uses
Qualifier3010.9% of uses
Reference2<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “event (Q1656682), work (Q386724): item must contain property “instance of (P31)” with classes “event (Q1656682), work (Q386724)” 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/P1110#Type Q1656682, Q386724, SPARQL
Range from “0” to “450000000000”: values should be in the range from “0” to “450000000000”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1110#Range, hourly updated report
Units: “novalue”: 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/P1110#Units
Integer: values should be integers (ie. they shouldn't have a fractional part) (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/P1110#integer, SPARQL
This property is being used by:

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


Guidelines

[edit]

This property is currently described as "number of people at an event", which is not very precise. It is currently used in Berwick Run for the Diamonds (Q4896006) apparently in the sense of "number of people taking part to the events (that is it does not count spectators, as I would have thought at first sight). I think we need to define more precisely if and how this property (and others) can apply to football match, exhibitions, yearly number of visitors for a monument, number of journey in a metro line, number of people flying from an airport, unique visitors of a website (I am trying to find examples that are very dissimilar so that we can see more clearly that things may be tricky). --Zolo (talk) 13:38, 1 February 2014 (UTC)[reply]

The annual number of visitor of a national park can be tricky, if I remember correclty, the number of visitor of La Mauricie National Park (Q1798539) can be 160000 by unique visitor to near 300000 by visitor/day. I am not totally sur, but maybe we shoud create attendance properties with different time period, or add a qualifier to mark the period (year, month, week, day, event). I also see the problem for sport event since they have two type of peoples, the spectators and the players. --Fralambert (talk) 04:45, 2 February 2014 (UTC)[reply]
We now have number of participants (P1132) whose meaning is clearer. Can we decide that this property should be the number of visitors/spectators and rename it accordingly ? @Danrok:. Actually, it seems to be what was meant in the proposal, judging by the example.
About the time frame, I would suggest that, when the item is not a punctual event, we use start date - end date qualifiers. That way, things are explicit. I would say that the preferred time range should be one year, but it might happen that sources give other time lengths.
For other issues, maybe we can use qualifiers like criterion used (P1013) and revisit things once we have more data ? --Zolo (talk) 14:05, 8 February 2014 (UTC)[reply]
Yes, I agree attendance would be the number of "punters", bums on seats, etc. Whereas participants could be the performers, sportspersons, musicians, or similar. Danrok (talk) 14:27, 8 February 2014 (UTC)[reply]
Although, I am not so sure that it is a good idea to use number of participants (P1132) to count teams or people. Perhaps, we need two types of number of participants (P1132) property, one for counting people and one for counting groups (teams, organizations). Otherwise it may be difficult to use the data for comparisons, and statistics. Danrok (talk) 14:37, 8 February 2014 (UTC)[reply]

Use for films

[edit]

I am wondering whether this property can be used to describe "tickets sold" for a film? I have made a tentative edit for The Olsen Gang Sees Red (Q1215282) [1]. Statistics Denmark (Q1164337) shows the results for "Solgte billetter" ("tickets sold"), rather than with a value that could be used with box office (P2142). I have also added a qualifier with country (P17). Alternatively, a new property should be proposed. — Finn Årup Nielsen (fnielsen) (talk) 14:30, 12 November 2018 (UTC)[reply]

I see that the property has already been used for French listings.
SELECT ?film ?filmLabel ?attendance WHERE {
  ?film wdt:P1110 ?attendance .
  ?film wdt:P31 wd:Q11424 .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
Try it!

I note that the qualifier is used inconsistently place of publication (P291) for Iron Man 2 (Q205028) and while I initially used country (P17) I now see that for France valid in place (P3005) is used, which I have switched to. — Finn Årup Nielsen (fnielsen) (talk) 21:36, 12 November 2018 (UTC)[reply]