You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example, the `temperature` data variable is an aggregation variable.
70
70
Its four-dimensional aggregated data with shape `(12, 1, 73, 144)` is constructed from two non-overlapping fragments, with data shapes `(3, 1, 73, 144)` and `(9, 1, 73, 144)`, which span the first 3 and last 9 elements respectively of the `time` aggregated dimension.
71
-
The fragment dataset locations are relative-path URI references, and so are assumed to be in the same directory as the aggregation file.
71
+
The fragment dataset names are relative-path URI references, and so are assumed to be in the same directory as the aggregation file.
72
72
73
73
The data for the `level`, `latitude` and `longitude` variables are omitted for clarity.
74
74
====
75
75
76
76
[[example-L.2]]
77
77
[caption="Example L.2 "]
78
-
.Aggregation variable with absolute URI fragment file locations
78
+
.Aggregation variable with fragment datasets defined by absolute URIs
79
79
====
80
80
----
81
81
dimensions:
@@ -100,16 +100,16 @@ variables:
100
100
temperature:units = "K" ;
101
101
temperature:cell_methods = "time: mean" ;
102
102
temperature:aggregated_dimensions = "time level latitude longitude" ;
This example is similar to <<example-L.1, Example L.1>>, but now the fragment dataset locations are absolute URIs (one local, one remote), and `time` is now also an aggregation coordinate variable, with its aggregated data being derived from the same fragment datasets as `temperature`.
150
+
This example is similar to <<example-L.1, Example L.1>>, but now the fragment dataset names are absolute URIs (one local, one remote), and `time` is now also an aggregation coordinate variable, with its aggregated data being derived from the same fragment datasets as `temperature`.
151
151
152
152
The data for the `level`, `latitude` and `longitude` variables are omitted for clarity.
153
153
====
@@ -178,8 +178,8 @@ variables:
178
178
temperature:units = "K" ;
179
179
temperature:cell_methods = "time: mean" ;
180
180
temperature:aggregated_dimensions = "time level latitude longitude" ;
In this example, three fragments are aggregated into a collection of discrete sampling geometry (DSG) timeseries feature types with contiguous ragged array representation.
308
308
The auxiliary coordinate variables `time`, `lon`, and `lat` are also aggregation variables.
@@ -314,7 +314,7 @@ No data have been omitted from the CDL.
314
314
315
315
[[example-L.5]]
316
316
[caption="Example L.5 "]
317
-
.Aggregation variable with unique fragment values
317
+
.Aggregation ancillary variable with unique fragment values
318
318
====
319
319
----
320
320
dimensions:
@@ -340,16 +340,16 @@ variables:
340
340
temperature:cell_methods = "time: mean" ;
341
341
temperature:ancillary_variables = "uid" ;
342
342
temperature:aggregated_dimensions = "time level latitude longitude" ;
This example is similar to <<example-L.1, Example L.1>>, but now there is an additional aggregation ancillary variable `uid` which defines its fragments from the unique values stored in the `fragment_unique_value` variable, that are intended to be broadcast across the `time` aggregated dimension.
389
+
This example is similar to <<example-L.1, Example L.1>>, but now there is an additional aggregation ancillary variable `uid` which defines its fragments from the unique values stored in the `fragment_unique_values` variable.
390
390
391
391
The data for the `level`, `latitude` and `longitude` variables are omitted for clarity.
0 commit comments