File formats
SWMM files
Section titled “SWMM files”| File | What it is |
|---|---|
.inp | The model. Text, human-readable, the standard SWMM input format. This is the file you keep |
.rpt | The engine’s text report from a run: continuity, summaries, warnings |
.out | Binary results. Every value at every time step |
Only the .inp is the model. The other two are outputs of a run and can always be
regenerated.
Round-tripping
Section titled “Round-tripping”.inp files are read and written as standard SWMM, so they open in EPA SWMM, PCSWMM and
InfoSWMM.
Sections you never edit are preserved verbatim - only sections you actually changed are regenerated. A file that goes out is not gratuitously reformatted, and sections the application does not parse are kept rather than dropped.
Shapefile (.shp with .dbf, .shx, and ideally .prj) and GeoJSON, both in and
out. Points become nodes, lines become links, polygons become subcatchments.
A .prj lets coordinates be reprojected automatically.
Data in
Section titled “Data in”CSV for time series: rainfall, SCADA and monitoring data, and observed flow for calibration.
Customer billing data as shapefile or GeoJSON, points or polygons, for dry-weather flow.
Results out
Section titled “Results out”| Export | Contents |
|---|---|
| Node summary CSV | Peak depth, head, inflow, flooding per node |
| Link summary CSV | Peak flow, velocity, depth, d/D per link |
| Time series CSV | Every reporting period, wide format |
.rpt | The engine’s own report |
| PDF report | Model summary, continuity, results tables, design check and next steps |
| GeoJSON / shapefile | The network, for GIS |