fflood-nep — SAR workflow and source-planning code

Original titleDBishal13/fflood-nep

The pinned repository tree and methods identify a SAR processing workflow and source/status records. README explicitly says the proposed flood-extent file was not yet produced. Retain code and documented source copies, with duplicate source manifestations distinguished from new evidence.

Status
Included
Provider
DBishal13
Resource type
Event Data Or Code
Evidence class
Analysis Code And Source Compilation

Completed catalogue assessment

Eligibility decision
Include · Include
Assessment date
28 September 2026
Decision reason
The pinned repository tree and methods identify a SAR processing workflow and source/status records. README explicitly says the proposed flood-extent file was not yet produced. Retain code and documented source copies, with duplicate source manifestations distinguished from new evidence.
Metadata corrections
[]

View the complete assessment and exclusion ledger.

Identity and coverage

Catalogue identifier
rec_012f5907-4826-5c9e-bd68-0dec7b5d9197
Original-title language
English
English-title status
Not applicable
Persistent identifier
Not stated
Resource version
Not stated
Publication date
Not stated
Last updated
Not stated
Metadata reviewed
28 September 2026
Language
English
Geographic coverage
Source area and/or Bhote Koshi–Trishuli corridor; provider-specific coverage, not a shared surveyed boundary.
Bounding box (WGS 84)
Not stated
Temporal coverage
Not stated; Event-Related Observations, Analyses And Source-Specific Historical References; Dates Vary By Component.
Themes
Not stated

Method and provenance

Production method
Not stated
Provenance
The pinned repository tree and methods identify a SAR processing workflow and source/status records. README explicitly says the proposed flood-extent file was not yet produced. Retain code and documented source copies, with duplicate source manifestations distinguished from new evidence.
Validation
Not Performed By Catalogue Review
Uncertainty
Catalogue eligibility does not establish scientific validation.
Limitations
Public code and documented files; not a completed SAR flood product. Repository-specific software terms must be checked; compiled Copernicus/other data keep upstream terms.

Access and reuse

Access
Source Specific Conditions; open access route
Licence
Not verified
Redistribution
Metadata and links only; third-party files are not redistributed
Catalogue status
Included

Assets

7 assets

Authoritative metadata sources

Spatial extent

Loading map…

Recorded bounding box