Property talk:P814
Jump to navigation
Jump to search
Documentation
IUCN protected areas category
protected areas category by the World Commission on Protected Areas. Used with dedicated items for each category.
protected areas category by the World Commission on Protected Areas. Used with dedicated items for each category.
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P814#Single value, SPARQL
One of IUCN category Ia: Strict Nature Reserve (Q14545608), IUCN category Ib: Wilderness Area (Q14545620), IUCN category II: National Park (Q14545628), IUCN category III: Natural Monument or Feature (Q14545633), IUCN category IV: Habitat/Species Management Area (Q14545639), IUCN category V: Protected Landscape/Seascape (Q14545646), IUCN category VI: Protected Area with sustainable use of natural resources (Q14545652), somevalue, novalue: value must be one of the specified items. Please expand list if needed. (Help)
List of violations of this constraint: Database reports/Constraint violations/P814#One of, values statistics, hourly updated report, 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/P814#Type Q473972, SPARQL
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/P814#Item P17, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P814#Item P17, search, 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/P814#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/P814#Item P625, SPARQL
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/P814#Item P2046, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P814#Item P2046, SPARQL
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/P814#Item P18, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P814#Item P18, 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/P814#Scope, hourly updated report, SPARQL
|
Value unknown (Q24238356) will be automatically replaced to value SOMEVALUE. Testing: TODO list |
|
|
Value incognita (Q2743596) will be automatically replaced to value SOMEVALUE. Testing: TODO list |
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||
“single” constraint?[edit]
Should we put a “single” constraint since most of the protected areas have only one category (with exception like de French National Parks)? --Fralambert (talk) 14:08, 25 August 2013 (UTC)
- Let's try. We can remove it if there too many false positives. -- Docu at 14:16, 25 August 2013 (UTC)
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)
- @Ahoerstemeier: I changed it for a type constraint. --Fralambert (talk) 01:58, 27 April 2014 (UTC)
Area constraint[edit]
Possibly area constraint should be either dropped or it'd benefit from adding specifing conditions. This is because WDPA item doesn't have to be an area, especially regarding those of IUCN category III (natural monument). See also Talk:Q12362543. --90.191.81.65 14:37, 6 March 2018 (UTC)
IUCN management category[edit]
protectedplanet.org uses term IUCN management category. I think it's worthwhile to use this as property label instead of current "IUCN protected areas category". Then it's hopefully more clear that IUCN categories are not applied on only protected areas, but on individual protected objects, too. So hopefully there'll be less confusion around constraints (see comment on area constraint above) and classification of objects assigned into IUCN categories. 2001:7D0:81F7:B580:DDF7:3D04:2313:191 09:41, 26 February 2019 (UTC)
Related discussion[edit]
See Wikidata:Property proposal/protected region scheme. --- Jura 08:58, 6 September 2019 (UTC)