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
I analyzed the problem. They put a space for the stop time which is not "empty" (space between commas , ,).
If exact arrival and departure times (timepoint=1) are not available, estimated or interpolated arrival and departure times (timepoint=0) should be provided.
Regarding timepoint the specification says:
If no timepoint values are provided, all times are considered exact.
When implementing MOTIS, I used this example which uses empty stop times (nothing between commas: ,,):
Bus legs inside Palma de Mallorca have durations of 0 seconds. Example:
Reason are missing timepoint values a can be seen here for example https://busmaps.com/en/spain/public_transit-line-1-2413739300-2494502523
Data comes from EMT Palma https://www.emtpalma.cat/ca/inici
Alls stops appear to be used, according their own plan: https://www.emtpalma.cat/ca/linia/-/L/1/portopi-sindicat
Primary gtfs data source: https://www.emtpalma.cat/en/open-data-en
gtfs validation report for example https://busmaps.com/en/spain/Empresa-Municipal/emtpalma
I'll try to nudge them via contact page https://www.emtpalma.cat/ca/atencio-al-client but I'm surely not the first.
As the first and last (and a few intermediate) stops have timepoint values, the timepoints at intermediate stops times might be interpolated.
The text was updated successfully, but these errors were encountered: