ELFIE Example Use Case Summaries
This page summarizes the use cases to be demonstrated in ELFIE with a user story and the data sources to be linked together in the use case.
Water consumer / water use decision maker is interested in potential ecological integrity impacts of further water use.
- River network
- Catchments (NFWHF)
- Low flow or temperature sensitive species distribution
- Monitoring locations (flow and temperature)
- Low flow forecasts (NWM)
- Ecological stream classification
- Streamflow statistics (percentiles, mean annuals, latest)
- Maybe a local source of ecological flow requirement information.
Water consumer is interested in water quality impacts of water allocation decisions. Relevant data:
- Monitoring sites
- Existing water allocations
- Diversions / discharges
- Water quality
- Blue line network
Farmers are interested in soil moisture state for irrigation application decisions.
- Soil moisture time series
- Allowed to pump / consent data.
- Water allocation
Citizen in a flood-impacted area needs an information product summarizing the risks of a given flood event.
- Blue line network
- Topography
- Flood extent (event)
- Flood plain map(s)
- Flood control assets
- Road infrastructure
- At risk assets (multi agency sources)
- Stream flow / forecast point(s)
State or Tribal water quality analyst is interested in what monitoring (PH, DO, Turbidity), real time surrogates, water quality samples, and ancillary environmental data.
- Real time water quantity/quality sites
- Water quality sample sites
- Real time model surrogates (if available)
- Mines
- Snowpack
- Flow forecast
Person looking for water quality and quantity monitoring in a watershed for characterization and analysis.
- Watershed Boundary
- Aggregate Hydrographic Network
- Stream Flow Monitoring sites from NWIS
- Water Quality Monitoring sites from the Water Quality Portal.
Cross border hydro-data user is interested in what data is available for their cross-border watershed.
- All the data associated with given catchments.
- How cross border catchments interact.
Uninitiated web user is interested in how water budgets differ across the continental US.
- Watershed boundaries
- Watershed outlet locations
- Average precip, ET, and runoff
- Links to more information
Local watershed stakeholder is interested in what the EPA has / has to say about the watershed.
- Impaired waters
- Drinking water violations
- Permitted facilities
- Infrastructure Investments
- Catchment characteristics
- Modeled data (nutrient concentrations)
Working with the state to install flood gages on major highways crossing major streams. These will measure stream depth, flow rate, velocity, and include HD camera for photographic images. They are less well suited to measure low flows. These will help provide ground truth for real-time validation/calibration of National Water Model forecasts.
HydroShare search users is interested in a search result that is associated with a watershed.
- Named watershed
- Set of hydroshare resources
Flood impact studying hydrologist is interested in collecting relevant information from various agencies.
- River Network (flowpaths)
- Catchments / Watersheds
- Hydro-locations
- Monitoring Locations (hydro)
- Meteo-monitoring
- DEM (maybe)
- Aquifer overlaps catchment
- Rainfall forecast
Water manager wants to explore data from a particular catchment, historical flows and seasonal streamflow forecast.
- Get catchments and contracted nodes (hydronexuses) from Geofabric
- Map river network for a catchment
- Find all monitoring locations upstream of point in a catchment
- Get historical flow and statistics for monitoring locations within a catchment
- Get seasonal streamflow forecasts for a catchment
Hydrologist needs to understand relevant information for a potential spill situation so they can make contingency plans and know what's available for future emergency response.
- Same list as above but add...
- Wells
- Bathymetry
Aquifer -> River -> Surface catchment
- datasets needed : the 3 above (+ maybe river segment/HY_Channel)
To manage groundwater abstraction authorizations and try to prevent drought situations, groundwater flow models are being fed by near real-time observation flows from identified/'contracted' monitoring facilities
- groundwater levels at piezometers
- surface water flow at river gage
- atmospheric information at meteo stations The output is an observation (prediction) Datasets needed :
- the 3 sets of monitoring facilities,
- associated observation,
- groundwater flow models
- the generated prediction
This use case allows to traverse the following datasets : borehole -> piezometer -> aquifer -> river -> river gage + associated observation
- dataset needed : the 5 features above (+ ground/surface water observation)
-
- the river network in order to do 'river -> river gage'
- geofabric river regions
- water data online station