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
Probably the most important feature FPTF is missing at the moment (IMHO) is the possibility to express departures and arrivals at a specific station (almost every public transport API has an interface for this).
I therefore propose a new type that could look like this (using fptf@1 keywords, disregarding the discussions in #27, #33 or #34 about possible changes in fptf@2 for now).
{type: 'stopover',// alternative proposals: 'arrival', 'departure', but this could be misleading since the accurate term in english would be "arrival or departure"station: '12345678',// station/stop object, required, name could be misleading since stops should also be valid. maybe 'halt' would be a better name - or two different keys "station" and "stop", but that's also probably not the best solutionplatform: '4-1',// string, optionalarrival: '2017-03-17T15:00:00+02:00',// ISO 8601 string (with destination timezone), required if `departure` is nullarrivalDelay: -45,// seconds relative to scheduled arrival, optionaldeparture: '2017-03-16T20:00:00+01:00',// ISO 8601 string (with station/stop timezone), required if `arrival` is nulldepartureDelay: 120,// seconds relative to scheduled departure, optionalschedule: '1234',// schedule id or objectmode: 'train',// see section on modes, overrides `schedule` modesubMode: …,// reserved for future use, overrrides `schedule` subModepublic: true,// publicly accessible?, overrides `schedule` publicoperator: 'sncf'// operator id or operator object, overrides `schedule` operator}
Any opinions / further proposals?
The text was updated successfully, but these errors were encountered:
I'm in favour of stop, as it would be consistent with route.
`platform: '4-1',
Some means of transport, including some ferries and trains, have different platforms on arrival and on departure. Although I'm usually in favour of keeping things simple, in this case platform would convey something wrong essentially.
Therefore I'd propose departurePlatform and arrivalPlatform, which would be consistent with journey.
I'm in favour of stop, as it would be consistent with route.
Agreed.
Some means of transport, including some ferries and trains, have different platforms on arrival and on departure. Although I'm usually in favour of keeping things simple, in this case platform would convey something wrong essentially.
Therefore I'd propose departurePlatform and arrivalPlatform, which would be consistent with journey.
Probably the most important feature FPTF is missing at the moment (IMHO) is the possibility to express departures and arrivals at a specific station (almost every public transport API has an interface for this).
I therefore propose a new type that could look like this (using
fptf@1
keywords, disregarding the discussions in #27, #33 or #34 about possible changes infptf@2
for now).Any opinions / further proposals?
The text was updated successfully, but these errors were encountered: