<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>J. Michael Johnson</dc:contributor>
  <dc:contributor>Andrew R. Bock</dc:contributor>
  <dc:contributor>Jessica Z. LeRoy</dc:contributor>
  <dc:contributor>Martin R Wernimont</dc:contributor>
  <dc:creator>David L. Blodgett</dc:creator>
  <dc:date>2023</dc:date>
  <dc:description>&lt;div class="paragraph"&gt;&lt;p&gt;The WaterML2: Part 3 - Surface Hydrology Features (HY_Features) Conceptual Model was published by OGC in 2018. This report documents the use of HY_Features concepts in support of two key tasks: (1) local to continental hydrologic modeling; and (2) referencing river corridor data to hydrographic networks. The presented use cases are applicable in hydroscience research and assessments, water resources engineering practices, and drought and flood responses.&lt;/p&gt;&lt;/div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;Before the HY_Features conceptual model there was no internationally recognized standard for the design of software and data for the hydroscience and engineering community. This report presents progress towards a logical data model that interprets the abstract HY_Features concepts for use in geospatial workflows, modeling applications, and web data systems that integrate hydrologic data.&lt;/p&gt;&lt;/div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;The use cases addressed include: (1) hydrologic model control volume definition; (2) hydrologic network connectivity; (3) characterization of catchments with landscape and atmospheric data; (4) river corridor characterization; (5) hydrologic location; and (6) flow network location. Each use case is described briefly along with an analysis of the information requirements. This report presents a summary of the logical model designed to satisfy the needs of these use cases and a summary of updates and changes proposed for HY_Features.&lt;/p&gt;&lt;/div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;Changes for consideration by the HY_Features Standards Working Group include the following.&lt;/p&gt;&lt;/div&gt;&lt;div class="olist arabic"&gt;&lt;ol class="arabic"&gt;&lt;li&gt;&lt;p&gt;Provide more clarity on the inherited properties and associations of features that "realize" the catchment and nexus concepts from HY_Features.&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;Add nexus realization feature types to represent the outlet of catchments that are "frontal" (terminate to the ocean or a large waterbody) or "inland sinks."&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;Add a "HY_Flowline" feature as a superclass of HY_Flowpath providing linear referencing on waterbodies that are not catchment realizations.&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;Add an association or interface to support connection between surface catchments and hydrogeologic units.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/div&gt;</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:language>en</dc:language>
  <dc:publisher>Open Geospatial Consortium</dc:publisher>
  <dc:title>Hydrologic modeling and river corridor applications of HY_Features concepts</dc:title>
  <dc:type>reports</dc:type>
</oai_dc:dc>