Property talk:P1082

From Wikidata
Jump to navigation Jump to search

Documentation

population
number of people inhabiting the place; number of people of subject
Descriptionnumber of people inhabiting the place [ human population (Q33829) ] ; use point in time (P585) as qualifier; use preferred rank for the most recent total value.
Representspopulation size (Q1613416)
Data typeQuantity
Template parameteren:Template:Infobox French commune (population + population date)
Domain
According to this template: geographic features: places
According to statements in the property:
territorial entity (Q1496967), state (Q7275), island (Q23442), statistical territorial entity (Q15042037), suburb (Q188509), human settlement (Q486972), continent (Q5107) and district (Q149621)
When possible, data should only be stored as statements
Allowed unitsnot applicable
Preferred rankdata with the most recent point in time qualifier (Q22676757)
ExampleSan Francisco (Q62) → 837,442
Åland Islands (Q5689) → 408
Sourcehttp://data.worldbank.org/indicator/SP.POP.TOTL
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: usageCategory:Pages using Wikidata property P1082 (Q20990019)
Tracking: local yes, WD nono label (Q32765317)
See alsofemale population (P1539), male population (P1540), tabular population (P4179), number of households (P1538)
Lists
  • Wikidata:Wikivoyage/Lists/Quickbar (Q25022717)
  • 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
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history
  • User:Laboramus/Units/P1082 (Units used)
  • Database reports/Complex constraint violations/P1082
  • Database reports/Constraint violations/P1082
  • Proposal discussionProperty proposal/Archive/18#P1082
    Current uses366,035
    [create] Create a translatable help page (preferably in English) for this property to be included here
    Units: “novalue”: value unit must be one of listed. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P1082#Units, SPARQL (new)
    Range from “0” to “10000000000”: values should be in the range from “0” to “10000000000”. (Help)
    List of this constraint violations: Database reports/Constraint violations/P1082#Range, hourly updated report, SPARQL (new)
    Qualifiers “determination method (P459), point in time (P585), criterion used (P1013), applies to part (P518), male population (P1540), female population (P1539): this property should be used only with the listed qualifiers. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P1082#Allowed qualifiers, SPARQL, SPARQL (new)
    Type “territorial entity (Q1496967), state (Q7275), island (Q23442), statistical territorial entity (Q15042037), suburb (Q188509), human settlement (Q486972), continent (Q5107), district (Q149621): element must contain property “instance of (P31)” with classes “territorial entity (Q1496967), state (Q7275), island (Q23442), statistical territorial entity (Q15042037), suburb (Q188509), human settlement (Q486972), continent (Q5107), district (Q149621)” or their subclasses (defined using subclass of (P279)). (Help)
    Exceptions are possible as rare values may exist. Known exceptions: Earth (Q2)
    List of this constraint violations: Database reports/Constraint violations/P1082#Type Q1496967, Q7275, Q23442, Q15042037, Q188509, Q486972, Q5107, Q149621, SPARQL, SPARQL (new)
    Conflicts with “country of citizenship (P27): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P1082#Conflicts with P27, SPARQL, SPARQL (new)
    Item “country (P17): Items with this property should also have “country (P17)”. (Help)
    Exceptions are possible as rare values may exist. Known exceptions: Earth (Q2)
    List of this constraint violations: Database reports/Constraint violations/P1082#Item P17, SPARQL, SPARQL (new)
    Conflicts with “point in time (P585): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P1082#Conflicts with P585, SPARQL, SPARQL (new)
    Integer: values should be integers (ie. they shouldn't have a fractional part) (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P1082#integer, SPARQL, SPARQL (new)
    Mandatory qualifier “point in time (P585): this property should be used with the listed qualifier. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P1082#mandatory qualifier, SPARQL, SPARQL (new)
    This property is being used by:

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

    Constraints[edit]

    Pictogram voting comment.svg Every country should have this property
    TODO: add P1082 (Help)
    Violations query: SELECT ?item { ?item wdt:P31 wd:Q6256 . FILTER NOT EXISTS { ?item wdt:P1082 [] } . FILTER NOT EXISTS { ?item wdt:P31 wd:Q3024240 } . }
    List of this constraint violations: Database reports/Complex constraint violations/P1082#Every country should have this property
    Pictogram voting comment.svg No preferred value
    P1082 with multiple values none of which is preferred (Help)
    Violations query: SELECT DISTINCT ?item { ?item wdt:P1082 []; p:P1082 ?statement; p:P1082 ?statement1 . FILTER( ?statement != ?statement1 ) . MINUS { ?item p:P1082/wikibase:rank wikibase:PreferredRank } . }
    List of this constraint violations: Database reports/Complex constraint violations/P1082#No preferred value

    Discussion[edit]

    Shouldn't this be a quantity, not a number?[edit]

    I think that this property has been created prematurely based on the newly-available "number" (dimensionless) datatype, and should instead wait for the "quantity" (with-dimension) datatype. The population is a number of things (in this case, persons), not just a number alone. James F. (talk) 00:45, 31 January 2014 (UTC)

    If this is the "number" datatype and not the "quantity" datatype, then it's horribly misnamed. TCN7JM 00:59, 31 January 2014 (UTC)
    I'm not sure entirely what you mean? See "Data type: <datatypes-type-number>" above (which no-doubt will get fixed soon to render as the intended message about it being a number). James F. (talk) 01:04, 31 January 2014 (UTC)
    Well, but I'm not sure that having a "people" dimension would be helpful... --Rschen7754 01:02, 31 January 2014 (UTC)
    Perhaps; however, the discussion last year about creating this was around making it as a quantity, not a number. James F. (talk) 01:03, 31 January 2014 (UTC)
    This property was created with the quantity datatype so I have no idea what this discussion here is about at all. Vogone talk 01:07, 31 January 2014 (UTC)
    @Vogone: Per Lydia's e-mail, you can only create quantities without dimensions (which were called 'numbers' for a while, but not now?)… James F. (talk) 01:22, 31 January 2014 (UTC)
    Even if that's the case, the datatype remains the same. There won't be a separation between a dimension-less 'numbers' datatype and a dimension-supporting 'quantities' datatype. Vogone talk 01:44, 31 January 2014 (UTC)
    Are you sure about that? --Rschen7754 01:46, 31 January 2014 (UTC)
    Aye, this is what Lydia told me on IRC. TCN7JM 03:31, 31 January 2014 (UTC)
    What dimension were you proposing? People? What is the SI definition of people?
    Number with dimension means that the number has a unit type and without it the number is meaning less. I can say the distance to there is 23 but until you know if that is metres or light-years that number is meaningless. Once you have that unit then you can convert into other units.
    Population does not need to have a unit to be meaningful so we can use a dimensionless number for it. Filceolaire (talk) 09:39, 21 February 2014 (UTC)

    Let's discuss it again, since dimensions are possible now. I propose that one can use human (Q5) or inhabitant (Q22947) as the main units. Also one can use additional variants for female population e.g., or number of households. So in these cases we won't need such qualifiers. --Infovarius (talk) 14:33, 30 September 2015 (UTC)

    What is the standard in adding which year is a population specified?[edit]

    Hi, I was wondering what is the qualifier to use to specify that this is the population for a said year. how about if it is not a year or a period. Also, are we just going to continuously add all population data on an item? or are we suppose to retain the 3 most recent? --Napoleon.tan (talk) 07:17, 12 February 2014 (UTC)

    Use point in time (P585). By the way, you can specify a more specific point in time than a year. I don't think we need to limit how many basic population statements are in an item. Historical population information is very useful. --Yair rand (talk) 07:30, 12 February 2014 (UTC)
    point in time (P585) is the most important qualifier but you should also specify the publication date (P577) and the retrieved (P813) for the data source, and the reference URL (P854) if it is online.

    Adjust for more generic use?[edit]

    Would it make sense to make the property more generic? Having something like "number of individuals" with more specific aliases it could be used to generally indicate quantity of humans (and even animals) and be used to specify the number of members of an organization (like a sports club), the number of employees of a company, the number of animals in a zoo and much more. With the process of adding new properties being very repelling, the property could be applied to a wide range of items right away. In addition, creating similar properties would be avoided.
    Imagining statements on properties, it should be possible to display a particular alias (specified via a statement) on specific item instances instead of displaying the generic property name, e.g. for cities, still, "population" would be displayed instead of the generic property name.
    - Random knowledge donator (talk) 10:13, 5 May 2014 (UTC)

    ±1[edit]

    Is there any way to get rid of this obnoxious, inaccurate addition to population values? Vanisaac (talk) 22:15, 30 June 2014 (UTC)

    Workaround: enter +-0 --JulesWinnfield-hu (talk) 10:30, 1 July 2014 (UTC)
    Thanks. That should probably be documented here and on other properties where it shows up automatically despite the values entered. Vanisaac (talk) 06:19, 3 July 2014 (UTC)

    Help[edit]

    I think it would help to type in the correct informations if this properties could inform you when there were two identical "points in time" and values. Is this possible? --Impériale (talk) 00:49, 26 December 2014 (UTC)

    Historical populations of current borders[edit]

    Some sources list historical populations of regions that didn't match the entity's borders at the relevant time period. For example, all World Bank population data on Sudan (Q1049) are of the populations within its current borders, including statistics for years when it still included all of South Sudan (Q958). How should this kind of data be handled? I imagine we wouldn't want to default to assuming that current borders are intended (requiring that all population data be thrown out every time borders change a bit), but we wouldn't want to leave this extra potentially-useful data unused. Thoughts? --Yair rand (talk) 13:29, 14 June 2015 (UTC)

    P459[edit]

    Hi,

    Can someone explain how determination method (P459) should / is supposed to be used ?

    Cdlt, VIGNERON (talk) 14:49, 8 July 2015 (UTC)

    The item mentioned in the sample uses it: Q62#P1082. Or Q495#P1082. I removed it from the mandatory constraints as most items failed it. This didn't matter that much until we had Special:ConstraintReport. --- Jura 15:24, 8 July 2015 (UTC)

    Rural population and city population[edit]

    Hi. Mudurnu (Q967446) is a district. I can add the value of the 1965 population. but, I can not add the cities and the rural population in 1965. What can we do to solve this problem?

    Example: Mudurnu (Q967446). 1965 population 25813. (Rural population 22086, city population 3727)

    --Sadrettin (talk) 17:36, 12 January 2016 (UTC)

    Population, point in time and reference[edit]

    {{#property:P1082}} gives e.g. for Belo Horizonte 2,479,175, but I want population according to 2010 census (2,375,151) and source for that. What should I type to get it? --BokicaK (talk) 06:06, 28 September 2016 (UTC)

    Determination method values[edit]

    The following query will display the values used for determination method (P459).

    SELECT ?determinemethod ?determinemethodLabel ?count WHERE {
      {
        SELECT ?determinemethod (COUNT(?determinemethod) AS ?count) WHERE {
          ?s p:P1082 ?popstatement .
          ?popstatement pq:P459 ?determinemethod .
        }
        GROUP BY ?determinemethod
      }
      SERVICE wikibase:label { bd:serviceParam wikibase:language "en" }
    }
    ORDER BY DESC(?count)
    

    Try it!

    --Bamyers99 (talk) 23:43, 22 December 2016 (UTC)

    female population (P1539) male population (P1540) as qualifiers?[edit]

    I just noticed this recent change. Are others in support of this? The way it is getting used (by the same user) can be seen at no label (Q18803429). --99of9 (talk) 00:11, 11 August 2017 (UTC)

    As you can see at Wikidata:Database_reports/Constraint_violations/P1082#Properties_statistics, there are about 15000 uses of each, all in a few countries. --99of9 (talk) 00:34, 11 August 2017 (UTC)
    Both models works, but I am not sure they easily can coexist. Our infoboxes at Wikipedia can be programmed to handle many possible ways to add a data. But make them adapt to all possible ways soon becomes tiresome. -- Innocent bystander (talk) 12:22, 11 August 2017 (UTC)

    Querying for the latest value[edit]

    Seems like all examples in the WDQS use wdt:P1082, which returns multiple values (all of history). What is the best way to get the latest one? E.g. "for a given list of WD ids, get the latest population value, and optionally, the year". Thanks! --Yurik (talk) 22:13, 9 October 2017 (UTC) Update, apparently the community has been using preferred to mark the most recent value, and there is no bot to maintain it. Currently there are over 10,000 constraint violations. Bot guru needed :) --Yurik (talk) 23:37, 9 October 2017 (UTC)

    @Yurik: There is a bot for this: PreferentialBot operated by Laboramus. But there are ways to get the latest data no matter what rank it has. But since I am not very good at WDQS, I cannot help you with that. This ListeriaBot-list helps me to find items with preferred rank set to an older date than the latest one. NB, it only looks into the set of pages I currently have interest in. (Two kinds of Swedish urban areas.) -- Innocent bystander (talk) 08:19, 10 October 2017 (UTC)

    Add ethnic group (Q41710) to "type constraint" allowed values[edit]

    Shouldn't instances of ethnic group (Q41710) be allowed as a value of population (P1082)?--Malore (talk) 16:35, 23 April 2018 (UTC)

    +1 . Conny (talk) 20:21, 4 May 2018 (UTC).