Importing of TAFs from JSON File and/or Ability for Imported Heights to Reflect on 'Calculated' View

Currently, SPIDAcalc only supports WMS and OSM layers. WMTS is an OGC standard that serves image tiles like WMS, except the tiles are pregenerated rather than created at request time. This allows for faster response times from the service. Here is...

To being able to have a more precise pole look, some equipment are attached on crossarm.

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.

We would like the, 'Year of the Pole' added as a text to go with 'height', 'class' and 'pole owner' when using "Export to CAD'. The Year is needed along side the pole profile. See attached sample. The 'Year' should be included in the Component Pro...

In Design Status, update the default Clearances icon to something other than a green check mark, which makes it appear that it is passing clearance requirements. Instead, do sometihng like the Analysis icon where if there are no results, it shows ...

With SpidaCalc's new clearance feature, it would be great if we could generate customized clearance report tables/templates (eg. CSA Table 23, Table 24, Table 2).

The ability to organize and edit elements across multiple design layers using hierarchical relationships would be very helpful. It could streamline workflows and improve consistency in projects.

Currently, the Profile View does not remember the last selected WEP in Profile View. It would be very helpful if it did, so you could visually compare designs by switching your selection back and forth between design layers. Unfortunately, as it c...

Profile View can misleadingly render the measured wire midspans in some situations. In particular, this happens when: Wire#1's attach height is larger than Wire#2's attach height on both poles. Wire#1's measured midspan is smaller then Wire#2's me...