Satellite Time Series Aggregation: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Line 40: Line 40:
I have looked at two files' DDS and DAS responses. Each file has 130 variables, although three are 'FakeDim' arrays. These FakeDim arrays are pseudo Maps for browse images (Byte arrays named BROWSE_Image_00 or ..._01 and are not used by any of the other variables. All of the other variables are similar to the Swath data except that the independent variables are one-dimensional arrays that index time only with a frequency of 0.25, 1 or 40 Hz. The main independent variables (which every dependent has one of) are:
I have looked at two files' DDS and DAS responses. Each file has 130 variables, although three are 'FakeDim' arrays. These FakeDim arrays are pseudo Maps for browse images (Byte arrays named BROWSE_Image_00 or ..._01 and are not used by any of the other variables. All of the other variables are similar to the Swath data except that the independent variables are one-dimensional arrays that index time only with a frequency of 0.25, 1 or 40 Hz. The main independent variables (which every dependent has one of) are:
<pre>
<pre>
    Float64 Data_1HZ_DS_UTCTime_1[Data_1HZ_DS_UTCTime_1 = 81216];
Float64 Data_1HZ_DS_UTCTime_1[Data_1HZ_DS_UTCTime_1 = 81216];
    Float64 Data_1HZ_Time_d_UTCTime_1[Data_1HZ_Time_d_UTCTime_1 = 81216];
Float64 Data_1HZ_Time_d_UTCTime_1[Data_1HZ_Time_d_UTCTime_1 = 81216];
   
   
    Float64 Data_40HZ_DS_UTCTime_40[Data_40HZ_DS_UTCTime_40 = 3248640];
Float64 Data_40HZ_DS_UTCTime_40[Data_40HZ_DS_UTCTime_40 = 3248640];
    Float64 Data_40HZ_Time_d_UTCTime_40[Data_40HZ_Time_d_UTCTime_40 = 3248640];
Float64 Data_40HZ_Time_d_UTCTime_40[Data_40HZ_Time_d_UTCTime_40 = 3248640];


    Float64 Data_4s_DS_UTCTime_4s[Data_4s_DS_UTCTime_4s = 20304];
Float64 Data_4s_DS_UTCTime_4s[Data_4s_DS_UTCTime_4s = 20304];
    Float64 Data_4s_Time_d_UTCTime_4s[Data_4s_Time_d_UTCTime_4s = 20304];
Float64 Data_4s_Time_d_UTCTime_4s[Data_4s_Time_d_UTCTime_4s = 20304];
</pre>
</pre>
Note that looking at the values of ''Data_1HZ_DS_UTCTime_1'' and ''Data_1HZ_Time_d_UTCTime_1'' there's no difference. I don't know why these appear doubled in the files, but it may be an artifact of the handler transforming the data 'into CF'.
Note that looking at the values of ''Data_1HZ_DS_UTCTime_1'' and ''Data_1HZ_Time_d_UTCTime_1'' there's no difference. I don't know why these appear doubled in the files, but it may be an artifact of the handler transforming the data 'into CF'.

Revision as of 19:51, 28 January 2015

<-- Back

Point Of Contact: James

Description

Satellite_Time_Series_1

Goal

The goal of this use case is, like many of its other parts, the same as the Satellite Swath Data use case. The primary difference is that this use case covers Time Series data.

Summary

Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.

Actors

List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.

Preconditions

Here we state any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case. Any assumptions about other systems can also be stated here, for example, weather conditions. List all preconditions.

Triggers

Here we describe in detail the event or events that brings about the execution of this use case. Triggers can be external, temporal, or internal. They can be single events or when a set of conditions are met, List all triggers and relationships.

Basic Flow

Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)

Alternate Flow

Here we give any alternate flows that might occur. May include flows that involve error conditions. Or flows that fall outside of the basic flow.

Post Conditions

Here we give any conditions that will be true of the state of the system after the use case has been completed.

Activity Diagram

Here a diagram is given to show the flow of events that surrounds the use case.

Notes

There is always some piece of information that is required that has no other place to go. This is the place for that information.

Where to find sample data for this use case:

I have looked at two files' DDS and DAS responses. Each file has 130 variables, although three are 'FakeDim' arrays. These FakeDim arrays are pseudo Maps for browse images (Byte arrays named BROWSE_Image_00 or ..._01 and are not used by any of the other variables. All of the other variables are similar to the Swath data except that the independent variables are one-dimensional arrays that index time only with a frequency of 0.25, 1 or 40 Hz. The main independent variables (which every dependent has one of) are:

Float64 Data_1HZ_DS_UTCTime_1[Data_1HZ_DS_UTCTime_1 = 81216];
Float64 Data_1HZ_Time_d_UTCTime_1[Data_1HZ_Time_d_UTCTime_1 = 81216];
 
Float64 Data_40HZ_DS_UTCTime_40[Data_40HZ_DS_UTCTime_40 = 3248640];
Float64 Data_40HZ_Time_d_UTCTime_40[Data_40HZ_Time_d_UTCTime_40 = 3248640];

Float64 Data_4s_DS_UTCTime_4s[Data_4s_DS_UTCTime_4s = 20304];
Float64 Data_4s_Time_d_UTCTime_4s[Data_4s_Time_d_UTCTime_4s = 20304];

Note that looking at the values of Data_1HZ_DS_UTCTime_1 and Data_1HZ_Time_d_UTCTime_1 there's no difference. I don't know why these appear doubled in the files, but it may be an artifact of the handler transforming the data 'into CF'.

Resources

In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include data and services, and the systems that offer them. This section will call out examples of these resources.


Resource Owner Description Availability Source System
name Organization that owns/ manages resource Short description of the resource How often the resource is available Name of system which provides resource