You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of people added properties we had no clue about (e.g., its architectural style, the fact it’s registered cultural heritage (and is linked to yet another URI for this fact), etc.)
At the bottom of the page you can then find all possible other identifiers given by different systems, including UIC codes, HAFAS codes, or local numbering systems.
What I propose is to have an extra field in the JSON ouput that links to the wikidata identifier of the station. In the case it does not yet exist, it would be great to create it in wikidata, and add basic information such as the other identifiers that you found so far
The text was updated successfully, but these errors were encountered:
Wikidata
https://www.wikidata.org/ is a collaborative knowledge base - it tries to create an identifier for all entities in the world.
With iRail in Belgium we decided to slowly move towards this for persistent identifiers.
Check for example this identifier: http://www.wikidata.org/entity/Q800814
A lot of people added properties we had no clue about (e.g., its architectural style, the fact it’s registered cultural heritage (and is linked to yet another URI for this fact), etc.)
At the bottom of the page you can then find all possible other identifiers given by different systems, including UIC codes, HAFAS codes, or local numbering systems.
And if you then look at OpenStreetMap, then you will see that the building identifier in OSM is linked to this wikidata URI (https://www.openstreetmap.org/way/226276044)
Proposal
What I propose is to have an extra field in the JSON ouput that links to the wikidata identifier of the station. In the case it does not yet exist, it would be great to create it in wikidata, and add basic information such as the other identifiers that you found so far
The text was updated successfully, but these errors were encountered: