Skip to content

Auditing a model

Two tools under Trace network that answer “can I trust this model” before you spend a day calibrating it.

Scans every element and reports, per field, which hold measured data and which hold a default. It separates:

  • Critical fields - the ones needed before it will run at all
  • Populated against assumed - a value that came from your data versus one the app or the importer supplied
  • Elements that are mostly filler

A data index summarises the whole model, and Highlight on map shows you where the gaps are geographically, which is usually more revealing than a percentage. Gaps cluster: one survey batch, one street, one era of record-keeping.

The headline description of a network: counts of nodes, links and catchments, total pipe length, the node elevation range, and a connectivity summary. Highlight jumps to what a row describes.

Worth a look immediately after an import. A pipe-length total an order of magnitude from what you expect, or an elevation range that spans two kilometres, is a units or datum problem showing itself early rather than three days later.