Skip to end of metadata
Go to start of metadata

Overview of "Visualize Data Product" Use Case

Provide dynamic visualization of Unprocessed (Raw) and Basic (L0) data products.

Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option

Related Jira Issues:   Open   •   All


Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors Integrated Observatory Operator, Data Process Operator
References Metadata Specification for Environmental Images
Uses UC.R2.17 Define Visualization Processing Pipeline
UC.R2.21 Transform Data in Workflow
Is Used By UC.R2.19 Produce Matlab Visualization
Is Extended By  
In Acceptance Scenarios AS.R2.01A Operate Marine Observatory, AS.R2.02C Instrument Life Cycle Support, AS.R2.03A Modelers Integrate External Model with OOI, AS.R2.04A Data Product Leads Drive Core Data Product Creation, AS.R2.03A Modelers Integrate External Model with OOI
Technical Notes UC.R2.17 Define Visualization Processing Pipeline does not have to be the chosen 'appropriate visualization' technique, it is simply informational.
Lead Team AS
Primary Service Data Analysis & Visualization Services Part 1
Version 2.3
UC Priority 4
UC Status Mapped + Ready
UX Exposure EUC


This information summarizes the Use Case functionality.

Using data streams for an Unprocessed Data Product and corresponding Basic Data Product, and an appropriate visualization processing pipeline for the data type, generate automatically a visualization (2D image, video, 3D image, etc) that is updated for the user as new values arrive.


  • The input data product (that is used as the source of the visualization) is produced automatically.
  • The visualization can be produced automatically.
  • An OOI User viewing a data resource will be apprised of, and able to view, the corresponding visualization as well.
  • The techniques can be used to produce visualizations of any data resource that has an appropriate, described structure.

Initial State

A data product exists to apply the visualization to, and an appropriate visualization processing pipeline exists for a data component in that data set.

Scenario for "Visualize Data Product" Use Case

  1. The Data Process Operator selects the visualization method
    1. The system provides a list of pre-defined visualization methods
    2. The chosen method is one piece of metadata assigned to the output visualization
  2. The Data Process Operator selects the data product(s) to be used to generate the visualization
    1. The system provides a list of applicable data products for input (and may help the user navigate to the final selection)
    2. One or multiple inputs may be selected depending on visualization method
  3. The Data Process Operator provides additional visualization parameters as needed
    1. Such as output format, output size, area of interest, specific variable to visualize, color scheme
    2. This selection may be very specific depending on visualization method
    3. The setting are included as part of the visualization product metadata, which can be attached using XMP to most image formats (see Metadata Specification for Environmental Images)
  4. (Variant 1) The Data Process Operator generates the visualization immediately (End of Use Case)
    1. This is a one time execution and the Data Process Operator can see the visualization
    2. The Data Process Operator can repeat steps above to change parameters and input products
    3. Use case ends here for this variant
  5. <3> (Variant 2) The Data Process Operator defines execution scheduling
    1. Such as immediately on arrival of new input data packet, or triggered by schedule
    2. Define notifications deviating from default scheme
  6. <3> The Data Process Operator defines the visualization output as a data product
    1. Includes whether it is private or public
    2. Provide additional metadata that can not be automatically derived
  7. <3> The Data Process Operator schedules the data product visualization
    1. The system schedules the visualization execution
    2. The system notifies any subscribed users based on the defined notification scheme
    3. Appropriate metadata are generated and associated with the finished visualization
  8. <3> The Data Process Operator deactivates and removes the data product visualization method
    1. When a data product visualization method is no longer of value, it may be removed by the originator.
    2. A copy is saved for future reference, as people with visualization products produced by that method may want to refer to it.

Final State

Appropriate visualizations get produced for the data of the visualizable data type.


These comments provide additional context (usually quite technical) for editors of the use case.

Observatory Operators are not empowered to create visualizations on the fly in Release 2, as this scenario is currently written.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B


r2-usecase r2-usecase Delete
usecase usecase Delete
productdescription productdescription Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.