Resource details
- Summary
- Two station query routes distributing upstream hydrological records. Malekhu extends the locally catalogued source access; Galchi duplicates a subset of the DHM observations. Separate service families do not represent independent measurements.
- Review findings
- Automated metadata assessment; independent human eligibility and manuscript inclusion remain unassigned. No component-specific open licence established. Public API access does not establish redistribution permission. Only descriptive metadata and source links are published; retrieved source responses remain private.
- Record type
- Official Observation Service
- Provider role
- Official Aggregation Service
- Original language
- English
- First identified
- 8 September 2026
- Geographic coverage
- Selected sites on the Trishuli corridor and Phalakhu tributary, Nepal
- Temporal coverage
- Requested 25–31 August 2026 UTC; Malekhu returns 25–26 August, Galchi 28–31 August.
- Collection licence
- Under review
- Redistribution
- Metadata And Links Only
- Source record
- Open the source record
- Metadata sources
Inventory
All 2 asset metadata records have been assessed. 2 have flagged follow-up. Read the screening method and findings.
- Listed assets
- 2
- Provider-stated total
- Not stated as stable dataset sizes; request bytes recorded separately
- Assets naming another contributor
- 2
- Confirmed reachable without registration
- 2 of 2
- Unavailable endpoints
- 0
Listed assets
Download CSV01
River water-level observations — Trishuli at Furke Khola, Malekhu, 25–26 August 2026 (UTC; record ends early)
No stable dataset byte size stated; per-request byte counts retainedJSON
Open source assetListed contributor
Classification
Data candidate · 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.
- Clarify the source description CDCP_TEST_2025 and the absence of a published Malekhu instrument/QC explanation.
- Establish component-specific reuse terms before redistributing upstream observations or alert contents.
Catalogue details
- Original source title
- Trishuli at Furke Khola(Malekhu)
- Asset reference
- acand_44e9b79c-f66e-5f7e-ac67-36e982438ffb
- Host / aggregator
- bipadportal.gov.np
- Relationship to record
- The bounded BIPAD query returned 161 readings from 2026-08-25T00:05:00+00:00 to 2026-08-26T05:55:00+00:00. Observed spacing is usually ten minutes, with internal gaps. The record stops on 26 August at 11:40 Nepal time. This is the last available sample, not an established flood-arrival time or event peak. The source description CDCP_TEST_2025 remains an unresolved instrument/QC label. BIPAD does not state units or a common gauge datum in the retrieved schema. Water level is not discharge or inundation depth.
- Upstream source
- hydrology.gov.np
- Upstream evidence
- Native dataSource/source fields; source agency and distribution host kept separate
- Dataset family
- River water-level records at Malekhu and Galchi — BIPAD archive for August 2026
- Acquisition date
- 2026-08-25T00:05:00+00:00 to 2026-08-26T05:55:00+00:00
- Spatial resolution
- Not applicable; station/alert point, not raster pixels or an inundation footprint
- Access result
- Reachable without registration on 8 September 2026
- Provenance
- Under review
- Rights
- Under review — No component-specific open licence established. Public API access does not establish redistribution permission. Only descriptive metadata and source links are published; retrieved source responses remain private.
- Redistribution
- Metadata And Links Only; Source Response Bodies Remain Private
- Production method
- Automated source metadata and structured-response charting; no independent measurement validation
02
River water-level observations — Trishuli at Galchi, 28–31 August 2026 (UTC; subset of DHM records)
No stable dataset byte size stated; per-request byte counts retainedJSON
Open source assetListed contributor
Classification
Data candidate · 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.
Catalogue details
- Original source title
- Trishuli at Galchi
- Asset reference
- acand_85b5a0f9-05df-54fc-b033-33069edf9620
- Host / aggregator
- bipadportal.gov.np
- Relationship to record
- The bounded BIPAD query returned 467 readings from 2026-08-28T11:05:00+00:00 to 2026-08-31T23:55:00+00:00. Observed spacing is usually ten minutes, with internal gaps. All 467 timestamps and numeric values exactly match the previously retrieved DHM Galchi series; DHM contains 541 additional timestamps. BIPAD warning-level metadata is null in 390 rows and 367 in 77 rows; the status label alone cannot establish safety. BIPAD does not state units or a common gauge datum in the retrieved schema. Water level is not discharge or inundation depth.
- Upstream source
- hydrology.gov.np
- Upstream evidence
- Native dataSource/source fields; source agency and distribution host kept separate
- Dataset family
- River water-level records at Malekhu and Galchi — BIPAD archive for August 2026
- Acquisition date
- 2026-08-28T11:05:00+00:00 to 2026-08-31T23:55:00+00:00
- Spatial resolution
- Not applicable; station/alert point, not raster pixels or an inundation footprint
- Access result
- Reachable without registration on 8 September 2026
- Provenance
- Under review
- Rights
- Under review — No component-specific open licence established. Public API access does not establish redistribution permission. Only descriptive metadata and source links are published; retrieved source responses remain private.
- Redistribution
- Metadata And Links Only; Source Response Bodies Remain Private
- Production method
- Automated source metadata and structured-response charting; no independent measurement validation
No candidate assets match these filters.

