@chuuchuu Milan, Budapest, Madrid. Sometimes Lyon, Hamburg, Berlin, Munich, Copenhagen, Warsaw.
Nice looking feature! :)
@stefanlindbohm you missed Glasgow, Manchester and the heaving metropolis of Bradford
i guess if you're being cheeky you could add Lille and Birmingham
@bovine3dom They said no London so I assumed no UK :). But yes!
(I also have some work of my own on these stations in the UK, even though Iâve caught up on some UK stuff recently.)
@stefanlindbohm ah but there's loads of them in GTFS
you're just doing future proofing :)
@bovine3dom Iâm actually missing the gondolas across Switzerland to mountain towns that are considered public transport, like Le Chable -> Verbier. Would help A LOT for skiers who donât know they should search Le Chable to go to Verbier etc.
Do you have other examples that would help long distance journeys?
@stefanlindbohm can't you ingest all the GTFS and exclude the one you know you already have?
seems easier than having to work out what's important
off the top of my head there's the new cable car in Paris and also one in Brest
not cable cars but Italy is riddled with funiculars
@bovine3dom I have some plans for a better import/filter/integration tool for timetable data. Right now weâre a bit limited but the idea is to do what you say. Hopefully the tool itself can be open source so we can all use and add to it!
Funiculars we have a few in some places, but the icon library we use didnât have a fitting icon so theyâre still just trains.
I guess the issue with gondolas is they donât really have a timetable, so need to be modeled as âfootpathsâ, which is often missing.
@cycling_on_rails Do you know of cable cars that are public transport and not timetabled? Timetables are easy, and gondolas with a fixed travel time should be easy enough, but I assumed all relevant cable cars would have a timetable. Otherwise weâd have to support displaying variable travel time or something, depending on your luck with timing đ
@cycling_on_rails I was thinking of those that go to a place youâd have as a long-distance travel destination, letâs say anywhere with more than one hotel. But yeah, this is getting very niche. I just like to present it nicely if the data exists and itâs not too much work :)
@stefanlindbohm @bovine3dom For Switzerland you can use https://www.sbb.ch/de/billette-angebote/abos/ga/ga-geltungsbereich.html as a reference. (zoom in twice to see cable transports)
Through line = GA is valid, so in the majority it's public subsidised (although some touristic cable transports accept GA as well)
Dotted line = GA counts as half-fare card, these lines aren't usually not subsidised but discounts for GA carriers will be granted as a courtesy.
@wrzlbrnft @bovine3dom I will definitely put this on my list of things to get back to. We just need some way to include a continuous link as a leg in our journey planner.
We already have ticketing access to include the gondolas through the Swiss national ticketing system, provided we figure out a way to link the station code with that travel leg.
@stefanlindbohm What is exactly the challenge? Most of Swiss cable transports are included in the Open Transport Data sets > https://data.opentransportdata.swiss/dataset/?groups=timetables . Also every cable transport station has it's own UIC code ( https://opendata.swiss/de/dataset/haltestellen-des-offentlichen-verkehrs ).
I see that there now is even a dedicated beta dataset for cable cars and ski lifts ( https://data.opentransportdata.swiss/dataset/seilbahnen-netex ).
@bovine3dom
@wrzlbrnft We (exclusively, for now) use the international timetable dataset (MERITS) where these are not included, and we donât have an internal structure for continuous links like gondolas. Maybe the latter is also the reason why theyâre not included in MERITS? (Havenât looked into how theyâre represented in NeTEx yet.)
Both are totally solvable issues, but we have many fish to fry and thatâs why :)