When changing client files there is a screen that shows the differences between the two client files. Currently there is no way to see the differences between Clearances.

Have a report function in SpidaCalc that exports the information steel manufacturers need to custom design steel poles. This would include the VTL (Vertical Tangential Load) & LCA (Load Case Assignment) and a load tree showing locations, vecto...

Keyboard shortcuts are always helpful, but going from Next/Previous poles would save a significant amount of time. Something like ctrl + arrow left or right to mirror the function of the Next/Previous buttons in 2D view would be great. Beyond just...

Without setting up a proxy to handle SPIDAcalc's non-compliant map tile requests, there is no way to correctly align overlays with SPIDAcalc's default basemap options. Current Functionality: When requesting map tiles, SPIDAcalc always formats the ...

Currently we have to click through pole by pole to update location forms. It's common for all forms on a project to have the same selection. It would save a lot of time for users to have the ability to select what option populates in the form when...

Looking for a deadend option that maintains the conductor spacing.

Currently, equipment is modeled on the face of the pole. For pole top mounted equipment (such as antennas), this leads to the equipment being centered on the face of the pole rather than the center of the pole, which offsets the equipment's weight...

In designing long runs of utility poles, 1 decimal of accuracy in angle and direction leads to huge errors and many adjustments down the line. It is difficult to match Spida with Auto-Cad civil 3d drawings.

When importing from other software certain values are given extra decimal places. In SpidaCalc you see the rounded value, but in the json you see the exact value. I have attached an example of the issue in a ZIP. On the first location (second pole...