Version compatibility
This page lists which software versions are compatible with each Giswater release. Compatibility is split into two groups:
- Core platform — required to install and run the QGIS plugin and database model (QGIS, PostgreSQL, PostGIS, pgRouting).
- EPA hydraulic engines — external simulation software used when exporting and running INP files via go2epa. EPANET applies to Water Supply (WS) projects; SWMM applies to Urban Drainage (UD) projects. See Hydraulic capabilities for the full workflow.
These components are required to run Giswater. PostGIS and pgRouting are PostgreSQL extensions.
| Giswater Version | QGIS | PostgreSQL | PostGIS | pgRouting |
|---|---|---|---|---|
| 3.5 | 3.22 – 3.28 | 10.x – 15.x | 3.3 – 3.6 | 3.3 – 3.7 |
| 3.6 | 3.34.5 – 3.40 | 10.x – 17.x | 3.3 – 3.6 | 3.3 – 3.7 |
| 4.X.Y (current) | 3.34.5 – 4.x | 16.X – 18.X | 3.3 – 3.6 | 3.8 – 4.x |
These engines are only required if you use hydraulic simulation workflows (go2epa). Inventory and OM features work without them.
| Engine | Project type | Supported |
|---|---|---|
| EPANET | WS | 2.2 – 3.2 |
| SWMM | UD | 2.0 – 5.2 |
These version ranges apply to all Giswater releases (3.5, 3.6, and 4.X.Y). For Giswater 3.5, EPANET is limited to 2 – 2.2.
For Giswater 4.X.Y, pgRouting 3.8.0 or newer is required (up to 4.x). Most recent PostgreSQL distributions include a compatible version by default; however, some older distributions might not. If your installation does not include pgRouting 3.8.0 or above, you can manually install or upgrade it. For detailed instructions, refer to the official pgRouting installation documentation.
The supported ranges above reflect what the Giswater developers actually use and test day to day. The current development stack is PostgreSQL 18 with pgRouting 4.0.1 — both fall within the listed ranges and work without issues. Whenever a new PostgreSQL, PostGIS, or pgRouting release comes out, the team upgrades to it early to validate compatibility and update the table if needed.
SWMM 5.1 (en-US) is recommended because it supports LID controls and other features used in UD projects. See How to fill LID controls catalog for details.
