linking-hms-to-hecras

Link HMS outputs to HEC-RAS boundary conditions for integrated modeling.

6|2|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/gpt-cmdr/hms-commander --skill linking-hms-to-hecras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linking-hms-to-hecras
Source: https://github.com/gpt-cmdr/hms-commander/tree/main/.claude/skills/linking-hms-to-hecras
Command: npx skills add https://github.com/gpt-cmdr/hms-commander --skill linking-hms-to-hecras

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ras-commander, and includes references (resource) components.

What problem does it solve?

This Skill automates the complex linkage between HEC-HMS hydrologic models and HEC-RAS hydraulic models.

Core Features & Use Cases

  • Hydrograph Export: Extract flow time series from HMS for RAS boundary conditions.
  • Spatial Matching: Document outlet locations for accurate cross-section matching between models.

Quick Start

Extract the outflow hydrograph for Watershed_Outlet from the results.dss file after running a design storm simulation.

Frequently Asked Questions about linking-hms-to-hecras

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I link HMS watershed model outputs to HEC-RAS boundary conditions?

Linking HMS to RAS involves extracting flow time series from HMS results via DSS, spatially matching HMS outlets to RAS cross sections, and formatting the hydrograph data into valid boundary-condition imports. This Skill automates the full workflow from HMS output through RAS-ready boundary conditions, handling DSS pathname formatting and time-series alignment.

What's required to export HMS hydrographs for use in HEC-RAS models?

Exporting HMS flows to RAS requires access to HMS results files in DSS format, outlet location documentation for spatial matching, and knowledge of proper DSS pathname construction. This Skill extracts and formats those hydrographs automatically, preparing them as validated boundary conditions ready for RAS import.

Can I automate the workflow from HMS design storm results to RAS boundary conditions?

Yes. This Skill automates the complete HMS-to-RAS workflow: it extracts outflow hydrographs from HMS results files, performs spatial matching of outlet locations to cross sections, validates time-series data, and formats DSS pathnames for seamless RAS boundary-condition imports.

Do I need to manually match HMS outlets to RAS cross sections?

This Skill documents and automates outlet-location matching between HMS and RAS models, eliminating manual cross-section lookup. It handles spatial alignment so flows are assigned to the correct boundary-condition locations in your RAS model.

What DSS infrastructure is needed to link HMS and RAS models?

Linking HMS to RAS via DSS requires RasDss, HmsResults, HmsDss, and HmsGeo components to extract flows, format pathnames, and validate data. This Skill manages that infrastructure internally, automating DSS interactions so you work directly with hydrograph exports and boundary-condition assignments.

How do I ensure HMS flows align correctly with RAS simulation time steps?

This Skill validates and aligns time-series data during the export process, ensuring HMS hydrograph time steps match RAS boundary-condition requirements. Quality validation catches alignment issues before import, preventing simulation errors.