Satellite Time Series Aggregation - Revision history

Jimg: /* Notes */

2015-01-28T20:11:26Z

Notes

@@ Line 139: / Line 139: @@
      Int16 Data_4s_Time_pl_timing_flg[Data_4s_Time_d_UTCTime_4s = 20302];
      Int16 Data_4s_Time_shot_time_flg[Data_4s_Time_d_UTCTime_4s = 20302];
 </pre>

Jimg: /* Notes */

2015-01-28T20:10:13Z

Notes

@@ Line 50: / Line 50: @@
 </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'.
 == Resources ==

Jimg: /* Notes */

2015-01-28T19:51:12Z

Notes

← Older revision		Revision as of 19:51, 28 January 2015
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'.

Jimg: /* Notes */

2015-01-28T19:50:45Z

Notes

@@ Line 37: / Line 37: @@
 Where to find sample data for this use case:
 * http://nsidc.org/opendap/GLAS/GLAH11.033/2003.02.21/contents.html
 == Resources ==

Jimg: /* Goal */

2015-01-28T18:22:52Z

Goal

← Older revision		Revision as of 18:22, 28 January 2015
Line 7:		Line 7:

	== Goal ==		== Goal ==
	~~<font size="-2" color="green">''~~The goal ~~briefly describes what~~ the ~~user intends to achieve with~~ this use case.~~''</font>~~		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 ==		== Summary ==

Jimg: /* Goal */

2015-01-28T17:17:30Z

Goal

← Older revision		Revision as of 17:17, 28 January 2015
Line 8:		Line 8:
	== Goal ==		== Goal ==
	<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>		<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>



	== Summary ==		== Summary ==

Jimg at 17:16, 28 January 2015

2015-01-28T17:16:29Z

← Older revision		Revision as of 17:16, 28 January 2015
Line 1:		Line 1:
	[[Use_cases_for_swath_and_time_series_aggregation \| <-- Back]]		[[Use_cases_for_swath_and_time_series_aggregation \| <-- Back]]

	'''Point Of Contact:''' ''~~A Human~~''		'''Point Of Contact:''' ''James''

	== Description ==		== Description ==
	~~<font size="-2" color="green">''Give a short descriptive name for the use case to serve as a unique identifier.''</font>~~		Satellite_Time_Series_1

	== Goal ==		== Goal ==
	<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>		<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>



	== Summary ==		== Summary ==
Line 34:		Line 36:
	== Notes ==		== Notes ==
	<font size="-2" color="green">''There is always some piece of information that is required that has no other place to go. This is the place for that information.''</font>		<font size="-2" color="green">''There is always some piece of information that is required that has no other place to go. This is the place for that information.''</font>

			Where to find sample data for this use case:
			* http://nsidc.org/opendap/GLAS/GLAH11.033/2003.02.21/contents.html

	== Resources ==		== Resources ==

Jimg: Created page with " <-- Back {{subst:Template:Use_Case}}"

2015-01-28T16:48:40Z

Created page with " <-- Back {{subst:Template:Use_Case}}"

New page

[[Use_cases_for_swath_and_time_series_aggregation | <-- Back]]

'''Point Of Contact:''' ''A Human''

== Description ==
''Give a short descriptive name for the use case to serve as a unique identifier.''

== Goal ==
''The goal briefly describes what the user intends to achieve with this use case.''

== 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.''

== 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.''

{| cellspacing="0" border="1"
|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''
|}