Signal timing

cycleLength, lostTimePerPhase, saturationFlowRate, and greenTimes (left and thru on each street) are the signal plan. They sit on the signal request, beside laneConfig, not inside globalInputs. isSignalPlanProvided is not used for a signal. cycleLengthConfig is ignored.

Defaults

When cycleLength is omitted, the cycle is 30 seconds times the number of critical phases. When lostTimePerPhase is omitted, lost time is 5 seconds per critical phase. Total effective green is the cycle minus that lost time times the phase count.

globalInputs.maxCycleLength and globalInputs.minCycleLength are accepted and are not applied. A Planning Guide case that uses a facility cycle longer than 30 seconds per phase, or 4 seconds of lost time per phase, has to send cycleLength and lostTimePerPhase.

Field	If omitted
cycleLength	30 × critical phase count
lostTimePerPhase	5 seconds per critical phase
saturationFlowRate	globalInputs.flowRatePerLane (default 1900)
greenTimes thru and left	Split from critical-lane flow

greenTimes has no right-turn key. A right turn uses the through green.

Telegraph Ave & Claremont Ave

The request on the right is the Planning Guide case with the facility cycle filled in: cycleLength 120 and lostTimePerPhase 4. maxCycleLength: 120 is still on globalInputs and still does not set the cycle.

Leaving both timing fields off uses two critical phases, a 60 second cycle, and 5 seconds of lost time per phase. Total effective green is 50 seconds, and the reported intersection volume-to-capacity is about 0.72. Sending the two fields on the right brings that ratio to about 0.64. The published 0.65 uses a rounded peak-hour factor and rounded critical volume. This API does not round those.