Property talk:P809

Documentation

WDPA ID
identifier in World Database on Protected Areas

Description

identifier in World Database on Protected Areas (Q1681293)

Associated item

World Database on Protected Areas (Q1681293)

Applicable "stated in" value

World Database on Protected Areas (Q1681293)

Data type

External identifier

Template parameter

"wpda" in fr:Template:Infobox_Aire_protégée

Domain

According to this template: places: protected areas

According to statements in the property:
protected area (Q473972)

When possible, data should only be stored as statements

Allowed values

[1-9]\d*

Example

Dry Island Buffalo Jump Provincial Park (Q3364718) → 18608
Harz National Park (Q702540) → 103142

Source

https://protectedplanet.net

Formatter URL

https://protectedplanet.net/$1

Tracking: same

no label (Q26860741)

Tracking: differences

no label (Q32163380)

Tracking: usage

Category:Pages using Wikidata property P809 (Q27642646)

Tracking: local yes, WD no

no label (Q32163391)

Lists

Proposal discussion

Current uses

Total	106,129
Main statement	104,412	98.4% of uses
Qualifier	33	<0.1% of uses
Reference	1,684	1.6% of uses

Search for values

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

Distinct values: this property likely contains a value that is different from all other items. (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/P809#Unique value, SPARQL (every item), SPARQL (by value)

Format “[1-9]\d*|”: value must be formatted using this pattern (PCRE syntax). (Help)

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

Item “country (P17)”: Items with this property should also have “country (P17)”. (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/P809#Item P17, search, SPARQL

Type “protected area (Q473972)”: item must contain property “instance of (P31)” with classes “protected area (Q473972)” 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/P809#Type Q473972, SPARQL

Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (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/P809#Item P131, search, SPARQL

Item “coordinate location (P625)”: Items with this property should also have “coordinate location (P625)”. (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/P809#Item P625, 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/P809#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (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/P809#Scope, SPARQL

Item “IUCN protected areas category (P814)”: Items with this property should also have “IUCN protected areas category (P814)”. (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/P809#Item P814, search, SPARQL

This property is being used by:

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

D before P[edit]

It must be WDPA, not WPDA. Someone needs to change it in the rest of the languages or provide sources for "WPDA". --Palnatoke (talk) 06:06, 24 August 2013 (UTC)[reply]

Thanks for fixing it.-- Docu at 08:59, 24 August 2013 (UTC)[reply]

instance of constraint[edit]

Why is it required to have instance of (P31) to be exactly protected area (Q473972), and not allowing subclasses? That would require to add this field redundantly, even though it is already implicitly given by the actual instance. Ahoerstemeier (talk) 19:52, 26 April 2014 (UTC)[reply]

Ramsar sites don't have IUCN statement.[edit]

The Ramsar sites have WDPA ID (P809) statement but don't have IUCN protected areas category (P814) statement this make only in Hungarian Ramsar states 29 constraint violations! See Old Drava bed of Szaporca (Q60026908) Texaner (talk) 19:57, 21 December 2018 (UTC)[reply]

Yes Special Protection Area (Q2463705) and site of community importance (Q796174) don't have also have IUCN protected areas category (P814), we sould probably delete this constraint. --Fralambert (talk) 20:37, 21 December 2018 (UTC)[reply]

It is always possible to set that property to no value, that will also solve the constraint warning. Ahoerstemeier (talk) 09:57, 13 February 2019 (UTC)[reply]

This would probably do if no value is rare or unusual. If no value is common, which seems to be the case here, then we would have to add useless statement to many items only in order to satisfy the constraint. This does not seem justified. For instance in Estonia, in addition to Ramsar areas and Natura 2000 areas, there are nearly 800 national protected areas that don't have IUCN category (assigned to zones of some of these protected areas, not whole protected areas). 2001:7D0:81F7:B580:C566:345:6BEC:3E07 11:47, 13 February 2019 (UTC)[reply]

There are many types of sites without an IUCN category in the WDPA, like the European Natura 2000 Network and not all protection types of all countries are assessed too. --GPSLeo (talk) 19:21, 12 December 2019 (UTC)[reply]

Yes, and that's why I made an attempt to remove the constraint earlier. The constraint is misleading in regard to many objects and it is counter-productive to the purpose of providing data that is meaningful and relevant, as I explained in greater depth here.

(I hope you don't mind that I moved your comment from the topic below.) 2001:7D0:81F7:B580:1D9F:D803:C7:CE86 10:25, 13 December 2019 (UTC)[reply]

Protected area constraint[edit]

I think this should be removed too (same as here). WDPA database indcludes objects of class natural monument (Q23790) too (not areas), i.e. individual trees, boulders etc. For instance there are over 1000 individual protected objects of this class in Estonia. 2001:7D0:81F7:B580:C566:345:6BEC:3E07 11:47, 13 February 2019 (UTC)[reply]

What does that have to do with the IUCN classification you removed? A protected entity does not have a defined area to have an IUCN class. --GPSLeo (talk) 08:52, 21 November 2019 (UTC)[reply]

GPSLeo, nothing. IUCN categories were discussed above: #Ramsar sites don't have IUCN statement.. 2001:7D0:81F7:B580:6DF5:BB17:83BE:AA4F 18:45, 12 December 2019 (UTC)[reply]

P131 restriction[edit]

At Q1538407, I noticed the error message that it should also have P:P131. But this is a marine protected area 120 nautical miles from land. It is in the Q5419701 but I don't think it is in a municipality. GoEThe (talk) 10:10, 17 July 2020 (UTC)[reply]