Currently the API only uses the current time even if the time is changed in the parameter.
Can't test, but there aren't much changes here to the API. So will upgrade this issue upstream soon.
AFAIK it was still working a couple of days ago. Back then the website was using 12 hour time format, but accepted 24 hour format. Also it's broken with the old 12 hour format aswell.
Haven't seen many suspect commits. Date format was changed to ISO8601, seemingly not affecting times.
DST fixes but those only impact the routing.
Stoptime filtering, only impacts GTFS reading
Problemen was known upstream as #666 and was fixed 3 days ago
@skywave Did you pull otp_nl and does it now work? Because I pulled everything from the upstream master last night and built and believe @skinkie restarted it all and it sill doesn't work. The only commit that's you added is related to something elevation (which we don't use).
Yes i tested it locally but let me recheck. Thought this was the fixing commit
I rebuilt everything just now, would just need a restart from @skinkie
Yes it it is working locally on branch otp_nl. See screenshot http://imgur.com/AIDQU
I do see your merge (a5b821c) contains the same patch to DateUtils.java as my merge (5765fc0). So you're probably right about the patch already in there at 21hours.
Most likely i didnt fetch after your merge, which would explain my build at midnight had this same bug, but after i merged (which complained about fast forward btw ) it was solved. Could it be that somehow with this compile this patch was left out? Otherwise i can upload the api-webapp build on this computer