An activity pattern describing when the toll is active and not active should be defined.
One possible method for defining this would be:
time_active_start : long - number of seconds after midnight when this toll becomes active
time_active_end : long - number of seconds after midnight when this toll is no longer active
Using this approach would mean that if a single toll lane is active more than once a day, the toll lane would have to be defined for each time that toll is active.
For example, if the SR 237 Westbound toll lane becomes active between the hours of 5:00 a.m. and 10:00 a.m., and again at 3:00 p.m. to 7:00 p.m., then it would be defined as something like this:
plaza
lane
description
time_active_start
time_active_end
5110
01
SR 237/I-880 Connector WB
18000
36000
5110
01
SR 237/I-880 Connector WB
54000
68400
Where 18000 is 5 a.m. and 36000 is 10 a.m., and so on.
Another possible solution would be to use a recurrence pattern such as iCalendar's recurrence rules, but this would put a fair amount of strain on developers to implement and decode.
An activity pattern describing when the toll is active and not active should be defined.
One possible method for defining this would be:
Using this approach would mean that if a single toll lane is active more than once a day, the toll lane would have to be defined for each time that toll is active.
For example, if the SR 237 Westbound toll lane becomes active between the hours of 5:00 a.m. and 10:00 a.m., and again at 3:00 p.m. to 7:00 p.m., then it would be defined as something like this:
Where 18000 is 5 a.m. and 36000 is 10 a.m., and so on.
Another possible solution would be to use a recurrence pattern such as iCalendar's recurrence rules, but this would put a fair amount of strain on developers to implement and decode.