← Back to What's New
June 21, 20262 min read
Weekly Update June 21, 2026
This week WatDis expands GeoJSON import with an editable mapping wizard, a more stable preview path, and a grouped Diagnostics report for reviewing QA findings with more context.
EN
Ver en españolwatdisgeojsonimportqadiagnostics

Highlights
-
WatDis can now infer GeoJSON layers and field aliases, let users adjust the mapping, and preview the parsed network before import.
-
Diagnostics can now turn a QA run into a grouped report by severity and rule, with counts, affected-ID samples, and navigation actions.
-
The current import flow also adds more conservative valve guardrails and a more stable preview path for real datasets.
What's New (By Category)
More Configurable GeoJSON Import
- The main product update this week is that GeoJSON import no longer depends on a fixed path and can now start with inferred layer roles and field aliases.
- The wizard lets users correct that mapping before import, review a preview of the parsed result, and continue through the worker-backed flow inside Network Designer.
- That makes the feature more realistic for user-owned GIS data without pretending every export is now zero-config.
Easier QA Review in Diagnostics
- Diagnostics can now group findings by severity and rule instead of forcing every review to begin with one-by-one findings.
- The report keeps counts, affected-ID samples, and the existing actions for select, zoom, and open properties.
- For teams checking an imported or edited network, that makes it easier to decide what to fix first.
Stronger Guardrails Around Import Review
- The current import path is more conservative around isolation valves and other ambiguous cases so the app does not make overly aggressive hydraulic assumptions from incomplete source data.
- Preview stability was also tightened to reduce unnecessary refresh loops and make pre-import review more dependable.
- The result is not just a new interface, but a clearer path for inspecting data before it becomes part of the working model.
Coming Next
- Wizard mapping persistence is still not part of this release.
- Bulk QA remediation is still out of scope; the new report is for review and navigation.
- Direct SHP or ZIP support remains future work.