When working on large numbers of poles, it's useful to separate them into categories such as Telco-only, Power-only, Joint Use, etc for easier report export. But when moving poles between leads you can only select one at a time and the list doesnt...
Enable clearance rules that are orientation-agnostic (apply regardless of which attachment is above or below) and optionally allow different minimum clearances depending on the relative position. Current rules require an upper-attachment → lower-a...
Add support for Component Groups of Component Groups
There are many NESC 2023 classifications that are grouped differently depending on the rule. For example, Table 232-1 combines the following in the first column:
Insulated Communication Conductors And Cable
Messengers
Overhead Shield/Surge-P...
Add a check box property to wires and equipment to identify them as grounded. Allow this property to be used in the creation of Component Groups for clearance analysis.
Add support for applying a phase label to a wire that applies throughout the connected length of wire. This is mostly for primary phasing. Allow these to be customized in the client file. Examples include: A, B, C Left, Center, Right Road, Center,...
Currently in SpidaCalc you can adjust the elevation between two WEP or pole structures. However, setting an anchor on an incline or decline (relative to the base of the pole) has a notable impact on the corresponding guy strength and vertical load...
I noticed that for the update from 24.0 to 24.1, the Project Details Report PDF no longer exports with the ability to navigate in Bluebeam with bookmarks- this was very handy for the 24.0 version.
Update the SPIDAcalc API to support: Reading project, form, lead, location, design, etc. properties Updating project, form, lead, location, design, etc. properties Getting the currently selected project, lead, location, or design Adding leads, loc...
2
Needs review