When creating corridors, it is occasionally necessary to assign an alignment as a secondary alignment that is also a point control, where it is not assigned as a secondary alignment. Usually, the cause is that the secondary alignment is running in the wrong direction and is needed by more than one corridor so that transposing the alignment will simply move the problem to the other corridor.
When a corridor design input report is generated, the secondary alignment is only identified by the xml attribute alignmentOID. An example of what the value looks like might be something like this: DGNEC::15a8a10000::ECXA::1
In the same report, if an HVControl is also listed, the attribute oidControl will contain a similarly cryptic value, but there is another attribute - controlName which has the value of the alignment name.
While it is possible therefore to match a non-secondary HV Control to a secondary alignment name manually, it would be very beneficial if the secondary alignment xml data contained the "human" name of the alignment just like the HV Control data.