Infrastructure & ExposureEvent / Post-Event AssessmentPublic access route

Road blockage at Ghatbesi–Galaudi, Gajuri-5, Dhading (NH17), starting 26 August 2026 — Department of Roads record

EnglishGalchhi-Junction Trisuli bridge

Administrative Road Record

Open access route (JSON)
Stable file size not stated; captured detail-response bytes recorded separately

Dataset Specifications

Spatial extent
Parent resource coverage: NH42 in Rasuwa and NH17 in Dhading and Chitwan; seven selected records, not all affected roads
Temporal coverageNot statedEvent / Post-Event Assessment · Disaster response period
Source & contributorDepartment of Roads, NepalListed as: Department of RoadsHost platform: navigate.dor.gov.np
Parent collectionRoad blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — Nepal Department of Roads, August–September 2026
Format & sizeJSON · Stable file size not stated; captured detail-response bytes recorded separately
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
Seven primary DoR JSON records retrieved and linked to BIPAD copies by source IDs. Preserve partial-open/closed-with-end-date/missing-end-date and timestamp conflicts; points do not measure damaged road length or certify present travel safety.
Information role
Administrative Road Record
Scientific validation
not_performed_by_catalogue_review
Access assessment
Retrieved Original Body
Rights assessment
Not Stated

Supporting asset · Metadata assessed 8 September 2026

Reachable without registration · Direct Open · checked 8 September 2026

  • Establish asset-specific reuse terms before redistributing source bodies.
  • Resolve update history, chainage placeholders and field confirmation before quantitative restoration or damage analysis.
  • Treat paired DoR/BIPAD records as seven shared-source records; do not sum them as 14 independent closures.
  • The 00:00 start may be a date placeholder. Do not infer event arrival or causation from midnight without independent timing evidence.
  • Obtain an official DoR timestamp convention before assigning timezone or comparing absolute times. BIPAD offsets do not define the DoR API schema.

Spatial extent

Loading map…

Recorded bounding box