Property talk:P2856

From Wikidata
Jump to navigation Jump to search

Documentation

EU Surface Water Body Code
unique EU identifier for a surface water body
Associated itemEuropean Union (Q458)
Data typeExternal identifier
Domain
According to this template: body of water (Q15324), bay (Q39594)
According to statements in the property:
body of water (Q15324), bay (Q39594) or waterbody (Q1389310)
When possible, data should only be stored as statements
Allowed values[A-Z]{2}[A-Z0-9_]+
ExampleOrlången (Q3424558)SE656833-162888
Canal through Walcheren (Q1723437)NL18_KANDWCRN
Sourcehttp://dd.eionet.europa.eu/vocabulary?vocabularyFolder.folderName=wise&vocabularyFolder.identifier=WaterBody&vocabularyFolder.workingCopy=false&filter.conceptStatusInt=147&filter.text=SurfaceWaterBodyCode&filter.visibleColumns=Notation&filter.visibleColumns=Status&filter.visibleColumns=Status+Modified&view=Search
http://dd.eionet.europa.eu/vocabulary/wise/IdentifierScheme/euSurfaceWaterBodyCode
Formatter URLhttp://dd.eionet.europa.eu/vocabularyconcept/wise/WaterBody/euSurfaceWaterBodyCode.$1 (Regex: ^(?!SE).+)
Tracking: usageCategory:Pages using Wikidata property P2856 (Q28007556)
Related to country European Union (Q458) (See 16 others) (European Union (Q458))
See alsoEU River Basin District code (P2965), Eionet bathing Water ID (P9616)
Lists
Proposal discussionProposal discussion
Current uses
Total7,652
Main statement7,650>99.9% of uses
Qualifier2<0.1% of uses
Search for values
[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/P2856#Single value, SPARQL
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/P2856#Unique value, SPARQL (every item), SPARQL (by value)
Format “[A-Z]{2}[A-Z0-9_-]+: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P2856#Format, hourly updated report, 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/P2856#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/P2856#Scope, SPARQL
This property is being used by:

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

Compare with Lake ID (Sweden)
see Lake ID (Sweden) (P761) (Help)
Violations query: SELECT ?item ?lacID ?otherID ?substr { ?item wdt:P2856 ?lacID. ?item wdt:P761 ?otherID. BIND (SUBSTR(STR(?lacID), 3) AS ?substr). FILTER (?substr != ?otherID) }
List of this constraint violations: Database reports/Complex constraint violations/P2856#Compare with Lake ID (Sweden)

Formatter URL[edit]

@Alicia Fagerving (WMSE): Hi! What did you wanted to say with this edits? If you meant that the formatter URL should apply only if the ID format matches ^(?!SE).+, then 1) property applies if regular expression matches (P8460) now should be used for expressing this and 2) which formatter URL should apply instead when the regular expression is not matched?

Moreover, why did you remove the link to viss.lansstyrelsen.se? Horcrux (talk) 10:38, 19 March 2024 (UTC)[reply]