Property talk:P1174

From Wikidata
Jump to navigation Jump to search

Documentation

visitors per year
number of people visiting a location or an event each year
Descriptionnumber of visitors to a museum, attraction, place - number of visitors per year / attendance per year - Qualify with point in time (P585) or [ start time (P580) + end time (P582) ] and provide a source. For event (Q1656682), rather use attendance (P1110).
Representsnumber of visitors per year (Q30699681)
Data typeQuantity
Template parameter"Visitors" in en:Template:Infobox museum and equivalent Template:Infobox museum (Q6232685)
Domain
According to statements in the property:
geographical feature (Q618123), exhibition (Q464980), institution (Q178706), amusement park (Q194195) or tourist attraction (Q570116)
When possible, data should only be stored as statements
Allowed values
According to this template: positive integer values
According to statements in the property:
0 ≤ 𝓧 ≤ 70,000,0000 ≤ 𝓧 ≤ 1,000,000,000
When possible, data should only be stored as statements
Allowed unitsnot applicable
Example
According to statements in the property:
Eiffel Tower (Q243) → 7,000,000
Salon de la maison (Q3470114) → 103,000
When possible, data should only be stored as statements
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: usageCategory:Pages using Wikidata property P1174 (Q21037712)
Tracking: local yes, WD nono label (Q101364311)
See alsoattendance (P1110), patronage (P3872)
Lists
  • Items with the most statements of this property
  • Count of items by number of statements (chart)
  • Count of items by number of sitelinks (chart)
  • Items with the most identifier properties
  • Items with no other statements
  • Most recently created items
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history (total)
  • Chart by item creation date
  • Minimum and maximum
  • User:Laboramus/Units/P1174 (Units used)
  • Database reports/Complex constraint violations/P1174
  • Database reports/Constraint violations/P1174
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Total99,038
    Main statement99,036>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]
    Range from “0” to “70000000”: values should be in the range from “0” to “70000000”. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Smithsonian Institution (Q131626), avenue des Champs-Élysées (Q550)
    List of violations of this constraint: Database reports/Constraint violations/P1174#Range
    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/P1174#Units
    Required qualifier “point in time (P585): this property should be used with the listed qualifier. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Leo-Center (Q1797088)
    List of violations of this constraint: Database reports/Constraint violations/P1174#mandatory qualifier, SPARQL
    Integer: values should be integers (ie. they shouldn't have a fractional part) (Help)
    List of violations of this constraint: Database reports/Constraint violations/P1174#integer, hourly updated report, SPARQL
    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/P1174#Scope, hourly updated report, SPARQL
    Range from “0” to “1000000000”: values should be in the range from “0” to “1000000000”. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Moscow Metro (Q5499)
    List of violations of this constraint: Database reports/Constraint violations/P1174#Range
    Citation needed: the property must have at least one reference (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/P1174#citation needed
    Single value: this property generally contains a single value. (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/P1174#Single value, SPARQL
    Missing P1174 on a Q570116
    Missing visitors per year (P1174) on a tourist attraction (Q570116) (Help)
    Violations query: SELECT ?item WHERE { ?item wdt:P31 wd:Q570116. FILTER NOT EXISTS { ?item wdt:P1174 [] }. } ORDER BY ?item
    List of this constraint violations: Database reports/Complex constraint violations/P1174#Missing P1174 on a Q570116
    Value in Thailand
    In Thailand (Q869) (Help)
    Violations query: SELECT ?item ?value { ?item wdt:P1174 ?value. ?item wdt:P17 wd:Q869. FILTER (?value > 32588303) }
    List of this constraint violations: Database reports/Complex constraint violations/P1174#Value in Thailand
    This property is being used by:

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


    Deletion proposal

    [edit]

    In February 2014 a request for deletion was made for this property; the conclusion was to keep it (see deletion discussion).

    Bad constraint?

    [edit]

    It seems in many languages, and most users assume, that things like museums or tourist attractions cannot be geographical objects, and that only things like mountains, dams, or settlements can be. Users have removed geographical feature (Q618123) from the item tree seemingly in order to exclude things like buildings from being geographical objects. Indeed, the English Wikipedia page also doesn't include smaller and more temporary objects (like buildings) in that category. I think fixed construction (Q811430) and/or geographic location (Q2221906) should be included as a constraint as well, maybe. --BurritoBazooka (talk) 01:18, 30 September 2015 (UTC)[reply]

    Orlando

    [edit]

    Orlando (Q49233) has 68 million visitors a year, so I increased the constraint to 70 million. --U+1F360 (talk) 22:22, 27 July 2018 (UTC)[reply]