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
As far as I can tell, the only major type of public transformation information we are currently completely unable to express in FPTF is vehicles and their location. I therefore propose adding a vehicle type to FPTF@2 which could look as follows:
{type: 'vehicle',// requiredid: '123456',// requiredlocation: {// optionaltype: 'location',longitude: 52.5,latitude: 13.2},accessible: true,// barrier-free (e.g. for wheelchair users), optionalmodel: '485'// model information, e.g. "Deutsche Bahn, Baureihe 485", optional}
Note that this makes much more sense if we actually implement #43 in FPTF@2 because updating vehicle location could then be done by simply publishing more recent vehicle objects sharing the same id, indicating changed position information.
Opinions? 😄
The text was updated successfully, but these errors were encountered:
As far as I can tell, the only major type of public transformation information we are currently completely unable to express in FPTF is vehicles and their location. I therefore propose adding a
vehicle
type toFPTF@2
which could look as follows:Note that this makes much more sense if we actually implement #43 in
FPTF@2
because updating vehicle location could then be done by simply publishing more recent vehicle objects sharing the sameid
, indicating changed position information.Opinions? 😄
The text was updated successfully, but these errors were encountered: