mike-resultslisted

# MIKE+ Results Reads MIKE+ `.res1d` result files (via mikeio1d). **No license / no MIKE+ install needed** — fully portable. ## When to use To find out what is in a result file, get peak values, extract a series for analysis/plotting, or answer "which manholes flood?". Use after `mike_run`, or on any existing `.res1d`. (Two result files side by side: `mike-compare`.) ## Tools - **`mike_results_list`** — `{res1d}` → quantities, element counts + sample ids (nodes/reaches/structures/catchments), time range. Start here to discover valid `quantity`/`element` values. - **`mike_results_summary`** — `{res1d, quantities?, skip_hours?}` → per-quantity peak (value, element, chainage, time), in the canonical schema. - **`mike_results_read`** — `{res1d, quantity, element, max_points?}` → a single downsampled time series (`times`, `values`, `unit`, `peak_value`, `peak_time`). - **`mike_results_flooding`** — `{res1d, skip_hours?, top_n?, include_outlets?}` → per node: peak water level vs `ground_level` (and `critical_level`) → `n_flooded`, `flooded[]` ranked by exceedance (`freeboard_m` < 0, with `peak_time`, node `type`), `n_above_critical`, `closest_to_flooding[]`. Outlets are skipped by default (their level is the boundary, not flooding). ## Conventions - Column identity is `Quantity:ElementId[:chainage]` (e.g. `Discharge:Link_29:33.5333`). `element` matches the id prefix. - Output follows the canonical, engine-agnostic schema (`{engine, quantity, element_id, chainage, unit, ...}`) s