Official road blockages and recorded end dates
Seven Department of Roads records match seven BIPAD copies by their source identifiers. Names identify the locality, road and blockage-start date. Metadata separates status, estimated end, actual end, repair-duration labels and source update times. The existing HDX road-blockage resource contains crowdsourced satellite interpretations; no individual equivalence with these official records has been established.
One CLOSED record also has an actual-end date, another is only PARTIAL_OPEN, and one estimated end precedes its stated start. Department of Roads timestamps do not state a time zone. These findings remain visible in the asset assessments and prevent unqualified claims about reopening or event timing.
Read which locally documented sources and products still need separate catalogue searches.
BIPAD river archives and flood-alert records
Two station query routes returned 161 Malekhu readings and 467 Galchi readings. Every recovered Galchi timestamp and value already appears in the DHM series. The catalogue links the distributions and retains their different coverage; these are not independent measurements.
Three corridor flood-alert records preserve alert start, database creation, expiry and embedded observation times separately. Their embedded measurements are later than the alert starts, and missing expiry does not establish an ongoing flood. Unit, gauge-reference, quality-control and reuse questions remain explicit in the five asset assessments.
Screening outcomes
5,652 records have no recorded follow-up flag. 679 have a recorded access, identity, rights or interpretation constraint. Missing technical fields remain explicitly unknown. The absence of a flag does not establish scientific validity or unrestricted reuse.
This is an automated metadata and technical assessment. Retaining an asset means retaining it in the evidence inventory; it does not establish resource eligibility, independent human review, local scientific accuracy or manuscript inclusion.
| Disposition | Assets |
|---|---|
| Data candidate | 795 |
| Follow-up needed | 70 |
| Baseline candidate | 921 |
| Download route not usable | 373 |
| Supporting asset | 3,962 |
| Linked manifestation | 105 |
| Cloud-obscured water product | 84 |
| Package includes retracted products | 2 |
| Retracted product — historical record | 6 |
| Modelled product | 12 |
| Interface support — excluded from scientific assets | 1 |
Hydrology sources added on 8 September
Four official-source searches added 79 station-page/query routes and 27 document links. Names distinguish river water levels, rainfall, forecasts, event reports, historical flood context and access guidance. Each asset records source identity, actual temporal coverage, access, rights and interpretation limits.
Missing intervals, early telemetry endings, unresolved station identities, a missing bulletin date, denied access and unreadable document text remain explicit. Current map labels are not historical flood observations; gauge stage is not discharge or inundation depth. All 106 new assets retain a reuse-scope follow-up.
Earlier repository assessment on 8 September
- 365 assets received descriptive names, with original filenames and identifiers retained. Names distinguish observations, modelled products, historical baselines, previews and documentation.
- 294 records received metadata and bounded structure inspection; 71 were assessed from source metadata without structural inspection of the file body. Fields include dates, versions, grids, layers, variables, units, rights and interpretation limits.
- 23 archive directories were inventoried. Complete-response hashes established 25 unique pairs of identical content; alternative copies remain linked without becoming independent evidence.
- Six retracted products and two packages containing retracted material are explicitly labelled. They no longer receive the default asset-opening action. The original source references remain in the assessment.
- Source conflicts, an empty observed-event GeoPackage, empty forecast collections, mixed-epoch elevations and uncalibrated radar encoding remain explicit follow-ups. A modelled 2 m inundation-depth threshold is distinguished from grid resolution.
- 113 assets in this phase retain at least one follow-up. Retaining a candidate means keeping it in the evidence inventory, with its limitations visible.
The earlier assessment's OPERA cloud flags, Charter authorization and malformed-route findings, NISAR acquisition pairs, GFM reference layers and survey-point distinctions remain in the current records with their original dates.
Unresolved constraints
| Finding | Affected asset records |
|---|---|
| Access Unresolved | 3 |
| Access Denied | 1 |
| Unavailable Or Invalid | 30 |
| Restricted Source Download | 339 |
| Invalid Source Uri | 33 |
| Noda Source Access | 26 |
| Sensor Conflict | 2 |
| Charter Reference Collision | 7 |
| Opaque Image Identity | 3 |
| Unexpected Html | 2 |
| Cloud Limited Damage Census | 2 |
| Interpolated Elevations | 2 |
| Package Contains Retracted Layers | 2 |
| Retracted Product | 6 |
| Figure Reuse Terms | 23 |
| Conflicting Scene Link | 1 |
| Conflicting Acquisition Date | 1 |
| Conflicting Version Fields | 2 |
| Empty Archive Member | 1 |
| Incomplete Bundled Licence Text | 1 |
| Mixed Epoch Dem | 1 |
| Inferred Radiometric Encoding | 1 |
| Asset Reuse Scope | 197 |
| Upstream Mobility Terms | 10 |
| Empty Forecast Collections | 1 |
| Generalization Not Established | 1 |
| Version Scope Mismatch | 1 |
| Geometry Provenance Limit | 4 |
| Incomplete Shapefile Components | 1 |
| Time Series Coverage Gap | 51 |
| Station Identity Conflict | 3 |
| Series Or Identity Gap | 4 |
| Document Text Not Established | 5 |
| Source Access Gap | 1 |
| Reported Volume Interval Ambiguity | 1 |
| Hydrology Reference And Qc | 2 |
| Historical Series Gaps | 2 |
| Instrument Label Unresolved | 1 |
| Duplicate Upstream Observations | 1 |
| Alert Timestamps Distinct | 3 |
| Alert Level Fields Differ | 3 |
| Alert Expiry Unstated | 1 |
| Road History And Geometry | 14 |
| Road Shared Source | 14 |
| Midnight Start Unconfirmed Precision | 2 |
| Source Time Zone Unstated | 7 |
| Partial Open Not Full Restoration | 2 |
| Closed With End Date | 2 |
| Estimated End Precedes Start | 2 |
| Actual End Not Stated | 2 |
An asset can have more than one finding, so these counts overlap. The follow-up export records the required action for each affected asset. Authentication, an unavailable response, missing content and an invalid URI are separate outcomes.
Rights follow-up distinguishes repository software licences, deposited data licences, compiled upstream data and individually credited figures. An accessible file does not by itself establish permission to redistribute it.
Method and evidence limits
The current inventory contains 270 assets under 27 reviewed resources and 6,061 asset links under 100 candidate resources. Asset counts include supporting material and access routes; they are not counts of independent resources. Candidate asset status in the source CSV follows its parent resource workflow. Asset-review files record metadata-assessment completion separately. Resource-level PRISMA eligibility decisions and manuscript inclusion remain unassigned.
The road-record phase recorded 25 anonymous source requests and two supplementary web-navigation queries. BIPAD returned 25 road identifiers; Department of Roads history queries returned 10. Each source retained seven matching records. The local holdings comparison covers 94 source-table rows, including aliases, literature and repeated citations; it is not a count of newly discovered datasets.
The BIPAD phase recorded 17 anonymous native requests and separately documented two supplementary web-navigation queries. Four station identities and 58 alert IDs were screened; 628 historical observation rows were charted separately from discovery records. The API’s placeholder total was excluded from all result counts.
The hydrology phase recorded 212 anonymous request attempts and used a 10 MiB response limit. The preceding repository assessment used 771 requests, with limits of 10 MiB per complete file, 2 MiB per range and 8 MiB per ZIP-directory inspection. These phases covered selected metadata, structured responses, package inventories and document text. Research code was not executed and scientific observations or raster pixels were not independently validated.
Values distinguish provider statements, current HTTP observations, derived metadata, representative evidence and unknown fields. A HEAD response establishes endpoint behavior, not valid file content. A licence identifier left unknown does not mean that no rights statement exists. Source acquisition resolution is not applied to preview pixels.
Nominal OPERA grids and interpretation limits follow the JPL DSWx product documentation. Composite windows and cloud-shadow cautions follow NASA LANCE flood documentation. Free-account access is documented by NASA/ASF and Copernicus Data Space; Charter access has separate authorization conditions.
Current combined assessment compiled (UTC): . Individual records retain their own assessment and access-check dates.
Download the current combined assessment
- One screening record per asset (CSV)
- Metadata values, field states, source URLs and locators (CSV)
- All unresolved constraints and follow-up actions (CSV)
- Complete review and metadata (JSON)
- Counts and review scope (JSON)