Datastream Roadmap #250
jameshalgren
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
|
Here's a diagram of what the datastream looks like with other data sources. There are implied interfaces in a number of areas in this diagram. Maybe someone with cooler skills can help create that. graph TD
%% Main Data Sources at the Top
subgraph "Main Data Sources & Models"
direction LR
USGS["USGS Streamflow Observations"]
NWM_V3["National Water Model (NWM) v3.0"]
COMM_DS["Community Model (NGIAB) Datastream"]
end
%% Details for NWM
NWM_V3 --- NWM_API[AWS & Google<br/>BigQuery API]
NWM_V3 --- NWM_Horizons[Horizons:<br/>SR, MR, LR]
%% Details for Community Model
COMM_DS --- COMM_Geo[Geography:<br/>- Local<br/>- VPU/HUC<br/>- Whole Domain<br/>- OCONUS]
COMM_DS --- COMM_Horizons[Horizons:<br/>SR, MR, LR]
%% Funneling into the Hydrologist
USGS --> Hydrologist
NWM_API --> Hydrologist
NWM_Horizons --> Hydrologist
COMM_Geo --> Hydrologist
COMM_Horizons --> Hydrologist
Hydrologist((Hydrologist<br/><i>Asks questions the<br/>data can answer</i>))
%% Applications at the Bottom
subgraph "Targeted User Applications"
direction LR
App1[First Responders]
App2[Reservoir Operators]
App3[Emergency Managers]
App4[Road Safety Specialists]
App5[Recreation Users]
end
Hydrologist --> App1
Hydrologist --> App2
Hydrologist --> App3
Hydrologist --> App4
Hydrologist --> App5
%% Feedback Loop
subgraph "Model Improvement Feedback Loop"
direction TB
Hydrologist_Feedback(Hydrologist<br/><i>Makes model improvements</i>)
Approval[Approval Chain]
PullRequest["Submits Pull Request"]
Hydrologist_Feedback --> Approval
Approval --> PullRequest
PullRequest --> COMM_DS
end
%% Styling
style Hydrologist fill:#f9f,stroke:#333,stroke-width:2px,color:#000;
style Hydrologist_Feedback fill:#f9f,stroke:#333,stroke-width:2px,color:#000;
linkStyle 0 stroke-width:2px,stroke:#1e90ff,fill:none;
linkStyle 1 stroke-width:2px,stroke:#1e90ff,fill:none;
linkStyle 2 stroke-width:2px,stroke:#1e90ff,fill:none;
linkStyle 3 stroke-width:2px,stroke:#1e90ff,fill:none;
linkStyle 4 stroke-width:2px,stroke:#1e90ff,fill:none;
linkStyle 5 stroke-width:2px,stroke:#008000,fill:none;
linkStyle 6 stroke-width:2px,stroke:#008000,fill:none;
linkStyle 7 stroke-width:2px,stroke:#008000,fill:none;
linkStyle 8 stroke-width:2px,stroke:#008000,fill:none;
linkStyle 9 stroke-width:2px,stroke:#008000,fill:none;
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Dropping links relevant here Community contributions approval workflow #209 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The datastream is both a software product and the actual stream of data produced by the application of that product to simulate historic or potential future hydrologic states of the CONUS and OCONUS stream networks in our domain of interest.
Simply put the CIROH community datastream is a demonstration of what operational hydrologic forecasting could be. We hope this demonstration makes it easier for life-saving advances to be implemented in ways that they can... save lives!
This issue
might be better asis now a discussion... the goal is to dynamically document where the datastream should go so that it can fulfill it's purpose.Beta Was this translation helpful? Give feedback.
All reactions