Laurent Courty

@RudyFrom3 > Once the depth is passed, the Weir/Orifice calculation identifies a Flow, which may or may not be excepted by the connecting pipe link. So a secondary calculation is...

@bemcdonnell I guess the best documentation would be a code example. Maybe I should make a pyswmm PR for the code I have? I really want to implement that new...

@RudyFrom3 I try to do a synthesis: First, in the nodes you want to couple you have to create openings with `swmm_setNodeOpening()`, and set the `couplingArea` with `swmm_setNodeParam()`. As well,...

This might be achieved by having a networkx (or similar) representation. IMHO, it could be interesting.

I believe there is a plan to add an API for the input/output of SWMM (can't find the issue, though). The original SWMM is heavily reliant on the text input...

@jennwuu It would be nice, but I think the first step is to get the I/O API to work. If not the plugin would be similar to [this one](https://github.com/Oslandia/qgis-swmm).

> GIS makes me think about coordinates. I think `getters` for coordinates for Nodes, Link vertices, and Subcatchment polygons would be nice as a **base** function. We could also debate...

@bemcdonnell As a use case example, coupling a surface model requires knowing the node coordinates. That is why itzi currently includes a swmm inp parser. More generally, whether or not...

@bemcdonnell I would consider the management of CRS out of scope. See Shapely as a example: no support for CRS. There is geopandas for that.

@abhiramm7 The embedded lite parser is fine to just expose the coordinates as object properties. If we want a more generic parser / writer, then maybe a separate, generic inp_parser...