reading-dss-boundary-data

Extract boundary time series from HEC-DSS files using the RasDss API methods. Read the DSS catalog with get_catalog, then call extract_boundary_timeseries or read_timeseries to pull specific boundary conditions. Results return as DataFrames with metadata in df.attrs for immediate use in HEC-HMS workflows or plotting.

Yes, read multiple time series boundaries in batch using read_multiple_timeseries. This method processes multiple boundary paths from a single HEC-DSS file (V6 or V7) and returns DataFrames, enabling efficient extraction across real projects without manual iteration.

Install the pyjnius dependency to enable Java interoperability. The Skill handles automatic Monolith download and JVM configuration on first use, so no manual Java or DSS library setup is required—lazy-loading startup prepares your environment automatically.

Yes, this Skill supports both HEC-DSS V6 and V7 files. Extract boundary conditions from either version using the same API, making it compatible with legacy and current DSS file formats in your HEC-HMS boundary workflows.

After extracting boundary time series from DSS files, use the returned DataFrames directly in HEC-HMS workflows. The metadata in df.attrs provides context for boundary conditions, enabling seamless integration with downstream HMS modeling or plotting without format conversion.

Use batch extraction with read_multiple_timeseries or extract_boundary_timeseries in loops across project files. The stable RasDss API and automatic environment setup enable automation of boundary-condition workflows at scale without manual JVM or Monolith configuration per file.