What changed in WatDis this week

This week in WatDis, three themes stood out: a much more practical georeferencing foundation inside the editor, meaningful performance gains for larger EPS visualizations, and several changes that improve product and deployment resilience.

Georeferencing is becoming more usable inside the product

WatDis moved georeferencing forward in a concrete way. This is no longer just a roadmap topic: the product now includes richer spatial metadata, coordinate-reference controls, control-point fit preview, and canvas-based point selection.

For teams working with basemaps, drawing alignment, or future KML/KMZ workflows, this brings the hydraulic model closer to a real spatial workflow instead of a disconnected engineering artifact.

Better performance for larger EPS review workflows

A second major theme was visualization performance. The system gained dense visual buffers, per-step overlay caching, cached link geometry, and adaptive detail rules for larger networks.

In practical terms, this should make EPS review feel lighter when moving through complex time-based model views, because the app now avoids more repeated work during redraws.

Stronger resilience across runtime and build paths

The week also included solid reliability work. watdis-next now recovers better from stale chunk failures after deploys, and SewerCalc builds were hardened by removing an unnecessary dependency on ignored build artifacts.

Alongside that, the Next.js apps were updated to version 16.1.1 and internal validation flows were improved. Together, these changes reduce friction for both users and maintainers.

Why it matters

Taken together, these updates show a productive week: more spatial capability inside the product, smoother visual review for larger models, and a stronger path for builds and deployments.

That may not look like one single headline feature, but it meaningfully improves how WatDis can be used and evolved in practice.