HY_Outfall rename to HY_HydroNexus

[dblodgett-usgs]

Rename “HY_Outfall” to “HY_HydroNexus” to reflect that this is the feature that serves the role of connecting two catchments. Gets the identity of the confluence or junction.

[dblodgett-usgs]

Need to make sure that we are clear about the intention of nexus as a potentially complex spatial feature that we idealize as a connection.

[sgrellet]

+1. 'we need to make sure that we are clear about the intention....' -> it's an important flowFeature to have . BTW, I prefer HY_HydroNexus term to 'fallout' (see #218)

[dblodgett-usgs]

My initial pass to change outfall to hydro nexus is done. There are three usages in the document.

• hydro nexus (singular conceptual) e.g. A hydro nexus is relate to catchments.
• hydro nexuses (plural conceptual) e.g. The catchment has inflow and outflow hydro nexuses.
• hydro nexus nodes or features referring to e.g. Hydro nexus features bound realized catchments. or Hydro nexus nodes bound catchments in a topology.

Does this seem reasonable? See here for a discussion of pluralization of nexus.

Next up I'm hoping @IrinaDornblut can get the UML figures that contain HY_Outfall and HY_OutfallRealization updated in the doc. See issue #214 for the latest document.

[dblodgett-usgs]

Figure 34 updated. "Hydro Nexus" section needs to be reviewed for clarity.

[dblodgett-usgs]

There are a few comments left in the doc, but this issue is basically complete going to close and leave the rest of this for future cleanup work.