Property talk:P2815

Documentation

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

ESR station code
unique railway station/operation point code used in USSR and later in former USSR countries

Represents	ESR station code (Q4173954)
Data type	External identifier
Template parameter	|код ЄМР= in uk:Шаблон:Станція, |код АСУЖД= in ru:Шаблон:Железнодорожная станция
Domain	operation point (Q124817561)
Allowed values	[0-9]{6}
Example	Dnipro Railway station (Q1989694) → 451100 Moscow Belorussky railway station (Q1367269) → 198230
Source	https://tr4.info
Formatter URL	https://tr4.info/station/$1
Robot and gadget jobs	import from infoboxes
Tracking: usage	Category:Pages using Wikidata property P2815 (Q56250864)
Related to country	Russia (Q159) (See 345 others) Ukraine (Q212) (See 57 others) Belarus (Q184) (See 27 others) Moldova (Q217) (See 1 other) Lithuania (Q37) (See 24 others) Latvia (Q211) (See 21 others) Estonia (Q191) (See 33 others) Georgia (Q230) (See 12 others) Armenia (Q399) (See 21 others) Azerbaijan (Q227) (See 2 others) Kazakhstan (Q232) (See 8 others) Uzbekistan (Q265) (See 3 others) Kyrgyzstan (Q813) (See 5 others) Turkmenistan (Q874) (See 1 other) Tajikistan (Q863) (See 2 others)
See also	Indian Railways station code (P5696)
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/P2815 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 14,001 Main statement 13,999 >99.9% of uses Qualifier 2 <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 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/P2815#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/P2815#Single value, SPARQL

Format “[0-9]{6}|”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P2815#Format, hourly updated report, SPARQL

Type “operation point (Q124817561)”: item must contain property “instance of (P31)” with classes “operation point (Q124817561)” 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/P2815#Type Q124817561, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

List of violations of this constraint: Database reports/Constraint violations/P2815#Entity types, hourly updated report

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/P2815#Scope, SPARQL

Item “country (P17)”: Items with this property should also have “country (P17)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P2815#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/P2815#Item P625, SPARQL

This property is being used by: ru:Шаблон:Железнодорожная станция ba:Ҡалып:Железнодорожная станция uk:Шаблон:Станція eo:Ŝablono:Informkesto Fervoja stacidomo, eo:Ŝablono:Informkesto stacio, eo:Ŝablono:Oficiala retejo ESR, eo:Ŝablono:Informkesto Fervoja stacidomo/dokumentado, eo:Ŝablono:Informkesto stacio/dokumentado fr:Modèle:Infobox Gare, fr:Modèle:Site ESR, fr:Modèle:Infobox Gare/Bac à sable Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Deprecating qualifier P642

@Entbert, @Lockal: We are in the process of deprecating of (P642) due to ambiguous use. It's used on P2815#P1630 (P2815#P1630) in an unsupported fashion (it triggers a constraint violation). Are you aware of any practical need for it on this particular property? Can it simply be removed? --SM5POR (talk) 20:19, 15 January 2023 (UTC)

@SM5POR, what do you mean by "this property"? It is not used right now. As for general usage, there is a User:Lucas Werkmeister/P642 considered harmful, which you might have already seen, I hope. There are a number of open question on discussion page there, but I hope they will be solved eventually. Lockal (talk) 03:16, 16 January 2023 (UTC)

@Lockal: Sorry, I wasn't very clear above. By "this property" I'm referring to the Property:P2815 entity ESR station code (P2815) itself (rather than to its potential use in a claim made on any item), and in particular to its Property:P2815#P1630 property formatter URL (P1630) with three claims, two of them deprecated. Each of those three claims includes a qualifier of (P642) referring to operation point (Q1318558), railway company (Q249556) and railway stop (Q55678), respectively. While formatter URL (P1630) does not support the of (P642) qualifier, only the third claim is actually marked "(!)" as a constraint violation, since the first two claims are deprecated anyway.

I'm aware of Lucas Werkmeister's article, and one year ago it had led to the creation of an effort to completely phase out of (P642) from WIkidata; see the project page Wikidata:WikiProject Data Quality/Issues/P642 for the current status of this effort (which I'm now taking part in). We have so far gone from over 10 million use cases to less than one million, but I believe most of the work is yet ahead of us. Yesterday I began looking into the Property namespace entities specifically, and that's how I found out about ESR station code (P2815).

I assume the qualifier was added to the three formatter URLs in order to identify their functions or otherwise tell them apart, but if this identification is necessary you will have to find some other way of expressing it. I hope you can do this yourself, or you may be able to find someone else who can. Look at the allowed qualifiers constraint (Q21510851) claim of P1630#P2302 (P1630#P2302) for suggestions of which qualifiers can be used with formatter URL (P1630). --SM5POR (talk) 07:18, 16 January 2023 (UTC)

Ah, you mean just 3 url formatters in Property:P2815#P1630... I converted them to Property:P518. And with that there are no more P642 for masks. Lockal (talk) 07:30, 16 January 2023 (UTC)

@Lockal: That looks perfect, thank you! --SM5POR (talk) 05:43, 17 January 2023 (UTC)