3 ms·

This is really nice, though the documentation is a bit lacking in parts (there's already a pull request to make things a bit nicer :) For example, I can see a

This is really nice, though the documentation is a bit lacking in parts (there's already a pull request to make things a bit nicer :) For example, I can see a station is missing, but is there any way to find its UIC code (or other identifiers) so I can add an entry? It's not clear what `is_suggestable` actually means, so I wouldn't know what to input. Also, while there are info:* columns for miscellaneous info, there doesn't seem to be multiple name:* columns for the localised station name (a lot of this data may already be in OpenStreetMap)?

tristramg 11y ago
Thank you. Indeed the data is incomplete yet. Bear in mind that the data comes from a specific use on https://www.capitainetrain.com https://www.capitainetrain.com That is why many countries are poorly covered (yet! we plan to eventually cover whole Europe). There is no magic to find the UIC code, sorry… Sometimes it is in OpenStreetMap, sometimes we get it from a rail operator… But it is not a required value, so you can add it with out the station. `is_suggestable` means that the user can input the station on capitainetrain.com. Leave it false for now ;) The idea behind the name vs. info is that name is the station as it is locally known. Info adds any information extra information to help to find which station it is (that includes translations, “Central Station” for people not understanding „Hbf“, disambiguation between similar names…)
- christop 11y ago
  > Info adds any information extra information to help to find which station it is [translations, disambiguation] These are two separate use cases, which should have their own structured fields. The current uses of info:* seem to be very free-form at the moment. If I want to travel to Cologne Trade Fair, I should be able to start typing "colo" and find it, without knowing that it's called "Köln Messe" in German. Whereas the info:* fields should separately have useful info, e.g. "Trains transfer from Cologne Main Station every few minutes." Much like on OpenStreetMap, doing a name search should match against all name:* fields. Info fields should be for info.

tristramg 11y ago

Thank you. Indeed the data is incomplete yet. Bear in mind that the data comes from a specific use on https://www.capitainetrain.com https://www.capitainetrain.com That is why many countries are poorly covered (yet! we plan to eventually cover whole Europe). There is no magic to find the UIC code, sorry… Sometimes it is in OpenStreetMap, sometimes we get it from a rail operator… But it is not a required value, so you can add it with out the station. `is_suggestable` means that the user can input the station on capitainetrain.com. Leave it false for now ;) The idea behind the name vs. info is that name is the station as it is locally known. Info adds any information extra information to help to find which station it is (that includes translations, “Central Station” for people not understanding „Hbf“, disambiguation between similar names…)

christop 11y ago
> Info adds any information extra information to help to find which station it is [translations, disambiguation] These are two separate use cases, which should have their own structured fields. The current uses of info:* seem to be very free-form at the moment. If I want to travel to Cologne Trade Fair, I should be able to start typing "colo" and find it, without knowing that it's called "Köln Messe" in German. Whereas the info:* fields should separately have useful info, e.g. "Trains transfer from Cologne Main Station every few minutes." Much like on OpenStreetMap, doing a name search should match against all name:* fields. Info fields should be for info.