Hydrology & FloodsEvent WindowPublic access route

River water-level observations — Trishuli at Galchi, 28–31 August 2026 (UTC; subset of DHM records)

EnglishTrishuli at Galchi

Observational Data

Open access route (JSON)
No stable dataset byte size stated; per-request byte counts retained

Dataset Specifications

Spatial extent
Parent resource coverage: Selected sites on the Trishuli corridor and Phalakhu tributary, Nepal
Temporal coverageNot statedEvent Window
Source & contributorBIPAD Portal; Nepal Department of Hydrology and Meteorology (source attribution)Listed as: hydrology.gov.npHost platform: bipadportal.gov.np
Parent collectionRiver water-level records at Malekhu and Galchi — BIPAD archive for August 2026
Format & sizeJSON · No stable dataset byte size stated; per-request byte counts retained
Licence & accessPublic Route Or Response Documented · No Asset Specific Reuse Grant Established — not_stated
Lineage & documentationNot stated
Catalogue assessment and metadata evidence
Follow-up needed

Completed catalogue decisions are recorded separately from technical inspection and scientific validation. Access and metadata evidence retain their original dates and scope.

Completed catalogue assessment

Eligibility decision
Include · Included Data
Assessment date
28 September 2026
Decision reason
Both original BIPAD queries retrieved. Malekhu has 161 observations 25–26 August; Galchi 467 observations 28–31 AugustUTC, so Galchi does not capture the initial flood arrival. Values have no stated unit/datum in BIPAD schema. Source is hydrology.gov.np; no independent instrument series is inferred.
Information role
Observational Data
Scientific validation
not_performed_by_catalogue_review
Access assessment
Retrieved Original Body
Rights assessment
Not Stated

Included data · Metadata assessed 8 September 2026

Reachable without registration · Direct Open · checked 8 September 2026

  • Resolve unit, gauge-reference and quality-control documentation before comparing station magnitudes or converting water level to another quantity.
  • Retain the actual coverage and internal gaps; do not infer flood arrival or event peak from the first or last available sample.
  • Use the existing DHM observations when counting independent Galchi measurements; BIPAD adds a distribution route, not new readings.
  • Establish component-specific reuse terms before redistributing upstream observations or alert contents.

Spatial extent

Loading map…

Recorded bounding box