Two current ideas:

1. a simple proportioning of the contributions to a point's displacements based on how many sides contribute, if 2, then each 50%, if 3, then each 30% etc. But may also need consideration for the angle. Simple geometrical solution (with warning) if nothing better received.




2. a geometric solution which could be coded and compared to finite element analysis.

Same ideas can apply to changes in ground movement curve between one wall and another.

Provide interpolation of imported displacements for the case where the imported displacement points do not coincide with the points already in the data file.

Ignore displacement points within tunnels (just as within excacations)

Summaries of all results for all stages required (i.e. worst cases of any and all stages). (Enveloping.) Database?

Specify displacement grid by centreline start and end points, width of grid and frequency of transects (then allow results to be displayed for grid lines in both directions?)

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

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

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

If a building has near-linear displacement, the checks in the program can cause the output to "flip" between sagging and hogging. Suggest adding a tolerance to this check (user-editable).

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

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

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

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)

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.

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

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

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

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