Property talk:P722
Documentation
identifier for a railway station in Europe, CIS countries, the Far East (China, Mongolia, Japan, Korea, Vietnam), North Africa and the Middle East
Description | UIC identifiers are used by railway operators to refer to railway stations in Europe, CIS countries, China, Mongolia, North Africa and the Middle East. | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Associated item | International Union of Railways (Q388314), Express-3 (Q4054091) | |||||||||
Data type | External identifier | |||||||||
Domain | public transport stop (Q548662) or operation point (Q124817561) | |||||||||
Allowed values | \d{7} | |||||||||
Example | Nantes station (Q2180175) → 8748100 Train station of Astorga (Q9161351) → 7120100 | |||||||||
Format and edit filter validation | UIC station reference always consists of 7 digits, beginning with a 2-digit UIC country code. If the station code consists of less than 5 digits, fill with 0, for example Trondheim S’s code is 7601126. | |||||||||
Tracking: usage | Category:Pages using Wikidata property P722 (Q58416575) | |||||||||
See also | IBNR ID (P954), ESR station code (P2815) | |||||||||
Lists |
| |||||||||
Proposal discussion | Proposal discussion | |||||||||
Current uses |
| |||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P722#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P722#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P722#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P722#Type Q548662, Q124817561, SPARQL
(10|2\d|3[0-3]|4[01249]|5\d|6[0125678]|7\d|8[0-8]|9\d).+|
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P722#Item P17
List of violations of this constraint: Database reports/Constraint violations/P722#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P722#Item P625, SPARQL
|
Control/Key digit?
[edit]Hello, is it possible to add the 8th digit used by some companies (like French company SNCF)? According to UIC the 8th digit is used as a control key, calculated with the 5 digits of station code (without the country digits). I don't know if a bot controls the length of "7 digits", then it would be appreciated (I think) that we could include this 8th digit? Thanks for your answers. Jeriby (talk) 16:49, 24 September 2013 (UTC)
What is this?
[edit]Which code should be met with P722? An UIC code has 8 digits (control key included), but IBNR has only 7 digits. Is there any resource to lookup UIC codes? --A.Bernhard (talk) 06:38, 1 October 2013 (UTC)
- Looks like we mix different systems in one property. Russian label of P722 is "код Экспресс-3" ("Express-3 code"). — Ivan A. Krestinin (talk) 19:11, 1 October 2013 (UTC)
- Hm... can't find any description of "Express-3 code" - will do some research. We have to solve these issues with station codes. See also Wikidata:Properties_for_deletion#Bahnhofscode_.28P296.29 --A.Bernhard (talk) 20:42, 1 October 2013 (UTC)
- I do not find any non-Russian sources about this system, in Russian: ru:АСУ «Экспресс». This is system that serves ticket and another operations in Russia and ex-USSR countries. Sample code: 2000030 (for Volokolamsk (Q4123858)). — Ivan A. Krestinin (talk) 21:24, 1 October 2013 (UTC)
- Translated ru @ wikipedia and got this: "The system of "Express-3" is a full member of the international community system of reserved seats, actively cooperates with other European electronic reservation systems within computer networks OSJD / UIC ." The question is how close is the cooperation? I tried your tool for IBNR and UIC codes and it doesn't give any response for these codes (tried also eastern europe cities like Praha or Budapest). List of a dozen UIC-station codes is available here and here's a IBNR lookup --A.Bernhard (talk) 21:36, 1 October 2013 (UTC)
- I do not find any non-Russian sources about this system, in Russian: ru:АСУ «Экспресс». This is system that serves ticket and another operations in Russia and ex-USSR countries. Sample code: 2000030 (for Volokolamsk (Q4123858)). — Ivan A. Krestinin (talk) 21:24, 1 October 2013 (UTC)
- Hm... can't find any description of "Express-3 code" - will do some research. We have to solve these issues with station codes. See also Wikidata:Properties_for_deletion#Bahnhofscode_.28P296.29 --A.Bernhard (talk) 20:42, 1 October 2013 (UTC)
I asked some days ago about it already, and on the French wikipedia an IP contributor explained me (for some of you who speak French you can see the subject here), that's why I asked about the 7 or 8 digits . It seems that France uses 8 digits of UIC, whereas Belgium and Switzerland use 7 digits code (same number as the 8 digits but without the control key. Jeriby (talk) 02:26, 2 October 2013 (UTC)
- I'm really not sure about this. Look here, in this UIC list Zurich HB has the code 8585200. If you check this code on the SBB here it doesn't find anything. But if you search for an IBNR here for Zürich HB, the answer is 8503000. And this isn't a UIC code but the SBB find the correct station here. I think the SBB uses the IBNR, because there system is based on the HAFAS system and they created the IBNR.--A.Bernhard (talk) 07:19, 2 October 2013 (UTC)
- I think the SBB combine both systems and uses UIC for France / Belgium etc. stations and IBNR for Germany / Austria / Switzerland etc. stations. And when they use UIC, they ignore the control digit.--A.Bernhard (talk) 07:21, 2 October 2013 (UTC)
- Ok thanks, then it would be better indeed to have UIC property and IBNR property separated and both available (and maybe including the control digit for UIC?) Jeriby (talk) 17:13, 2 October 2013 (UTC)
Control/Key digit? (again)
[edit]I really don't understand why the bot Escabot is adding UIC code with 7 digits with « Document de référence du réseau; annexe 7.3 - Liste des gares de voyageurs (Q14915744) » as a source WHEREAS this official PDF source shows UIC code with the control/key digit (without the country code, but with this "famous" 8th digit). It's not very rigorous to add a code with a source but a different data compared to the source we refer. Then I'm asking again (I didn't get an answer last time): is it possible to add the 8th digit? (According to UIC the 8th digit is used as a control key, calculated with the 5 digits of station code (without the country digits)). Thank you. Jeriby (talk) 18:26, 14 November 2013 (UTC)
- In France, SNCF Open Data (SNCF Open Data) lists railway stations with 8 digits UIC codes. I had to do a small template using Luhn algorithm to convert the 7 digits from Wikidata P722 to full 8 digits codes (Uic8). --Dominik (talk) 05:31, 31 October 2020 (UTC)
Operation point
[edit]I've added operation point (Q1318558) as an allowable class for this property. The Swiss assign UIC numbers to non-passenger points (like Umler (Q33508650)); it's useful for verifying information and I think we should encourage it. Mackensen (talk) 14:45, 8 March 2021 (UTC)
Which UIC code?
[edit]There are two types of UIC codes, Location code (used for all types of locations on European Railways, also freight-only and technical points), and UIC Reservation Code, used in sales systems for passenger traffic. They look alike, but are completely different. Example: UIC location code for Stockholm Centralstation is 7403751, UIC Reservation code is 7400001. Which one is this property meant for? --Kitayama (talk) 10:35, 28 November 2021 (UTC)
- Hello, p722 is the location code. The reservation codes depend of the sale system. Tilcago (talk) 14:25, 3 December 2021 (UTC)
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with format constraints
- Properties with constraints on type
- Properties with constraints on items using them
- Properties with conflicts with constraints
- Properties with entity type constraints
- Properties with scope constraints