Property talk:P1850

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

SSR place name number
identifier for a place name in the Norwegian Mapping Authority's place name registry Sentralt stedsnavnregister (SSR)

Applicable "stated in" value	SSR (Q12718242)
Data type	External identifier
Domain	terrain/landform (note: this should be moved to the property statements)
Allowed values	[1-9][0-9]{0,6}
Example	Glittertind (Q397876) → 70857 Stiikogáisá (Q101109100) → 20043 Biellogiellasjávrrit (Q101111447) → 81938
Source	http://www.norgeskart.no/
Formatter URL	https://stadnamn.kartverket.no/fakta/$1
Robot and gadget jobs	Will be uploaded from a prepared dataset
Tracking: usage	Category:Pages using Wikidata property P1850 (Q28840513)
Related to country	Norway (Q20) (See 97 others)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P1850 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 96,644 Main statement 47,908 49.6% of uses Qualifier 3 <0.1% of uses Reference 48,733 50.4% of uses
Search for values

[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)

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

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/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

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)

URL doesn't work anymore.

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)

All ID's has now been corrected. Stigmj (talk) 09:21, 31 January 2017 (UTC)

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)

Format constraint

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)

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)

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)

Country contraint

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)