Support mean_wait_ time/safe_wait_ time and other flex travel time fields?

[gcamp]

I'm unsure if this should be supported or we should concentrate only on having real time updates having this information.

[timMillet]

The mean- and the safe wait times from GTFS-OnDemand are needed for providing wait time estimates based on static data. What's the refresh rate that is aiming with GOFS data? If it is similar to GBFS or GTFS-RT, then the need for supporting mean- and safe wait times is very low.

[gcamp]

I'm trying to see how a GTFS-OnDemand to GOFS-lite converter will work without too much state if possible. But maybe it's not possible. At least we should focus on getting the best spec so far and see about compatibility/converter later.

[gcamp]

Exact same issue with fares.

[timMillet]

We can see it later. The current spec reuses a lot of GTFS concepts.

PS: If the refresh rate of GOFS data is high, then it should be ok to transcribe wait times from GOFS lite into safe wait times of GTFS-OnDemand.

[timMillet]

[...] Unless there is still a need for describing time ranges for wait times, even in real-time. Mean_wait_times and safe_wait_times allow producers to provide these time ranges, even though it's not the minimum/maximum we may think at first.