Currently immediately above the surface level of an excavation the calculated ground movement = 0mm. It would be helpful to have the ground movements calculated extend above the top of the polygon excavation

Translation for imported displacements and PDisp files, as for DXF.

Highlight (e.g. red dot) in 3D Graphics any displacement locations that are in excvations.

Identify null points (in excavations) as e.g. NaN rather than zero displacement when output in CSV output

Allow the user to avoid calculating any displacement points, lines, polylines or grids that are not used in damage calculations

Greater granularisation of utility and building resutls on 3D Graphics, rather than single colour for whole building/whole utility, break into many along building/utility and/or text box to display detailed results e.g. strain values, chainages etc.

Flatten the polygonal excavations dialog and circular excavations dialog to allow ease of copy/paste. Straightforward for Circular Excavations, but coordinates and gm curves would have to sit in pop-up dialog for each row (as polylines) for Polygonal Excavations (with comma-separated coordinates shown in table view only)

Allow user to create custom selection for Text Output to avoid e.g. History if they want all other input data

Avoid multi-segment tunnels and replace with alignment tool with displacements calculated as distance from tunnel axis

Import any number of JSON or xdd XDisp files to an open file.

For utilities approaching and over bridges, and approaching manholes.

As per GSA for static headers/scrolling table content

Export rail damage assessment location data as Displacement Points for PDisp analysis

Shadows of generic buildings and generic utilities at transects

Import JSON file of Imported Displacements (not only CSV as an option)

Enter rail track by 3D Graphical Input

DXF Import of rail tracks

Scaling factors for diameters of utilitites (generic and specific), deflected shape delta x, y and z etc.

Database for results (to give user-defined display, post-processing)

Object/results inspector window (e.g. with critical results for each entity)