(Issue copied here from SFCTA Asana task)
Original issue:
When using DTA Anyway to build an AM network, DTA Anyway imports a PM schedule.
This task is to pull out hard-coding of "PM" period so that time of day can be
specified in DTA run script. Also create a user note to specify the hour of
interest for traffic signal import, e.g. 5p-6p instead of 3:30p-6:30p.
Update:
Discovered some additional problems. Did a quick fix for now, but will come
back later and replace the "AM" and non-"AM" scripts with a single set that
takes time period as an input.
Need to convert all times and time periods to lookup values based on time
period input. Several scripts refer to time-specific fields, e.g. lane_am or
buslane_pm. Suggest adding time periods to Util.py so "AM" value in run script
will lead lane_am being used and tpplus transit line import knowing time period
is 3hours and starts at 9:00am.
Moving back date to allow immediate attention on validation and project model
runs.
Original issue reported on code.google.com by dan.tisc...@sfcta.org on 20 Jan 2015 at 8:02
Original issue reported on code.google.com by
dan.tisc...@sfcta.orgon 20 Jan 2015 at 8:02