Property talk:P4179

Documentation

• Start a query
• Current uses
• Statistics by class
• List of qualifiers
• Count

tabular population
same as population (P1082); used when there is data for many different points in time

Represents	number of individuals (Q1613416)
Data type	Tabular data
Allowed values	(?i).+\.tab
Example	Taipei (Q1867) → Data:Taipei Population.tab Kocaeli Province (Q83965) → Data:Kocaeli Population.tab
Formatter URL	https://commons.wikimedia.org/wiki/$1
See also	population (P1082), based on tabular data (P8265), tabular case data (P8204)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis 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) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P4179 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 2,121 Main statement 2,119 >99.9% of uses Qualifier 2 <0.1% of uses

[create Create a translatable help page (preferably in English) for this property to be included here]

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/P4179#Scope, hourly updated report, SPARQL

Item “population (P1082)”: Items with this property should also have “population (P1082)”. (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/P4179#Item P1082, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (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/P4179#Entity types

Link to Commons namespace “Data”: this property should contain a well-formed link to an existing page on Wikimedia Commons. (Help)

List of violations of this constraint: Database reports/Constraint violations/P4179#Commons link, hourly updated report

Format “(?i).+\.tab”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P4179#Format, hourly updated report, SPARQL

Data structure

Is there any way we can standardize these data so that a software client understands that the software client understands that in commons:Data:Taipei Population.tab "1337350" refers the female population in February 2001. Ideally, I suppose the header would have a reference to a Wikidata item for female population. -Zolo (talk) 08:12, 27 August 2017 (UTC)

I updated the sample data to a later revision (per the talk section on the original proposal). The headers are more easy to parse now. S-1-5-7 (talk) 15:05, 27 August 2017 (UTC)

Is the text in the headers after the underscore really necessary? I feel like it just confuses things. Also, I don't suppose there are any constraints that work with this datatype that would help enforce the standard? (If there isn't, is there a place to propose new constraint types?) --Yair rand (talk) 00:15, 5 September 2017 (UTC)

@Yair: They make it more human readable and it would be trivial to parse out in code (e.g., regex "^([PS]\d+)"). They wouldn't even need to be standardised since the P###/S### is the only important part. I am not sure about the constraints.S-1-5-7 (talk) 07:19, 5 September 2017 (UTC)