search

opengeospatial / HY_Features

http://opengeospatial.github.io/HY_Features/
Other
8 stars 1 forks source link

Clarify outfall as a natural confluence or arbitrary location. #201

Closed dblodgett-usgs closed 7 years ago

dblodgett-usgs commented 7 years ago

Consider further clarifying outfall as a natural confluence or an arbitrary location on the network.

Obstacles such as falls, rapids, dams, and barrages are given as realizations of outfalls, as are hydrometric stations and other entities (Annex B). On page 54 the following statement is given: “The outfall represents the logical place where a catchment interacts with another catchment, i.e. where the outflow of a contributing catchment becomes inflow into a receiving catchment.” So presumably outfall plays different roles, that quoted plus a general term for obstacle, and perhaps other roles as well. Is this correct? Note that many falls and rapids are fairly small and practically would not have realized catchments associated with them. This also applies to many small dams that were built a century ago and are no longer treated as active control structures.
Pour point, outfall, hydrometric feature. Pour point is not found either in this document or the International Glossary of Hydrography. Presumably it can be treated as a hydrometric feature, whether or not it is part of a hydrometric network. Of interest here is the correct term for arbitrary positions along a flow path for which a hydrologist might want a catchment defined to feed hydrologic models. Presumably these positions can all be considered as outfalls. Is this correct?

Related primarily to #188 and #189. This issue can be closed when the concept of a hydrolocation, catchmentoutlet, and hydroNexus have been documented in the spec.

dblodgett-usgs commented 7 years ago

Fixes an issue raised in #182.

dblodgett-usgs commented 7 years ago

Response:
The term "outfall" is no longer going to be used in the normative specification. It was being used in several ways which lead to confusion. The feature that was HY_OutFall is now named HY_HydroNexus to be clear that this is a feature meant to represent the logical place where a catchment interacts with another. What was HY_OutfallRealization is now named HY_HydroLocation and is meant to represent features that are referenced to the network and, if catchments were realized to accompany them, could become HY_HydroNexus features. HY_HydroLocations can be given a wide variety of types, including outlet, pour point, and others. This clarification will be made in the spec.

sgrellet commented 7 years ago

+1

dblodgett-usgs commented 7 years ago

This has been fixed with changes for #218.

dblodgett-usgs commented 7 years ago

Done in version of doc from 5-17. Will upload soon.