Here is my Synchro wish list…

Synchro:

•A TRUE scenario manager, wherein different times of day will all be incorporated into a single file, and geometric changes will only have to be input once. I envision a single roadway network, which happens to have different traffic volumes, lane configurations (contra-flow, parallel parking allowance, etc.), and signal timing plans.

•The ability to encode Time-of-day-specific on-street parking. As the time of day changes, sometimes different parking schemes occur, which affects the laneage.

•Color coding that denotes which program is affected by an attribute (Synchro, Simtraffic, or both).
•Ability to model more than one through movement (as in a 5-way intersection with a two-way couplet merging into a single two-way road.

•Input variable: Crosswalk length and assumed global walking speed. Synchro could then calculate the FDW internally.

•NO automatic encoding of walk phase for turning movements.

•Ability to switch mode between HCM and percentile method for on-screen results.

•The option to use delay as a means of optimization. Since delay is our jurisdiction’s primary MOE, would seem fitting to use this as our criteria for optimization.

•Automatic de-facto turning lane encoding.

•RTOR for double right-turn lane for one lane only.

•On report preview, the ability to zoom in.

Simtraffic:

•Ability for O-D combinations exceeding 1 link. Many times, the complex paths vehicles take are crucial to proper calibration. Although I know would be difficult to encode this on a system-wide basis, give us at least a 4-link assignment, if possible.

•Explicit modeling of Bus traffic and stops

•Explicit Lane utilization modeling, with the ability to specify how each lane is used. I have recently had difficulty modeling a situation where the leftmost lane of 3 is underutilized.

•Change the default settings to reflect a reduction in “cheating” behavior, wherein drivers force unrealistic lane changes, thereby clogging the entire road.

•Proper modeling of acceleration lanes. The modeling of acceleration lanes should be a link attribute, as opposed to the current obligatory creation of a downstream node. Further, currently, Synchro usually forces mainline vehicles to give way to those in acceleration lane. This worsens conditions for the mainline.

•Encoding of lane width by link, as well as by intersection.

•Ultra-low capacity. Currently the capacity lower limit is 1000 vph. However, what if one wanted to model a lane that is metered by a congested parking lot that creates queue spillback onto the main road? I need a punitive fudge factor to reduce capacity when all other measures have failed.

•Iterative assessment of timing schemes. I was told that for simulation, manual modification of timing schemes is best. Could Simtraffic be made to assess the effectiveness of certain timing schemes, and make revisions to timing accordingly?


3D Viewer:

•A greater variety of object types:
•Retail
•Mountain
•School
•Church

•In the absence of an appropriate object, modifiable grey boxes with like on Google earth

•Ability to increase/decrease the size of a building

•Sun/Shading/Blue sky like on google earth

•Ability to import dxf file with topographical information, including elevations

•Ability to include roadway features on a link-level basis:

•Pavement markers (color, spacing - per lane)
•Lightpoles (Choose type, spacing)
•Fire hydrants (Choose type, spacing)
•Shoulder (Width)
•Bike Path (yes/no)
•Sidewalk (Left/right, Width ____ )
•Trees 1 (left/right/median, type, height)
•Trees 2, 3, 4, etc. (left/right/median, type, height)

•Standard cut/copy/paste controls

On the above list, i second the followings:
Synchro - 3, 6, 8
Synctraffic - 1

I'm in support of couple of the ideas above

Synchro
1- A "true" scenario manager as he mentioned would definitely benefit from managing a single file; perhaps the user would simply be able to switch between peak hours on the same Synchro. Public agencies we've encountered doing signal synch projects tend to take a magnifying glass to the geometric base early on, then request a number of modifications to lane geometries and other static settings per the city reviewer's discretion. Making these changes only ONCE would drastically improve our ability to manage the network, and reduce the error margin on duplication work.

3- Some kind of denotion indicating the Synchro Studio component (Synchro, SimTraffic, Warrants) that is directly affected by a changing a particular attribute on the Synchro base would be very convenient. Maybe some non-intrusive notes on the bottom of the active window (where error and warning messages show up) when the attribute is clicked/selected.