Closed juliuste closed 6 years ago
station: '12345678',
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
.
mode: 'train',
This should be required, right?
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.
Agreed.
mode: 'train',
This should be required, right?
Agreed.
😄
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?