Property talk:P1850

From Wikidata
Jump to navigation Jump to search

Documentation

SSR place name number
identifier for a place name in the Norwegian Mapping Authority's place name registry Sentralt stedsnavnregister (SSR)
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[1-9][0-9]{0,6}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1850#Format, hourly updated report, 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/P1850#Unique value, SPARQL (every item), SPARQL (by value)
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/P1850#Single value, SPARQL
Item “country (P17): Norway (Q20): Items with this property should also have “country (P17): Norway (Q20)”. (Help)
"exceptions" is incompatible with "mandatory" parameter List of violations of this constraint: Database reports/Constraint violations/P1850#Item P17, hourly updated report, 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/P1850#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/P1850#Item P131, search, 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/P1850#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/P1850#Scope, SPARQL
Label required in languages: nb: Entities using this property should have labels in one of the following languages: nb (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/P1850#Label in 'nb' language, search, SPARQL
Label required in languages: nn: Entities using this property should have labels in one of the following languages: nn (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/P1850#Label in 'nn' language, search, SPARQL


About geo positions

[edit]

Note that the geo positions (locations) used in SSR are the positions on the maps for the written strings, not the named object. Jeblad (talk) 08:25, 14 December 2015 (UTC)[reply]

URL doesn't work anymore.

[edit]

It seems that Kartverket has changed their database. All the IDs has changed, and the new url is : https://stadnamn.kartverket.no/fakta/62752 -PeterFisk (talk) 11:47, 22 December 2016 (UTC)[reply]

All ID's has now been corrected. Stigmj (talk) 09:21, 31 January 2017 (UTC)[reply]
I have changed the titles and descriptions to reflect the current usage. Calling the current values "name id" was just wrong, as the successor to that concept is a different (composite) value. However, I have no established English translations, so I just put the Norwegian term there. I think they (will) correspond to something in the INSPIRE standard, but not without a namespace prefix. Ters (talk) 16:53, 31 January 2017 (UTC)[reply]

Format constraint

[edit]

I noticed that the format is defined as 0 through 6 digits. This is not the technically correct limit for stedsnummer. Accepting 0 digits is just plain wrong. What the correct upper limit should be is more tricky. Strictly speaking, according to the data model for SSR, stedsnummer is a signed 64-bit integer value. (Another delivery format doesn't state the size of the integer data type.) As such, it can contain a lot more digits than six. However, I do think the biggest value currently in use is just six digits, and numbers are allocated sequentially, but the value is close to reaching seven digits. Should the upper bound reflect the actual data model from which the values come, or should it be limited to the at any given time maximum value to stop people from entering an obviously too large value? Ters (talk) 05:04, 13 July 2017 (UTC)[reply]

It's currently defined as having 1 to 7 digits. [1-9] means 0 isn't accepted as a single digit.
--- Jura 05:23, 13 July 2017 (UTC)[reply]
Sorry, I missed that the first digit was separate from the rest. That is, I read it as [0-9]{0-6}. The main question of whether to use the formally defined actual possible range for the value, or what appear the be the range in practice at the current time, still stands. Ters (talk) 19:48, 13 July 2017 (UTC)[reply]

Country contraint

[edit]

FYI: SSR place name numbers have been assigned for places outside Norway as well. 328689 is the number for Sweden. SSR is not authoritative for such places of course, but that is also the case for some places in Norway as well. Ters (talk) 14:58, 23 May 2018 (UTC)[reply]