NR: Turns out arrivals/departure doesn't actually respect UTC indication
This commit is contained in:
parent
67d7a20c5c
commit
9f04faaa90
1 changed files with 1 additions and 1 deletions
|
@ -134,7 +134,7 @@ class Module(object):
|
||||||
|
|
||||||
method = client.service.GetArrivalDepartureBoardByCRS if len(location_code) == 3 else client.service.GetArrivalDepartureBoardByTIPLOC
|
method = client.service.GetArrivalDepartureBoardByCRS if len(location_code) == 3 else client.service.GetArrivalDepartureBoardByTIPLOC
|
||||||
try:
|
try:
|
||||||
query = method(100, location_code, datetime.now().isoformat().split(".")[0] + "Z", filter["period"],
|
query = method(100, location_code, datetime.now().isoformat().split(".")[0], filter["period"],
|
||||||
nr_filterlist, "to", '', "PBS", False)
|
nr_filterlist, "to", '', "PBS", False)
|
||||||
except WebFault as detail:
|
except WebFault as detail:
|
||||||
if str(detail) == "Server raised fault: 'Invalid crs code supplied'":
|
if str(detail) == "Server raised fault: 'Invalid crs code supplied'":
|
||||||
|
|
Loading…
Reference in a new issue