Weekly Update June 14, 2026

Highlights

• WatDis now includes a real GeoJSON import flow inside Network Designer, with multi-file loading and profile selection.

• The new importer keeps DMA overlays and auxiliary records out of the saved hydraulic network by default.

• This first release ships with GeoJSON-to-INP round-trip validation, synthetic samples, and a reproducible manual for checking the workflow.

What's New (By Category)

GeoJSON Import

• The main story this week is straightforward: WatDis moved from importer design work to a real product path for bringing GeoJSON network data into the app.
• Parsing runs through a worker-backed flow, which helps move heavier import work away from the main UI thread while source files are being processed.
• The interface already supports multi-file loading and profile selection instead of staying at the level of an isolated internal prototype.

Data Safety and Model Boundaries

• The importer separates DMA overlays and other auxiliary data from the main saved network payload so contextual records are not silently mixed into the hydraulic model.
• When source data is ambiguous, WatDis stays conservative and does not force every point asset into a hydraulic link without enough confidence.
• That boundary makes the first release more useful for inspection and preparation without pretending the pipeline is blindly automatic.

Validation and Repeatability

• The new path now includes GeoJSON -> WatDis -> INP -> WatDis validation so exchange integrity is easier to verify.
• It also ships with synthetic sample files and an importer manual covering checks, warnings, and export notes for more repeatable setup review.
• This week also included several EPANET parsing and import-guardrail fixes that reduce avoidable data loss and brittle edge cases.

Coming Next

• Direct SHP or ZIP support is still not part of this release.
• Reprojection for geographic CRS inputs is still out of scope for now, so that limit should be read as a safety boundary rather than full GIS compatibility.
• Point-asset conversion will stay intentionally conservative until the source data carries more reliable direction and mapping signals.