Wikidata:Property proposal/IFOPT stop identifier
IFOPT stop identifier[edit]
Originally proposed at Wikidata:Property proposal/Transportation
| Description | Unique identifier for a stop place or stop component, following the Identification of Fixed Objects in Public Transport (Q5988215) norm |
|---|---|
| Represents | Identification of Fixed Objects in Public Transport (Q5988215) |
| Data type | External identifier |
| Domain | transport infrastructure (Q376799) |
| Allowed values | ^[a-z]{2}\:.* |
| Example 1 | Leipzig Hauptbahnhof (tief) (Q56808924)IFOPT stop identifierde:14713:8098205 |
| Example 2 | Ostkreuz (Q660045)IFOPT stop identifierde:11000:900120003 |
| Example 3 | Basel Badischer Bahnhof (Q666725)IFOPT stop identifierch:23005:6 |
| Number of IDs in source | >= 10.000 |
| Expected completeness | eventually complete (Q21873974) |
| See also | station code (P296) |
Motivation[edit]
The European IFOPT norm (EN 28701:2012, Identification of Fixed Objects in Public Transport (Q5988215)) standardizes a so-called "stop identifier" for stop places (e.g. train stations) and stop components (e.g. railway platforms). This identifier has been incorporated into the NeTEx standard (NeTEx (Q22907245)), a data standard which all European transport infrastructure operators are required to use for data publishing (at least in theory). This means that, at some point in the future, every public transport stop in Europe will have been assigned such a globally unique "stop identifier". Given that, I propose the addition of a new Wikidata property, as described above, to enable collection of these identifiers, which will be very useful when linking Wikidata to other datasets.
Some additional notes:[edit]
- The IFOPT standard describes other objects besides "stop places", which is why I included the term "stop identifier" in the proposed property name, even though some other datasets (e.g. OSM) simply refer to this id as "IFOPT"
- The IFOPT standard contains a recommendation on how these stop place identifiers should be constructed, but aside from a country-specific namespace prefix (e.g. "de:" for Germany), no further specifications seem to be mandatory. I therefore only added a very simple regex restriction for the property in my proposal (at least for now)
- Given the non-binding specification on how to construct these identifiers, some countries created their own standard for their respective namespace, e.g. the German DHID standard for IFOPT stop identifiers starting with "de:". It would also be possible to create separate sub-properties for every national standard, but given that this id aims to be a globally unique identifier at least for the entire European Union, I would suggest to only introduce this global property, at least for now.
--Julius Tens (talk) 17:12, 16 January 2024 (UTC)
Discussion[edit]
Support This seems like a good idea. I assume there's no hope of a formatter URL for these? ArthurPSmith (talk) 18:55, 18 January 2024 (UTC)
- Thanks for supporting! Yes, I don't think there will be a website for these soon. And if there were at some point, it would probably be a community effort rather than an official one… Julius Tens (talk) 09:38, 19 January 2024 (UTC)
- Support as this is the standardized identifier being rolled out all over europe a dedicated property is a good thing Dekarl (talk) 21:03, 22 January 2024 (UTC)
- Support needed indeed as this is used in a number of other data sets, OSM and public transport APIs Volker.krause (talk) 18:42, 31 January 2024 (UTC)
