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
The serviceDay + scheduledDeparture sum 1483915500 converts to 01/08/2017 @ 10:45pm (UTC) which in Finnish time equals 1/9/2017, 12:45:00 AM GMT+2:00.
It seems to be because of incorrect serviceDay: "20170108" in the query. Do you have any suggestions how to handle such queries near day changes?
edit:
On further inspection there's nothing wrong in the graphQL data, only it is now difficult to tell the start date for a trip without always including full list of stoptimes in the query and checking the first one. Would be very helpful to have a startDate property available in Trip itself.
The text was updated successfully, but these errors were encountered:
Querying stoptimes for route 110T at around 01 AM 08.01.2016 using
returns the first stoptime as follows
The serviceDay + scheduledDeparture sum 1483915500 converts to 01/08/2017 @ 10:45pm (UTC) which in Finnish time equals 1/9/2017, 12:45:00 AM GMT+2:00.
It seems to be because of incorrect serviceDay: "20170108" in the query. Do you have any suggestions how to handle such queries near day changes?
edit:
On further inspection there's nothing wrong in the graphQL data, only it is now difficult to tell the start date for a trip without always including full list of stoptimes in the query and checking the first one. Would be very helpful to have a startDate property available in Trip itself.
The text was updated successfully, but these errors were encountered: