Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026 | Publicly Available Data Resources for the 2026 Nepal Glacier-Related Hazard Cascade

Resource details

Summary: BIPAD distribution of seven DoR records. Source IDs and matching fields establish shared provenance with the primary DoR family; these are not independent observations. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Review findings: Seven assessed records. Automated assessment does not assign human eligibility. No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Record type: Official Road Status Service
Provider role: Official Aggregation Service
Original language: English
First identified: 8 September 2026
Geographic coverage: NH42 in Rasuwa and NH17 in Dhading and Chitwan; seven selected records, not all affected roads
Temporal coverage: Closure starts 26 and 30 August 2026; source state retrieved 8 September UTC / 9 September Nepal time
Collection licence: Under review
Redistribution: Metadata And Links Only
Source record: Open the source record
Metadata sources: Source 1: bipadportal.gov.np
Source 2: navigate.dor.gov.np

Inventory

All 7 asset metadata records have been assessed. 7 have flagged follow-up. Read the screening method and findings.

Listed assets: 7
Provider-stated total: No stable dataset file size; response bytes in request ledger
Assets naming another contributor: 7
Confirmed reachable without registration: 7 of 7
Unavailable endpoints: 0

Listed assets

Download CSV

Road blockage at Ghatbesi–Galaudi, Gajuri-5, Dhading (NH17), starting 26 August 2026 — BIPAD copy

Stable file size not stated; captured detail-response bytes recorded separatelyJSON

Open source asset

Listed contributor

dor

Department of Roads, Nepal; BIPAD Portal

Classification

Administrative Road Record

Event And Post Event

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.

Screening findings and extracted metadata

Automated metadata and technical review. Resource eligibility and manuscript inclusion are separate decisions.

Inspection basis: Metadata And Structure Reviewed
Temporal assessment: Event And Post Event
Provider: BIPAD; upstream DoRSource Recorded · source · Native road record
Distribution host: bipadportal.gov.npObserved Http · source · Native road record
Linked file format: JSONObserved Structure · source · Native road record
Source identifier: 304Source Recorded · source · Native road record
Department of Roads record identifier: 868Source Recorded · source · roadDataId
Road number: NH17Source Recorded · source · Native road record
Road-section code: NH17-002Source Recorded · source · Native road record
Location stated by this source: Gajuri-5, DhadingSource Recorded · source · Native road record
Responsible road division: NuwakotSource Recorded · source · Native road record
District field in this source: 26Source Recorded · source · Native road record
Starting chainage as stated: 0+000Source Recorded · source · Native road record
Ending chainage as stated: Not stated
Road status in the retrieved record: OPENSource Recorded · source · Native road record
Recorded start of blockage: 2026-08-26T00:00:00+05:45Source Recorded · source · dateRoadblockStart
Estimated end of blockage: 2026-08-26T19:00:00+05:45Source Recorded · source · dateRoadblockEndEstimated
Actual-end field supplied by the source: 2026-08-28T18:30:00+05:45Source Recorded · source · dateRoadblockEnd
Estimated repair duration: 19 hoursSource Recorded · source · repairEta
Repair-duration label supplied by the source: 2 daysSource Recorded · source · actualRepairTime
Reason attributed by the source: GLOF from Rasuwagadhi-TimureSource Recorded · source · closureReason
Remarks supplied by the source: Managed to open the road as such traffic has to move over the debris.Source Recorded · source · remarks
Response activity reported by the source: Equipment standby to deploy as soon as the flood gets decreased.Source Recorded · source · effortsBeingMade
Record creation date: 2026-08-26Source Recorded · source · dateCreated
Source database modification time: 2026-09-09T03:45:06.177053+05:45Source Recorded · source · modifiedOn; aggregation sync time is not proven road-status change time
Road-record point coordinates: {"type":"Point","coordinates":[84.9017,27.8056]}Source Recorded · source · point
File coordinate system: Not stated
Observation time zone: UTC+05:45 explicitly presentSource Recorded · source · ISO offsets on native timestamps
Detailed location stated by the Department of Roads: Ch. 33+000, Ghatbesi-GalaudiSource Recorded · source · location; may contain a textual chainage despite structured chainage 0+000
Highway identifier embedded in the earlier BIPAD alert: 304Cross Record Identifier Resolution · source · Saved alert embeds realtime.highway pk; this is the BIPAD highway identifier
Relationship between Department of Roads and BIPAD records: DoR id 868 = BIPAD roadDataId; matched fields: road_refno, link_code, closure_type, chainage, end_chainage, repair_eta, actual_repair_time, closure_reason, remarks, efforts_being_made. Location and road-title representations differ.Cross Record Identifier Resolution · source · Compared retrieved DoR detail with linked BIPAD detail
Comparison of timestamp fields across sources: [{"dor_field":"date_roadblock_start","dor_value":"2026-08-26 00:00:00","bipad_value":"2026-08-26T00:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end_estimated","dor_value":"2026-08-26 19:00:00","bipad_value":"2026-08-26T19:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end","dor_value":"2026-08-28 18:30:00","bipad_value":"2026-08-28T18:30:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"}]Derived From Observed Structure · source · Wall-clock comparison only; DoR timezone not supplied
Unresolved road-record findings: ["MIDNIGHT_START_UNCONFIRMED_PRECISION"]Review Assessment · source · Source contradictions and unresolved temporal fields
Limits of the available road history: Current state of historical incidents; complete revision log and field confirmation not recovered. Repair-duration strings are source labels, not independently calculated exact durations.Review Assessment · source · Native road record
Differences from the earlier alert reference: [{"field":"status","embedded_alert_value":"CLOSED","highway_detail_value":"OPEN"},{"field":"dateRoadblockEndEstimated","embedded_alert_value":"2026-08-27T10:00:00+05:45","highway_detail_value":"2026-08-26T19:00:00+05:45"},{"field":"dateRoadblockEnd","embedded_alert_value":null,"highway_detail_value":"2026-08-28T18:30:00+05:45"},{"field":"repairEta","embedded_alert_value":"1 days","highway_detail_value":"19 hours"},{"field":"remarks","embedded_alert_value":"Flood Debris got spread over the road around 200m","highway_detail_value":"Managed to open the road as such traffic has to move over the debris."},{"field":"actualRepairTime","embedded_alert_value":null,"highway_detail_value":"2 days"}]Derived From Observed Structure · source · Compared current detail with saved referenceData in prior alert retrieval; not a complete history
Limits of road location and length information: Point only. Structured chainage 0+000 and absent endChainage are unresolved. Location/remarks length statements are reported descriptions, not measured geometry.Review Assessment · source · Native road record
Image links listed in the BIPAD record: 0Derived From Observed Structure · source · BIPAD images array; no road photograph asset retrieved
Rights statement: No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.Review Assessment · source · Native road record
Licence identifier: Not stated
HTTP response size: 1032Observed Http · source · Bytes in the captured detail response; not a stable file size
Interpretation limit: Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.Review Assessment · source · Native road record

Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
The 00:00 start may be a date placeholder. Do not infer event arrival or causation from midnight without independent timing evidence.

Download screening decisions · Download all metadata and field sources

Catalogue details

Original source title: Naubise-Mugling-Pokhara (Prithvi Rajmarg)
Asset reference: acand_f7e32eca-1c44-513c-a305-3eef171634de
Host / aggregator: bipadportal.gov.np
Relationship to record: Official incident record 868; status OPEN in the retrieved representation. The 00:00 start may be a date placeholder. Do not infer event arrival or causation from midnight without independent timing evidence. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Upstream source: https://navigate.dor.gov.np/api/Road_closure_history_api/getSingle/868
Upstream evidence: DoR id and BIPAD roadDataId correspondence; paired native fields charted
Dataset family: Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026
Acquisition date: Closure start 2026-08-26T00:00:00+05:45
Spatial resolution: Point record; no raster resolution or measured closure footprint
Access result: Reachable without registration on 8 September 2026
Provenance: Under review
Rights: Under review — No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Redistribution: Metadata And Links Only; Raw Contacts Excluded
Production method: Automated source metadata and field-level comparison; no independent field validation

Evidence: source 1 · source 2 · source 3 · source 4

Road blockage at Galchhi–Baireni, Galchi-6, Dhading (NH17), starting 26 August 2026 — BIPAD copy

Stable file size not stated; captured detail-response bytes recorded separatelyJSON

Open source asset

Listed contributor

dor

Department of Roads, Nepal; BIPAD Portal

Classification

Administrative Road Record

Event And Post Event

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.
PARTIAL_OPEN does not establish full restoration; an end date may reflect partial access.

Screening findings and extracted metadata

Automated metadata and technical review. Resource eligibility and manuscript inclusion are separate decisions.

Inspection basis: Metadata And Structure Reviewed
Temporal assessment: Event And Post Event
Provider: BIPAD; upstream DoRSource Recorded · source · Native road record
Distribution host: bipadportal.gov.npObserved Http · source · Native road record
Linked file format: JSONObserved Structure · source · Native road record
Source identifier: 305Source Recorded · source · Native road record
Department of Roads record identifier: 867Source Recorded · source · roadDataId
Road number: NH17Source Recorded · source · Native road record
Road-section code: NH17-002Source Recorded · source · Native road record
Location stated by this source: Galchi-6, DhadingSource Recorded · source · Native road record
Responsible road division: NuwakotSource Recorded · source · Native road record
District field in this source: 26Source Recorded · source · Native road record
Starting chainage as stated: 0+000Source Recorded · source · Native road record
Ending chainage as stated: Not stated
Road status in the retrieved record: PARTIAL_OPENSource Recorded · source · Native road record
Recorded start of blockage: 2026-08-26T11:20:00+05:45Source Recorded · source · dateRoadblockStart
Estimated end of blockage: 2026-08-26T19:00:00+05:45Source Recorded · source · dateRoadblockEndEstimated
Actual-end field supplied by the source: 2026-08-27T18:30:00+05:45Source Recorded · source · dateRoadblockEnd
Estimated repair duration: 7 hoursSource Recorded · source · repairEta
Repair-duration label supplied by the source: 1 daysSource Recorded · source · actualRepairTime
Reason attributed by the source: GLOF from Rasuwagadhi-TimureSource Recorded · source · closureReason
Remarks supplied by the source: Heavy flood out of GLOF at Rasuwagadhi-Timure has deposited debris over 1200m length at Galchhi-Baireni areaSource Recorded · source · remarks
Response activity reported by the source: Clearance ongoing with loader.Source Recorded · source · effortsBeingMade
Record creation date: 2026-08-26Source Recorded · source · dateCreated
Source database modification time: 2026-09-09T03:45:06.238334+05:45Source Recorded · source · modifiedOn; aggregation sync time is not proven road-status change time
Road-record point coordinates: {"type":"Point","coordinates":[84.9943,27.7998]}Source Recorded · source · point
File coordinate system: Not stated
Observation time zone: UTC+05:45 explicitly presentSource Recorded · source · ISO offsets on native timestamps
Detailed location stated by the Department of Roads: Ch. 20+000 to 21+500, Galchhi-Baireni around 1200m lengthSource Recorded · source · location; may contain a textual chainage despite structured chainage 0+000
Highway identifier embedded in the earlier BIPAD alert: 305Cross Record Identifier Resolution · source · Saved alert embeds realtime.highway pk; this is the BIPAD highway identifier
Relationship between Department of Roads and BIPAD records: DoR id 867 = BIPAD roadDataId; matched fields: road_refno, link_code, closure_type, chainage, end_chainage, repair_eta, actual_repair_time, closure_reason, remarks, efforts_being_made. Location and road-title representations differ.Cross Record Identifier Resolution · source · Compared retrieved DoR detail with linked BIPAD detail
Comparison of timestamp fields across sources: [{"dor_field":"date_roadblock_start","dor_value":"2026-08-26 11:20:00","bipad_value":"2026-08-26T11:20:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end_estimated","dor_value":"2026-08-26 19:00:00","bipad_value":"2026-08-26T19:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end","dor_value":"2026-08-27 18:30:00","bipad_value":"2026-08-27T18:30:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"}]Derived From Observed Structure · source · Wall-clock comparison only; DoR timezone not supplied
Unresolved road-record findings: ["PARTIAL_OPEN_NOT_FULL_RESTORATION"]Review Assessment · source · Source contradictions and unresolved temporal fields
Limits of the available road history: Current state of historical incidents; complete revision log and field confirmation not recovered. Repair-duration strings are source labels, not independently calculated exact durations.Review Assessment · source · Native road record
Differences from the earlier alert reference: [{"field":"status","embedded_alert_value":"CLOSED","highway_detail_value":"PARTIAL_OPEN"},{"field":"dateRoadblockEndEstimated","embedded_alert_value":"2026-08-26T10:00:00+05:45","highway_detail_value":"2026-08-26T19:00:00+05:45"},{"field":"dateRoadblockEnd","embedded_alert_value":null,"highway_detail_value":"2026-08-27T18:30:00+05:45"},{"field":"repairEta","embedded_alert_value":"1 hours","highway_detail_value":"7 hours"},{"field":"actualRepairTime","embedded_alert_value":null,"highway_detail_value":"1 days"}]Derived From Observed Structure · source · Compared current detail with saved referenceData in prior alert retrieval; not a complete history
Limits of road location and length information: Point only. Structured chainage 0+000 and absent endChainage are unresolved. Location/remarks length statements are reported descriptions, not measured geometry.Review Assessment · source · Native road record
Image links listed in the BIPAD record: 0Derived From Observed Structure · source · BIPAD images array; no road photograph asset retrieved
Rights statement: No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.Review Assessment · source · Native road record
Licence identifier: Not stated
HTTP response size: 1045Observed Http · source · Bytes in the captured detail response; not a stable file size
Interpretation limit: Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.Review Assessment · source · Native road record

Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
PARTIAL_OPEN does not establish full restoration; an end date may reflect partial access.

Download screening decisions · Download all metadata and field sources

Catalogue details

Original source title: Naubise-Mugling-Pokhara (Prithvi Rajmarg)
Asset reference: acand_cd418976-09c6-5f67-9266-9b21577d2d0d
Host / aggregator: bipadportal.gov.np
Relationship to record: Official incident record 867; status PARTIAL_OPEN in the retrieved representation. PARTIAL_OPEN does not establish full restoration; an end date may reflect partial access. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Upstream source: https://navigate.dor.gov.np/api/Road_closure_history_api/getSingle/867
Upstream evidence: DoR id and BIPAD roadDataId correspondence; paired native fields charted
Dataset family: Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026
Acquisition date: Closure start 2026-08-26T11:20:00+05:45
Spatial resolution: Point record; no raster resolution or measured closure footprint
Access result: Reachable without registration on 8 September 2026
Provenance: Under review
Rights: Under review — No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Redistribution: Metadata And Links Only; Raw Contacts Excluded
Production method: Automated source metadata and field-level comparison; no independent field validation

Evidence: source 1 · source 2 · source 3 · source 4

Road blockage at Khalte–Syafrubesi–Timure, Rasuwa (NH42), starting 26 August 2026 — BIPAD copy

Stable file size not stated; captured detail-response bytes recorded separatelyJSON

Open source asset

Listed contributor

dor

Department of Roads, Nepal; BIPAD Portal

Classification

Administrative Road Record

Event And Post Event

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.
Source status is CLOSED although an actual end date is supplied. Resolve the conflict before treating the road as reopened.

Screening findings and extracted metadata

Automated metadata and technical review. Resource eligibility and manuscript inclusion are separate decisions.

Inspection basis: Metadata And Structure Reviewed
Temporal assessment: Event And Post Event
Provider: BIPAD; upstream DoRSource Recorded · source · Native road record
Distribution host: bipadportal.gov.npObserved Http · source · Native road record
Linked file format: JSONObserved Structure · source · Native road record
Source identifier: 302Source Recorded · source · Native road record
Department of Roads record identifier: 866Source Recorded · source · roadDataId
Road number: NH42Source Recorded · source · Native road record
Road-section code: NH42-014Source Recorded · source · Native road record
Location stated by this source: Gosaikunda-5, RasuwaSource Recorded · source · Native road record
Responsible road division: NuwakotSource Recorded · source · Native road record
District field in this source: 23Source Recorded · source · Native road record
Starting chainage as stated: 0+000Source Recorded · source · Native road record
Ending chainage as stated: Not stated
Road status in the retrieved record: CLOSEDSource Recorded · source · Native road record
Recorded start of blockage: 2026-08-26T11:30:00+05:45Source Recorded · source · dateRoadblockStart
Estimated end of blockage: 2026-08-31T11:33:00+05:45Source Recorded · source · dateRoadblockEndEstimated
Actual-end field supplied by the source: 2026-09-02T11:33:00+05:45Source Recorded · source · dateRoadblockEnd
Estimated repair duration: 5 daysSource Recorded · source · repairEta
Repair-duration label supplied by the source: 7 daysSource Recorded · source · actualRepairTime
Reason attributed by the source: Huge flood from Tibet Region has swept away entire river route roadSource Recorded · source · closureReason
Remarks supplied by the source: Rescue operations going on from concerned authoritiesSource Recorded · source · remarks
Response activity reported by the source: Source Recorded · source · effortsBeingMade
Record creation date: 2026-08-26Source Recorded · source · dateCreated
Source database modification time: 2026-09-09T03:45:06.295857+05:45Source Recorded · source · modifiedOn; aggregation sync time is not proven road-status change time
Road-record point coordinates: {"type":"Point","coordinates":[85.3384,28.165]}Source Recorded · source · point
File coordinate system: Not stated
Observation time zone: UTC+05:45 explicitly presentSource Recorded · source · ISO offsets on native timestamps
Detailed location stated by the Department of Roads: Khalte, Syafrubesi, TimureSource Recorded · source · location; may contain a textual chainage despite structured chainage 0+000
Highway identifier embedded in the earlier BIPAD alert: 302Cross Record Identifier Resolution · source · Saved alert embeds realtime.highway pk; this is the BIPAD highway identifier
Relationship between Department of Roads and BIPAD records: DoR id 866 = BIPAD roadDataId; matched fields: road_refno, link_code, closure_type, chainage, end_chainage, repair_eta, actual_repair_time, closure_reason, remarks, efforts_being_made. Location and road-title representations differ.Cross Record Identifier Resolution · source · Compared retrieved DoR detail with linked BIPAD detail
Comparison of timestamp fields across sources: [{"dor_field":"date_roadblock_start","dor_value":"2026-08-26 11:30:00","bipad_value":"2026-08-26T11:30:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end_estimated","dor_value":"2026-08-31 11:33:00","bipad_value":"2026-08-31T11:33:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end","dor_value":"2026-09-02 11:33:00","bipad_value":"2026-09-02T11:33:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"}]Derived From Observed Structure · source · Wall-clock comparison only; DoR timezone not supplied
Unresolved road-record findings: ["CLOSED_WITH_END_DATE"]Review Assessment · source · Source contradictions and unresolved temporal fields
Limits of the available road history: Current state of historical incidents; complete revision log and field confirmation not recovered. Repair-duration strings are source labels, not independently calculated exact durations.Review Assessment · source · Native road record
Differences from the earlier alert reference: []Derived From Observed Structure · source · Compared current detail with saved referenceData in prior alert retrieval; not a complete history
Limits of road location and length information: Point only. Structured chainage 0+000 and absent endChainage are unresolved. Location/remarks length statements are reported descriptions, not measured geometry.Review Assessment · source · Native road record
Image links listed in the BIPAD record: 0Derived From Observed Structure · source · BIPAD images array; no road photograph asset retrieved
Rights statement: No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.Review Assessment · source · Native road record
Licence identifier: Not stated
HTTP response size: 998Observed Http · source · Bytes in the captured detail response; not a stable file size
Interpretation limit: Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.Review Assessment · source · Native road record

Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Source status is CLOSED although an actual end date is supplied. Resolve the conflict before treating the road as reopened.

Download screening decisions · Download all metadata and field sources

Catalogue details

Original source title: Thori-Bhandara-Malekhu, Galchi-Trishuli-Betrawati-Mailung-Syaphrubesi-Rasuwagadhi
Asset reference: acand_4663aa5a-3e48-57a3-a2e2-fe615f16f84a
Host / aggregator: bipadportal.gov.np
Relationship to record: Official incident record 866; status CLOSED in the retrieved representation. Source status is CLOSED although an actual end date is supplied. Resolve the conflict before treating the road as reopened. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Upstream source: https://navigate.dor.gov.np/api/Road_closure_history_api/getSingle/866
Upstream evidence: DoR id and BIPAD roadDataId correspondence; paired native fields charted
Dataset family: Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026
Acquisition date: Closure start 2026-08-26T11:30:00+05:45
Spatial resolution: Point record; no raster resolution or measured closure footprint
Access result: Reachable without registration on 8 September 2026
Provenance: Under review
Rights: Under review — No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Redistribution: Metadata And Links Only; Raw Contacts Excluded
Production method: Automated source metadata and field-level comparison; no independent field validation

Evidence: source 1 · source 2 · source 3 · source 4

Road blockage at Chalise, Gajuri-2, Dhading (NH17), starting 26 August 2026 — BIPAD copy

Stable file size not stated; captured detail-response bytes recorded separatelyJSON

Open source asset

Listed contributor

dor

Department of Roads, Nepal; BIPAD Portal

Classification

Administrative Road Record

Event And Post Event

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.

Screening findings and extracted metadata

Automated metadata and technical review. Resource eligibility and manuscript inclusion are separate decisions.

Inspection basis: Metadata And Structure Reviewed
Temporal assessment: Event And Post Event
Provider: BIPAD; upstream DoRSource Recorded · source · Native road record
Distribution host: bipadportal.gov.npObserved Http · source · Native road record
Linked file format: JSONObserved Structure · source · Native road record
Source identifier: 303Source Recorded · source · Native road record
Department of Roads record identifier: 869Source Recorded · source · roadDataId
Road number: NH17Source Recorded · source · Native road record
Road-section code: NH17-002Source Recorded · source · Native road record
Location stated by this source: Gajuri-2, DhadingSource Recorded · source · Native road record
Responsible road division: NuwakotSource Recorded · source · Native road record
District field in this source: 26Source Recorded · source · Native road record
Starting chainage as stated: 0+000Source Recorded · source · Native road record
Ending chainage as stated: Not stated
Road status in the retrieved record: OPENSource Recorded · source · Native road record
Recorded start of blockage: 2026-08-26T12:30:00+05:45Source Recorded · source · dateRoadblockStart
Estimated end of blockage: 2026-08-26T19:00:00+05:45Source Recorded · source · dateRoadblockEndEstimated
Actual-end field supplied by the source: 2026-08-28T17:00:00+05:45Source Recorded · source · dateRoadblockEnd
Estimated repair duration: 6 hoursSource Recorded · source · repairEta
Repair-duration label supplied by the source: 2 daysSource Recorded · source · actualRepairTime
Reason attributed by the source: GLOF flood at Rasuwagadhi-Timure spread over roadSource Recorded · source · closureReason
Remarks supplied by the source: Debris spread over 100-200 m on road surfaceSource Recorded · source · remarks
Response activity reported by the source: Equipment ready to mobilize as soon as the flood gets decreased.Source Recorded · source · effortsBeingMade
Record creation date: 2026-08-26Source Recorded · source · dateCreated
Source database modification time: 2026-09-09T03:45:06.116892+05:45Source Recorded · source · modifiedOn; aggregation sync time is not proven road-status change time
Road-record point coordinates: {"type":"Point","coordinates":[84.8515,27.8079]}Source Recorded · source · point
File coordinate system: Not stated
Observation time zone: UTC+05:45 explicitly presentSource Recorded · source · ISO offsets on native timestamps
Detailed location stated by the Department of Roads: Ch. 40+000, ChaliseSource Recorded · source · location; may contain a textual chainage despite structured chainage 0+000
Highway identifier embedded in the earlier BIPAD alert: 303Cross Record Identifier Resolution · source · Saved alert embeds realtime.highway pk; this is the BIPAD highway identifier
Relationship between Department of Roads and BIPAD records: DoR id 869 = BIPAD roadDataId; matched fields: road_refno, link_code, closure_type, chainage, end_chainage, repair_eta, actual_repair_time, closure_reason, remarks, efforts_being_made. Location and road-title representations differ.Cross Record Identifier Resolution · source · Compared retrieved DoR detail with linked BIPAD detail
Comparison of timestamp fields across sources: [{"dor_field":"date_roadblock_start","dor_value":"2026-08-26 12:30:00","bipad_value":"2026-08-26T12:30:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end_estimated","dor_value":"2026-08-26 19:00:00","bipad_value":"2026-08-26T19:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end","dor_value":"2026-08-28 17:00:00","bipad_value":"2026-08-28T17:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"}]Derived From Observed Structure · source · Wall-clock comparison only; DoR timezone not supplied
Unresolved road-record findings: []Review Assessment · source · Source contradictions and unresolved temporal fields
Limits of the available road history: Current state of historical incidents; complete revision log and field confirmation not recovered. Repair-duration strings are source labels, not independently calculated exact durations.Review Assessment · source · Native road record
Differences from the earlier alert reference: [{"field":"status","embedded_alert_value":"CLOSED","highway_detail_value":"OPEN"},{"field":"dateRoadblockEndEstimated","embedded_alert_value":"2026-08-27T10:00:00+05:45","highway_detail_value":"2026-08-26T19:00:00+05:45"},{"field":"dateRoadblockEnd","embedded_alert_value":null,"highway_detail_value":"2026-08-28T17:00:00+05:45"},{"field":"repairEta","embedded_alert_value":"21 hours","highway_detail_value":"6 hours"},{"field":"actualRepairTime","embedded_alert_value":null,"highway_detail_value":"2 days"}]Derived From Observed Structure · source · Compared current detail with saved referenceData in prior alert retrieval; not a complete history
Limits of road location and length information: Point only. Structured chainage 0+000 and absent endChainage are unresolved. Location/remarks length statements are reported descriptions, not measured geometry.Review Assessment · source · Native road record
Image links listed in the BIPAD record: 0Derived From Observed Structure · source · BIPAD images array; no road photograph asset retrieved
Rights statement: No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.Review Assessment · source · Native road record
Licence identifier: Not stated
HTTP response size: 1028Observed Http · source · Bytes in the captured detail response; not a stable file size
Interpretation limit: Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.Review Assessment · source · Native road record

Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.

Download screening decisions · Download all metadata and field sources

Catalogue details

Original source title: Naubise-Mugling-Pokhara (Prithvi Rajmarg)
Asset reference: acand_2d329e1e-4fa2-588f-9116-24a1d045276a
Host / aggregator: bipadportal.gov.np
Relationship to record: Official incident record 869; status OPEN in the retrieved representation. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Upstream source: https://navigate.dor.gov.np/api/Road_closure_history_api/getSingle/869
Upstream evidence: DoR id and BIPAD roadDataId correspondence; paired native fields charted
Dataset family: Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026
Acquisition date: Closure start 2026-08-26T12:30:00+05:45
Spatial resolution: Point record; no raster resolution or measured closure footprint
Access result: Reachable without registration on 8 September 2026
Provenance: Under review
Rights: Under review — No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Redistribution: Metadata And Links Only; Raw Contacts Excluded
Production method: Automated source metadata and field-level comparison; no independent field validation

Evidence: source 1 · source 2 · source 3 · source 4

Road blockage at Jawang Khola, Benighat Rorang-10, Dhading (NH17), starting 26 August 2026 — BIPAD copy

Stable file size not stated; captured detail-response bytes recorded separatelyJSON

Open source asset

Listed contributor

dor

Department of Roads, Nepal; BIPAD Portal

Classification

Administrative Road Record

Event And Post Event

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.
Estimated end 26 August 06:30 precedes stated start 13:30 on the same date. Preserve the source error; do not silently correct AM/PM.

Screening findings and extracted metadata

Automated metadata and technical review. Resource eligibility and manuscript inclusion are separate decisions.

Inspection basis: Metadata And Structure Reviewed
Temporal assessment: Event And Post Event
Provider: BIPAD; upstream DoRSource Recorded · source · Native road record
Distribution host: bipadportal.gov.npObserved Http · source · Native road record
Linked file format: JSONObserved Structure · source · Native road record
Source identifier: 306Source Recorded · source · Native road record
Department of Roads record identifier: 871Source Recorded · source · roadDataId
Road number: NH17Source Recorded · source · Native road record
Road-section code: NH17-003Source Recorded · source · Native road record
Location stated by this source: Benighat Rorang-10, DhadingSource Recorded · source · Native road record
Responsible road division: NuwakotSource Recorded · source · Native road record
District field in this source: 26Source Recorded · source · Native road record
Starting chainage as stated: 0+000Source Recorded · source · Native road record
Ending chainage as stated: Not stated
Road status in the retrieved record: OPENSource Recorded · source · Native road record
Recorded start of blockage: 2026-08-26T13:30:00+05:45Source Recorded · source · dateRoadblockStart
Estimated end of blockage: 2026-08-26T06:30:00+05:45Source Recorded · source · dateRoadblockEndEstimated
Actual-end field supplied by the source: 2026-08-26T19:00:00+05:45Source Recorded · source · dateRoadblockEnd
Estimated repair duration: 7 hoursSource Recorded · source · repairEta
Repair-duration label supplied by the source: 5 hoursSource Recorded · source · actualRepairTime
Reason attributed by the source: GLOF hit Bhotekoshi, TimureSource Recorded · source · closureReason
Remarks supplied by the source: Debris of flood spread over road around 300m lengthSource Recorded · source · remarks
Response activity reported by the source: Loader, Backhoe and Grader being deployedSource Recorded · source · effortsBeingMade
Record creation date: 2026-08-26Source Recorded · source · dateCreated
Source database modification time: 2026-09-09T03:45:05.941158+05:45Source Recorded · source · modifiedOn; aggregation sync time is not proven road-status change time
Road-record point coordinates: {"type":"Point","coordinates":[84.6747,27.8157]}Source Recorded · source · point
File coordinate system: Not stated
Observation time zone: UTC+05:45 explicitly presentSource Recorded · source · ISO offsets on native timestamps
Detailed location stated by the Department of Roads: Ch. 64+100 to 64+400, Jawang KholaSource Recorded · source · location; may contain a textual chainage despite structured chainage 0+000
Highway identifier embedded in the earlier BIPAD alert: 306Cross Record Identifier Resolution · source · Saved alert embeds realtime.highway pk; this is the BIPAD highway identifier
Relationship between Department of Roads and BIPAD records: DoR id 871 = BIPAD roadDataId; matched fields: road_refno, link_code, closure_type, chainage, end_chainage, repair_eta, actual_repair_time, closure_reason, remarks, efforts_being_made. Location and road-title representations differ.Cross Record Identifier Resolution · source · Compared retrieved DoR detail with linked BIPAD detail
Comparison of timestamp fields across sources: [{"dor_field":"date_roadblock_start","dor_value":"2026-08-26 13:30:00","bipad_value":"2026-08-26T13:30:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end_estimated","dor_value":"2026-08-26 06:30:00","bipad_value":"2026-08-26T06:30:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end","dor_value":"2026-08-26 19:00:00","bipad_value":"2026-08-26T19:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"}]Derived From Observed Structure · source · Wall-clock comparison only; DoR timezone not supplied
Unresolved road-record findings: ["ESTIMATED_END_PRECEDES_START"]Review Assessment · source · Source contradictions and unresolved temporal fields
Limits of the available road history: Current state of historical incidents; complete revision log and field confirmation not recovered. Repair-duration strings are source labels, not independently calculated exact durations.Review Assessment · source · Native road record
Differences from the earlier alert reference: [{"field":"status","embedded_alert_value":"CLOSED","highway_detail_value":"OPEN"},{"field":"dateRoadblockEnd","embedded_alert_value":null,"highway_detail_value":"2026-08-26T19:00:00+05:45"},{"field":"actualRepairTime","embedded_alert_value":null,"highway_detail_value":"5 hours"}]Derived From Observed Structure · source · Compared current detail with saved referenceData in prior alert retrieval; not a complete history
Limits of road location and length information: Point only. Structured chainage 0+000 and absent endChainage are unresolved. Location/remarks length statements are reported descriptions, not measured geometry.Review Assessment · source · Native road record
Image links listed in the BIPAD record: 0Derived From Observed Structure · source · BIPAD images array; no road photograph asset retrieved
Rights statement: No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.Review Assessment · source · Native road record
Licence identifier: Not stated
HTTP response size: 998Observed Http · source · Bytes in the captured detail response; not a stable file size
Interpretation limit: Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.Review Assessment · source · Native road record

Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Estimated end 26 August 06:30 precedes stated start 13:30 on the same date. Preserve the source error; do not silently correct AM/PM.

Download screening decisions · Download all metadata and field sources

Catalogue details

Original source title: Naubise-Mugling-Pokhara (Prithvi Rajmarg)
Asset reference: acand_b98f4004-84da-5545-b850-575245bdc204
Host / aggregator: bipadportal.gov.np
Relationship to record: Official incident record 871; status OPEN in the retrieved representation. Estimated end 26 August 06:30 precedes stated start 13:30 on the same date. Preserve the source error; do not silently correct AM/PM. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Upstream source: https://navigate.dor.gov.np/api/Road_closure_history_api/getSingle/871
Upstream evidence: DoR id and BIPAD roadDataId correspondence; paired native fields charted
Dataset family: Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026
Acquisition date: Closure start 2026-08-26T13:30:00+05:45
Spatial resolution: Point record; no raster resolution or measured closure footprint
Access result: Reachable without registration on 8 September 2026
Provenance: Under review
Rights: Under review — No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Redistribution: Metadata And Links Only; Raw Contacts Excluded
Production method: Automated source metadata and field-level comparison; no independent field validation

Evidence: source 1 · source 2 · source 3 · source 4

Road blockage at Mowa Khola, Ichchhakamana-3, Chitwan (NH17), starting 26 August 2026 — BIPAD copy

Stable file size not stated; captured detail-response bytes recorded separatelyJSON

Open source asset

Listed contributor

dor

Department of Roads, Nepal; BIPAD Portal

Classification

Administrative Road Record

Event And Post Event

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.

Screening findings and extracted metadata

Automated metadata and technical review. Resource eligibility and manuscript inclusion are separate decisions.

Inspection basis: Metadata And Structure Reviewed
Temporal assessment: Event And Post Event
Provider: BIPAD; upstream DoRSource Recorded · source · Native road record
Distribution host: bipadportal.gov.npObserved Http · source · Native road record
Linked file format: JSONObserved Structure · source · Native road record
Source identifier: 307Source Recorded · source · Native road record
Department of Roads record identifier: 870Source Recorded · source · roadDataId
Road number: NH17Source Recorded · source · Native road record
Road-section code: NH17-004Source Recorded · source · Native road record
Location stated by this source: Ichchhakamana-3, ChitwanSource Recorded · source · Native road record
Responsible road division: BharatpurSource Recorded · source · Native road record
District field in this source: 35Source Recorded · source · Native road record
Starting chainage as stated: 0+000Source Recorded · source · Native road record
Ending chainage as stated: Not stated
Road status in the retrieved record: OPENSource Recorded · source · Native road record
Recorded start of blockage: 2026-08-26T13:30:00+05:45Source Recorded · source · dateRoadblockStart
Estimated end of blockage: 2026-08-26T18:00:00+05:45Source Recorded · source · dateRoadblockEndEstimated
Actual-end field supplied by the source: 2026-08-26T19:00:00+05:45Source Recorded · source · dateRoadblockEnd
Estimated repair duration: 4 hoursSource Recorded · source · repairEta
Repair-duration label supplied by the source: 5 hoursSource Recorded · source · actualRepairTime
Reason attributed by the source: GLOF at Rasuwagadhi flooded over highwaySource Recorded · source · closureReason
Remarks supplied by the source: Debris of flood spread over road about 100m lengthSource Recorded · source · remarks
Response activity reported by the source: Equipment mobilised, BackhoeSource Recorded · source · effortsBeingMade
Record creation date: 2026-08-26Source Recorded · source · dateCreated
Source database modification time: 2026-09-09T03:45:06.055535+05:45Source Recorded · source · modifiedOn; aggregation sync time is not proven road-status change time
Road-record point coordinates: {"type":"Point","coordinates":[84.6605,27.8286]}Source Recorded · source · point
File coordinate system: Not stated
Observation time zone: UTC+05:45 explicitly presentSource Recorded · source · ISO offsets on native timestamps
Detailed location stated by the Department of Roads: Ch. 66+700, Mowa Khola areaSource Recorded · source · location; may contain a textual chainage despite structured chainage 0+000
Highway identifier embedded in the earlier BIPAD alert: 307Cross Record Identifier Resolution · source · Saved alert embeds realtime.highway pk; this is the BIPAD highway identifier
Relationship between Department of Roads and BIPAD records: DoR id 870 = BIPAD roadDataId; matched fields: road_refno, link_code, closure_type, chainage, end_chainage, repair_eta, actual_repair_time, closure_reason, remarks, efforts_being_made. Location and road-title representations differ.Cross Record Identifier Resolution · source · Compared retrieved DoR detail with linked BIPAD detail
Comparison of timestamp fields across sources: [{"dor_field":"date_roadblock_start","dor_value":"2026-08-26 13:30:00","bipad_value":"2026-08-26T13:30:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end_estimated","dor_value":"2026-08-26 18:00:00","bipad_value":"2026-08-26T18:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end","dor_value":"2026-08-26 19:00:00","bipad_value":"2026-08-26T19:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"}]Derived From Observed Structure · source · Wall-clock comparison only; DoR timezone not supplied
Unresolved road-record findings: []Review Assessment · source · Source contradictions and unresolved temporal fields
Limits of the available road history: Current state of historical incidents; complete revision log and field confirmation not recovered. Repair-duration strings are source labels, not independently calculated exact durations.Review Assessment · source · Native road record
Differences from the earlier alert reference: [{"field":"status","embedded_alert_value":"CLOSED","highway_detail_value":"OPEN"},{"field":"dateRoadblockEnd","embedded_alert_value":null,"highway_detail_value":"2026-08-26T19:00:00+05:45"},{"field":"actualRepairTime","embedded_alert_value":null,"highway_detail_value":"5 hours"}]Derived From Observed Structure · source · Compared current detail with saved referenceData in prior alert retrieval; not a complete history
Limits of road location and length information: Point only. Structured chainage 0+000 and absent endChainage are unresolved. Location/remarks length statements are reported descriptions, not measured geometry.Review Assessment · source · Native road record
Image links listed in the BIPAD record: 0Derived From Observed Structure · source · BIPAD images array; no road photograph asset retrieved
Rights statement: No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.Review Assessment · source · Native road record
Licence identifier: Not stated
HTTP response size: 996Observed Http · source · Bytes in the captured detail response; not a stable file size
Interpretation limit: Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.Review Assessment · source · Native road record

Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.

Download screening decisions · Download all metadata and field sources

Catalogue details

Original source title: Naubise-Mugling-Pokhara (Prithvi Rajmarg)
Asset reference: acand_66b18ea7-8171-57d2-8fde-7db045e1c918
Host / aggregator: bipadportal.gov.np
Relationship to record: Official incident record 870; status OPEN in the retrieved representation. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Upstream source: https://navigate.dor.gov.np/api/Road_closure_history_api/getSingle/870
Upstream evidence: DoR id and BIPAD roadDataId correspondence; paired native fields charted
Dataset family: Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026
Acquisition date: Closure start 2026-08-26T13:30:00+05:45
Spatial resolution: Point record; no raster resolution or measured closure footprint
Access result: Reachable without registration on 8 September 2026
Provenance: Under review
Rights: Under review — No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Redistribution: Metadata And Links Only; Raw Contacts Excluded
Production method: Automated source metadata and field-level comparison; no independent field validation

Evidence: source 1 · source 2 · source 3 · source 4

Road blockage at Krishna Bhir, Benighat Rorang-7, Dhading (NH17), starting 30 August 2026 — BIPAD copy

Stable file size not stated; captured detail-response bytes recorded separatelyJSON

Open source asset

Listed contributor

dor

Department of Roads, Nepal; BIPAD Portal

Classification

Administrative Road Record

Event And Post Event

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.
No actual end date supplied. Preserve unknown completion; an estimate is not an observed reopening.

Screening findings and extracted metadata

Automated metadata and technical review. Resource eligibility and manuscript inclusion are separate decisions.

Inspection basis: Metadata And Structure Reviewed
Temporal assessment: Event And Post Event
Provider: BIPAD; upstream DoRSource Recorded · source · Native road record
Distribution host: bipadportal.gov.npObserved Http · source · Native road record
Linked file format: JSONObserved Structure · source · Native road record
Source identifier: 310Source Recorded · source · Native road record
Department of Roads record identifier: 874Source Recorded · source · roadDataId
Road number: NH17Source Recorded · source · Native road record
Road-section code: NH17-003Source Recorded · source · Native road record
Location stated by this source: Benighat Rorang-7, DhadingSource Recorded · source · Native road record
Responsible road division: NuwakotSource Recorded · source · Native road record
District field in this source: 26Source Recorded · source · Native road record
Starting chainage as stated: 0+000Source Recorded · source · Native road record
Ending chainage as stated: Not stated
Road status in the retrieved record: CLOSEDSource Recorded · source · Native road record
Recorded start of blockage: 2026-08-30T08:10:00+05:45Source Recorded · source · dateRoadblockStart
Estimated end of blockage: 2026-09-10T17:00:00+05:45Source Recorded · source · dateRoadblockEndEstimated
Actual-end field supplied by the source: Not stated
Estimated repair duration: 11 daysSource Recorded · source · repairEta
Repair-duration label supplied by the source: Not stated
Reason attributed by the source: LandslideSource Recorded · source · closureReason
Remarks supplied by the source: Road washed away due to toe cutting by Trishuli river. Cracks along the road around 100m length along centre line of roadSource Recorded · source · remarks
Response activity reported by the source: Currently under discussion how to open the road.Source Recorded · source · effortsBeingMade
Record creation date: 2026-08-30Source Recorded · source · dateCreated
Source database modification time: 2026-09-09T03:45:05.725919+05:45Source Recorded · source · modifiedOn; aggregation sync time is not proven road-status change time
Road-record point coordinates: {"type":"Point","coordinates":[84.7337,27.796]}Source Recorded · source · point
File coordinate system: Not stated
Observation time zone: UTC+05:45 explicitly presentSource Recorded · source · ISO offsets on native timestamps
Detailed location stated by the Department of Roads: 57+150, Krishna BhirSource Recorded · source · location; may contain a textual chainage despite structured chainage 0+000
Highway identifier embedded in the earlier BIPAD alert: 310Cross Record Identifier Resolution · source · Saved alert embeds realtime.highway pk; this is the BIPAD highway identifier
Relationship between Department of Roads and BIPAD records: DoR id 874 = BIPAD roadDataId; matched fields: road_refno, link_code, closure_type, chainage, end_chainage, repair_eta, actual_repair_time, closure_reason, remarks, efforts_being_made. Location and road-title representations differ.Cross Record Identifier Resolution · source · Compared retrieved DoR detail with linked BIPAD detail
Comparison of timestamp fields across sources: [{"dor_field":"date_roadblock_start","dor_value":"2026-08-30 08:10:00","bipad_value":"2026-08-30T08:10:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end_estimated","dor_value":"2026-09-10 17:00:00","bipad_value":"2026-09-10T17:00:00+05:45","wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"},{"dor_field":"date_roadblock_end","dor_value":null,"bipad_value":null,"wall_clock_components_match":true,"timezone_equivalence":"not_established_from_DoR_response"}]Derived From Observed Structure · source · Wall-clock comparison only; DoR timezone not supplied
Unresolved road-record findings: ["ACTUAL_END_NOT_STATED"]Review Assessment · source · Source contradictions and unresolved temporal fields
Limits of the available road history: Current state of historical incidents; complete revision log and field confirmation not recovered. Repair-duration strings are source labels, not independently calculated exact durations.Review Assessment · source · Native road record
Differences from the earlier alert reference: [{"field":"dateRoadblockEndEstimated","embedded_alert_value":"2026-08-31T17:00:00+05:45","highway_detail_value":"2026-09-10T17:00:00+05:45"},{"field":"repairEta","embedded_alert_value":"1 days","highway_detail_value":"11 days"}]Derived From Observed Structure · source · Compared current detail with saved referenceData in prior alert retrieval; not a complete history
Limits of road location and length information: Point only. Structured chainage 0+000 and absent endChainage are unresolved. Location/remarks length statements are reported descriptions, not measured geometry.Review Assessment · source · Native road record
Image links listed in the BIPAD record: 0Derived From Observed Structure · source · BIPAD images array; no road photograph asset retrieved
Rights statement: No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.Review Assessment · source · Native road record
Licence identifier: Not stated
HTTP response size: 1065Observed Http · source · Bytes in the captured detail response; not a stable file size
Interpretation limit: Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.Review Assessment · source · Native road record

Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
No actual end date supplied. Preserve unknown completion; an estimate is not an observed reopening.

Download screening decisions · Download all metadata and field sources

Catalogue details

Original source title: Naubise-Mugling-Pokhara (Prithvi Rajmarg)
Asset reference: acand_ad102ad8-d40f-5c15-b682-12169b253057
Host / aggregator: bipadportal.gov.np
Relationship to record: Official incident record 874; status CLOSED in the retrieved representation. No actual end date supplied. Preserve unknown completion; an estimate is not an observed reopening. Administrative road-status records, not field-validated damage measurements or a complete revision history. Source reasons are attributed statements. Road points and demographic associations do not establish affected road length or affected people. Recorded OPEN is not a current travel-safety assurance.
Upstream source: https://navigate.dor.gov.np/api/Road_closure_history_api/getSingle/874
Upstream evidence: DoR id and BIPAD roadDataId correspondence; paired native fields charted
Dataset family: Road blockages and recorded reopening dates in Rasuwa, Dhading and Chitwan — BIPAD, August–September 2026
Acquisition date: Closure start 2026-08-30T08:10:00+05:45
Spatial resolution: Point record; no raster resolution or measured closure footprint
Access result: Reachable without registration on 8 September 2026
Provenance: Under review
Rights: Under review — No asset-specific open licence established. Public retrieval does not establish redistribution permission. Catalogue metadata and source links only; raw responses and personal contact fields remain private.
Redistribution: Metadata And Links Only; Raw Contacts Excluded
Production method: Automated source metadata and field-level comparison; no independent field validation

Evidence: source 1 · source 2 · source 3 · source 4