Fixed the following defects
On writing a PI Based Alignment the POB Coordinate values were transposed.
On reading a Vertical Alignment, Asymmetrical Vertical Curves were not read correctly
If you created a PI Based HAL and saved it and then reopened it to add a Vertical Alignment, it would incorrectly read the vertical alignment as a horizontal alignment
We added the ability to add the third column into a slope table for the vertical curves at the change points.
Hey Alan, any chance you guys can add a superelevation tab?
As real superelevation or as a slope table?
Alan
As a superelevation table with the fields the same as super tab in the Alignment Editor. It’s the only one we can’t copy and paste at this point.
Thanks
Hey @alan.sharp Any potential to add superelevation elements as a spreadsheet?
| Rate |
Begin Trans |
Begin Max |
End Max |
End Trans |
| 4.0% |
235585 |
235730 |
236440 |
236585 |
Or, Advanced:
| Rate |
Runout |
Runoff |
% Runoff |
| 5.6% |
102 |
287 |
80.0% |
% Runoff in the tangent is what is on every planset I have ever seen listing these ‘advanced’ parameters, but TBC wants the % in curve… whichever works.
Also Normal Cross Slope, and the spreadsheet editor might need a PI of each curve. Again, TBC rebuffs the industry standard and lists the PC of each curve. Not sure how to best manage compound curves or special circumstances like only rotate one side of the road or rotate the outside edge only up to level crown.
Thanks