New PlanConnection time values were parsed using Date object's toTimeString() method, which always outputs local time zone. This is wrong: the client should display itineraries using the time zone which matches the routing data and request parameters.
Now UI primarily parses time of day from the original datetime strings coming from OTP. In some rare cases, hh:mm is extracted from epoch time using a new epochToTime() utility, which gets the forced time zone from the configuration.
In addition, following two fixes are included:
Joensuu planner has correct service area polygon
Dead code related to rendering delayed legs removed
New PlanConnection time values were parsed using Date object's toTimeString() method, which always outputs local time zone. This is wrong: the client should display itineraries using the time zone which matches the routing data and request parameters.
Now UI primarily parses time of day from the original datetime strings coming from OTP. In some rare cases, hh:mm is extracted from epoch time using a new epochToTime() utility, which gets the forced time zone from the configuration.
In addition, following two fixes are included: