Property talk:P964

From Wikidata
Jump to navigation Jump to search

Documentation

Austrian municipality key
identifier for municipalities in Austria (ÖSTAT-Nummer), format: 5 digits
Descriptionnumber sequence for the identification of municipalities in Austria
RepresentsCommunity Identification Number (Q23003), municipality of Austria (Q667509)
Data typeExternal identifier
Template parameter'Gemeindekennziffer=' in de:Vorlage:Infobox Gemeinde in Österreich
Domain
According to this template: places: all municipalities in Austria (as well as the Statutarstädte and Wiener Stadtbezirke)
According to statements in the property:
municipality of Austria (Q667509) or district of Vienna (Q261023)
When possible, data should only be stored as statements
Allowed values\d{5}
ExampleGraz (Q13298)60101
Innsbruck (Q1735)70101
Sourcehttps://www.statistik.at/blickgem/index.jsp
Formatter URLhttps://www.statistik.at/blickgem/gemDetail.do?gemnr=$1
Tracking: sameno label (Q28605269)
Tracking: differencesno label (Q24194573)
Tracking: usageCategory:Pages using Wikidata property P964 (Q24194575)
Tracking: local yes, WD nono label (Q24194572)
Related to country Austria (Q40) (See 81 others)
See alsocadastral municipality ID in Austria (P8322), locality number in Austria (P8384)
Lists
Proposal discussionProposal discussion
Current uses
Total2,542
Main statement2,53899.8% of uses
Qualifier2<0.1% of uses
Reference2<0.1% 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" is incompatible with "mandatory" parameter List of violations of this constraint: Database reports/Constraint violations/P964#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P964#single best value, SPARQL
Format “\d{5}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P964#Format, hourly updated report, SPARQL
Item “country (P17): Austria (Q40): Items with this property should also have “country (P17): Austria (Q40)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P964#Item P17, hourly updated report, search, SPARQL
Item “coordinate location (P625): Items with this property should also have “coordinate location (P625)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P964#Item P625, hourly updated report, SPARQL
Item “GeoNames ID (P1566): Items with this property should also have “GeoNames ID (P1566)”. (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/P964#Item P1566, search, SPARQL
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P964#Scope, 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/P964#Entity types
Label required in languages: de: Entities using this property should have labels in one of the following languages: de (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/P964#Label in 'de' language, search, SPARQL
municipality in Austria without number
municipality of Austria (Q667509) lacking a Austrian municipality key (P964) statement specifying the Community Identification Number (Q23003) (Help)
Violations query: SELECT ?item WHERE { ?item wdt:P31/wdt:P279* wd:667509 . MINUS { ?item wdt:P964 ?any . } }
List of this constraint violations: Database reports/Complex constraint violations/P964#municipality in Austria without number

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

We should also allow statutory city of Austria (Q262882) and district of Vienna (Q261023) to have this property, see de:Amtlicher_Gemeindeschlüssel#.C3.96sterreichischer_Gemeindeschl.C3.BCssel:_Aufbau_der_Gemeindekennziffer_.28-kennzahl.29. Is this technically possible?

I accidentely suggested to create the property without knowing that it already exists, see here. --Zuphilip (talk) 14:23, 2 November 2013 (UTC)[reply]

I have already asked here: Template talk:Constraint#Extend Constraint:Item to subclasses of the item (or to one of a specified list of items)? --UV (talk) 19:57, 2 November 2013 (UTC)[reply]
And again, I doubled that Template_talk:Constraint:Item#Several_values. Maybe it helps to become faster a reaction ;-) By the way I wanted to ask for a bot import from de-wiki for all municipalities (and Statutarstädte) in Austria together with some other properties, see some notes at Wikidata:Country_subdivision_task_force/Austria. Did you do that already? --Zuphilip (talk) 20:32, 2 November 2013 (UTC)[reply]
Good! No, I did not ask for such a bot import. Greetings, --UV (talk) 20:49, 2 November 2013 (UTC)[reply]
If number of such items is low then this can help. — Ivan A. Krestinin (talk) 18:51, 29 November 2013 (UTC)[reply]


All Statutarstädte and Wiener Stadtbezirke are added as "exceptions". Moreover, I imported the values of all municipalities including Statutarstädte and Wiender Stadtbezirke. --Zuphilip (talk) 18:04, 13 December 2013 (UTC)[reply]

Great, thanks a lot for doing this import! --UV (talk) 21:43, 13 December 2013 (UTC)[reply]